Web Development

Website Migration SEO Checklist: Redirects, Content, Tracking

The order of work that protects rankings when a site changes domain, platform or URL structure: record the old site, map every URL, test 301 redirects, keep tracking alive and watch the right reports afterwards.

Website Migration SEO Checklist: Redirects, Content, Tracking

Traffic lost in a site migration is almost always lost to the same few mistakes: old URLs with no redirect, a noindex tag carried over from staging, pages that were quietly dropped, and analytics that stopped recording on launch day so nobody noticed for a week. All of them are avoidable with a list and a fixed order of work.

This website migration SEO checklist is the sequence we follow when a site changes domain, platform, URL structure or design. Most of the work that protects rankings happens before anything goes live, so that is where it starts.

A website migration SEO checklist starts with the old site

Risk depends on what moves. A new host with the same URLs is low risk. A redesign that keeps its URLs is moderate, because content and internal links change. A new platform usually changes URL patterns, and a new domain changes every URL at once. Combine several of these in one launch and you will not know which change caused a drop, so separate them when the business allows.

Then capture the old site while it still exists:

  • Crawl it with a crawler such as Screaming Frog SEO Spider, and export every URL with its status code, title, meta description, h1 and canonical tag.
  • Collect the URLs a crawl cannot find: the XML sitemap, the pages listed in Search Console's Performance report, landing pages from analytics, and the most-linked pages from Search Console's Links report. Orphan pages with backlinks are the ones that get forgotten.
  • Record a baseline: clicks and impressions per page, rankings for the queries that bring business, and conversions per landing page. Without it, "traffic is down" cannot be measured.
  • Keep a full backup of files and database, so content can be recovered after the old site is gone.

Build the URL map

The URL map is a spreadsheet with one row per old URL: the old address, the new address and a note. It is the most important document in the project.

  • Map each page to its closest equivalent, one to one. An old service page goes to the new service page, not to the home page. Google's guidance on site moves says not to send many old URLs to one irrelevant destination such as the home page, which may be treated as a soft 404.
  • For content you are removing on purpose, redirect to the nearest relevant category if there is one. If nothing is relevant, let the URL return 404 or 410.
  • Include things that are not pages: PDFs, images that rank in image search, and old campaign landing pages that still receive clicks.
  • Decide the rules for variants once: http or https, www or not, trailing slash or not, upper and lower case.
  • Where old and new structures follow a pattern (/blog/2019/05/title becomes /blog/title/), one rule can cover thousands of rows. Spot-check the results anyway.
  • Sort the sheet by clicks and backlinks, and review the top rows by hand.

Write the 301 redirects and test them on staging

Use server-side permanent redirects (301 or 308). Google treats a permanent redirect as a signal that the new URL should replace the old one in search results, which a temporary 302 does not give. Where the rules live depends on the stack: the web server configuration, an .htaccess file, the application's router or a redirect plugin.

# Apache (.htaccess)
Redirect 301 /services/web-design.html /services/website-design/

# nginx
location = /services/web-design.html {
    return 301 /services/website-design/;
}

Send each old URL straight to its final address. A chain such as http to https to www to the new path wastes crawl effort and slows visitors down, so collapse it into one hop. Then test every row of the map against staging, not a sample. One line of curl shows the status and the destination:

curl -sI https://staging.example.com/services/web-design.html | grep -i -E "^(HTTP|location)"

Run that in a loop over the first column of the spreadsheet and compare each result with the second column. Fix anything that returns 404, 302 or more than one hop.

Carry the on-page signals across

A redirect delivers the visitor. What the new page says decides whether it keeps ranking. For each important URL, compare old and new:

  • title tag, meta description and h1;
  • the body copy itself, since redesigns often trim the text that was doing the ranking;
  • internal links, updated to point at the new URLs directly instead of passing through redirects;
  • a self-referencing rel="canonical" on every new page, pointing at the new address;
  • structured data such as product, FAQ, article and breadcrumb markup;
  • hreflang annotations on multilingual sites;
  • image file names and alt text.

Prepare a new XML sitemap that lists only the new, final URLs, and a robots.txt for production that is not a copy of the staging one.

Launch day, in order

  1. A few days ahead, lower the DNS TTL if the server is changing, so the switch takes effect quickly.
  2. Freeze content on the old site, so nothing is published after the final copy.
  3. Deploy the new site and switch DNS or the web root.
  4. Remove every staging block: password protection, noindex meta tags, an X-Robots-Tag header and Disallow: / in robots.txt. On WordPress, check that Settings > Reading > Discourage search engines from indexing this site is unticked.
  5. Run the redirect test script again, this time against production.
  6. Crawl the new site and look for 404s, redirect loops, pages marked noindex and canonicals that still point at the old or the staging domain.
  7. Submit the new sitemap in Search Console.
  8. If the domain changed, use Search Console's Change of Address tool. It is for moves between domains or subdomains, not for path changes or a switch to HTTPS.
  9. Update the links you control: Google Business Profile, ad destinations, social profiles and email templates.

Keep tracking continuous

If measurement breaks at launch, you lose the ability to see everything else on this list. Check on the live site, on the day:

  • the analytics tag or Tag Manager container fires on every template, including checkout and thank-you pages, and still reports into the same property as before, so the history stays comparable;
  • conversions still count. Google Analytics 4 calls them key events, and any that were defined by a page address, such as a thank-you URL, need updating if that address changed;
  • forms deliver, and their submissions appear in analytics and in the CRM;
  • both the old and the new site are verified in Search Console. For a domain move you need both properties, to watch one fall as the other rises;
  • the cookie consent banner still controls the tags it is supposed to control.

Write the launch date and time where the team will find it later, so a change in the charts can be tied to the migration.

What to watch after launch, and for how long

Check daily for the first two weeks, then weekly for a couple of months.

  • Search Console's Page indexing report. Rising counts of new URLs under "Not found (404)", "Soft 404" or a noindex reason mean something above was missed. "Page with redirect" for old URLs is expected.
  • Server logs or a 404 monitor. Every old URL that visitors or crawlers still request and that returns 404 is a missing row in the map. Add the redirect.
  • Clicks and rankings for the pages on your baseline list, compared page by page, old URL against new.
  • Crawl activity. Crawling tends to rise while Google works through the redirects, so make sure the server has room for it.

Some movement is normal. Google's documentation on site moves with URL changes says a small or medium site can take a few weeks for most pages to move, and larger sites longer. The same page advises keeping redirects for as long as possible, generally at least a year. Keep the old domain registered too, or the redirects stop working and someone else can buy it.

When a migration needs a specialist

A small brochure site moving to a new theme with the same URLs can be handled in-house with this checklist. Bring in people who have done it before when the site earns its revenue from organic search, when it has thousands of URLs or several languages, when a store's product and category URLs are changing, or when the domain, the platform and the design all change in one launch. A mistake there costs sales.

We plan and run these moves as part of our migration and modernization service, including WordPress migrations. If a new design is part of the project, read website redesign mistakes that cost traffic and leads first, and for stores, replatforming an online store without losing SEO or orders. A migration is also a good moment for performance optimization of slow templates.

Frequently asked questions

Will rankings drop after a website migration?

A short dip while search engines process the redirects is common, even when everything is done correctly. With complete one-to-one redirects and unchanged content, sites generally recover. A drop that keeps going instead of recovering usually points to missing redirects, removed content or an indexing block.

How long should 301 redirects stay in place?

As long as you can keep them. Google's guidance is generally at least a year, and there is little reason to remove them afterwards, because other sites and old bookmarks keep sending visitors to the old addresses for much longer.

Is it safe to change the domain, the platform and the design at once?

It can be done, and it is the riskiest combination, because any drop could come from three different causes. If the schedule allows, move the platform and design first while keeping the URLs and the domain, let that settle, and change the domain as a separate step.

Add WorldWin Coder to your preferred sources

Add worldwincoder.com as a preferred source on Google, or open this article in your AI assistant to use it as a source.

Swati Priyadrshni
· Founder & CEO at WorldWin Coder

I'm Swati Priyadarshani, Founder & CEO of LMS Advisor and Co-Founder of WorldWin Coder Pvt. Ltd. (est. 2019). Over the last 10+ years, I've helped enterprises build learning platforms that actually get used - not just deployed.

Keep reading

Have something to build, fix or move?

Tell us where you are. A developer reads every inquiry, and you get next steps and a free quote within one business day.