How to move an old website to a new one without losing your Google rankings

The most dangerous moment in a website's life isn't the day you decide to rebuild it. It's the morning after the new one goes live, when someone searches Google for exactly what you sell, clicks the old result and lands on a blank page that says "404 — page not found." The customer doesn't know you relaunched. All they see is that you're not there anymore, so they move on to the next name on the list.

The redesign decision is about when: when your design has fallen behind, when it no longer looks right on a phone, when you want a different structure. Migration is a completely different problem, and it's about how: how you move content from the old addresses to the new ones without Google and your customers losing you along the way. The first is a business decision. The second is a technical moment where, if you get it wrong, you vanish from the results in the very week you meant to look better.

Why a new site can cut off your customers overnight

Google doesn't index "your website." It indexes each address (URL) individually: the services page, the blog article that brings half your visits, the contact page. Each one has built up a reputation over years — that's why it shows up where it does.

When you build a new site, the addresses almost always change. `site.com/haircut-services.html` becomes `site.com/services`. The old structure Google knew simply no longer exists. If you tell no one where each page moved to, three things happen at once:

• Customers who have the old address in a bookmark or a link get a 404 and leave.
• Google finds dead addresses where it used to have valuable pages and, over time, drops them from the results.
• The reputation each page built (the links others gave it, its history) doesn't transfer on its own to the new address.

This is where the 301 redirect comes in.

What a 301 redirect is, in plain terms

A 301 redirect is a "I've moved for good" note the server hands to anyone who asks for the old address. When a customer or Google requests `site.com/haircut-services.html`, the server answers: "this page has permanently moved to `site.com/services`" and sends them straight there. No blank page, no lost click.

The detail that matters: "301" means permanent. Unlike a temporary redirect (302), a 301 tells Google to carry the reputation over from the old address to the new one. In practice you move not just the visitor but the trust the page had built. That's why a proper 301 is the difference between a migration nobody notices and one after which the phone goes quiet for two months.

The redirect map: the piece most people skip

Before you publish anything new, you need a list of every old address and the new address that replaces it. Not the "important pages" — all of them. Here's how:

• Pull the full list of old addresses. From Google Search Console (the indexed-pages report) and from a crawl of the site. This surfaces pages you'd forgotten but that Google still sends people to.
• Put the new address next to each one. One-to-one: each old page goes to its new equivalent, not all of them to the homepage.
• Flag what disappears entirely. A page deleted with no logical replacement should be redirected to the nearest category, not to a 404.

The classic mistake is "just send them all to the homepage." It's convenient and it's wrong: Google treats a wholesale redirect to the front page almost like a 404, and the customer who was looking for one specific thing ends up frustrated on the homepage, starting over. Each address goes to the page that actually continues what was there.

The launch checklist (order matters)

The order you do the steps in matters as much as the steps themselves. The rule we work by: nothing public until the redirects are ready and tested.

Step 4 is the one almost everyone skips and the one that saves the migration. Take ten real old addresses, paste them into a browser, and check each one lands on the correct new page — not the homepage, not a 404.

What doesn't move on its own (and must be checked)

Redirects handle the addresses, but a few things need separate attention after launch:

• The SSL certificate — the new site must start straight on `https`, not `http`. A missing padlock scares off the customer and Google alike.
• Google Business Profile and social links — if the link in your profile pointed to a specific old address, update it. This matters especially for your Google profile and for customers who find you locally.
• Search Console — submit the new sitemap and watch the coverage report for a few weeks. This is where you see in black and white whether Google understood the move.
• Speed — if the reason for the redesign was a slow site, check on a phone that the new one really does load fast. Otherwise you changed the clothes, not the problem.

A small, short dip in traffic in the first two or three weeks is normal: Google needs time to reindex. A slump that lasts for months is not normal — it's the sign of an incomplete redirect map.

When a redesign is a good idea anyway

Migration sounds technical, but it's no reason to keep postponing a site that's holding your business back. If the current one doesn't work on a phone, loads slowly or looks like it's from ten years ago, the cost of keeping it is higher than the care of a move done right. On whether a new site is worth it at all we wrote separately in why I need a website, and on the money in how much a website costs. What to take from this article: the redesign is the decision, the 301 redirects are the execution, and customers only get lost when you skip the second part.

With us, migration comes included in the project, not as a surprise on the invoice: we prepare the address map, switch on the redirects at the move, and watch the errors for a month after launch. Prices start at €290 for a landing page and €490 for a presentation site, with maintenance from €29/month if you'd rather never think about the technical side again.

Let's look at your old site together

The simplest thing is to show us what you have now. Message us on WhatsApp, we'll look at the old site and build you — for free — a sample of a new page, so you can see how it would look before you decide anything. Message us on WhatsApp and we'll start from your real site, not from a promise.