How to rebuild a website without losing the search traffic you have
The short version
The short version. You keep your search traffic through a rebuild by treating it as a move, not a fresh start. Before the build, list every page that earns visits and links. During the build, map each old URL to one new URL with a single permanent redirect, keep the titles, content, internal links and structured data that work, and keep the staging site out of the index. On launch day, remove the staging blocks, switch on the redirects and submit the new sitemap. Then watch Search Console for several weeks and fix what it reports.
In this piece8 sections
- The short version
- Why does a rebuild put search traffic at risk?
- What should you record before the rebuild starts?
- How do you map every old URL to a new one?
- Which parts of the old site should you keep as they are?
- How do you test the new site on staging without it being indexed?
- What should you check on launch day?
- What should you watch in Search Console after launch?
- Before you brief the rebuild
- Five things to keep
- Questions we hear often
You rebuild a website without losing search traffic by treating the rebuild as a move, not a fresh start. Before the build, list every page that earns visits, links and enquiries. During the build, give each old URL one new home with a single permanent redirect, keep the titles, content, internal links and structured data that already work, and keep the staging site out of search. On launch day, remove the staging blocks, switch on the redirects and submit the new sitemap. Then watch Search Console for several weeks and fix what it reports.
If you have already weighed whether to modernise your current site or rebuild it and chosen to rebuild, this is the next question. The design is the part everyone talks about. The search traffic you keep depends on the parts nobody sees.
Why does a rebuild put search traffic at risk?
Google has spent months or years learning which of your pages answer which questions. A rebuild changes the things it learned from: the addresses, the wording, the headings, the links between pages and the code underneath. When those change all at once, Google has to work it out again.
Some of that relearning is normal. Google's own guide to site moves with URL changes (opens in a new tab) says to expect rankings to fluctuate while it recrawls and reindexes, and that a small or medium site can take a few weeks for most pages to move. The losses that last come from something else. A page that brought in enquiries is dropped because nobody knew it mattered. An old address leads to an error page. A setting that hid the staging site is copied to the live one. Each of these is avoidable, and each is easier to prevent than to repair.
What should you record before the rebuild starts?
Start with an inventory of what the current site already earns. You cannot protect what you have not written down.
- Every URL on the site. Take them from your sitemap, a crawl of the site and your analytics, because each one finds pages the others miss.
- The pages that bring in visits. From Search Console, note the pages with the most clicks and impressions over the last year, and the queries behind them.
- The pages that bring in enquiries. A page with modest traffic that produces calls is worth more than a busy page that produces none.
- The pages other sites link to. Search Console lists your most linked pages. Those links are hard to earn again.
- What each important page says. Save its title, its main heading, its copy and its structured data, so the new version can be checked against it.
Keep a dated copy of these numbers. After launch, they are the baseline you compare against. A technical SEO audit at this stage also shows problems worth fixing in the rebuild rather than carrying across.
How do you map every old URL to a new one?
Once you know what exists, decide where each page goes. Every old URL needs one of three outcomes: it stays at the same address, it moves to a new address that covers the same thing, or it is retired with a reason. Pages that move get a permanent redirect, a 301 or 308, from the old address to the new one.
Two rules keep the map honest. First, send each old page to the closest match, not to the home page. A redirect to an unrelated page tells visitors and Google very little. Second, redirect straight to the final address. Google advises against chains of redirects (opens in a new tab) and recommends going to the destination directly, so if an old page already redirects somewhere, point it at the new address in one step.
A redirect map is just a table. Here is how part of one might look for a service business:
| Old URL | New URL | Action | Why |
|---|---|---|---|
| /services.html | /services/ | 301 | Same page, new address format |
| /our-team/ | /about/ | 301 | Team content merged into About |
| /seo-services-dubai/ | /services/seo/dubai/ | 301 | Same topic, new structure |
| /blog/2019/opening-offer/ | none | Retire, 410 | Expired offer, no links or traffic |
| /contact/ | /contact/ | Keep | Address unchanged, no redirect needed |
Fill one row for every URL in the inventory, not only the important ones. The quiet pages are the ones that end up forgotten. Keep the redirects for as long as you can. Google says generally at least a year, and old links from other sites keep arriving long after that.
Which parts of the old site should you keep as they are?
Keep what earns its place. A rebuild is a good time to improve a site, but the pages that already rank are the wrong place to experiment on launch day.
- Titles and main headings on pages that rank, unless you have a clear reason to change them.
- The content itself. If a page answers a question well enough to rank, carry the substance across. Tighten it later, once the move has settled.
- Internal links. The links between your own pages tell Google which pages matter most. Rebuild them on the new site and point them at the new addresses, not at the old ones through a redirect.
- Structured data. If the old pages describe your business, services or questions with schema markup, make sure the new templates output the same, updated with the new URLs.
- Canonical tags and language tags. Each new page should point its canonical tag at itself. If you serve India, the UAE and the UK with separate pages, update the hreflang tags to the new addresses too.
The new site should also be at least as fast and stable as the old one. A redesign that adds heavy images and scripts can undo good work, so test its Core Web Vitals before launch, not after.
How do you test the new site on staging without it being indexed?
Build and review the new site on a staging address that search engines cannot reach. If staging is indexed, Google can find two copies of your site and the wrong one can appear in results.
A password on the staging site is the most reliable way to keep it private. A robots.txt block on its own is weaker than it looks. Google's guidance on blocking indexing with noindex (opens in a new tab) explains that a page blocked by robots.txt cannot have its noindex rule read, and can still appear in results if other pages link to it. If you use noindex on staging, keep a written list of every place it is set.
Use staging to test the redirect map before launch. Run every old URL from the table against the staging site and confirm each one lands on its new address in a single step, with the right status code. Fix the rows that fail while it is still cheap to do so.
What should you check on launch day?
Launch day is when most avoidable mistakes happen, because the settings that protected staging are still in place. Work through a short list, in order, and tick each item off with the person who made the change.
- Remove the staging password, every noindex rule and any robots.txt block that was only there for staging.
- Check the live robots.txt allows the pages you want found.
- Switch on the redirects and test a sample of old URLs, including your most visited and most linked pages.
- Confirm canonical tags on the live site point at the live addresses.
- Check that structured data on key pages is valid with the new URLs.
- Submit the new sitemap in Search Console. Google suggests keeping a sitemap of the old URLs as well, so you can watch them drop out of the index.
- Update links you control elsewhere: your Google Business Profile, social profiles, email signatures and directory listings.
- Make sure analytics and conversion tracking are firing on the new pages and forms.
- Submit a test enquiry through every form and confirm it arrives.
What should you watch in Search Console after launch?
Expect some movement for the first few weeks. What matters is the direction, measured against the baseline you saved before the rebuild.
In the first days, look at the page indexing report for errors on pages that should work, and at the sitemaps report. The number of indexed pages in the new sitemap should rise while the old one falls. Check the pages that had the most clicks before launch and confirm they, or their new addresses, still appear.
Over the following weeks, compare clicks and impressions for your most important pages and queries against the same period before launch. A page that has dropped sharply is worth inspecting: check its redirect, its content against the version you saved, and whether it is indexed at all. Search Console will also report old URLs that now redirect, which is expected during a move.
Keep the redirect map open throughout. Most fixes after launch are a missing or wrong row in that table.
Before you brief the rebuild
Put the inventory and the redirect map into the brief, so they are part of the job from the start and not a task added the week before launch. Whoever builds the site should know which pages earn your traffic, where each one is going and who checks the redirects on launch day.
If you would like a second pair of eyes on that plan, see our search and visibility and website services, or book a call and bring your current site.
Five things to keep
- A rebuild is a site move. Plan it as one before anyone designs a page.
- Start from the pages that already earn visits, links and enquiries.
- Every old URL gets one new home and one permanent redirect, with no chains.
- Keep staging out of search, and remove every block on launch day.
- Expect some movement for a few weeks. Read Search Console, not the mood in the room.
Built on Intent studio. A founder-led studio in India that plans and builds websites, search and AI visibility, and AI systems for businesses in India, the UAE and the UK. Reviewed by Srikar, founder. We do not publish invented numbers; where a figure appears, its source is named in the sentence.
How the studio works
