Website migration

Website Migration Checklist: Keep Your SEO When You Move

Website Migration Checklist: Keep Your SEO When You Move: MeraSEO article cover
Key takeaways
  • Most SEO loss in a migration comes from URLs that change without a 301 redirect, so build a URL map before anything else.
  • Take a full inventory first: every URL, its traffic and rankings, backlinks, forms and tracking tags. You cannot check what you did not record.
  • Test on a staging site that search engines cannot index, then remove the block at launch. Forgetting that block is a classic mistake.
  • After cutover, watch Search Console and server logs daily for two weeks and keep the old host running until DNS has fully settled.

A migration is any change that moves your site: a new host, a new platform (say, a custom PHP site to WordPress, or WooCommerce to Shopify), a new domain, or a switch from HTTP to HTTPS. The site can look identical afterwards and still lose most of its search traffic, because Google ranks URLs, not designs. If an address that ranked yesterday returns an error or lands on the wrong page today, the ranking goes with it.

This checklist walks through the work in the order it should happen: inventory, URL mapping, staging, cutover, and the first two weeks after launch. It is about moving a site safely. It is not a design brief or a routine maintenance list, and we link to those separately where they help.

Know which kind of migration you are doing

The risk depends on what changes. Use this table to judge how much care the move needs.

Type of moveWhat changesMain SEO risk
New host, same platform and URLsServer, IP address, sometimes speedDowntime, broken SSL, slower response, lost email records
New platform (CMS or store)URL patterns, templates, metadata, schemaChanged URLs, missing titles and canonicals, dropped content
New domain or rebrandEvery URL on the siteRankings can fluctuate while Google processes the move; backlinks still point to the old domain
HTTP to HTTPS, or www to non-wwwProtocol or hostnameRedirect chains, mixed content, duplicate versions of the site

A host change with identical URLs is the lowest risk. A domain change combined with a new platform is the highest, and we advise doing them as separate moves when the timeline allows.

Step 1: Build the pre-migration inventory

Do this before anyone touches the new site. Save everything in a spreadsheet and keep a copy outside the site itself.

  1. Crawl the live site. Export every indexable URL with its status code, title, H1, canonical and word count. A desktop crawler works for small sites; a site with thousands of URLs also needs the sitemap and server logs, because crawlers miss orphan pages.
  2. Pull performance data. From Search Console, export clicks, impressions and average position by page and by query for the last 12 months. From GA4, export sessions and key events by landing page. The pages that earn the traffic and enquiries get the most careful treatment.
  3. Export backlinks. List the pages that other sites link to. These are the URLs that must redirect correctly or you waste links you earned.
  4. List functional pieces. Contact and enquiry forms, WhatsApp buttons, payment gateways (Razorpay, PayU), GST invoice settings, login areas, third-party embeds and every tracking tag (GA4, Google Ads, Meta pixel).
  5. Record the technical setup. Current DNS records including MX and SPF for email, SSL certificate details, redirect rules in .htaccess or nginx, robots.txt and the XML sitemap location.
  6. Take a full backup of files and database, and confirm you can restore it.

On sites we host, the backup step also catches a common problem: old database dumps and backup archives sitting inside the public web folder. Do not copy those to the new server. Leave them out of the migration and keep backups in a private location.

Step 2: Map every old URL to a new one

This is the step that decides whether the migration is safe. Create three columns: old URL, new URL, redirect type. Every old URL that had traffic, links or a ranking gets a row.

Rules for the redirect map

  • Use 301 (permanent) redirects. A 302 tells search engines the move is temporary.
  • Send each old URL to the closest equivalent page, not to the homepage. Google can treat a redirect to an unrelated page, such as the homepage, as a soft 404, so the old page’s value is lost.
  • Redirect straight to the final URL. Avoid chains such as http to https to www to a new path, since each hop adds delay and risk.
  • If a page has no equivalent, let it return 404 or 410 rather than redirecting to something unrelated.
  • Keep the redirects in place for at least a year. Backlinks and bookmarks keep arriving long after launch.

A frequent trap on WordPress sites: WordPress automatically redirects a renamed post slug, but it does not do the same for a renamed page slug. If your migration or cleanup renames pages, add each 301 yourself in .htaccess or a redirect tool, and test it.

Worked example. Moving from a custom PHP site to WordPress, the old address /services.php?id=4 becomes /seo-services/. The map row is: old /services.php?id=4, new /seo-services/, type 301. Query-string URLs need rules that match the parameter, so test them explicitly. If you are changing platform, our migration and upgrade services include this mapping as a standard step.

Step 3: Prepare and test on staging

Build or copy the site to a staging address and block it from search engines with a password (HTTP authentication is more reliable than a robots.txt rule or a noindex tag alone). Then check:

  • Titles, meta descriptions, H1s, canonical tags and structured data match the inventory, page for page.
  • Internal links point to final URLs, not to the staging hostname.
  • Forms deliver email, the WhatsApp button opens the right number, and a test payment completes.
  • Mobile layout and speed. Compare the staging site’s Core Web Vitals against the live site; a “good” Largest Contentful Paint is 2.5 seconds or less. Our technical SEO work covers this in depth.
  • Your redirect map, run as a script against every old URL, reports the expected final URL and status code.

Write down what to remove at launch: the password, any “noindex” setting in the CMS (WordPress has a “discourage search engines” checkbox that is easy to leave ticked), and staging-specific robots rules.

Step 4: Cutover day

  1. Lower DNS TTL to a few minutes a day or two before (at least as long as the current TTL), so the switch spreads quickly and can be reversed.
  2. Choose a quiet window for your traffic, often late night in India for a domestic business. Avoid campaign launches and sale days.
  3. Freeze content and orders on the old site, then take a final backup and copy the latest database to the new server.
  4. Install the SSL certificate on the new host before pointing DNS, so visitors never see a certificate warning.
  5. Update DNS and keep the old server running. Different networks see the change at different times.
  6. Preserve email records. Copy MX, SPF, DKIM and DMARC records exactly. Email silently stopping is a common side effect of a host move.
  7. Switch on the redirects and remove the staging password and noindex setting.

If your site sits behind a CDN, remember it may keep serving an old copy for a while. On Hostinger, the CDN can serve a cached version of a page for up to 10 minutes after a change, so test with a cache-busting query string such as ?v=2 or wait before deciding something is broken.

Step 5: Post-launch checks in the first two weeks

First hour

  • Open the homepage, five top landing pages and one old URL from the map in a private browser window.
  • Check robots.txt allows crawling, and the page source has no stray noindex.
  • Submit a test enquiry and check that it arrives. Confirm GA4 and Google Ads tags fire. Note that a conversion tag loaded through Google Tag Manager will not appear in the raw HTML, so check with Tag Assistant or the gtm.js request before assuming it is missing.
  • Submit the new XML sitemap in Search Console.

First two weeks

  • Watch the Pages report in Search Console for new “Not found (404)” and “Page with redirect” entries, and the Crawl stats report for server errors.
  • Re-crawl the new site and compare it to the inventory: any URL that had traffic and now returns 404 gets a redirect.
  • Compare clicks and impressions for your top 20 pages with the 12-month export. Small dips for a week or two are normal; a steady fall on specific pages points to a missing redirect or changed content.
  • For a domain change, use the Change of Address tool in Search Console on the old property. Google documents the full process in its Search Central documentation.
  • Ask the owners of your best backlinks to update their links to the new URL where it is easy to do so.

After a domain change, keep the old domain registered and redirecting for at least a year, and longer if it has strong backlinks. Renewing it is cheap compared with losing the redirects. After a host change, cancel the old server only once DNS has settled and its access logs show no more visitors.

Common losses and how to avoid them

What goes wrongWhy it happensPrevention
Whole site drops out of GoogleStaging noindex or robots block left on at launchLaunch checklist item, checked in the first hour
Rankings fall on key pagesTitles, headings or body copy rewritten during the moveCarry content across unchanged first, then improve later
Enquiries stopForm email, SMTP settings or tags not movedTest every form and tag on launch day
Email stops arrivingMX records overwritten during DNS changeExport the DNS zone before changing anything
Backlink value wastedLinked URLs return 404 or redirect to homepageCheck the backlink export against the redirect map

Once the site is stable, move it onto a routine; our website maintenance checklist covers the recurring tasks, and the technical SEO checklist covers crawling, indexing and schema. If the migration is part of a larger visual overhaul, read about our website redesign approach too.

Frequently asked questions

Will changing my web host affect SEO?

Only if something breaks. Moving to a new host with the same URLs and content should not change rankings. The risks are downtime, a slower server, an expired or missing SSL certificate, and lost email DNS records. Keep the old server running until DNS has settled, and compare page speed before and after.

How long does it take to recover rankings after a migration?

It depends on the type of move and how clean the redirects are. A host change with identical URLs often shows no visible dip. A platform or domain change can take weeks for Google to reprocess every URL. If a specific page keeps falling after a few weeks, look for a missing redirect or changed content.

Should I use 301 or 302 redirects when moving a site?

Use 301 for a permanent move, which is what a migration is. A 302 signals a temporary change, so search engines may keep the old URL in the index. Redirect each old URL to its closest equivalent on the new site rather than sending everything to the homepage, and avoid chains of multiple redirects.

Do I need to tell Google when I change domains?

Yes, for a domain change use the Change of Address tool in Search Console, after the 301 redirects are live. Add and verify both the old and new properties first. The tool does not replace redirects; it works alongside them. For a host change or HTTPS switch, no notification is needed.

Planning a move to a new host, platform or domain?

We handle the inventory, redirect map, staging tests and cutover, then monitor Search Console after launch so traffic and enquiries keep flowing.

Talk to us about migration →

Related Post

Call Now Button