Here’s how a redesign goes wrong. The new site launches. It looks great. Three weeks later the phone goes quiet. Someone checks Google, and the search results that used to send customers every day now point at pages that don’t exist. The old site had spent years earning those positions, and the new one threw them away on launch day without anyone noticing.
This happens constantly, and it’s almost entirely preventable. What follows is the process I use, built on Google’s own published guidance for moving a site.
Why redesigns lose rankings
Google doesn’t rank your website. It ranks individual pages, by their exact addresses. Everything a page has earned (links from other sites, years of being the answer to a particular search) is attached to that address. Redesigns lose rankings when:
- Addresses change and nothing points the old ones to the new ones. Google arrives at the old address, finds an error page, and eventually drops it. This is the big one.
- Pages get deleted or merged. The old site had a page for each service; the new one has a slick single page. Each of those old pages was ranking for something.
- The words change. A service page that ranked because it explained the service in 400 plain words gets rewritten as a 12-word slogan. Google no longer knows what it’s about.
- The new site is slower. Heavier theme, bigger images, more scripts. Speed is part of how Google judges pages.
- Something was left switched off. New sites are usually built on a hidden staging address that tells Google to stay away. If that setting ships with the live site, the whole thing vanishes from search.
Before you touch anything: take inventory
You can’t keep what you haven’t listed. Before the new site is designed, collect every address on the old one:
- Export the list. Your old sitemap, Google Search Console’s “Pages” report, and your analytics all list URLs. Google’s advice is to combine them, and to include images and documents, not just pages.
- Mark what matters. For each address, note whether it gets search traffic, which searches it shows up for (Search Console tells you), and whether other websites link to it.
- Decide each one’s fate: keep as is, move to a new address, merge into another page, or drop. “Drop” should be rare for anything in the first two groups.
This list becomes the redirect map, and it’s the single most important document in the project.
Keep the addresses where you can, redirect where you can’t
The simplest way not to lose rankings is not to change addresses. If the old site had /kitchen-remodeling, the new site can too. Where that’s not possible, each old address gets a permanent (301) redirect to its closest new equivalent. Google’s guidance is specific about how:
- One to one. The old kitchens page goes to the new kitchens page. Don’t send everything to the homepage; Google treats that as a soft error and the rankings don’t transfer.
- Direct. Old → new in one hop, not old → other old → new. Chains lose signal and slow things down.
- Permanent, and kept. Google says to leave redirects in place for at least a year so it can transfer everything over. In practice, leave them forever; they cost nothing.
- Merged pages redirect to the page that absorbed them. Dropped pages with no equivalent can return a proper “gone” response, but only after you’ve checked they weren’t earning anything.
Source: Google Search Central, Site moves with URL changes.
Keep what was working
Look at the pages that bring you search traffic and treat their text with respect. The page titles, the headings, and the paragraphs that explain what you do are what earned the ranking. You can make them read better, add to them, reorganise them. Don’t cut a 500-word page that ranks down to a headline and a stock photo because it “looks cleaner.” Clean and empty look the same to a visitor and very different to Google.
Make it faster, not slower
A redesign is the one moment you can fix speed properly, because everything’s being rebuilt anyway. It’s also the moment it most often gets worse, because the new theme is heavier and the new photos are bigger. Test the new site on pagespeed.web.dev before launch and compare it to the old one. If the new site scores lower, that’s a reason to delay. Here’s what usually causes it.
Launch day checklist
- Redirects live and tested. Open twenty old addresses from your list and confirm each lands on the right new page, in one hop.
- Nothing telling Google to stay away. No “noindex” tag, no blocking in robots.txt, no password left over from staging.
- Every page has a title, a description and a canonical address pointing at itself.
- New sitemap submitted in Search Console. Google suggests keeping the old one around for a while to watch the redirects get picked up.
- Internal links updated to the new addresses, so nothing on your own site goes through a redirect.
- Google Business Profile, social bios and email signatures point at the right addresses.
- Analytics and Search Console are connected to the new site and recording.
- HTTPS works and the old http:// and www versions all land on the one canonical address.
After launch: what to watch
Google says rankings can fluctuate while it re-crawls and re-indexes a moved site, and that for a medium-sized site this takes a few weeks or more. That’s normal. What you’re watching for is anything that doesn’t recover.
- Search Console → Pages, weekly for the first two months. Any “Not found (404)” entries for old addresses mean a redirect is missing. Add it.
- Search Console → Performance. Compare clicks for the month after launch to the month before. A dip that recovers is fine; a dip that doesn’t is a page that lost its text or its redirect.
- Your phone. If calls drop and nothing above explains it, check that the number on the new site is right. You’d be surprised.
If you’re also changing your domain
Moving from one domain to another (say, from an old name to your business name) adds one step. Everything above still applies, and you also tell Google about the move in Search Console with the “Change of address” tool. Google is clear this is only for domain changes; don’t use it for switching to HTTPS or dropping the www, which are handled by redirects alone. And keep the old domain registered and redirecting for years, not months; old business cards have long lives.
Every redesign I do starts with the inventory and ends with the redirect map being tested address by address before launch. It’s the least glamorous part of the project and the one that protects the thing you actually hired me for, which is the phone ringing. If your current developer hasn’t mentioned redirects, ask. It’s the question that separates people who build websites from people who build websites that keep working.
A redesign should change how your site looks, not whether Google can find it.
Want me to look at your site?
Send me the address and I’ll tell you what’s slowing it down, what it’s missing, and what I’d fix first. No charge, no pressure.