Website migration SEO

Website migration SEO checklist

Move a site, change its URLs or switch platforms without losing Google traffic: what to do before launch, on launch day and in the weeks after, with redirect checks for large listing sites.

Explore the live demo →

5 days free · no card needed · ends on its own

Updated

A website migration SEO checklist is the set of checks that keeps your Google traffic when a site changes its URLs, domain, platform or structure. The core of it: list every URL that earns search traffic, map each one to its new URL, put permanent (301 or 308) redirects live on launch day, check every redirect in bulk, then compare traffic by page type with your pre-launch numbers for the next few weeks.

Google’s own guide to site moves with URL changes sets the expectation: a small to medium-sized website can take a few weeks for most pages to move, larger sites take longer, and rankings fluctuate in the meantime. A dip in the first weeks is normal. A dip that stays is almost always a redirect, indexing or content problem you can find and fix.

Short version: benchmark by page type before you touch anything, map URLs by pattern (not one by one), use one-hop 301s to the matching page, never send old URLs to the home page, keep redirects for at least a year, and check the redirects of every URL that had Search Console traffic, not just a sample.

Which kind of migration is this?

“Migration” covers several different changes. They share the redirect work, but they carry different risks, and only one needs Google’s Change of Address tool.

ChangeExampleChange of Address tool?What usually goes wrong
Domain changeolddirectory.com → newdirectory.comYes, for each verified variant of the old domainDeep pages left without redirects; old domain allowed to expire
HTTPS or www switchhttp:// → https://NoInternal links and canonicals still point at the old version
New URL structure/austin/plumbers → /plumbers/austin-txNoPatterns nobody mapped; chains through older redirects
Platform or CMS changeCustom build → WordPress with a directory pluginOnly if the domain changes tooNew URL patterns, missing fields, a staging noindex left on
Redesign or consolidationMerging thin city pages into metro pagesNoContent and internal links removed along with the old design

Source: Google’s Change of Address tool help, which says to use the tool when moving from one domain or subdomain to another, and not for HTTPS switches or path changes within a site.

Before launch

1. Benchmark by page type

Record what you have now, split the way your site is built: clicks, impressions and position for listings, city pages, category pages, category × city pages and guides, plus how much of each Google has indexed. After launch you compare each line with its own baseline. A site-wide total hides a 40% loss on one template behind a gain on another.

Save the top pages by clicks and by impressions for at least the last 3 months, and keep a copy: Search Console only keeps 16 months, and the old URLs’ history is what tells you later whether the new ones caught up.

2. Build the full list of old URLs

Google suggests compiling old URLs from your sitemaps, your most-trafficked pages, your CMS, server logs and Search Console’s Links report, including images, videos, JavaScript and CSS. On a directory add two more sources: every URL with impressions in Search Console (city and category pages that rank on page three still matter), and expired or merged listings that still get links.

3. Map URLs by pattern, then handle the exceptions

A directory with 40,000 URLs does not need 40,000 hand-written rows. It needs one rule per page type, plus a short list of exceptions. Write the rules first, run every old URL through them, and look at what falls out.

Page typeOld patternNew pattern
Category × city/{city}/{category}/{category}/{city}-{state}
City/city/{city}/{state}/{city}
Listing/listing.php?id={id}/listing/{business-slug}
Category/category/{category}/{category}

Exceptions are where migrations leak traffic: cities with the same name in different states (Springfield), categories renamed or merged, listings whose slug changed, and anything with a query string. Every URL that had search traffic needs a target you have looked at.

4. Decide what will not move

Not every old URL needs a redirect. For content you are dropping, Google says the URLs should return a 404 or 410 on the new site. What it warns against is the lazy middle ground: “Don’t redirect many old URLs to one irrelevant single URL destination, such as the home page of the new site.” Redirect when a real equivalent exists; otherwise let the URL go. See which 404s to leave alone.

5. Prepare and crawl the new site on staging

6. Pick the timing and the size

Launch in a quiet traffic period. Google suggests large sites can move in sections; on a directory that can mean moving one state or one category first, checking it, then moving the rest.

Launch day

  1. Turn on the redirects. Server-side, permanent (301 or 308), straight to the final URL. Google advises “no more than 3 and fewer than 5” redirects in a chain; one hop is the target.
  2. Remove staging blocks. The noindex tags, the robots.txt disallow and the password. Leftover noindex and robots.txt blocks are on Google’s list of common migration mistakes. See where a noindex can hide.
  3. Check every old URL that had traffic. Not a sample. More on bulk checks below.
  4. Inspect a few pages of each type with the URL Inspection tool live test: indexable, canonical correct, content rendered.
  5. Submit sitemaps. Google’s guide says to submit both the new-URL sitemap and the old-URL one you saved while mapping, so Google crawls the old URLs and sees the redirects. Remove the old one later.
  6. Domain change only: submit the Change of Address in Search Console for the old property, for every verified variant. You need to be an owner of both properties, with a 301 from the old home page to the new one.

After launch

First week

Weeks 2 to 6

Months 2 to 12

The website migration SEO checklist, in one table

PhaseTaskHow to check it
BeforeBenchmark clicks, impressions and indexed share by page typeSaved export or report per template
BeforeFull old-URL list, including every URL with impressionsCount matches sitemap + Search Console + CMS
BeforePattern rules for each page type, exceptions listedEvery old URL with traffic has a target
BeforeDropped content returns 404 or 410, not the home pageNo redirect targets the home page
BeforeStaging crawled and compared with the live siteTitles, content and internal links match or improve
BeforeSelf-referencing canonicals; internal links to new URLsCrawl shows no internal links to redirects
BeforeNew site verified in Search Console; analytics liveBoth properties visible, data arriving
Launch301 or 308 redirects, one hopBulk check: status, hops, target
LaunchStaging noindex, robots.txt block and password removedLive test in URL Inspection
LaunchOld and new sitemaps submittedSearch Console Sitemaps report
LaunchChange of Address (domain changes only)Search Console confirms the move
AfterErrors and 404s in the first weekCrawl stats, server logs
AfterTraffic by page type against the baselineEach template within normal swing of its baseline
AfterOld URLs fading from results, new ones indexedImpressions shift from old to new URLs
AfterRedirects kept for at least a yearCalendar reminder; old domain renewed

Migrating a directory or listing site

Directories migrate differently from brochure sites because almost every URL is generated. That makes mapping easier (patterns) and mistakes bigger (one wrong rule breaks 3,000 pages).

How to check redirects in bulk

A bulk redirect check takes the list of old URLs and, for each, follows every hop and records the status codes and the final URL. Then you compare the final URL with your map. Free browser-based bulk redirect checkers handle a few hundred URLs; a desktop crawler in list mode handles more. For a quick check from the command line:

while read url; do
  curl -s -o /dev/null -L -w "%{http_code} %{num_redirects} %{url_effective} $url\n" "$url"
done < old-urls.txt

Each line shows the final status, the number of redirects and where the URL ended up. Then look for:

The list you check matters more than the tool. Check every old URL that had clicks or impressions in Search Console before launch, sorted by that traffic, so the problems that cost the most come first.

How DirectoryLens checks a URL change

In DirectoryLens, URL changes (under Advanced) runs this check for you after go-live. You give it a name, the go-live date and, optionally, a CSV of old URL to new URL (up to 2,000 rows). It takes your top 100, 250 or 500 pages by Google visits in the 28 days before go-live, plus every mapped URL, and visits each one as DirectoryLensBot at one request a second, following redirects hop by hop and reading the noindex and canonical on the page it lands on. URLs your robots.txt blocks are reported, not fetched.

Two limits, honestly. The check starts once the change is live; before launch, use the page type reports for your baseline and URL list. And it is built for URL changes within one site, including HTTPS and www switches: on a move to a new domain it flags the redirects as leaving the site rather than following them, so check a domain move with a crawler as well. You can try the reports on the live demo.

Questions

What is a website migration in SEO?

Any change that alters how Google finds and indexes your pages: a new domain, a switch to HTTPS, a new URL structure, a new platform or a large redesign. The SEO work is keeping each old URL’s traffic by redirecting it to its new equivalent.

How long does it take Google to process a site migration?

Google says a small to medium-sized site can take a few weeks for most pages to move, and larger sites take longer. Expect rankings to fluctuate during that time.

How long should I keep 301 redirects after a migration?

Google advises keeping them as long as possible, generally at least one year. After a domain change, keep the old domain registered so the redirects keep working.

Do I need the Change of Address tool?

Only when moving from one domain or subdomain to another. Google says not to use it for HTTPS switches, www changes or path changes within the same site.

Should I redirect old URLs to the home page?

No. Google warns against redirecting many old URLs to one irrelevant page such as the home page. Redirect to the matching new page, or return 404 or 410 if there is none.

How do I check redirects in bulk?

Run your list of old URLs through a bulk redirect checker, a crawler in list mode or a curl loop, and record each URL’s status, hops and final URL. Check every URL that had Search Console traffic, not a sample.

Will I lose traffic after a website migration?

Some temporary fluctuation is normal while Google recrawls. A loss that lasts more than a few weeks usually points to missing or wrong redirects, pages Google hasn’t indexed, or content that changed in the move.

Check your next URL change against real traffic.

Connect Search Console, and DirectoryLens checks the redirects of the pages that earned your visits, by page type.

Explore the live demo →

5 days free · no card needed · ends on its own