How to Redesign a Website Without Losing Google Rankings
By Mike Evan — Founder, Social Media Strategy HQ•Updated October 2026
Keep every page that earns traffic or links, and keep what made it rank: its words, its title and the links pointing to it. Redirect each retired address one-to-one with a permanent redirect, never to the homepage. Check search blocks, canonicals and tracking on launch day, then watch Search Console for six weeks.
Most business owners hear about this risk from the wrong direction: a new site launches, it looks far better than the old one, and three weeks later the phone is quieter and nobody can say why. This guide is for the owner who is about to sign a redesign and wants to keep the search traffic they already have. If you are still deciding whether to rebuild at all, start with the signs you need a new website. If you want to know what a redesign should cost, including the migration line, that is in what a website redesign costs. This piece is about the move itself.
A Redirect Moves the Address, Not the Reasons It Ranked
The standard advice for a redesign is one sentence long: set up 301 redirects. It is correct and badly incomplete. A redirect tells search engines that the page which used to live at one address now lives at another. It says nothing about whether the page that lives there now is the same page.
A page ranks because of what is at the address, not because of the address. If the old service page had nine hundred words explaining exactly who you serve and how, and the new design replaced it with a hero image and three short bullet points, the redirect works perfectly and the ranking still disappears. Search engines followed the redirect, found a thinner page, and ranked it accordingly. That is the single most common way a carefully redirected site still loses its traffic, and it is the one a redirect checklist never catches.
The five things every URL carries
It helps to think of each ranking page as a container holding five things, all of which have to survive the move.
The address itself, with every link other websites have pointed at it over the years. Redirects protect this, and only this. The words — the specific language that matches what people search, which designers often trim because it looks long in a mockup. Its place in the site — how many internal links point to it and how close it sits to the homepage; a page that drops from the main menu to a footer link has been demoted. Its labels — the page title, the description, the headings and any structured data. And the promises other systems made about it: your Google Business Profile link, the final URLs in your ad campaigns, links in old emails, QR codes on printed materials, directory listings, and the citations AI assistants have already recorded.
A redesign that protects all five rarely loses anything. A redesign that protects only the first one is a gamble.
Four Kinds of Move, and Why You Should Not Stack Them
“Redesign” covers four quite different changes, each with its own risk. A domain change moves everything to a new name. A platform change moves the site to a different system, which almost always changes how addresses are formed. A structure change reorganizes pages and renames addresses. A content and design change rewrites what is on the pages while leaving the addresses alone.
Doing one of these is routine. Doing all four in a single launch is where most serious losses happen, and not only because more can break. When traffic drops after a four-way move, nobody can tell which change caused it, so the fix becomes guesswork. Where you can, separate them. Keep the existing addresses on the new platform, even if a few of them are not as tidy as you would like. Change the domain on its own, before or after the redesign rather than during it. If everything has to happen at once for business reasons, accept that the monitoring after launch needs to be much more careful.
If the move involves leaving a platform or a vendor you do not fully control, check what you actually own before planning anything. The details are in do I own my website; you cannot redirect addresses on a domain you cannot log into.
Want it done for you?
Websites, SEO, and AEO — built with Claude Code in days, not months.
Get a Custom QuoteBefore Anything Changes: The Snapshot
The pages that matter are rarely the ones in your navigation. They are an old blog post that still brings in a dozen enquiries a year, a PDF price sheet another site linked to in 2019, a location page nobody on staff remembers creating. A redesign planned from the sitemap the designer can see will miss them. So the first job is a snapshot of what the current site actually does, taken from four sources.
Search, links, conversions and a full crawl
From Google Search Console, export every page that received clicks over the longest period available, with the queries each one is found for. From a backlink tool, list every page that other websites link to, even pages with no search traffic. From your analytics, list the pages where enquiries, calls and bookings actually start. Then crawl the whole site, including PDFs and images, so that you have every address that exists, not just every address someone remembers.
Combine those four lists into one spreadsheet. Every address on it gets a decision: keep as is, keep and improve, merge into another page, or retire. Most small-business sites have far fewer pages that matter than the owner fears and far more than the designer assumed. If you are rethinking which pages the new site needs at all, how many pages a small-business website needs covers how to decide, and its rule applies here: merge before you delete.
Write the before numbers down
Record weekly search clicks, the number of indexed pages, and weekly enquiries for the two months before launch. Without a baseline, a launch-week dip and a real loss look identical, and you will not know which one you are looking at until the quiet phone tells you.
The Redirect Map, Done Properly
Every address in the snapshot that will not exist on the new site needs a destination, and the destination has to be the single page that best answers the same question. Four rules cover most of what goes wrong.
One to one, not many to homepage. Pointing dozens of retired pages at the homepage looks tidy and tells search engines the content is gone. Permanent, not temporary. A 301 says the page has moved for good; a temporary redirect, which some platforms use by default, says it might come back. No chains. If an address was already redirected in a previous redesign, point the oldest address straight to the final one rather than hopping through the middle. Keep them. Google’s own guidance is at least a year; our advice is indefinitely, because old links, printed materials and AI citations keep sending people to old addresses long after anyone remembers them.
Then do the part that is usually forgotten: update the links you control so they point to the new addresses directly. Your internal links, your Google Business Profile, your ad destinations, your email templates and your main directory listings. A redirect is a safety net, not a substitute for correcting the source.
Launch Day: The One-Hour Check
Most redesign disasters are not caused by strategy. They are caused by a setting that was correct on the test site and wrong on the live one. In the first hour after launch, check these on the live site, not the staging copy.
The robots file is not blocking the whole site, and no page carries a leftover noindex tag — test sites are supposed to be hidden from search, and that setting travels to production far more often than anyone admits. Canonical tags point to the live domain, not the staging address. A sample of twenty old addresses from the snapshot each land on the right new page in a single hop. The new sitemap lists only live, final addresses and has been submitted in Search Console. Every form sends, and the enquiry arrives where it should. And analytics and conversion tracking are firing.
That last one deserves emphasis. A launch that breaks tracking at the same moment it breaks something else is the worst possible combination: you lose traffic and lose the ability to see that you lost it. Speed belongs on this list too, because a new site that loads slower than the old one gives back ground on every page; why is my website so slow explains what to look for.
The Six Weeks After: What Normal Looks Like
Some movement after a redesign is normal. Search engines re-crawl the site, re-read the redirects, and re-evaluate pages that changed. On a small site that was moved carefully, positions typically wobble for a couple of weeks and then settle around where they were, or a little better if the new site is faster and more clearly organized.
The signs that something is wrong are different and specific. A rising count of not-found errors in Search Console means the redirect map missed addresses. Pages from the snapshot dropping out of the index means something is blocking them or they now look duplicated. A single page, usually the homepage, starting to appear for searches that used to land on a specific service page means that service page lost its words or its links. And enquiries falling while traffic holds steady means the new design is converting worse, which is a design problem rather than a search one — my website gets traffic but no leads covers that case.
Check weekly against the before numbers for six weeks. Problems found in week one usually cost an afternoon to fix. Problems found in month four have usually cost a season of enquiries.
The Reader You Forgot: AI Assistants
Search engines are no longer the only systems that have learned your old site. AI assistants that recommend local businesses have also recorded your services, your service area, your hours and, sometimes, specific pages. Two things protect that during a redesign. First, the redirects above, because those systems also follow old links. Second, and less obvious, keep your basic business facts identical at launch. A redesign is a tempting moment to rename services, rewrite the service area or describe the business differently, and every one of those changes creates a mismatch between your site and the directories and reviews that describe you. As we found in what AI assistants actually cite, an assistant faced with conflicting facts tends to pass over the business rather than guess. If the facts need to change, change them everywhere in the same week. That consistency work is part of what we cover under answer engine optimization.
Five Questions to Ask Whoever Builds It
You do not have to do any of this yourself, but you should know whether your vendor will. Ask these before signing. Where will the list of existing pages come from — the menu, or Search Console, backlinks, analytics and a crawl? Will I see the redirect map before launch, and who signs it off? Which of the four kinds of move are we making, and can any be separated? What exactly is checked in the first hour after launch? And who watches Search Console for the six weeks after, and what happens if something drops?
A vendor who answers all five clearly has done this before. A vendor who says “we will set up redirects” and nothing more is describing the first of five things a page carries. When we rebuild a site under AI website building, the snapshot, the map and the six-week watch are part of the build, priced as their own line, and handled with our SEO services team rather than left to the designer. Because we build with Claude Code, the production work is fast, which leaves more of the project’s time for this part — the part that decides whether the new site keeps the customers the old one was already bringing in.