How to Redesign Your Website Without Losing Your Google Rankings: The SEO Migration Checklist
Redesigns routinely wipe out years of SEO in a single launch. This is the checklist we run before, during and after every rebuild so traffic goes up after launch, not down.
The most expensive mistake in web design
A company spends $20,000 on a beautiful new website, launches on a Friday, and by the following month organic leads have fallen by half. We see this several times a year, and the cause is almost always the same: the redesign was treated as a design project instead of a migration.
Google ranks URLs, not designs. When you change URLs, remove pages, rewrite content or slow the site down without a plan, you reset years of accumulated trust. Industry data suggests uncontrolled redesigns commonly lose 10 to 25 percent of traffic in the first month and can take months to recover. A controlled migration, on the other hand, usually dips briefly and then grows, because the new site is faster and better structured.
Here is the checklist we run on every rebuild. Share it with whoever is building your site and make sure each item has an owner.
Phase 1: Before design starts
1. Crawl and inventory the current site. Use a crawler such as Screaming Frog to export every URL, including ones not in your sitemap. Record title, meta description, H1, word count, inbound links and status code for each.
2. Pull performance data. From Google Search Console, export twelve months of clicks and impressions by page. From Analytics, export organic sessions and conversions by landing page. Now you know which pages earn your living. Those pages are untouchable without a plan.
3. Identify your backlinks. Use Search Console's Links report or a tool like Ahrefs to list every page with external links. (Google Search Console Help) These pages carry authority you cannot afford to lose.
4. Decide what changes and what does not. Google's own guidance is to change one major thing at a time where practical. (Google Search Central) If you are redesigning, try to keep the domain and URL structure. If URLs must change, do not also change the domain or hosting in the same launch.
5. Set the goals. Faster load times, better mobile experience, clearer conversion paths, and every existing ranking preserved. Write these down so "make it look modern" does not quietly become the only success criterion.
Phase 2: During the build
6. Build the URL map. A spreadsheet with every old URL in column A and its new destination in column B. One to one wherever possible. Pages that are being retired go to the closest relevant page, never to the homepage in bulk. This spreadsheet is the single most important deliverable of the project.
7. Preserve content parity. If a page ranks, keep its content. Shorten nothing that earns traffic. Designers love removing text; Google does not. Rewrite for clarity by all means, but keep the topics, headings and depth.
8. Carry over on-page SEO. Titles, meta descriptions, H1s, image alt text, internal links and canonical tags move with each page. Do not let the CMS generate new defaults.
9. Keep or improve structured data. Organization, LocalBusiness, Service, FAQ, Breadcrumb and Article schema should exist on the new site from day one. Test with Google's Rich Results Test on staging.
10. Build for speed. Target Largest Contentful Paint under 2.5 seconds, minimal layout shift and fast interaction on mid-range phones over mobile data. (web.dev Google) Modern frameworks, optimized images and edge hosting make this achievable. Speed is a ranking factor and a conversion factor. (Google Search Central)
11. Block staging from Google. Password-protect the staging site or use noindex. (Google Search Central) A staging site that gets indexed creates duplicate content that confuses the launch.
12. Test the redirects on staging. Load the URL map into the staging environment and check every row returns a single 301 hop to the correct destination. No chains (A to B to C), no loops, no 302 temporary redirects. (Google Search Central)
Phase 3: Launch day
13. Launch mid-week, in the morning. Never on a Friday. You want a full team available for 48 hours.
14. Remove noindex and staging blocks the moment the site goes live. Forgetting this is the second most common redesign disaster.
15. Deploy the 301 redirects server-side and spot-check the top 100 pages by traffic manually.
16. Submit the new XML sitemap in Search Console and request indexing on your most important pages.
17. Update Google Business Profile, social profiles, ad landing pages and email signatures with any changed URLs.
18. Verify analytics and conversion tracking fire on the new site. A surprising number of "traffic drops" after launch are just broken tracking.
Phase 4: The first 90 days
19. Watch Search Console daily for two weeks. Coverage errors, 404s, soft 404s and crawl anomalies show up here first. Fix new 404s with redirects immediately.
20. Compare rankings and traffic weekly against the pre-launch baseline, page by page. A dip of a few positions for two to four weeks is normal. A page that vanishes is not.
21. Keep the redirects live for at least a year, and preferably forever. Old links live on in other websites, bookmarks and printed material.
22. Monitor Core Web Vitals in Search Console once real-user data accumulates, and fix regressions.
23. Re-crawl the live site at week one and week four to catch broken internal links, missing metadata and orphaned pages.
Special cases
Changing platforms (for example WordPress to a modern headless setup): URL structures usually change. Budget extra time for the URL map and expect a slightly longer stabilization period.
Changing domains: follow everything above plus use Search Console's Change of Address tool, update every citation and profile, and allow two to three months for full recovery. (Google Search Console Help)
Consolidating multiple sites into one: map every page on every old domain, keep the old domains registered and redirecting indefinitely, and expect the combined site to outrank all of the originals once Google reprocesses the links.
The payoff
A migration done this way is not just damage control. Because the new site is faster, better structured and free of the technical debt of the old one, rankings usually end up higher than before within two to three months, and conversion rates rise immediately. That is the whole point of a redesign.
Every website Better Businesses builds includes this migration process as standard, because a beautiful site that loses your rankings is a liability, not an asset. If you are planning a redesign, talk to us before the design work starts. It is far cheaper to protect rankings than to rebuild them.
Sources
- Site Moves and Migrations | Google Search Central | Documentation | Google for Developers — Google Search Central
- Links report - Search Console Help — Google Search Console Help
- Largest Contentful Paint (LCP) | Articles | web.dev — web.dev (Google)
- Understanding Core Web Vitals and Google search results | Google Search Central | Documentation | Google for D — Google Search Central
- Block Search Indexing with noindex | Google Search Central | Documentation | Google for Developers — Google Search Central
- Redirects and Google Search | Google Search Central | Documentation | Google for Developers — Google Search Central
- Change of Address tool - Search Console Help — Google Search Console Help
Sources checked September 2026.
Frequently asked questions
- Will a website redesign hurt my SEO?
- It can, badly, if URLs change without redirects, content is cut or the new site is slower. Done with a proper migration plan, most sites see a small dip for two to six weeks and then outperform the old site because the new one is faster and better structured.
- How long do I need to keep 301 redirects?
- Google recommends keeping redirects for at least one year, and from a user perspective it is best to keep them permanently. Old links from other websites, bookmarks and printed materials keep pointing at the old URLs for years.
- Should I redirect old pages to my homepage?
- No. Google treats mass redirects to the homepage as soft 404s and the ranking value is lost. Redirect each old page to the most relevant new page, one to one, and only send genuinely obsolete pages to a related category or hub.
- How long does it take rankings to recover after a redesign?
- With a clean migration, rankings typically stabilize in four to six weeks. If the domain also changes, allow two to three months. A botched migration without redirects can take six months or longer to recover, and some pages never do.
Want help putting this into practice?