Website Migration SEO Checklist: Before, Launch Day, After
A website migration SEO checklist in three phases: crawl and baseline first, a redirect map for every old URL, a parity check, then 90 days of watching.
Website migration SEO means every old URL still answers after the move, with a 200 at the same address or a 301 to its closest match, and every rebuilt page keeps the titles, canonicals, and structured data it ranked with. Those two things are most of what separates a move that costs you traffic from a few weeks of normal movement while Google recrawls.
Google says to expect temporary ranking fluctuation during a site move, and that a medium-sized site can take a few weeks or more before the new URLs replace the old ones in results. The checklist below is how you tell that normal movement from a real loss, and how you avoid the losses in the first place.
It runs in three phases: before the move, launch day, and the 90 days after. It covers leaving Webflow, Framer, or WordPress for a coded site, and the AI search checks.
Key Takeaways
- Crawl the old site and save a Search Console baseline per page before anything changes. Without them, you cannot prove what the move broke.
- List what is already broken (old 404s, missing titles, duplicates) before the move, so nobody blames the new site for problems it inherited.
- Build the redirect map from every URL that has had traffic or links: the crawl, the sitemaps, Search Console, and your backlinks. Map one to one, with no chains and no mass redirects to the home page.
- Check every rebuilt page against the original: title, meta description, canonical, hreflang, structured data, internal links, image alt text, and Open Graph tags.
- Keep the pages AI answers cite at the same URL, and make sure the new host's robots.txt and bot protection let search and AI crawlers in.
Before the Move: Crawl, Baseline, and What Is Already Broken
The first phase is a record of the old site as it stands today. Everything later in this checklist is a comparison against that record, so it has to be complete before the first page is rebuilt.
Crawl the old site and save the result
Run a full crawl, starting from the XML sitemaps and following every internal link. Save the export, because it becomes the spec for the rebuild.
For each URL, record what the page must keep:
- Status code, title, meta description, and H1
- Canonical, meta robots, and hreflang
- Structured data and Open Graph tags
- Internal links, images, and their alt text
- Forms, and the scripts that run on the page
Save a Search Console baseline per page
Export clicks and impressions per page from Search Console, for as long a period as you can, plus the queries behind your top pages. Save the Page indexing report as it is today.
This is the number every page will be judged against after launch. A sitewide total hides a lost page behind a seasonal rise elsewhere, so keep it per page.
List what is already broken
Use the same crawl to list what is wrong before you touch anything: pages that already return 404, redirect chains, missing titles and descriptions, missing H1s, duplicate titles, and images without alt text.
Say the crawl finds 30 old blog URLs that already return 404, linked from pages that still rank. If nobody wrote that down, the first Search Console report after launch shows 30 errors, and the new site takes the blame.
With the list in hand, you decide what to fix during the rebuild and you have a clean line between inherited problems and new ones.
Note which pages AI answers cite
Run the questions your buyers ask through ChatGPT, Perplexity, Gemini, and Google's AI Overviews, and note which of your URLs they cite. Those pages get extra care in the redirect map and the parity check.
How to Build the Redirect Map
The redirect map pairs every old URL with its new address. Google's site move guide makes this mapping a step of its own and asks for permanent, server-side redirects, such as 301 or 308, wherever a URL changes.
Collect every URL that has ever mattered
A crawl only finds pages that are still linked. Old campaign pages, renamed posts, and pages that other sites link to can be missing from it, so pull URLs from every source:
- The crawl of the live site
- Every XML sitemap, including old ones
- Search Console: pages with clicks or impressions, and the Links report for pages with internal and external links
- Your backlink tool: every URL on your site that another site links to
- Analytics landing pages, and server logs if you have them
- Images, PDFs, and other files, which Google asks you to move like any other content
- The redirects already set up in your current platform
Apply four rules to every row
Every row in the map follows the same rules, and most come straight from Google's site move guide:
- Keep the same address where you can. A URL that does not change needs no redirect at all. On a platform change, most pages can keep their exact path.
- Map one to one, to the closest match. Don't send many old URLs to one irrelevant page, such as the home page. Google says this might be treated as a soft 404. If several old pages were merged into one, redirect them all to that page.
- Avoid chains. Point every old URL straight at its final address. That includes the redirects you already have: if an old redirect points to a page that is now moving, update it so it points to the new address directly.
- Let what you drop return 404 or 410. If a page has no match on the new site, it should not redirect anywhere. Google asks for exactly that for content you do not move.
The map is a spreadsheet you own. It outlives the migration, because every future URL change gets added to it.
Platform Notes: Leaving Webflow, Framer, or WordPress
Each platform leaves its own marks in the URLs and in what you can export. These are the ones to plan for.
Webflow
Webflow puts CMS collection items under a folder slug, such as /blog/post-name. Webflow lets you rename that folder and tells you to set 301s when a live URL changes.
When you leave, you can keep the folder exactly as it is, which needs no redirects, or clean it up and map every item one by one. Either way, carry over the 301s already set up in Webflow.
Framer
Framer's help center says plainly that Framer does not offer HTML export for self-hosting. So the new site has to be rebuilt by hand, page by page.
That makes the crawl the only full record of every title, meta tag, and URL the site ranks with. Crawl it before you start, and compare against it page by page.
WordPress
Your permalink settings define the post and page URLs, so read them from the live site and keep them. Category, tag, author, and date archives are a separate call: keep the ones Search Console shows earning clicks, and redirect or drop the rest one by one.
Check for attachment pages too. Before WordPress 6.4, WordPress created an attachment page for every upload, and sites that upgraded keep them. If yours are indexed, redirect each one to its file or its parent post.
If an SEO plugin set your titles and descriptions, copy them from the crawl, not from the theme templates. The crawl shows what Google saw.
The Parity Check: Compare Every Rebuilt Page Before Launch
A parity check compares each rebuilt page on staging against its row in the crawl. A page that differs goes back to the build and is fixed before launch.
Check these on every page:
- Title and meta description, character for character
- Canonical: Google wants a self-referencing canonical on each new URL
- Meta robots: no leftover noindex from staging
- H1 and the main body copy
- Hreflang, pointing at the new URLs
- Structured data, run through a structured data validator
- Internal links, pointing at final URLs and never through a redirect
- Images present, with their alt text
- Open Graph and social tags
- Forms submitting to the new endpoint, and analytics firing
Compare screenshots of old and new as well. Layout rarely matches to the pixel, but a missing section or a moved call to action shows up at once.
Launch Day: The Cutover Checklist
Launch day is short if the first two phases were done properly. Google suggests moving at a time of lower traffic and, for small and medium sites, moving all URLs at once rather than section by section.
Work through this list in order:
- Put the new site and the redirects live at the same time.
- Replace the staging robots.txt with the launch version, and remove every noindex that was only there for staging.
- Test every old URL in the map. Each must return a 200 or a single 301 to the right page. Paste them into our free redirect checker in bulk to see every hop and status code.
- Submit the new sitemap in Search Console and Bing Webmaster Tools. Google also suggests submitting the old sitemap for a while; warnings that its URLs redirect are normal.
- Run the URL Inspection tool on your top pages.
- If the domain changed, file a Change of Address in Search Console. On the same domain you do not need it.
- Keep the old site's export, and its hosting if you can, until every check has passed.
Google notes it crawls a new site more heavily than usual after a migration, so make sure the new host can take the load.
Keep AI Answers Pointing at Your Pages
Google says there are no additional technical requirements for AI Overviews and AI Mode: a page has to be indexed and eligible for a snippet. Its best practice is to make sure crawling is allowed in robots.txt and by any CDN or hosting setup.
That last part is where a migration can go wrong. A new host or CDN can ship with bot protection that blocks crawlers, and a robots.txt written from scratch can miss a rule you had.
Check three things after the move:
- The cited pages answer at the same URL. A page an AI answer links to should keep its address, so the link in the answer never depends on a redirect.
- AI crawlers are not blocked. OpenAI says a site that disallows OAI-SearchBot is left out of ChatGPT search answers. Our redirect checker also shows what each host's robots.txt lets GPTBot, PerplexityBot, and ClaudeBot reach, and our guide to AI crawlers lists the exact token for each bot.
- Your llms.txt came across. If the old site had one, move it and update every URL in it. The llms.txt guide covers the format.
After the Move: What to Watch for 90 Days
Google gives no fixed end date for a move: it has to visit every URL on the old and new site at least once, and crawl frequency varies. Plan to watch for at least 90 days and fix what breaks in that window, while the map is still fresh.
Watch these, weekly at first:
- In the Page indexing report, look at Not found (404), Page with redirect, and Soft 404. Compare every new error against your list of what was already broken.
- In the Crawl Stats report, check the share of 404 and server error responses, and the host status. The report only works on a root-level property.
- Check analytics or server logs for visitors hitting 404s on old URLs the map missed, and add each one.
- Compare clicks per page against the baseline. A page that dropped while the rest held usually points to a mapping or parity problem. Normal recrawl movement hits every page at once.
- Rerun the AI prompts from the baseline and check that the same pages are still cited.
Keep the redirects for as long as possible. Google says at least one year, and indefinitely from your visitors' point of view.
A platform move does not have to cost you search traffic. When Ookulli, one of our clients, moved off Framer to a coded site on July 11, 2026, its search clicks did not drop after the move.
Moving Your Site Off Webflow, Framer, or WordPress
We run this whole checklist for B2B and SaaS marketing sites leaving Webflow, Framer, or WordPress for code. Every old URL is mapped and tested before launch, and we watch Search Console and AI answers for 90 days after. You own the repo, the hosting account, the domain, and the redirect map.
If a move is on your roadmap, book a strategy call and we will start with the crawl and the list of what is already broken.
Frequently Asked Questions
How long does it take rankings to settle after a website migration?
Google says a medium-sized site can take a few weeks or more before the new URLs replace the old ones in results, and larger sites longer. Expect some fluctuation in that window, and judge each page against its own baseline.
Should I use a 301 or a 302 redirect?
Use a permanent redirect, 301 or 308, for a move. Google does not treat a temporary redirect (302 or 307) as a sign that the new URL should be canonical, so the old URL can stay in results.
Should I change my domain at the same time as the platform?
Google advises changing one thing at a time, for example moving the domain first and changing the layout after. If you must do both, map and test every URL, and file a Change of Address in Search Console.
How long should I keep the redirects?
Google says as long as possible, generally at least a year, and indefinitely for visitors. If you changed domains, Change of Address forwards signals for 180 days, and Google advises keeping the old domain registered for at least a year.
Can I redirect old pages to the home page?
Not in bulk. Google may read a mass redirect to the home page as a soft 404, so send each URL to its closest match or let it return 404 or 410.
Do I need the Change of Address tool when I leave Webflow, Framer, or WordPress?
Only if the domain or subdomain changes. Google says you do not need it for HTTP to HTTPS, www to non-www, or path changes on the same domain, so a platform move on the same domain goes without it.