Website Migration Without Losing Google Rankings: A Checklist

A website migration without losing Google rankings comes down to this: every old URL still works, at the same address or through a 301 to its matching new page, and Google can crawl the new site. Benchmark first, test before launch, then watch Search Console.
I moved this site from Webflow to Astro, so this list comes from a move I did myself. If you would rather hand the whole move to someone, see my website design, migration and SEO page. If you have not picked a builder yet, compare an AI website builder with a designer first.
What decides whether rankings survive a website migration?
Three things decide it: the addresses, the content and the crawl. Google ranks pages at specific URLs. If a URL disappears without a redirect, the page that held the ranking is gone. If the new page says something very different, the ranking can move. And if Google cannot crawl the new site, nothing gets read at all.
Google splits migrations into two kinds, and each has its own checklist. Know which one you are doing before you start.
| Type of move | Example | What changes | Google’s guide |
|---|---|---|---|
| Move with no URL changes | New CMS, new host or new design with the same addresses | The server and the code | Site move without URL changes |
| Move with URL changes | New domain, new folder structure, or HTTP to HTTPS | The addresses themselves | Site move with URL changes |
The first kind is the easier one. The second needs a redirect map and, for a domain change, Search Console’s Change of Address tool. Many real moves are both: the platform changes and a few URLs change with it. In that case, do both lists.
What did I do when I moved my own site from Webflow to Astro?
I rebuilt the site on Astro and tested a full copy before I touched DNS. Here is what that looked like:
- I exported the site’s content from Webflow and rebuilt the pages from the export with an import script, so the content and the page slugs came straight from the export.
- I put a copy on a temporary address first. The real domain kept serving the old Webflow site while I tested the new one.
- I did not touch the nameservers. Google Workspace runs the email for the domain, so a careless DNS change could have broken mail as well as the site.
- I kept the same Google Analytics property. The history stayed continuous through the switch.
- I carried over the 49 redirects Webflow already had, and kept a separate file for new ones after the move.
- I kept the component gallery out of Google. The template ships a style guide page, so I excluded it from the sitemap and set it to noindex.
- I submitted the new sitemap in Search Console. I left the old sitemap address in the list, and it now returns a 404. That is a loose end I would clean up, because Google says to remove the old sitemap once the new one is in use.
I am not showing a before-and-after traffic chart here, so treat this as a process, not a result. The part I would repeat on any move is the order: copy, test, then switch.
If you are choosing where to build next, in my website design video I recommend Astro, a free open-source site builder, with Cloudflare for domains and hosting, and I encourage anyone unhappy with WordPress or Webflow to move there.
Video · 31 min
GPT 6.2 Astra vs Fable 5.2 Website Design (One CLEAR Winner)
I show how I design a site with Claude and why I build on Astro and host on Cloudflare, the platform this site moved to.
Watch the video →
What should you do before the move?
Before the move, record where you stand, list every URL, and decide where each one goes. Most migrations that go wrong were damaged at this stage, not on launch day.
Early on, we didn’t know much about analytics or tracking, so we threw money everywhere and assumed it was working. You can’t improve what you don’t track, so measure everything. That is why step one is a benchmark.
- Benchmark. Export your organic clicks and impressions from Search Console, your top pages, and your top 20 or so keywords with their positions. Save the files with today’s date. Without them you cannot tell a normal dip from a real problem.
- Inventory every URL. Crawl the old site with a crawler such as Screaming Frog, and add the URLs from your CMS export, your sitemap and Search Console. Mark the pages that bring traffic or have links from other sites. Those are the ones you cannot afford to lose.
- Decide the new address for each one. If the address stays the same, write “same.” If it changes, write the new one.
- Build the redirect map. One row per old URL. A small example looks like this:
| Old URL | New URL | Type | Note |
|---|---|---|---|
| /blog/seo-tips | /blog/seo-tips/ | 301 | Trailing slash added |
| /services-old | /services/websites/ | 301 | Closest match |
| /summer-sale-2024 | (none) | 410 | Expired offer, no replacement |
| /about | /about/ | 301 | Same page, new format |
Google asks for permanent server-side redirects, a 301 or 308, straight from each old URL to its final page, with no chains. It also advises against sending many old URLs to one unrelated page, such as the homepage. I would let a page with no real replacement return a 404 or 410 instead. 5. Build and test on a hidden copy. Google suggests a temporary hostname with a noindex tag for testing, then using the URL Inspection tool to confirm Googlebot can reach the new host. Check pages, images, forms and PDFs, and make sure no firewall blocks Googlebot. 6. Carry over your verification and analytics. Google says to keep Search Console verification working on the new copy, for example by carrying over the HTML file, meta tag or analytics code. Reinstall your tracking too, so the data has no gap. 7. Plan the DNS change. Google recommends lowering the DNS TTL to a few hours at least a week before the move, so the switch spreads quickly. Write down every DNS record, especially email, before you change anything.
What do you check on launch day?
On launch day, the job is to remove everything you used for testing and then prove the new site answers like the old one. Treat it as a short, boring checklist.
- Remove the test blocks. Take off any robots.txt disallow rule and every noindex tag or header you added for staging. A page with a noindex tag stays out of search, so check the live pages, not just the template.
- Test the redirects. Do not trust a spreadsheet. Run the old URLs and read the answers. This one-liner checks a list of full URLs, one per line:
while read u; do
curl -s -o /dev/null -w "%{http_code} %{redirect_url} <- $u\n" "$u"
done < old-urls.txt
Every line should show a 301 or 308 pointing at the right page, or a 200 where the address did not change. A redirect that points to another redirect is a chain, so fix it.
- Check the basics on the new site. Titles, meta descriptions, headings, canonical tags, internal links, images and structured data should match what was on the old pages.
- Submit the new sitemap in Search Console, and keep the old sitemap file around for a while. Google suggests saving the old-URL sitemap so you can watch the old addresses drop out of the index as the new ones come in.
- Watch email. If the domain’s mail goes through the same DNS, send a test message the minute the switch happens.
What do you watch after the launch?
After launch, watch Search Console and your redirects, and do not change anything in a panic. Wobbles in the first days are normal.
In paid ads, we used to panic two days after a change and change it back. The lesson I took from that is to give changes time to work and look at the data before deciding something failed. A migration is the same. SEO is a very long-term commitment, and judging a move in the first week can lead you to undo a change that was working.
Check these on a schedule:
| When | What to check | Where |
|---|---|---|
| Day 1 | Home page and top 10 pages load, redirects work, no noindex, mail works | Browser, curl, a test email |
| Week 1 | Crawl errors, pages with “Page with redirect” or “Not found”, sitemap status | Search Console, Pages report |
| Weeks 2 to 4 | Clicks and impressions against your benchmark, top pages still indexed | Search Console, Performance report |
| Weeks 4 to 8 | Rankings for your top keywords, links from other sites that still point to old URLs | Your benchmark files, a link report |
One guide recommends monitoring for 4 to 8 weeks after launch. Google says most pages of a small or medium site move over in a few weeks, and bigger sites take longer. I think that if a top page is still missing after the first month, something specific is wrong, and it is worth looking for the cause.
Keep the redirects after that window ends. Google says to keep them for at least one year. An SEO guide I read says to leave them indefinitely, because old links and bookmarks keep using the old addresses, and I would lean that way for any page that ever earned a link.
What are the most common migration mistakes?
Most migrations that fail make one of these mistakes.
- No benchmark. You cannot measure the damage, so you cannot fix it.
- Redirects missing or wrong. Old URLs return a 404, loop, or chain through two or three hops.
- Everything redirected to the homepage. Google advises against it. Match each old page to its closest new page.
- A leftover noindex or a robots.txt block. The staging settings go live with the site.
- The content changed along with the platform. If you rewrite every page and change every address in the same week, you cannot tell which change caused a drop. Where you can, move first and redesign later.
- Email broken by a DNS change. Copy the records before you change anything.
- Analytics lost. The new site goes live without the tracking code, so you have a gap exactly when you need data.
- Judging too early. A dip in week one is not a verdict.
Should you do this yourself or get help?
Do it yourself if the site is small and every URL stays the same. Get help if you have hundreds of pages, a domain change, a new URL structure, or a site that brings in leads you cannot afford to lose.
Quality still matters after the move. There’s a second E in EEAT now: experience. If I write about plumbing and I’m not a plumber, Google will probably rank a master plumber’s post higher. That is why I would not rewrite your best-ranking pages during a migration just to make them “fresh.”
If you want a person to plan the move, build the redirect map and watch the results, start with my website design, migration and SEO page, or see how I work with business owners on my AI consulting page. For the marketing side after the move, see AI marketing tools a small business should try first, and to get the new site quoted in AI answers, read AEO and GEO.
Sources
- Google Search Central, Site move with URL changes, read November 19, 2026. Source of the redirect types, the one-year minimum for redirects, the advice against chains and homepage redirects, the old-URL sitemap tip and the few-weeks timeline for small and medium sites.
- Google Search Central, Site move without URL changes, read November 19, 2026. Source of the temporary hostname with noindex, the URL Inspection check, the DNS TTL advice and the verification carry-over.
- urllo, Sean Pasemko, Website migration SEO: migrate without losing rankings, dated August 25, 2026, read November 19, 2026. Source of the 4 to 8 week monitoring window, the several-weeks-to-a-few-months stabilization range and the advice to keep redirects indefinitely.
- Search Engine Journal, Adam Heitzman, The website migration process: a 16-step checklist, published January 29, 2025, read November 19, 2026. Source of the benchmark, inventory, staging and pre-launch check steps.


