What Happens to Your Rankings When You Rebuild

Rebuilds have a bad reputation for losing traffic, and it is earned. It is also entirely avoidable, and the avoiding happens before launch rather than after.

What actually causes the loss

Not the new design. Not the new content. Addresses that stop working.

Every page on your current site has an address. Some of those have rankings, some have links pointing at them from other sites, some are in somebody's bookmarks or on a quote from two years ago.

If the new site puts that content at a different address and nothing connects the two, all of it is gone. The page returns an error, the ranking goes, the link points at nothing.

Google's own guidance on moving a site with URL changes is clear that mapping is the job. Everything else is detail.

Before you start

Get the full list of what exists now. Not what the menu shows, everything. Your sitemap, Search Console's page report, an analytics export of every page that received a visit in the last year. Combine them and de-duplicate.

This routinely turns up pages nobody remembered: an old service, a landing page from a campaign, a blog post that quietly earns a trickle of traffic every month.

Mark which ones matter. Sort by traffic and by links. The top twenty pages usually account for most of it, and those are the ones that must not break.

Decide the destination for every single one. Same content at a new address, merged into something broader, or genuinely retired. Every old address needs a row in that list.

What the map actually looks like

A spreadsheet, four columns, and it is the single most valuable document in the whole project.

Old address	Visits last year	New address	Why
/services/blocked-drains	410	/drain-unblocking	Renamed
/services/drains-christchurch	95	/drain-unblocking	Merged, same job
/special-offer-2023	4	/contact	Campaign finished
/about-us/our-team	60	/about	Merged

Build it before anybody designs anything. It tells you how many pages the new site actually needs, which is usually a different number to the one in the quote, and it means nobody is making these decisions at eleven at night on launch day.

At launch

Redirect permanently. A 301 tells Google the move is permanent and passes on most of what the old page earned. A temporary redirect says come back and check, which is not what you mean.

Point each page at its closest equivalent. Not all of them at the home page. Bulk-redirecting everything to the home page is treated as if the pages were deleted, and it loses the thing you were protecting.

Avoid chains. Old page to interim page to final page loses a little at each hop and is easy to create accidentally when a site has been rebuilt twice. Point the original straight at the destination.

Keep the sitemap honest. Submit the new one. Do not leave the old addresses in it.

Do not change the domain at the same time unless you have to. One variable at a time is easier to diagnose when something goes wrong.

After launch

Check the redirects actually fire. Take the top twenty old addresses and open each one. This takes ten minutes and catches the ones that were typed wrong, which there are always a few of.

Watch Search Console for errors. The coverage report will show pages returning errors that it expected to find. That list is your snagging list.

Expect a wobble. Even a clean migration usually dips for a few weeks while Google recrawls and reprocesses. This is normal and it is also the reason people panic and start changing things, which makes it worse.

Know what is not normal. A drop still there after two months is a fault, not settling. Go back to the mapping.

Keep the redirects forever

A redirect is not a temporary bridge you remove once things settle.

Links on other sites do not get updated. The supplier who listed you in 2019 is not going to rewrite their page. A redirect that has been in place three years is still doing work, and removing it during the next rebuild is how businesses lose the same traffic twice.

Carry the old map forward into every future rebuild. It only grows.

The thing that bites small businesses

The old site is often already gone. A host lapsed, a developer disappeared, somebody rebuilt in a hurry eighteen months ago and nobody thought about it.

You can still fix a lot of this retrospectively. Search Console keeps months of history, and the Internet Archive usually has a record of what the old addresses were. Map them, redirect them, and some of what was lost comes back.

It is a worse position than doing it properly, and it is not hopeless.

Why this is not optional

A rebuild that loses your rankings has cost you both the build and the traffic, and the traffic took years. It is the most expensive avoidable mistake in this trade.

It is also why mapping old addresses to new ones is a standard part of anything I build rather than a line item. Not doing it is not a cheaper option, it is just a bill that arrives later.