Website Migration SEO Checklist: Keep Rankings When You Change Platforms
A website migration SEO checklist is the list of checks that keeps search traffic when URLs, CMS or platform change. In “Website Migration SEO Checklist: Keep Rankings When You Change Platforms”, Pavlo Zhydkykh, who moves startup sites to Framer and Astro, covers the URL map, 301 redirects and launch checks.
Pavlo ZhydkykhUpdated · 6 min read
Short answer
The SEO side of a migration is planned before the design, not in the week before launch. A platform change keeps its rankings when the URL map, the redirects and the launch checks are ready before the first page is built. This is the checklist I use when I move a startup site to Framer or to Astro + Sanity, and every rule in it comes from Google's own guidance on site moves.
Key takeaways
- URL redirection makes a page available under more than one address, so visitors and crawlers on an old URL land on the new one.[1]
- Google says 301 and other permanent redirects do not cause a loss in PageRank, and advises keeping such redirects for at least a year.[2]
- Redirecting many old URLs to one irrelevant page, such as the new home page, may be treated as a soft 404.[2]
- Permanent redirects make Google show the new URL in results; temporary ones such as 302 keep the old URL there.[3]
- Pavlo Zhydkykh runs platform migrations for a fixed $2,200 in 2 to 4 weeks, with a 301 redirect for every changed URL.
What is URL redirection?
URL redirection is a technique that makes a web page available under more than one address: whoever opens the old URL lands on a new one. In a website migration, permanent 301 redirects carry visitors and search signals from each old page to the matching new page.
“The URL map decides a migration. I write the map before any design work starts, and I keep the redirects for years, not weeks.”
Last checked · 6 min read
What a platform change puts at risk
Google does not rank a platform. It ranks URLs, the content on them and the links that point at them. When a site moves from WordPress or Webflow to Astro or Framer, the design changes, but the risk sits in three places: URLs that change without a redirect, content that gets cut or rewritten on the way, and settings that do not survive the move, such as titles, canonical tags, robots rules and structured data.
Google's own guide to moving a site also asks you to change one thing at a time: if you plan a new domain, a new CMS and a new layout, do them one after the other. Startups rarely wait that long, so the checklist below assumes you change the platform and the design together and keep the domain.
Before the build: list every URL you have
The first deliverable of a migration is a spreadsheet, not a design. It holds every URL that exists today and a few facts about each one.
- All URLs from the current sitemap, the CMS export and a full crawl of the live site.
- The pages that bring traffic, from Search Console and your analytics, for at least the last 12 months.
- The pages other sites link to, from the Links report in Search Console.
- Images, PDFs and other files you host. Google points out that these may already get traffic from Search and from links.
- For each URL: title, meta description, H1, canonical tag, indexing status and structured data types.
This export is also your test sheet. After launch you compare the new site against it, line by line.
The URL map: one row per old URL
The URL map has two columns: the old URL and the new one. Every row ends in one of three answers.
- Same URL. The best case. Keep every slug that can stay the same, and no redirect is needed.
- New URL. A 301 redirect from the old address to the closest new page.
- Removed. If the content is gone on purpose and has no close match, the old URL returns 404 or 410, as Google recommends for deleted content.
The common mistake is a fourth answer: send everything that does not fit to the home page. Google warns that redirecting many old URLs to one irrelevant page, such as the new home page, can confuse users and might be treated as a soft 404. Merged content is the exception. If three old posts became one guide, all three can redirect to that guide.
Redirect rules that keep rankings
Google's page on redirects and Google Search sorts redirects into two groups. Permanent redirects tell Google to show the new URL in results. Temporary ones keep the old URL there.
| Permanent: 301, 308 | Temporary: 302, 307 | |
|---|---|---|
| URL Google shows in results | The new one | The old one |
| Target treated as canonical | Yes | No, unless other signals point to it |
| Link credit | Kept: Google says no PageRank is lost | Not meant for a move |
| Use in a migration | Every page that moved for good | Short outages and tests only |
Three more rules come from Google's site move guide:
- Use server side redirects. Client side redirects, such as JavaScript, are a last resort.
- Redirect to the final page in one hop. Googlebot follows up to 10 hops, but Google advises keeping any chain you cannot avoid to no more than 3.
- Keep the redirects for as long as possible, generally at least a year.
One trap on Cloudflare Pages, where many Astro sites live: in a _redirects file the status code defaults to 302 when you leave it out, and one file takes up to 2,000 static and 100 dynamic redirects, according to Cloudflare's docs. I write 301 on every line, so no move ever ships as temporary.
The migration SEO checklist
This is the list I work through on every move. Print it, or copy it into the same spreadsheet as the URL map.
| When | Check |
|---|---|
| Before launch | Old site crawled; URLs, titles, descriptions and H1s exported |
| Before launch | URL map complete: every row is same URL, 301 or 404/410 |
| Before launch | Titles, meta descriptions and structured data carried over |
| Before launch | Every new page has a self-referencing canonical tag |
| Before launch | Internal links point to the new URLs, not through redirects |
| Launch day | Development noindex rules and robots.txt blocks removed |
| Launch day | Redirects live, and a script confirms every row of the map |
| Launch day | New sitemap submitted in Search Console |
| Launch day | Analytics and Search Console verification work on the new build |
| First weeks | Indexing and crawl reports checked every week |
| First weeks | New 404s from old links fixed with extra redirects |
| First weeks | Profiles, ad campaigns and top linking sites updated |
Launch day and the weeks after
On launch day I run the whole URL map through a script that requests each old URL and checks two things: the status is 301, and the redirect lands on the planned page with a 200. Google's URL Inspection Tool is fine for a single page; for hundreds of rows a script is the only way that stays accurate.
Then the waiting starts. Google says a medium-sized site can take a few weeks or more before the new URLs replace the old ones in results, and that rankings can fluctuate while Google recrawls. Watch the indexing and Sitemaps reports in Search Console during that time. Warnings about redirects in the old sitemap are normal, and Google says you can ignore them.
If the domain changes too, submit a Change of Address in Search Console for the old site. Google says the tool is only for moves from one domain or subdomain to another, not for HTTP to HTTPS or path changes on the same domain.
Finally, update the links you control: social profiles, ad campaigns and the partner sites that send the most visits. Every link you fix is one redirect fewer for your visitors.
Carry over what AI search reads
A migration is also the moment AI assistants can lose track of a site. If the old build had structured data, an llms.txt file or an FAQ that answered buyer questions, carry them over to the new templates and point them at the new URLs. My guides to schema markup and llms.txt cover what each one should hold.
Check one more thing before launch: open the source of a few new pages and make sure the text is in the HTML the server sends. Astro renders pages to HTML on the server by default, which is one reason I build content sites on it.
What a migration costs with me
I move startup sites to Framer and to Astro + Sanity, from Webflow, WordPress, Wix and older builds. A migration is a fixed $2,200 and takes 2 to 4 weeks. The URL map, the redirects, the metadata and the launch checks are part of that price, as are SEO and GEO basics. After launch, help costs $30 an hour with no retainer.
The routes I take most often have their own pages: Webflow to Astro, WordPress to Astro and Webflow to Framer. All of them are on the migration page, and the pricing page lists every fixed price. If you are still choosing the platform, start with Astro vs Webflow or what a headless CMS is.
My recommendation
Start with the spreadsheet. When the URL map is complete before design starts, the rest of the migration is careful work, not a gamble. Keep every URL you can, redirect the rest with a 301 in one hop, never dump old pages on the home page, and leave the redirects in place for years. Then give Google a few weeks before you judge the result.
If you need this built
A migration to Framer or Astro starts at $2,200 and takes 2 to 4 weeks, with every old URL mapped to its new page.
See migrationsFrequently asked questions
Will I lose rankings when I change platforms?
You may see a temporary dip. Google says rankings can fluctuate while it recrawls a changed site and that they settle down over time. A medium-sized site can take a few weeks or more. Keeping the content and redirecting every changed URL is what lets them settle where they were.
Do 301 redirects lose link equity?
No. Google says 301 and other permanent redirects do not cause a loss in PageRank. Long chains are the real risk, so redirect each old URL straight to its final page.
How long should I keep redirects after a migration?
Google recommends keeping them for as long as possible, generally at least a year, so it can move all signals and links to the new URLs. For visitors with old bookmarks, keeping them for good is better.
Should I redirect deleted pages to the home page?
No. Redirect a page to its closest match, or let it return 404 or 410 if the content is gone. Google warns that many URLs redirected to one irrelevant page may be treated as a soft 404.
Do I need the Change of Address tool in Search Console?
Only when the domain or subdomain changes, for example example.com to example.net. Google says you do not need it for HTTP to HTTPS, www to non-www or path changes on the same domain.
How long does a migration take with Pavlo, and what does it cost?
Two to four weeks for a typical marketing site, at a fixed $2,200. The URL map, redirects, metadata, launch checks and SEO and GEO basics are included; later help is $30 an hour.
Free tool Does ChatGPT recommend you? Free report in 48 hours · 5 AI engines
Checklist
6 migration mistakes that cost rankings
Each of these shows up in Google’s own site move guidance as something to avoid. Pavlo Zhydkykh checks for all six before a new build goes live.
1. Every old page sent home
Many URLs redirected to the home page can count as soft 404s; each old URL needs the closest match or a 404.
2. Temporary redirects
A 302 keeps the old URL in results. On Cloudflare Pages a rule without a code is a 302, so Pavlo writes 301 on every line.
3. Redirect chains
Old redirects pointing at new redirects add hops; Pavlo sends every old URL straight to the final page.
4. Development blocks left on
A noindex rule or a robots.txt block from the build phase that ships with the launch hides the new site.
5. Images and PDFs forgotten
Files you host may already get search traffic and links, and Pavlo gives them the same redirects as pages.
6. Redirects removed too early
Google advises keeping redirects generally at least a year so signals and links can move to the new URLs.
Fit check
Is a platform migration right now
right for you?
A good fit if
- The current platform blocks the site: slow pages, a costly plan or a CMS the team avoids.
- You can freeze big content changes for the 2 to 4 weeks of the move.
- Someone owns the URL map and checks it against the live site, as Pavlo does on every migration.
- You keep the same domain, so only the platform and design change at once.
Not the right fit if
- You also plan a new domain and a new site structure in the same week: Google advises one change at a time.
- Your busiest season starts next week; Google suggests moving during a traffic dip.
- Nobody can edit server or hosting redirects after launch.
- The current site is fast, ranks and is easy to edit: Pavlo would leave the site alone.
Compared
Permanent vs temporary redirects in a migration
Both send visitors to the new page. Only the permanent kind tells Google that the move is final, and Pavlo Zhydkykh uses that kind for every changed URL.
| Criterion | 301 or 308 (permanent) | 302 or 307 (temporary) |
|---|---|---|
| URL shown in results | The new URL | The old URL |
| Canonical signal | The target becomes canonical | Not used as a canonical signal |
| PageRank | Not lost, Google says | Not meant for a move |
| Right use | Pages that moved for good | Short outages and tests |
| Default in Cloudflare _redirects | Must be written as 301 | Used when no code is given |
In their words
Site moves, in the words
of Google and clients
Word for word, with the source linked: research, official documentation and the people Pavlo Zhydkykh has worked for.
“If you need to change the URL of a page as it is shown in search engine results, we recommend that you use a permanent server-side redirect whenever possible.”
“This timeframe allows Google to transfer all signals to the new URLs, including recrawling and reassigning links on other sites that point to your old URLs.”
“A _redirects file is limited to 2,000 static redirects and 100 dynamic redirects, for a combined total of 2,100 redirects.”
“One of the best contractors I have worked with. Really thoughtful about communication. Went above and beyond in delivering the results that our team needs. Would 100% hire again for our projects.”
“The collaboration went smoothly and the work was delivered as agreed. Communication was timely, and the final result aligned with the initial expectations. Overall, a very positive and rewarding experience!”
“Pavlo was a pleasure to work with on this project. The web and mobile designs he created were amazing. His communication was prompt which made for a smooth project. I highly recommend his services.”
About the author
Pavlo Zhydkykh
Pavlo Zhydkykh is a web designer and developer in Eastern Europe who has built websites for AI, fintech and B2B startups since 2016, designing and building each project himself on Framer or Astro + Sanity. Clients include MStudio Asia, Silicon Data, Inturai, Accolade Pro, NimbleStax and Sancts.
- Top Rated on Upwork
- 100% Job Success
- 10 years since 2016
- 50+ sites shipped
- 90+ PageSpeed at launch
About Pavlo LinkedInUpworkContra Privacy policy
Page reviewed by Pavlo Zhydkykh · Updated
In this topic
Platforms compared
10 articles
- 01 Figma MCP with Claude Code: What 15,280 Calls Taught Me 6 min
- 02 Best Claude Code Skills for Web Design: I Counted 259 Calls 8 min
- 03 Website Migration SEO Checklist: Keep Rankings When You Change Platforms You are here
- 04 What Is a Headless CMS, and When Does a Marketing Site Need One? Next
- 05 Astro vs Webflow in 2026: Which Fits a Startup Website? 6 min
- 06 Framer vs Webflow 2026: Which Platform Wins? 8 min
- 07 Framer vs WordPress 2026: Which Should You Choose? 5 min
- 08 Framer vs Figma Sites 2026: What's the Difference? 6 min
- 09 Should Your SaaS Site Be Custom-Coded or No-Code? 6 min
- 10 Webflow to Framer SEO: Redirects That Keep Rankings 6 min