Website migration
Website Migration Checklist: Keep Your SEO When You Move
Updated 7 November 2026·10 min read·MeraSEO, Mumbai
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.
The risk depends on what changes. Use this table to judge how much care the move needs.
| Type of move | What changes | Main SEO risk |
|---|---|---|
| New host, same platform and URLs | Server, IP address, sometimes speed | Downtime, broken SSL, slower response, lost email records |
| New platform (CMS or store) | URL patterns, templates, metadata, schema | Changed URLs, missing titles and canonicals, dropped content |
| New domain or rebrand | Every URL on the site | Rankings can fluctuate while Google processes the move; backlinks still point to the old domain |
| HTTP to HTTPS, or www to non-www | Protocol or hostname | Redirect 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.
Do this before anyone touches the new site. Save everything in a spreadsheet and keep a copy outside the site itself.
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.
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.
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.
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:
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.
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.
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.
| What goes wrong | Why it happens | Prevention |
|---|---|---|
| Whole site drops out of Google | Staging noindex or robots block left on at launch | Launch checklist item, checked in the first hour |
| Rankings fall on key pages | Titles, headings or body copy rewritten during the move | Carry content across unchanged first, then improve later |
| Enquiries stop | Form email, SMTP settings or tags not moved | Test every form and tag on launch day |
| Email stops arriving | MX records overwritten during DNS change | Export the DNS zone before changing anything |
| Backlink value wasted | Linked URLs return 404 or redirect to homepage | Check 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.
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.
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.
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.
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.
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 →WhatsApp us