Rebuilding your website without losing your Google rankings

You have finally agreed to rebuild the website. The old one is slow, and it looks dated. Nobody on the team can change it without calling a developer. The new design looks far better.

Then the new site goes live, and the enquiries slow down. A few weeks later, someone checks Google. Pages that used to appear for your main services have gone. Visitors who click old links land on an error page.

This is one of the most common and expensive website mistakes. The old site may have taken years to earn its place in search results. A careless move can lose much of that in a day. Winning it back can take months, and during that time buyers are finding your competitors instead.

The good news is that this risk is well understood. With a clear plan, you can rebuild and keep your rankings.

Why rankings drop after a rebuild

Google does not rank "your website". It ranks individual pages. Each page has its own address, called a URL (for example, yoursite.co.uk/services/audit). Over time, Google learns which URLs answer which questions. Other websites link to those URLs too.

A rebuild often changes these addresses. Pages get new names, move into new sections, or disappear. To Google, the old page has simply vanished. The trust it built does not move to the new page on its own.

The main causes are usually these:

• Changed URLs with no redirects. Old addresses lead to a "page not found" error.
• Content removed or cut down. A detailed service page becomes three short lines.
• Lost page titles and descriptions. The text Google shows in results is left blank or made generic.
• Slower pages. Large images or heavy code make the new site slower than the old one.
• Pages hidden from Google by mistake. A test setting that blocks search engines is left switched on at launch.

None of these are hard to avoid. They happen because nobody owned the job.

What a redirect is, and why it matters most

A redirect is an instruction on your website. It says: "This page has moved. Go here instead." The permanent version is called a 301 redirect.

When a visitor or Google asks for an old URL, the redirect sends them to the right new page. Most of the trust the old page earned moves across with it. Old links in emails, brochures and other websites keep working.

The key word is right. Sending every old page to the homepage is a common shortcut. It is better than an error, but not by much. Someone looking for your pricing page does not want the homepage. Google treats this kind of redirect as weak too.

Each important old page should point to the single new page that best matches it.

Start with a content map

A content map is a simple list of every page on the old site and where it will live on the new one. It is the most useful document in any rebuild. It can be a spreadsheet.

To build it, you need a full list of current pages. Your developer can produce this with a crawl, which is a tool that visits every page on your site, like Google does. Add data from Google Search Console, the free tool that shows which pages get search traffic.

Then sort the pages into three groups:

1. Keep. Pages that get traffic, have links from other sites, or matter to buyers.
2. Merge. Thin or overlapping pages that are better combined into one stronger page.
3. Remove. Out-of-date pages with no traffic and no value. These still need a redirect to the closest relevant page.

This step also helps the new site. It forces a useful question: which pages actually help a buyer decide? That is how we approach every bespoke website build, with structure and content agreed before design.

Options and trade-offs

Not every rebuild carries the same risk. The choice is often between keeping your URL structure and changing it.

Keep the same URLs where you can. This is the safest option. Fewer redirects mean fewer chances to get it wrong. It works well if your current structure is already clear.

Change the structure. Sometimes the old structure is the problem. Pages may be buried, badly named, or organised around your team instead of your buyers. A better structure can help both visitors and search in the long run. The cost is more planning, more redirects and more checking.

Change the domain as well. Moving to a new web address, for example after a rebrand, adds another layer of risk. It can be done well, but it needs extra steps, such as telling Google about the move in Search Console.

A short dip in traffic for a few weeks after a large change is fairly normal while Google re-reads the site. A deep, lasting drop is not. That usually points to a missed step.

A practical launch checklist

The rebuild is not finished when the design is signed off. Most ranking losses happen in the days around launch. Before and after go-live, someone should check these items:

• Before launch: every row in the content map has a redirect set up and tested.
• Before launch: page titles, descriptions and headings are in place for every key page.
• Before launch: structured data is added. This is hidden code that tells search engines and AI tools what a page is about, such as a service, an article or your business address.
• Before launch: pages are fast on a mobile phone, with images in modern, compressed formats.
• At launch: the setting that blocks search engines on the test site is switched off.
• At launch: a new sitemap, a file that lists all your pages for search engines, is sent to Google Search Console.
• After launch: crawl the live site to find broken links and missing redirects.
• After launch: check Search Console weekly for errors and changes in traffic for at least the first two months.

Keep a record of rankings and traffic for your main pages before launch. Without it, you cannot tell whether anything changed.

If you also run paid ads or other campaigns, tell whoever manages them about the new URLs. Ad links that point to old pages waste budget. Our sister practice handles digital marketing if you need support there.

Who should own this

The biggest risk is that everyone assumes someone else is handling it. The designer focuses on looks. The developer focuses on the build. Your marketing team assumes search is covered.

Before the project starts, ask your web partner direct questions:

• Who builds the content map, and when will I see it?
• How will you test the redirects before launch?
• What will you check in the first weeks after go-live?
• What happens if traffic drops?

Clear answers to these questions are a good sign. Vague answers are a warning.

Your next step

Before you brief anyone on a new design, export a list of your current pages and see which ones bring in traffic and enquiries. That list is the foundation of a safe rebuild. If you would like a second opinion on your plan, talk to us.