How to Redesign a Website Without Losing SEO Rankings

You keep SEO through a redesign by treating old URLs, titles and content as assets, not leftovers. Map every live page, 301-redirect anything that moves, and do not replace ranking copy with thin template text. Skip those steps, and a weekend launch can wipe months of organic traffic.

Start with an inventory, not a new design

I will not pick colours or layouts until I know what the current site already earns. You should do the same, even if you are briefing someone else. Export the last 12 months from Google Search Console: pages, clicks and impressions. Export landing pages from Google Analytics. Crawl the live site so you have a clean list of every URL that returns a 200 status.

Mark three groups: pages with clicks, pages with backlinks (Search Console has a simple links report), and pages that convert even if they barely appear in Google, such as a contact or quote form. Those three lists are the real brief. Anything not on them can change freely. Anything on them needs a plan.

A typical small business site in the UK has 15 to 80 indexable URLs. A brochure site might only have 12 that matter. An old WordPress install can hide 400 tag, category and parameter URLs that Google still knows about. You need the full list, not the menu.

Keep existing URLs wherever you can

The single biggest ranking loss I see after a rebuild is a new URL structure. /boiler-repair becomes /services/heating, /about-us becomes /our-story, trailing slashes flip, or the CMS adds /blog/ in front of every post. Google treats a new path as a new page. A 301 helps, but it is not a perfect transfer, especially if you also change titles and body copy on the same day.

If the current paths are ugly but indexed, keep them. You can change the visible heading and the design without changing the slug. If you must change a path, change as few as possible, and never change the domain, HTTP to HTTPS, www and the slug in one go.

If you want to redesign a website without losing SEO, this is the decision that matters more than the new homepage hero.

Build the redirect map before anyone writes a line of code

Every old URL that is not staying put needs a 301 to the closest equivalent new URL. Not a 302 temporary redirect. Not a JavaScript send. Not a blanket rule that dumps unknown paths on the homepage. Homepage dumps waste whatever ranking value the old page had, and they annoy anyone who bookmarked a service URL.

Include PDFs, old campaign landing pages and HTTP versions. Test by crawling the staging site against the live list. I put time in for this on every rebuild because it is where cheap redesigns cut corners. A 40-page site might need 40 to 120 redirect rules once you count leftover plugin paths.

Do not 301 everything to Home. Match service to service, post to post. If a page has no equivalent, either keep it or write a short replacement that still answers the same job, then redirect there.

Protect the copy, titles and headings that already work

A new template is not a reason to throw the words away. If a service page already brings enquiries, keep the H1 close to the current one, keep the paragraphs that name the job, the area and the price range, and keep the internal links that point to it. You can tighten sentences. You should not swap 800 words of specific copy for six lines of generic claims.

Title tags and meta descriptions are often the exact lines Google shows in results. Change them only when they are wrong or cut off.

If you merge two thin pages into one stronger page, 301 both old URLs to the survivor, and make sure the survivor still covers both topics in the body and subheadings.

Technical mistakes that look like an upgrade

• Staging left on noindex, then that robots meta copied live.
• A theme that puts the main copy in client-side JavaScript.
• Canonical tags pointing at staging, or every page canonicalised to Home.
• XML sitemap missing, or still listing old URLs.
• Internal links, including old blog posts, still hitting 404s.
• Heavier Core Web Vitals: a slider, an uncompressed hero, or a page builder dumping extra CSS.
• New filter or pagination URLs exploding the index.

Aim to match or beat the current Largest Contentful Paint on mobile. For a typical small business page that means a compressed hero, subsetted fonts, and no third-party chat widget until the rest of the page is fast. Under 2.5 seconds LCP on a mid-range phone is a sensible target.

Launch from staging, with a written checklist

Never redesign on the live site. Clone it, build on staging with a noindex header, and only go live when every item below is ticked.

1. Final URL list matches the inventory, or every change has a 301.
2. Redirects tested: old URLs return 301, then 200, with the right canonical.
3. robots.txt allows crawling; noindex is off on live.
4. XML sitemap submitted in Search Console; the old sitemap is removed.
5. HTTPS, preferred host (www or bare) and trailing-slash rule are consistent.
6. Title, H1 and primary copy on money pages match the keep-or-tweak list.
7. Internal links, including footer and posts, point at new paths.
8. The 404 page exists and is not a soft 200.
9. Analytics and Search Console still fire; a sample crawl shows no surprise 404s.
10. Forms, click-to-call and booking paths work on a phone.

Switch hosting or DNS at a quiet time, then fetch a handful of key URLs with the Search Console URL Inspection tool so Google sees the new versions sooner. Recrawl can take days on a small site and a few weeks if you had thousands of URLs. That delay is normal. A collapse in clicks on your top five landing pages is not.

Watch the first 30 days

Check Search Console coverage and the 404 report twice in the first week, then weekly. Compare clicks on the pages you marked as valuable, not only the site-wide total, which can hide a disaster on one service URL. If a money page drops, inspect it: is it 200, indexed, with the right canonical, and is the content still there?

Expect some wobble while Google recrawls. What you need to catch fast is a clean break: old URLs returning 404, or every page canonicalised to Home. Fix those within 48 hours. Weaker titles you can adjust without another full launch.

What this costs, and who should do it

A careful small business redesign in the UK usually sits between £2,000 and £8,000 as a one-off project, more if you have hundreds of URLs, ecommerce or a domain change. The redirect map, crawl and Search Console work is not a free extra. If a quote comes in well below that range and never mentions redirects, you are paying for a new skin and you will own the SEO mess afterwards.

If you cannot fund a lump sum, a pay-monthly website plan is the other honest route: a setup fee, then a monthly price that includes hosting, updates and ongoing management. That suits a small business with no upfront budget. I offer both a one-off build and that pay-monthly route; figures are on arlowebstudio.com.

Either way, put the inventory, the keep-URL rule and the 301 map in the brief. Ask to see the redirect spreadsheet before go-live, not after. Domain changes, mixing HTTP to HTTPS into the same weekend, and starting again from a blank homepage are the three requests I push back on.

Frequently asked questions

Will rankings drop after a redesign even if I do this?

A short wobble is common while Google recrawls. A lasting drop usually means 404s, a leftover noindex, bad canonicals, or ranking copy that was deleted. If your top landing pages stay on 200, indexed, with the same paths or clean 301s, most small sites settle within two to six weeks.

Should I change domain at the same time as the redesign?

No, not if you can avoid it. A domain move plus new templates plus new URLs is three migrations in one weekend. Finish the redesign on the current domain first. Move the domain later with host-level 301s, and only if you still have a real reason to.

How long should 301 redirects stay in place?

Years, not weeks. Leave them in place for as long as the old URLs still get hits or still appear in Search Console. I treat them as permanent unless a specific old path has had zero requests for a long stretch.

Can I switch CMS without losing SEO?

Yes, if the URLs stay the same or 301 correctly, and the new templates still output the text in HTML rather than only in JavaScript. The CMS is not what ranks. Paths, content, internal links and crawlability are.

What if I have no Search Console or Analytics history?

Verify Search Console on the live domain before you launch, then crawl the current site and export its XML sitemap. At minimum, 301 every URL in that sitemap and keep the visible service pages intact. Do not wait until after go-live to set property access up.

Does a cheap rebuild protect SEO?

Only if the redirect map and content preservation are in the quote. A £500 to £1,200 reskin that ignores URLs is a common way traffic disappears. Pay for the map, or build the spreadsheet yourself before anyone touches hosting.