Migrating Your Website to a New Provider - Without Losing Rankings

Switching to a new provider or platform is the moment when many SMBs lose their Google rankings - often without noticing right away. The damage only becomes apparent weeks later, when the enquiries dry up. The good news: a clean migration is a craft, not a matter of luck. If the key steps are followed, your rankings stay stable. We run seven of our own brands in production and have carried out migrations often enough ourselves to know where things really get tricky.

Why a migration can cost you rankings

Google ties your rankings not to your hosting, but to your URLs. A migration becomes dangerous the moment those URLs change - for example because the new system forces a different structure. /leistungen/sanierung then turns into /services?id=42, and the search engine loses the connection between old and new. This is exactly where the loss happens:

• Changed URL structure without redirects - old Google results lead nowhere (404).
• Forgotten redirects for individual sub-pages that brought in traffic but went unnoticed because they weren't in the menu.
• Lost content - texts get trimmed or pages disappear that used to rank for a keyword.
• Technical pitfalls - an accidentally set noindex directive or a blocking robots.txt carried over from the test environment that goes live.

If your new provider keeps the same URLs and carries over the same content, the risk is low. The moment anything changes about addresses or content, you need a plan.

The migration checklist

Work through these points in order. The list covers the cases that most often go wrong in practice.

Before the migration

• Capture all old URLs. Export the list from Google Search Console and supplement it with a crawl of the existing site. That way no one overlooks an important sub-page.
• Identify your top pages. Which pages bring in clicks and enquiries? These take priority - nothing here is allowed to get lost.
• Back up your content. Document texts, images, meta titles and meta descriptions in full, so they can be carried over one to one.
• Full backup of the old site. Files and database, in case a rollback becomes necessary.

During the migration

• Keep your URLs wherever possible. The safest migration is the one where no address changes. Demand this from your new provider explicitly.
• Set up 301 redirects for every URL that does change after all. A 301 is a permanent redirect and passes the ranking on to the new address - a 302 doesn't do that reliably.
• Redirect one to one, not everything blanket-style to the homepage. Google treats a catch-all redirect to / practically like a 404 and throws away every ranking.
• Test against the new environment before it goes live: on a staging domain protected from Google by a password or noindex.

On go-live day

• Remove noindex. Check that no page is accidentally set to noindex and that the robots.txt allows crawling. This is the most common avoidable total failure.
• Test the redirects. Open a few of your most important old URLs - they have to land on the correct new page without any detour.
• Check HTTPS and the domain. All variants (with and without www, http and https) must point cleanly to one target version.
• Generate a new sitemap.xml and submit it in Search Console.

After the migration

• Monitor Search Console. Check coverage in the first few weeks: are 404 errors rising? Are excluded pages suddenly showing up?
• Update internal links so they point directly to the new URLs instead of running through redirect chains.
• Be patient. A brief fluctuation in rankings during the first one to two weeks is normal, as long as the redirects are in place. Only after that is it worth drawing conclusions.

When you don't need to worry

Not every migration is a risk. If only the hosting changes, the domain stays the same and all URLs and content are carried over unchanged, nothing usually happens. Google barely notices a pure server switch. It only gets critical when the technology and the structure change at the same time - that is, with a genuine relaunch. That's when you need the full checklist.

What to look for in a new provider

A reputable service provider raises the topic on their own initiative instead of staying quiet about it. Ask specifically before you place the order:

• Will the existing URLs be carried over - and if not, is there a 301 redirect for each one?
• Will the site be tested on a protected staging environment before go-live?
• Is there a backup of the old site and a rollback plan in case something goes wrong?
• Who submits the new sitemap and keeps an eye on Search Console after the migration?

If a provider can answer these questions clearly, there's a high chance your migration will go through without any loss of rankings. A migration is no black magic - but it needs someone who takes the inconspicuous details seriously, because that is exactly where rankings get lost.