The Complete SEO Migration Checklist 2026: Every Step Before, During, and After Your Website Move
The checklist that saves your rankings is the one built eight weeks before launch — not the week before.
Head of Search Intelligence & AI · Conversion Game
The checklist that saves your rankings is not the one your development team builds the week before launch. It is the one built eight weeks before launch, validated against your Search Console data, and verified against a full crawl of every URL your site has ever indexed. The week-before version is damage control. The eight-weeks-before version is the process that means damage control is never needed.
KEY TAKEAWAYS
The 2026 migration checklist has five phases — the 2022 three-phase version does not cover the GEO and AEO readiness layer that now determines AI search visibility
The pre-migration audit is the most important phase — compress it and you compress your ability to prevent problems in every phase that follows
Launch day noindex verification is the single most critical check — a staging noindex that goes live with the production site stops Google crawling completely
The 30-day post-migration monitoring window is when problems are cheapest to fix — silent issues not caught in this window compound significantly over the following months
Migration failures are almost never caused by technical incompetence — they are caused by timeline compression that forces technical shortcuts
Why the 2022 migration checklist is officially broken in 2026
The standard migration checklist that most agencies and developers work from was built for a search environment that has changed significantly. The 2022 version covered the fundamentals correctly: crawl the site, map the redirects, verify the canonicals, resubmit the sitemap, monitor Search Console for crawl errors. Those fundamentals still matter. They are the foundation. What the 2022 checklist does not cover is the layer that has become critical in 2026 — the AI search visibility layer.
Nearly 60% of Google searches now end without a click. AI Overviews answer queries before users reach any website. If your migration checklist does not include GEO and AEO readiness items, you are successfully protecting a search presence that is shrinking while ignoring the one that is growing. The 2026 migration checklist has five phases instead of three. The additional phases are not optional — they are standard requirements for any migration that wants to protect its full search visibility.
EXPERT NOTE
“The checklist that saves your rankings is not the one your development team builds the week before launch. It is the one built eight weeks before launch, validated against your Search Console data, and verified against a full crawl of every URL your site has ever indexed. The week-before version is damage control. The eight-weeks-before version is the process that means damage control is never needed.”
Phase 1 — Pre-migration audit
Crawl the entire current site and export every URL with its status code, title tag, H1, meta description, canonical tag, and internal link count. Export your full URL list from Google Search Console filtered by clicks descending — this gives you the traffic-weighted URL priority list. Export your backlink profile — every page with external backlinks pointing to it needs a verified 301 redirect. Document your current featured snippet and People Also Ask positions — these are your AEO assets and are highly volatile during migrations.
Test your current AI citation footprint. Search your top 20 keywords in Google and note every AI Overview that appears. Ask ChatGPT and Gemini about your brand, your services, and your industry. Screenshot the results. This is your GEO baseline — the AI visibility you need to protect and rebuild on the new site. Audit your existing schema implementation and document every schema type currently active across the site.
Phase 2 — Technical migration execution
The redirect map is the central deliverable of the technical migration phase. Every URL in your crawl data and Search Console export that has traffic, backlinks, or featured snippet positions needs a row in the redirect map specifying the old URL, the new URL, and the redirect type. The redirect map is implemented and tested in a staging environment before launch. Every redirect is followed programmatically and confirmed to return a 301 status code to the correct destination URL. Redirect chains longer than two hops need to be flattened to single-hop redirects.
Canonical tags on the new site need to be audited before launch. The XML sitemap should contain only indexable, canonical URLs — not redirect URLs, not noindex URLs, not parameter-driven duplicates. Meta tags need to be verified on the new platform before launch. Schema markup on the new site needs to be implemented before launch as a minimum stack: Organisation on every page, FAQPage on every page with FAQ content, Article on every blog post with author attribution, BreadcrumbList on every non-homepage page, Product schema on every ecommerce product page.
Phase 3 — Launch day protocol
The first action after launch is to check that the production site is not returning a noindex header or meta robots noindex tag. This is the single most catastrophic launch day error — the site goes live with the staging noindex active and Google stops crawling. Verify that at least five high-priority redirects are returning 301 status codes on the production environment. Check that GA4 is tracking correctly by completing a test transaction or form submission and confirming the event appears in GA4 in real time.
Submit the new sitemap to Google Search Console immediately after launch and request indexing of the homepage and five to ten key pages. Check that SSL is functioning correctly — the padlock should appear in the browser address bar for every page on the new site.
Phase 4 — Post-migration monitoring (the 30-day window)
Day 1 to 3: Check Search Console daily for crawl errors. Any page returning a 404 that should be returning a 301 indicates a gap in the redirect map — fix within 24 hours. Day 7: Pull the ranking report for your top 20 keywords and compare against the pre-migration baseline. Day 14: Check featured snippet positions — are the answer engine positions documented in Phase 1 still holding? Day 30: Run a full crawl of the new site and compare the indexed URL count against the pre-migration baseline.
Phase 5 — GEO and AEO readiness check
At day 7 repeat the AI citation baseline test from Phase 1. Search your top 20 keywords in Google and note every AI Overview. Test your brand in ChatGPT and Gemini. Compare the results against your pre-migration baseline. AI citations that existed before the migration may disappear temporarily during the first two to four weeks as AI models update their entity models for the new site architecture.
At day 30 run the full GEO readiness score against the new site. Rate entity consistency, content extractability, schema coverage, AI citation frequency, and brand entity strength on the same 1-10 scale used in the Phase 1 baseline. The scores should be equal to or higher than the pre-migration baseline. If any dimension scores significantly lower, that dimension needs targeted improvement work before the migration is considered complete.
The one thing that causes most migration failures
If I had to reduce fifteen years of migration experience to one insight it would be this: migration failures are not caused by technical incompetence. They are caused by timeline compression. A migration that needs twelve weeks gets approved for six. The pre-migration audit gets compressed from four weeks to two. The redirect map gets built in three days instead of two weeks. And the launch happens on schedule — with gaps in the redirect map, incomplete schema, unverified GA4 tracking, and no GEO baseline to measure recovery against. The specialist’s job is to protect the timeline. Not to accommodate compression.
FREQUENTLY ASKED QUESTIONS
How long should a migration checklist take to complete?
The time to complete a migration checklist depends entirely on site size and complexity. For a small site with under 500 URLs and a simple URL structure, the five-phase checklist can be completed in six to eight weeks. For a mid-sized site with 1,000 to 5,000 URLs the timeline is ten to fourteen weeks. For large sites with over 10,000 URLs the timeline is sixteen to twenty-four weeks. The phase that is most frequently underestimated is the pre-migration audit — for mid-sized sites this phase alone requires three to four weeks of dedicated work to compile all six components correctly. Attempting to compress the audit phase to one week on a mid-sized site almost always results in an incomplete redirect map.
Can I use automated tools to build the redirect map?
Automated redirect mapping tools can accelerate the process for large catalogues but they cannot replace the human validation step. Automated tools match old URLs to new URLs based on URL pattern rules — they work well when the URL structure change follows a predictable formula. They fail when old URLs have custom structures, when content has been reorganised into different categories on the new site, or when some old URLs should be redirected to pages that do not have a direct structural equivalent on the new platform. Every automated redirect map needs to be reviewed against the Search Console traffic data to verify that the highest-traffic URLs are correctly mapped and that the most linked-to URLs are correctly handled.
What should I do if my rankings drop after launch?
Ranking drops in the first two weeks after a migration launch are common and do not necessarily indicate a problem. Google re-evaluates new URL architectures and ranking positions often fluctuate by five to ten positions during the re-evaluation period before stabilising. The questions to ask are: are the rankings stabilising or continuing to fall? Are the 301 redirects returning the correct status codes? Are there any crawl errors appearing in Search Console for the pages that have dropped? Are the canonical tags correctly implemented on the affected pages? A ranking drop that stabilises within two weeks and then recovers is normal migration volatility. A ranking drop that continues falling after two weeks or that affects pages where the redirect map was validated correctly indicates a deeper technical issue that needs specialist investigation.
How do I know if my GEO visibility has recovered after migration?
GEO visibility recovery is measured by comparing your post-migration AI citation footprint against the pre-migration baseline captured in Phase 1. The measurement process is manual: search your top 20 keywords in Google and note every AI Overview citation, then ask your target buyer questions in ChatGPT and Gemini and note which brands and sources are cited. Compare the results against your Phase 1 screenshots. Full GEO visibility recovery typically takes 60 to 90 days for a well-executed migration with the complete GEO architecture implemented before launch. If AI citations that existed before migration are still absent at the 90-day mark, the entity architecture — schema implementation, entity consistency, content extractability — needs to be investigated and improved.
READY TO MIGRATE THE RIGHT WAY?
Every move is calculated. Let’s map yours.
We have managed hundreds of migrations. Not one site tanked under our direct oversight. The five-phase checklist above is what we verify on every migration we oversee. Book a free 30-minute strategy conversation.
Business and corporate email addresses only.