Website redesign SEO: how to keep your rankings
Website redesign SEO in 5 steps: the inventory, redirect map, copy check and launch day tests that keep your Google rankings and enquiries through a rebuild.
On this page
- Why do websites lose rankings after a redesign?
- Step 1: take an inventory before anyone opens a design tool
- Step 2: decide what happens to every single address
- Step 3: keep what each page was ranking for
- Step 4: don’t let the build change the plumbing by accident
- Step 5: check everything on launch day
- What a good redesign looks like to Google
- A short checklist for your next redesign
- Keep your enquiries coming through the redesign
Most businesses redesign because the site looks old. Nobody redesigns because they want to lose half their enquiries. Yet without a website redesign SEO plan, the second thing happens to the first group more often than anyone likes to admit. And it almost always happens for the same handful of reasons.
Rankings drop after a redesign when something the search engine relied on quietly disappears. It might be an address, a page, a paragraph, a heading or a link. Protect those and a new site can hold its rankings through launch and build on them. Ignore them and the new site starts again from nothing, however good it looks.
Why do websites lose rankings after a redesign?
Websites lose rankings after a redesign because search engines rank each page at its own address. When a page that earned traffic disappears, moves without a redirect, or comes back with thinner copy, its rankings go with it. Technical slips at launch, such as a leftover noindex tag, can wipe out the rest.
Search engines don’t rank websites. They rank pages, for the queries each page has proven it answers. Your old site’s traffic isn’t spread evenly. It’s concentrated. On many small business sites, a handful of pages bring in most of the search visits. Those pages are often the ones nobody in the business thinks about. It might be a blog post from 4 years ago, or a suburb page nobody has touched since it went live. It might be a service page with an awkward heading that happens to match what people type.
That concentration is the whole problem. A redesign brief is written from the business’s point of view: new brand, new navigation, fewer pages, cleaner structure. The search engine sees it differently. It cares about the page that used to answer a query. Does it still exist at an address the search engine can find? Does it still answer the query as well as it did?
So the first job of any redesign is finding out which pages are carrying the business. Design comes after.
Step 1: take an inventory before anyone opens a design tool
Before a single layout is drawn, pull 3 lists:
- Every URL the current site has, from a crawl and from the sitemap, including the ones that aren’t in the menu.
- Every URL that has earned search traffic over the last 12 to 16 months, from Google Search Console. A year or more matters, because plenty of businesses are seasonal.
- Every URL other websites link to, from a backlink tool or Search Console’s links report. Those links are votes, and a vote for a page that no longer exists is a vote thrown away.
Put them in one spreadsheet and sort by clicks. The top of that sheet is the part of the site the redesign isn’t allowed to break. We run this as the first step of every migration SEO project, because every later decision depends on it.
Step 2: decide what happens to every single address
Each row in the inventory gets one of 3 outcomes:
- Keep. The page stays at the same address. This is the safest outcome and should be the default for anything that earns traffic.
- Move. The page’s content lives on at a new address, and the old one sends a permanent (301) redirect to it. One old address, one new address, as close a match in topic as possible.
- Retire. The page has no replacement. It either redirects to the closest parent page or returns a 410, so the search engine stops asking for it.
Whatever happens, don’t redirect everything to the homepage. It’s the most common shortcut in a rushed launch. Search engines treat it much the same as a missing page, because a homepage doesn’t answer the question the old page answered.
Build the redirect map into the plan from the start, alongside the sitemap for the new site. It’s a content decision, so it can’t wait for the last day.
Step 3: keep what each page was ranking for
Compare the new copy with the old page before sign-off. The main heading should still name what people search for. The questions the old page answered should still be answered. Internal links pointing at the page should still exist. The title and meta description should be rewritten on purpose, rather than deleted. A thinner page usually ranks lower.
A page can keep its address and still lose its position, because the new version says less. This is the redesign trap nobody sees coming. A designer trims a long service page into 3 short blocks and a hero. The copy gets “tightened”. The heading that matched the search query becomes a brand line. The FAQs at the bottom disappear because they looked cluttered.
Every one of those changes removes something the page was being ranked for. Before the new copy is approved, compare it with the old page and check:
- The main heading still names the thing people search for, in words they use.
- The questions and details the old page answered are still answered, even if they’re better organised.
- Internal links that pointed at the page from elsewhere on the site still exist, or have been replaced.
- The page title and meta description have been rewritten on purpose, and nothing was simply deleted.
A better page is fine. A thinner page is a demotion you asked for.
Step 4: don’t let the build change the plumbing by accident
Some ranking losses have nothing to do with content. They come from the new site’s technical setup. They’re easy to miss because the site looks perfect in a browser. The ones we see most:
- The staging site’s “do not index” setting goes live with it. Every page carries an instruction telling search engines to drop it. Traffic falls off a cliff within days, and nobody notices until the phone stops ringing.
- Canonical tags point at the staging domain. They tell search engines the main version of every page lives somewhere else.
- Content moves behind JavaScript that search engines render slowly or partially. A page that used to be plain text now looks empty on first crawl.
- Page speed gets worse. Bigger images, heavier fonts and a stack of new scripts can push a page from passing Core Web Vitals to failing them.
None of these are hard to prevent. They just need someone to check, on the live site, the day it launches. A technical SEO review before launch catches most of them. A crawl of the live site in the first hour catches the rest.
Step 5: check everything on launch day
On launch day, crawl every old URL and confirm each one loads at the same address or redirects once to the right new page. Add the new XML sitemap in Search Console. Check key pages are allowed to be indexed. Then spot check canonical tags, titles and headings on your top 20 pages.
In order:
- Crawl every old URL from the inventory. Confirm each one returns either a 200 at the same address or a single 301 to the right new page. You want no chains, no loops and no 404s.
- Add the new XML sitemap in Search Console’s Sitemaps report.
- Check that the robots meta tag on key pages says the page may be indexed.
- Spot check canonical tags, titles and headings on the top 20 pages.
Then watch. Over the following weeks, Search Console shows crawl errors, indexing changes and movement for each query. Some movement in the first fortnight is normal while the search engine re-crawls. A steady slide on specific pages is a signal to look at what changed on those pages.
What a good redesign looks like to Google
From the outside, a well-run redesign is almost boring for a search engine. The same addresses answer the same questions. The pages that moved say clearly where they went. The content is better organised and a little more complete. The site is faster. Nothing it relied on has disappeared.
That’s the standard we hold a website redesign to. The new design is what the business sees. The inventory, the redirect map and the launch day checks keep the enquiries coming while it happens.
A short checklist for your next redesign
- Export 12 to 16 months of Search Console data before anything changes.
- Build the redirect map from the inventory, one old address to one new address.
- Compare old and new copy for every page that earns traffic.
- Remove the staging “noindex” setting and check it on the live site.
- Crawl the old URLs on launch day and fix anything that doesn’t resolve cleanly.
- Watch Search Console weekly for the first 2 months.
If your current site earns enquiries from search and a redesign is on the table, plan the migration before the design starts. The week before launch is too late.
Keep your enquiries coming through the redesign
A new look is the easy part. We rebuild websites with the inventory, redirect map and launch checks done first, so the pages that bring in work keep doing it. Nobody can honestly guarantee a position on Google, and we won’t either. See how our website redesign service works. Book a free strategy call before anyone touches your current site.
General information, current when published, and not legal or professional advice for your circumstances. For advice on your own site, book a free strategy call.