Protect search visibility by treating the redesign as a change to an existing customer path, not a blank canvas. Understand which pages matter, preserve useful content and addresses where practical, and test the new site before and after launch. These steps reduce avoidable disruption; they cannot guarantee unchanged rankings.
Record what customers can find today
Before changing the site, keep a list of important pages and the questions or services each page covers. Add search visits, relevant inquiries, and any known links from other sites. This combines search data with business context: a quiet service page can matter more than a busy article attracting the wrong audience.
Save a dated baseline from Search Console and your website reporting, including the date range and filters used. Note seasonal patterns and current advertising. Without that context, a later change may be blamed on the redesign even when the cause is different demand, altered tracking, or a change in the kinds of visits arriving.
Give each important page a clear destination
Mark each page as staying, improving, combining with another page, or being removed. Preserve useful addresses when there is no reason to change them. When an address must change, map the old page to the new page that answers the same need, rather than sending every old link to the homepage.
Google's site-move guidance calls for URL mapping, appropriate permanent redirects, and updated canonical and sitemap references. Ask for those checks in the redesign plan. The business decision is simpler than the implementation: a person following an old link should arrive somewhere that still makes sense.
Improve the presentation without erasing the answer
A shorter page is not necessarily a clearer page. Keep the details a buyer needs to understand your service, location, fit, and next step. Remove repetition and outdated claims, but do not replace every specific explanation with a broad slogan simply to make the new layout look cleaner.
Review text alongside headings, links, and images. Important explanations should remain readable text rather than becoming part of a graphic. Use real examples where you have permission and evidence. If a page previously answered a useful question, make sure the redesigned version still gives that answer somewhere easy to find.
Test the new site as a visitor and as a search engine
Check a sample of important journeys on phone and desktop, including an old external link, a service search landing page, and a contact request. A successful visual review does not prove that redirects, forms, or page metadata work. Keep separate checks for appearance, navigation, discovery, and inquiry delivery.
A staging site may intentionally block indexing while it is under review. Verify that any temporary restriction is removed from the public release, without exposing private staging content. Ask for a launch checklist showing which pages were checked and who owns anything still unresolved.
- Important old links reach relevant working pages.
- Public pages have the intended titles, canonical addresses, and indexability.
- Navigation, internal links, and the sitemap use current destinations.
- Forms and booking links still reach the correct tools.
Watch specific pages, not just one traffic total
After launch, compare the pages and searches that mattered in your baseline. Investigate missing pages, broken links, and unexpected indexing changes before rewriting more content. Review customer inquiries alongside search data so a reporting change is not mistaken for a business loss.
Some movement does not prove that the project failed, and a stable total does not prove every service survived intact. Keep the old-to-new page map available and review unusual changes with the team that made them. A redesign is complete when the new experience works and the important old paths have been accounted for.