Introduction
A website migration is one of the easiest times to damage existing search visibility.
Designers and developers often focus on the new interface while old URLs, redirects, canonicals and internal links are treated as cleanup work.
Google's current site-move documentation recommends planning URL mappings, using server-side permanent redirects where possible and updating sitemaps after the move.
The safest migration is the one planned before the new site launches.
1. Crawl and Record the Existing Website
Before changing anything, create an inventory of existing URLs.
Record important status codes, titles, canonicals, internal links and organic landing pages.
Use Search Console and analytics to identify pages receiving impressions, clicks, backlinks or conversions.
Do not rely only on the navigation menu because valuable URLs may exist deeper in the site.
2. Decide Which URLs Will Stay the Same
If a useful URL does not need to change, keeping it stable can reduce migration complexity.
A redesign does not require every slug to be rewritten.
Changing URLs only to make them look cleaner can create redirect work and temporary search disruption without meaningful benefit.
Change URLs when there is a clear structural reason.
3. Build a One-to-One Redirect Map
For every important old URL that changes, choose the most relevant new destination.
Do not redirect every old page to the homepage.
Google recommends server-side permanent redirects such as 301 or 308 where technically possible.
Map directly to final destinations to avoid unnecessary redirect chains.
4. Preserve Valuable Content
A redesign should improve presentation without accidentally deleting the information that made important pages useful.
Compare old and new service pages, guides, product content and FAQs.
If a high-performing page is being consolidated, move its useful information into the new destination rather than preserving only the URL.
Migration planning should consider content as well as redirects.
5. Check Canonical Tags
After launch, canonical tags should normally point to the new preferred URLs.
Old-domain canonicals or staging URLs can send contradictory signals.
Keep canonicals aligned with redirects, sitemaps and internal links.
Check representative templates instead of assuming one successful page proves the whole site is correct.
6. Remove Temporary Staging Blocks
Staging sites are often protected with noindex or robots restrictions.
Google's migration guidance specifically warns site owners to remove noindex and robots.txt blocks that were only needed during development.
Check both the new production site's HTML and HTTP headers.
A perfect redirect map will not help if the destination pages remain noindexed.
7. Update Internal Links
Internal links should point directly to the new final URLs.
Do not rely on redirects permanently for menus, breadcrumbs and content links.
Updating internal links reduces unnecessary hops and reinforces the new site structure.
Also update canonical links, hreflang references and structured-data URLs when relevant.
8. Update the XML Sitemap
Generate a sitemap containing the new canonical URLs.
Remove old redirected URLs from the active sitemap.
Submit the updated sitemap in Search Console.
Google's current migration documentation specifically lists forgotten sitemap updates as a common migration mistake.
9. Test Redirects and Error Pages
Crawl the old URL list after launch and verify the response for each important page.
Check for redirect loops, chains, accidental 404s and redirects to irrelevant destinations.
Google says it can follow redirect chains, but recommends keeping them low and redirecting directly to the final destination where possible.
Also check that genuinely removed content returns an appropriate response.
10. Monitor Search Console After Launch
Expect some fluctuation while search engines process the changes.
Monitor indexing, not-found errors, sitemap status and important queries.
Inspect representative old and new URLs when something looks wrong.
Large problems discovered in the first few days are much easier to fix than problems noticed months later.
11. Keep Redirects Long Enough
Do not remove redirects immediately after search traffic appears stable.
Old URLs may continue receiving links, bookmarks and crawler requests for a long time.
Permanent redirects should be treated as part of the site's long-term compatibility strategy where practical.
Frequently Asked Questions
Can a redesign hurt SEO? — Yes, especially when URLs, content, redirects and indexing directives are changed carelessly.
Should I change all URLs during a redesign? — No. Keep useful existing URLs when there is no strong reason to change them.
Should old URLs redirect to the homepage? — Usually not. Redirect each old page to the closest relevant new destination.
How should permanent moves be redirected? — Google currently recommends server-side permanent redirects such as 301 or 308 when possible.