Most SEO migration checklists were written for a world where Google was the only thing that mattered. That world is gone. In 2026, you can run a flawless redirect map, keep every ranking intact, and still lose visibility in ChatGPT, Gemini, and Perplexity, because those platforms read your site differently than Google does. They depend on entity signals and structured data that a standard redirect-and-rankings checklist never touches.
A study of 892 website migrations found the average recovery time, when SEO wasn’t treated as a priority from day one, was 523 days. Nearly 17% of sites never recovered at all. That’s the cost of treating a migration as a developer task with an SEO review bolted on at the end.
Here’s what to actually check, broken into three phases.
Phase 1: Before you touch anything
The work that prevents problems happens here, not during the migration itself. If you haven’t run a proper SEO audit recently, start there, since a migration amplifies whatever’s already broken.
- Crawl the existing site and export every URL. Pages, posts, category pages, product pages, all of it.
- Benchmark your current rankings, organic traffic, and top-performing pages. You can’t measure recovery if you don’t know what you’re recovering to.
- Export your current schema markup, including Organization and entity-level structured data. This is the piece that protects your AI search visibility, and it’s the piece almost every migration checklist skips entirely.
- Document your title tags, meta descriptions, header structure, and internal linking. You’ll need this as a reference once the new site is live.
- Build a URL redirect map. Every old URL mapped to its exact new destination, one hop only. No redirect chains.
Phase 2: During the migration
- Implement 301 redirects exactly per your map. No guessing, no shortcuts.
- Carry over schema and entity markup to the new URLs, not just the visible content on the page.
- If you’re moving to a headless setup, confirm your key pages use server-side rendering. AI crawlers and traditional search crawlers both need to actually see your content, not just your site visitors.
- QA on staging before launch. Crawl the staging site the same way you crawled the live one, and diff the two so nothing slips through.
- Submit a GSC Change of Address if you’re changing domains, and resubmit your sitemap either way.
You don’t need an llms.txt file for any of this, despite what you might read elsewhere. We’ve covered why that’s not a thing worth your time. What actually matters is standard, well-structured schema that both Google and AI crawlers can parse correctly.
Phase 3: After launch
- Monitor daily for the first two weeks, then weekly for two months. Watch impressions and position in Search Console, not just clicks. AI Overviews and zero-click search already eat into clicks even when rankings hold steady, so clicks alone will lie to you. We’ve written about why traffic can drop even when nothing’s technically wrong.
- Re-crawl and request indexing on your highest-value pages instead of waiting for Google to find them on its own schedule.
- Check whether your brand and core category terms still surface correctly in AI answers. This matters more now than it did a year ago. Google confirmed in October 2026 that AI Overviews and AI Mode are surfacing more inline links, placing them higher in the response, and rolling out a dedicated sources section for certain queries, with Preferred Sources usage up 7x this year. A site that loses its entity signals in a migration isn’t just risking a ranking drop anymore, it’s risking being left out of a system that’s actively getting better at crediting sources it trusts. [Source: Search Engine Land, Oct 15, 2026]
- Compare against your Phase 1 benchmarks at 30, 60, and 90 days. If something’s drifting, you’ll catch it early instead of three months in.
If you want to know whether your brand is actually showing up in AI answers right now, before or after a migration, that’s exactly what a GEO audit is for.
Frequently asked questions
How long does SEO take to recover after a site migration?
Recovery timelines vary by site size and how much changed, but one analysis of nearly 900 migrations found an average recovery time of 523 days when SEO wasn’t prioritized from the start. Migrations planned with SEO built in from day one typically recover in weeks, not months.
How many hours should you budget for SEO on a site migration?
It depends on site complexity, but the biggest time cost is almost always the pre-migration audit and redirect mapping, not migration day itself. Underbudgeting this phase is the most common reason migrations go sideways.
How do you migrate a website without losing SEO?
Benchmark everything before you start, map every URL to its new destination with a single-hop 301 redirect, carry over all schema and metadata, and monitor closely for the first two months after launch. Skip any of these and you’re relying on luck.
Does a CMS migration affect SEO?
It can, especially if the new CMS changes how pages render for crawlers, like a move to a JavaScript-heavy or headless setup without server-side rendering. The platform change itself isn’t the risk. Losing redirects, schema, or crawlability in the process is.
What is an SEO migration audit?
A pre-migration audit benchmarks your current rankings, traffic, top pages, and technical setup so you have a clear baseline to measure recovery against, and so you know exactly what needs to carry over to the new site.
Before you flip the switch
A migration is one of the highest-risk moments in organic search, and most of the risk is avoidable if someone’s actually watching for it.
Thinking about a migration and want it done without the guesswork?
Tabula runs the SEO and AI-visibility side of migrations for e-commerce brands, so nothing gets lost in the move.
Talk to Tabula →