Website Migration SEO Checklist: Keep Rankings When You Move

A website move should not erase years of search equity. Most ranking losses after a redesign or domain change come from skipped inventory, weak redirects, or staging settings that ship to production. A website migration SEO checklist catches all three before launch.

Google's site-move guidance is clear: temporary ranking fluctuation while URLs are recrawled is normal. Permanent redirects do not lose PageRank. Your job is to make the new URLs easy to discover and map.

This checklist walks a US service-business owner through before, launch day, and after. Use it yourself, or hire help through our website migration SEO service when the URL map is large or the launch window is tight.

What protects rankings during a website migration?

Start with a full inventory and traffic baseline. Build a one-to-one redirect map from old URLs to the closest new URLs. Keep staging noindex and auth off the live site. Launch with server-side 301 or 308 redirects and a fresh XML sitemap. Then watch Google Search Console for weeks and fix gaps fast.

Change one major thing at a time when you can. Stacking a domain move, CMS swap, and full redesign in the same cutover makes diagnosis harder if rankings wobble.

What kinds of migrations need SEO care?

Not every move risks the same signals. Match your plan to the type of change before you rewrite a single page.

Even a "same URLs" redesign still needs crawl checks, schema review, and proof that robots rules never blocked production. For the broader technical layer around crawlability and indexing, see our technical SEO work.

Google recommends changing one major factor at a time when possible. If you must combine moves, document every change so you can isolate problems after launch.

How do you inventory and baseline before the move?

You cannot protect what you never measured. Export a pre-migration snapshot so you know which pages matter and what "normal" looked like.

• Crawl the live site and save the full URL list with status codes.

• Export the current XML sitemap and compare it to the crawl.

• Pull Search Console pages and queries for at least three months.

• Export analytics landing pages and conversion paths for the same window.

• Capture backlinked URLs from a link tool or Search Console links report.

Also export titles, meta descriptions, canonicals, H1s, and any structured data on high-value pages. Flag service pages, city pages, and blog posts that already earn clicks or links.

A focused SEO audit is the cleanest way to run that baseline. For what belongs in a full review without restating the whole scope here, read what an SEO audit should include.

Keep the baseline file somewhere the launch team can open on day one. You will need it when Search Console starts showing 404s.

How should you build the redirect map?

Every important old URL needs a permanent path to the closest relevant new URL. Guessing later is how equity leaks.

• Map old URL to the closest equivalent new URL, not to a vague hub.

• Use server-side 301 or 308 redirects, never JavaScript-only redirects.

• Do not dump unmatched URLs onto the homepage.

• Avoid redirect chains and loops; point once to the final URL.

• Use 404 or 410 only when there is no useful replacement.

Here is a tiny example of the spreadsheet shape you want:

Test the map on staging with sample requests before launch. Confirm the response is a true redirect status, then a 200 on the destination.

Which staging and noindex traps wipe a launch?

Staging environments often block crawlers on purpose. That is correct for staging. It is a disaster if those controls reach production.

• Keep staging behind auth, IP allowlists, or noindex while you build.

• Write a launch checklist item that removes noindex, basic auth, and Disallow rules.

• Open robots.txt by hand on the live hostname after deploy.

• Confirm the live homepage and top service pages return 200 without a noindex header or meta tag.

• Keep URLs identical when the new platform allows it, so you need fewer redirects.

Also check that the CMS did not ship a default "discourage search engines" setting. That single checkbox has blanked more launches than most people admit.

What belongs on the launch-day checklist?

Treat launch as a controlled cutover, not a hope-and-refresh moment. Work the list in order.

1. Deploy the redirect map with the new site, not as a follow-up ticket.

2. Spot-check your top URLs: old path should 301 or 308, then the new URL should 200.

3. Confirm canonical tags on key pages point to the new live URLs.

4. Submit the new XML sitemap in Search Console.

5. For domain moves, verify both old and new properties and use Change of Address.

6. Confirm analytics, tag manager, call tracking, and conversion tags fire.

7. Update internal links you control, plus profiles and citations you own.

Have one person watching Search Console and server logs while another clicks through the money pages. Split ownership so nothing waits overnight without a check.

How do you monitor after launch?

The first two weeks catch missing redirects and blocked pages. Stay close to the data.

• Check Search Console coverage and 404 reports daily for about two weeks, then weekly.

• Compare clicks and impressions on key pages against your pre-move baseline.

• Fix missing redirects as soon as a valuable old URL appears as a soft 404 or 404.

• Keep redirects in place for at least a year. Google's guidance treats that as a minimum, not a stretch goal.

• If the domain changed, keep the old domain resolving with redirects rather than letting it expire early.

Expect temporary ranking fluctuation while Google recrawls and reprocesses URLs. Patience is part of the plan. Panic rewrites in week one make the signal harder to read.

If you need ongoing crawl and ranking care after the cutover, managed SEO services can fold migration aftercare into the broader program.

What mistakes wipe rankings during a move?

These patterns show up again and again on failed migrations. Avoid them on purpose.

Most of these mistakes are process gaps, not platform bugs. Assign an owner for redirects and an owner for Search Console before launch day.

When should you get migration SEO help?

Hire help when the URL map is large, the launch date is fixed, the CMS is new to your team, or nobody owns redirects and monitoring. A redesign with stable URLs is lighter. A domain move plus platform change is not.

AllureSEO handles technical SEO and website migrations as a focused engagement. Start on the website migration SEO page when you want a partner on the checklist above. For the wider hire-versus-in-house decision, see in-house SEO vs SEO agency.

Browse our case studies for how we approach technical and growth work for service businesses. Those examples are general SEO outcomes, not migration-specific promises.

FAQ

Do I need a redirect for every page?

You need a permanent redirect for every URL that still earns traffic, links, or rankings, and for any URL you want users to find again. Low-value or truly retired pages can return 404 or 410 when there is no relevant replacement. Do not mass-redirect leftovers to the homepage.

Will a redesign hurt SEO even if URLs stay the same?

It can, if staging noindex ships live, templates drop content, internal links break, or tracking and schema disappear. Same URLs reduce redirect risk, but you still need crawl checks, content parity, and a launch-day review of robots rules and canonicals.

How long until rankings settle after a site move?

Google says temporary ranking fluctuation is normal while URLs are recrawled and reprocessed. There is no fixed recovery clock. Larger URL changes take longer to settle than a same-URL redesign. Monitor Search Console and fix gaps rather than chasing a guaranteed date.

Should I change content and URLs at the same time?

Avoid it when you can. Changing URLs and rewriting copy together makes it hard to tell which change caused a ranking shift. Keep content parity through the move, then improve copy in a later sprint once redirects and indexing look healthy.

What is the difference between a 301 and a 302 in a migration?

A 301 or 308 signals a permanent move and is the right choice for migrations you intend to keep. A 302 signals a temporary redirect and can leave Google treating the old URL as the primary one. Use permanent redirects for site moves unless the change is truly short-term.

What if I keep the same URLs?

Same URLs simplify the move because you may not need a large redirect map. You still must clear staging noindex, confirm robots.txt, preserve titles and core content where possible, and verify analytics and canonicals on launch day. Treat it as a controlled cutover, not a free pass.

How long should redirects stay up?

Keep redirects for at least a year. Google's site-move guidance treats long-lived redirects as the safe baseline. Many teams keep them indefinitely while the old URLs still receive links or type-in traffic. Removing them early creates avoidable 404s.

Do I need Change of Address?

Use Google Search Console Change of Address when you move from one domain to another and both properties are verified. It is not a substitute for server-side redirects. For path-only changes on the same domain, focus on redirects, sitemaps, and monitoring instead.

Planning a redesign, domain move, or CMS change?

Talk to AllureSEO before the cutover, not after rankings slip. Bring your current URL list, Search Console access, and launch date. We will help you pressure-test redirects, staging controls, and monitoring. Reach us through our contact page, or call (718) 252-5040 or (212) 301-7615.