A new website should bring in more enquiries, not fewer. Yet many businesses launch a rebuild and watch their Google traffic drop within days. Usually the design isn't to blame. Old page addresses vanish, content gets cut, and Google can't connect the old site to the new one.
Google itself says that for medium-sized websites, "it can take a few weeks or more for Google to gradually start showing the new URLs" after a site move (Google Search Central). Some movement is normal. A lasting drop usually isn't. It's mostly avoidable with planning.
This guide walks through what to do before, during and after a rebuild to protect the rankings you've already earned. It's written for business owners working with a web designer or agency, so you'll know what to ask for and what to check.
Key takeaways
- Most ranking losses come from missing redirects. Google recommends "server side permanent redirects from the old URLs to the new URLs" (Google Search Central). Every old page that earns traffic or links needs one.
- Map before you build. Google says "It's important to map your old site's URLs to the URLs for the new site." Start with a list of every page that gets visits, rankings or links.
- Keep the content that ranks. Cutting or merging well-ranked pages removes the very text Google was ranking. Improve those pages; don't delete them.
- Expect some movement, then recovery. Google says it "can take a few weeks or more" for medium-sized sites to settle. Keep redirects "generally at least 1 year".
- Don't change everything at once. Google advises: "Plan your changes to your site one after the other, not everything at the same time." A new design, new domain and new content in one go makes problems hard to trace.
Why do websites lose rankings after a rebuild?
Most drops happen because Google can't match old pages to new ones. When an old address returns "page not found", the rankings and links it built up have nowhere to go. Google says permanent redirects tell it "that the redirect target should be canonical" (Google Search Central). Without them, Google treats the new pages as new.
The most common causes are:
- Changed page addresses with no redirects.
/family-law-servicesbecomes/services/family-law, and the old address simply breaks. - Content cut in the redesign. A long, detailed service page is trimmed to three lines because it "looks cleaner".
- Pages left out. Old blog posts or location pages that quietly brought in traffic aren't moved across.
- The new site is blocked from Google. Settings that hid the site while it was being built are left on at launch.
- Titles and descriptions lost. Page titles that were carefully written get replaced with defaults like "Home" or "Services".
- A slower site. Heavy new images, animations or scripts make pages slower than before.
None of these are design problems. They're planning problems, which is why the work before the build matters most.
What should you do before the rebuild starts?
Start by recording what the current site does well. Google's advice for site moves begins with preparation: "It's important to map your old site's URLs to the URLs for the new site" (Google Search Central). You can't map what you haven't listed.
1. List every page that matters
Export every page address on your current site. Then mark the ones that matter most:
- Pages that get visits from Google (Search Console, Performance report, Pages tab)
- Pages that bring enquiries (Google Analytics, if your forms are tracked)
- Pages other websites link to
- Pages listed in your Google Business Profile or ads
Your web designer can crawl the site to get the full list. Ask for it in a spreadsheet you can keep.
2. Record your starting numbers
Save a snapshot of how the site performs now, so you can compare after launch. At a minimum, record:
- Clicks and impressions from Google Search Console for the last 3 and 12 months
- Your top 20 search terms and the pages that rank for them
- Monthly enquiries from the website
- Page speed results for your main pages
Without these numbers, you won't know whether a dip after launch is normal or a problem.
3. Map old addresses to new ones
Build a simple table that pairs every old page with its new home. This becomes the redirect list. Each old page should point to the closest matching new page, not just the homepage.
| Old address | New address | Action |
|---|---|---|
| /family-law-services | /services/family-law | 301 redirect |
| /about-us | /about | 301 redirect |
| /blog/old-post-name | /blog/old-post-name | Keep the same address |
| /special-offer-2023 | /contact | 301 redirect (closest match) |
| /old-test-page | none | Let it return 404 (no traffic, no links) |
Where you can, keep the same addresses. A page that doesn't move doesn't need a redirect, and carries no risk.
4. Decide what changes, and what doesn't
Google advises: "Plan your changes to your site one after the other, not everything at the same time" (Google Search Central). A new design, new platform, new domain and new content all at once makes it very hard to find what went wrong.
If you're also changing your domain name, consider doing that as a separate step. And if you're choosing a new platform, our WordPress or Next.js guide compares the two most common options.
What should happen during the build?
While the new site is being built, keep it out of Google and keep the good content in. Google notes that "some site owners block all crawling while in development" and advises making a list of anything that needs noindex removed at launch (Google Search Central). Forgetting that list is one of the easiest ways to vanish from Google.
Keep the test site hidden, the right way
Your designer will build the new site on a test (staging) address. Ask them to password-protect it, or add a noindex rule so Google doesn't show it in search. Don't rely on robots.txt alone: Google warns that for noindex to work, "the page or resource must not be blocked by a robots.txt file" (Google Search Central).
Carry over the content that ranks
Your top pages rank because of what's on them. Keep their main text, headings and answers, and improve them rather than starting again. If the new design has less room, find a layout that fits the content, not the other way round.
Also carry over each page's title and description. Google's guidance is to write "descriptive and concise" titles that are distinct for each page (Google Search Central).
Update internal links and canonical tags
Google says to "Change the internal links on the new site from the old URLs to the new URLs", and that each new page should have a self-referencing canonical tag (Google Search Central). In plain English, the new site should link to its own new addresses, not lean on redirects.
Check speed before launch
A rebuild is a chance to make the site faster, but it can easily go the other way. Test the main pages on the staging site with PageSpeed Insights. Google's Core Web Vitals call for the main content to load "within 2.5 seconds" (web.dev).
What should you check on launch day?
Launch day is when redirects go live and Google starts to see the new site. Google recommends "server side permanent redirects from the old URLs to the new URLs" (Google Search Central). It treats 301 and 308 redirects as permanent, and 302 and 307 as temporary (Google Search Central).
Use this checklist on the day:
- Redirects are live. Test 20 or so old addresses from your map, especially the top pages. Each should go straight to the right new page in one step, using a 301.
- The site isn't blocked. Remove
noindextags and password protection, and check robots.txt doesn't block the whole site. - Titles and descriptions are in place on every main page.
- Forms and phone links work. Send a test enquiry from your phone.
- Tracking works. Google Analytics and any ad tracking are recording visits and enquiries.
- New sitemap submitted. Google says to "Submit the new sitemap in Search Console".
- Google Business Profile updated if any page addresses it links to have changed.
- Change of Address tool used, only if the domain changed. Google says to use it when "moving from one domain or subdomain to another". It isn't needed for a redesign on the same domain.
What should you watch after launch?
Watch Google Search Console closely for the first few weeks. Google says that for medium-sized websites, "it can take a few weeks or more for Google to gradually start showing the new URLs" (Google Search Central). Small ups and downs in that time are normal. Steady falls on important pages aren't.
Week 1: catch broken pages fast
- Check Search Console's Page indexing report for new "Not found (404)" errors and fix them with redirects.
- Test your top 20 pages from the old site again.
- Make sure enquiries are still arriving.
Weeks 2 to 6: watch the trend
- Compare clicks and impressions with the starting numbers you saved.
- Check your top search terms. Are the new pages ranking where the old ones did?
- Google says to expect "a drop in indexed URL counts on the old site" as the new site's pages are indexed. That's a good sign.
Months 2 to 12: keep the redirects
Google recommends you "Keep the redirects for as long as possible, generally at least 1 year" (Google Search Central). Don't let a later update or a hosting change quietly remove them. Ask whoever looks after the site to keep the redirect list on file.
What if rankings drop and don't come back?
Go back to the starting numbers and find which pages lost traffic. Then check each one: is the old address redirecting to the right page, did the content survive the move, and is the new page indexed? Most lasting drops trace back to one of those three. Fix them page by page, starting with the pages that brought the most enquiries.
If you'd like a second pair of eyes, our SEO services include checking a site after a rebuild.
Frequently asked questions
It can, for better or worse. If old addresses redirect properly and your best content carries over, rankings usually settle within weeks. Google says medium-sized sites can take "a few weeks or more" to show new URLs. Missing redirects and cut content are what cause lasting drops.
For a well-planned rebuild, most sites settle within a few weeks. Google says it "can take a few weeks or more" for medium-sized websites. If important pages are still down after two months, check their redirects, content and indexing in Search Console rather than waiting longer.
Yes, for any page whose address changes. Google recommends "server side permanent redirects from the old URLs to the new URLs" for site moves. Keeping the same domain helps, but a page that moves from /about-us to /about still needs a redirect. Pages that keep their address don't.
Google says to keep them "for as long as possible, generally at least 1 year". In practice, there's little reason to remove them at all. Old links from other websites, emails and bookmarks keep working, and the redirect list is small to maintain.
No. Redirect each old page to the closest matching new page. Sending everything to the homepage confuses visitors and gives Google no clear replacement. Google says to map old URLs "to the URLs for the new site" one by one. Pages with no traffic or links can simply return a 404.
Planning a rebuild?
A website rebuild doesn't have to cost you rankings. List the pages that matter, map every old address to a new one, keep the content that ranks, and check redirects on launch day. Then watch Search Console for the first few weeks and keep the redirects for at least a year.
We plan rebuilds so the new site keeps what the old one earned, and we hand you the redirect map and starting numbers so you can see it for yourself. See how we approach website design and development, or read what a small business website costs before you budget. Talk to us about your project.