How to migrate a website to new hosting without losing SEO - Zephyra Studio

A site migration only causes a traffic drop when it is done without a plan. If page addresses stay the same, if old addresses redirect to new ones and if the switch does not coincide with a change of structure, Google barely registers that anything happened. The work has four stages: copying to the new server, testing before the DNS change, the switch itself with a lowered TTL, and then two to four weeks of monitoring. In practice one decision causes most of the trouble: changing hosting and addresses at the same time. When both happen together, any drop cannot be attributed to a single cause, so there is nothing to fix either.

What actually affects rankings during a migration

Google ranks an address and the content on it, not a server. If the address does not change and the content stays the same, a hosting switch is almost invisible to search. That is why a hosting migration and an address migration are treated as two separate jobs, with different risk and different duration.

The damage comes from redirects that loop, pages that return an error after the switch, and protection that gets switched off for a moment, sending Google hundreds of errors exactly when the most bots arrive. In practice all three happen on the same day when the switch is done without checking beforehand.

Speed is the second factor. New hosting can be faster or slower, and if the server responds noticeably slower that shows up in page experience data too. That is why speed is measured before and after, on the same page and the same device, rather than judged by feel.

Preparation before the switch

Preparation takes longer than the switch itself, and that is where most of the work happens. The goal is for the new server not to be discovered before it is fully ready.

• Take a full backup and verify that a restore actually runs, because a migration without a tested backup is gambling rather than migrating
• Copy both the database and the files, including every image and attachment, since the uploads directory is the thing most often forgotten
• If the domain changes, replace the old addresses in the database, taking care with serialised data on WordPress
• Put the site on the new server and open it through a temporary address or a local hosts file edit, without touching DNS yet
• Open the key pages, forms and, where relevant, the cart and checkout, and confirm they work and send mail
• Lower the TTL on the DNS records a day earlier, so the change propagates quickly
• Check that the SSL certificate is issued and the site opens without a warning

Switch day, step by step

The switch itself takes a few minutes and leaves little room for improvisation. Order matters, because every step has a check that is easy to skip in a hurry.

DNS is changed first, and traffic then flows to the new server gradually. That is why some visitors still reach the old one in the first hours, which is normal and does not mean something is wrong.

If the host is the same company, the change is often immediate, and then it matters more that the old server stayed available as a fallback. When moving to a different provider, the old account is not closed until everything is confirmed working, usually after a week or two.

The first weeks after the switch

The first check is technical and happens straight away: the site opens, forms submit, mail sends and receives, the cart works. The second check is in Search Console, where the indexation report shows whether new errors appear or pages that were indexed before drop out.

If the domain changed, a change of address is filed and the new sitemap is submitted. If only hosting changed there is nothing to file, because addresses stay the same, but the server error report is worth reading and the old sitemap should still be checked as reachable.

Monitoring lasts two to four weeks, which is how long the data needs to settle. If organic traffic drops by ten to fifteen per cent in that period and recovers, that is usually normal fluctuation. If the drop persists and the report shows errors, the cause is technical and is fixed by restoring redirects or correcting addresses rather than by waiting.

Sites that also changed platform are a different case, and there the old addresses are mapped to new ones in advance. That work is covered by our hosting migration and redesign service, and a temporary dip is expected, because the structure changes as well.

What gets forgotten and breaks later

Beyond the site, a number of services are tied to the domain that do not look like part of a migration until they stop working. Mail is the most important but not the only one: payment systems, campaign tools, accounting connections and services that accept requests only from a known address.

Such connections often have an allow list of addresses or a key tied to the domain. When the server changes, the service keeps working in one direction and stops in the other, and the problem surfaces only when a message or a payment fails to arrive.

On sites with several subdomains it pays to list them in advance and note what each is for. The one most often forgotten is a helper subdomain for an older version of the site or for a support tool, which then gets deleted along with the other records.

That is why a list is drawn up before migration, covering everything tied to the domain with a note of who is responsible for each item. The list takes ten minutes and shortens the search for a cause from hours to minutes if something stops working.

Source

Key takeaways

• Changing hosting without changing addresses barely affects rankings, provided the new server behaves correctly.
• A hosting migration and an address migration are never done at the same time, because the causes cannot be separated afterwards.
• A full copy and a tested restore are a condition, not an extra precaution.
• Test the site through a temporary address before touching DNS, and keep the old server available as a fallback.
• Watch indexation errors in Search Console for two to four weeks after the switch.

Conclusion

A migration is a job measured by the absence of problems, which makes it easy to underestimate. If addresses do not change and the new server was tested before the switch, rankings stay put, and the only real difference is speed, which is worth measuring. Moving to a new platform is more involved, because addresses are then mapped page by page, and that is the work our hosting migration service covers. If the move coincides with a redesign, run through our website launch checklist as well, because the same omissions tend to repeat.