redesign can improve search performance, but changing design, content, URLs and infrastructure at the same time also changes many of the signals search engines already understand. The goal is not to freeze the old site. It is to preserve what has earned visibility, deliberately retire what has not, and give users and crawlers an unambiguous path from every important old URL to its new home.
Export the current URLs, search queries, landing-page traffic, conversions, backlinks, titles, headings, canonicals and index status. Mark pages that generate enquiries or have strong external links even if they look visually dated. This evidence prevents a redesign from deleting value simply because it was not visible in the design file.
- Keep a URL unchanged when its purpose and content remain substantially the same.
- Map a changed URL to the most relevant new equivalent, not automatically to the homepage.
- Merge overlapping pages only when the new page genuinely serves the same intent.
- Return a real 404 or 410 for material that has no replacement.
- Record title, H1, canonical and primary internal links for each important destination.
Google recommends mapping old URLs to their new format and using permanent server-side redirects when the move begins. Avoid chains in which an old URL redirects through another old URL before reaching the final page. Keep the old domain and redirect rules running long enough for users, crawlers and links in old documents to continue working.
Staging should be protected from indexing, but the production release must not inherit a site-wide noindex or blocked robots file. Update canonicals, internal links, hreflang where used, structured data and the XML sitemap to the final production URLs. Preserve Search Console verification and analytics so pre- and post-launch performance can be compared.
Google says significant moves can cause temporary ranking fluctuation while pages are recrawled and reindexed. Monitor server errors, redirect hits, submitted versus indexed URLs, selected canonicals, crawl activity, query impressions and conversions. Fix patterns rather than chasing daily position noise. If the redesign also changes domain, CMS and content, separating those changes where possible makes problems easier to diagnose.
A visual redesign does not require a new path structure. Keeping successful URLs stable reduces variables. When information architecture must change, create a page-by-page redirect map from crawl, Search Console and backlink evidence before templates are replaced.
If the redesign also moves WordPress to Next.js, treat it as a full site migration. Preserve content meaning, ensure priority copy is in rendered HTML, compare old and new crawls, validate production canonicals and retain redirects long term.
- Benchmark traffic, conversions, rankings and Core Web Vitals by page group.
- Freeze an approved URL and content inventory before implementation.
- Test status, indexability, canonical, metadata, headings, links and structured data for every template.
- Keep analytics annotations and a rollback path for critical launch failures.
- Monitor page groups after launch instead of relying on total traffic alone.