A website redesign can improve navigation, accessibility, performance, and conversion paths. It can also disrupt organic visibility if important URLs disappear, redirects are incomplete, internal links point to old paths, or a staging directive reaches production. The safest redesign treats search migration as part of product delivery from the first planning meeting.
This checklist is for teams changing a website’s design, platform, domain, URL structure, or content model. It focuses on preserving useful access and making the new site understandable to visitors and search engines. It cannot guarantee that rankings will remain unchanged; search systems may reassess pages after a move.
Google’s documentation explains how to move a site with URL changes and recommends mapping old URLs to relevant new URLs with permanent redirects where appropriate. Use the current documentation for the project’s exact setup.
Phase 1: Set the migration scope
First record what is changing: visual design, CMS, domain, URL patterns, navigation, content, or all of these. Identify the teams responsible for development, content, analytics, and DNS. Agree who can approve URL changes and who will monitor the launch.
Choose a realistic launch window with enough time for checks and rollback decisions. Make sure access is available to the current CMS, hosting, analytics, Search Console, DNS, and any edge or redirect configuration. Keep a written record of the existing setup before changing it.
Phase 2: Build a complete URL inventory
Export URLs from multiple sources because no single source is complete:
- crawl the current live site
- export URLs from the XML sitemap
- review analytics landing pages and Search Console performance pages
- check backlinks and important referral URLs
- ask content and product teams for campaign, support, and documentation URLs
Record the current status code, canonical, indexability, title, traffic, conversions, backlinks where known, and the proposed action. Mark whether each page should remain, move, merge, be removed, or be excluded from indexing. Pay attention to old but still-linked resources and campaign URLs.
Do not preserve every URL automatically. The goal is to keep pages that serve a distinct purpose and route obsolete paths to the closest useful destination. If no relevant replacement exists, decide deliberately whether the old URL should return a not-found status rather than redirecting everything to the home page.
Phase 3: Create and review the redirect map
Create a one-to-one mapping for URLs that have a relevant replacement. Use permanent server-side redirects for permanent moves and avoid redirect chains. A path that previously redirected from A to B should ideally lead directly to its final destination after the redesign.
Review the map for:
- missing high-value URLs
- loops and chains
- incorrect case, slash, parameter, or language behavior
- unrelated pages being sent to the same destination
- URLs that should remain unchanged but were accidentally rewritten
- old paths with external links or active traffic
Run automated checks against a sample and then the complete map. Confirm response codes and final destinations, including important query-string behavior. Keep the map in a versioned file or deployment configuration so the team can audit it later.
Phase 4: Check the staging site
Before launch, crawl the staging environment and compare its structure with the approved inventory. Test templates, not only the home page. Confirm that important pages have the intended titles, headings, canonicals, internal links, structured data, and indexability. Review forms, navigation, mobile layouts, and page speed on representative templates.
Staging should not be indexed as a duplicate public site. Use access controls or an appropriate noindex approach, and confirm that the restriction will not be carried into production. A robots.txt block alone can prevent crawling without reliably removing a URL already known to Google, so use the right control for the environment.
Check that the new XML sitemap contains only preferred, canonical URLs that should be indexed. Remove staging paths, redirected URLs, and noindex pages. Validate analytics and consent behavior in staging without polluting production reporting.
Phase 5: Launch with a focused checklist
At deployment, verify the site from outside the development environment:
- Confirm the domain resolves over HTTPS and important URLs return the expected status.
- Test redirects from a sample of old URLs and every high-value mapped URL.
- Check that production pages are indexable and staging protections are absent.
- Review canonical tags, robots directives, hreflang where used, and sitemap location.
- Test internal links, navigation, forms, and conversion events.
- Review mobile rendering and the most important page templates.
- Inspect server logs and error reporting for elevated 404s or 5xx responses.
Submit or update the sitemap in Search Console when appropriate. Sitemap submission helps Google discover preferred URLs but does not force immediate crawling or preserve rankings. Use URL Inspection for a small set of important pages when diagnosing a specific issue, not as a substitute for a complete migration check.
Phase 6: Monitor the first weeks
Track the migration by URL group. Compare indexed pages, clicks, impressions, landing pages, errors, and conversions with the baseline. Watch for old URLs that are still receiving traffic, new URLs that are not being discovered, unexpected noindex pages, and redirect destinations that do not match user intent.
Review Search Console Page indexing and performance reports alongside analytics and server logs. A fall in measured analytics traffic may come from broken tagging or consent behavior; check whether Search Console impressions and clicks changed too. A rise in 404s may be normal for old URLs that were never in the redirect map, or it may expose an important omission. Investigate examples before acting on totals alone.
Keep a clear issue log with URL, symptom, evidence, owner, fix, and validation. Correct mistakes quickly, but avoid repeated structural changes based on noisy daily movement. Google may need time to recrawl and process redirects after a site move.
Common migration mistakes
- Launching without a URL inventory or a redirect map.
- Redirecting every missing path to the home page.
- Removing content before checking its traffic, links, and customer purpose.
- Forgetting canonical, noindex, sitemap, or internal-link checks on production.
- Leaving a staging restriction or temporary domain reference in place.
- Changing design, URL structure, copy, navigation, and analytics simultaneously without a change log.
- Treating a sitemap submission as an instant indexing guarantee.
Frequently asked questions
Will a redesign automatically cause rankings to drop?
No. A redesign does not guarantee a decline or unchanged performance. Risk depends on what changes and how carefully the team preserves useful URLs, content, links, and technical signals.
Should every old page redirect to the new homepage?
No. Redirect a moved page to its closest relevant replacement. If there is no suitable destination, a clear not-found response is usually more accurate than an unrelated redirect.
How long should I keep redirects?
Follow Google’s current site-move guidance and keep permanent redirects in place for as long as possible, especially for URLs with users or external links. Also update internal links and references you control so they point directly to the new URL.
What should I check first if traffic falls after launch?
Check whether the change is in Search Console or only analytics, then inspect indexability, canonical tags, redirect destinations, server errors, and affected page groups. Compare against the documented launch timeline.
If your project includes a new platform or application, explore our custom web development approach. The same checklist is part of every redesign we scope, including web development projects in London, Leeds and Edinburgh.





