Redesigning Your Website Without Losing Your Google Rankings

Your website looks tired, a new one is on the way, and there’s a nagging worry underneath the excitement. Google sends you enquiries now. What happens to them the day the new site goes live?

The main risks are ones you can prevent: old web addresses that now lead nowhere, pages that quietly disappear, and a new site that launches still hidden from Google. Google publishes a clear process for avoiding all three. It also says to expect some movement in your rankings for a few weeks while it catches up, so “without losing rankings” really means “without losing them for avoidable reasons”.

Here it is in plain English, stage by stage, with how we followed it on our own site in September 2026 and the questions to put to whoever is building yours.

What actually puts your rankings at risk

Google indexes and ranks pages one by one, and each page lives at a URL, its web address (for example yoursite.co.uk/boiler-repair/). The risks come from breaking the link between the pages Google already knows and the pages on your new site:

• Addresses change and nothing points from old to new. Google’s guidance on HTTP status codes is blunt: “URLs that are already indexed and return a 4xx status code are removed from the index.” A page that ranked last week and now shows “not found” drops out rather than handing over to its replacement.
• Content that was earning visits gets cut because it didn’t fit the new design.
• The new site launches blocked from Google. Some site owners block search engines while a new site is being built. If that block isn’t removed at launch, the new site can’t be indexed. It’s the first common mistake Google lists in its site-move guide.
• Smaller slips add up. Internal links still point at old addresses, business details and FAQ markup don’t get carried across, or a mobile layout drops content the desktop version had.

None of these is about how the new site looks. The danger is in what happens to addresses, content and access.

First, what kind of change are you making?

“New website” can mean four different things, and Google treats them differently.

The change	What’s different	Relative risk (our reading)	Extra steps
New design, same addresses	Look and layout change; every page keeps its URL	Lowest: nothing to redirect	Keep the content; make sure the site is open to Google at launch
New addresses, same domain	Pages move, e.g. /services/boiler-repair.php becomes /boiler-repair/	Higher: Google treats this as a site move	A redirect map for every changed URL
New hosting, same addresses	The site moves to a different server or company	Moderate, if handled carefully	Test copy kept out of Google; plan the DNS switch
New domain name	e.g. moving from one .co.uk to another	Highest	Everything above, plus Google’s Change of Address tool

Google’s general advice for site moves is to “change only one thing at a time”: if you’re changing domain, content management system and layout, do them one after another. That isn’t always practical, but each extra change adds risk. The Change of Address help page warns that if you combine a domain move with a redesign of content and URL structure, “you will probably see some traffic loss as Google might need to relearn and reassess the individual pages.”

For a hosting-only move, Google’s guide to moves without URL changes says to set up and test a copy of the site on the new hosting and keep that test copy out of Google. It suggests lowering your DNS “time to live” setting at least a week in advance, and shutting the old hosting down only once nobody, Googlebot included, is still using it.

If you’re leaving an old WordPress or Wix site, or changing web designer, look hard at the second row: a new platform can mean new page addresses even on the same domain. The rest of this guide focuses on that case. The launch and follow-up checks apply to every row.

Before launch

This is where the work is. Done properly, it turns launch day into switching things on and checking them.

1. Record what you have and what’s working

Before anything is removed or rebuilt, list every page on your current site and note which matter most. Google suggests starting with your most important URLs, found from your sitemap (the file listing your site’s pages for search engines), your analytics and Search Console. Google Search Console is Google’s free tool for site owners. If you don’t have access to it, sort that out first; you’ll need it at every stage.

In Search Console’s Performance report, which shows the past three months by default, you can see which pages and searches bring in clicks. Note your top pages and the searches they appear for, plus any pages other websites link to (the Links report shows these), and keep a record of the totals. After launch, this is the baseline you’ll compare against.

Done when: you have a list of every current URL, with the pages that bring in visits and enquiries clearly marked.

Still deciding whether you need a new site at all? Our guides to how much a website costs in the UK and checking your current site’s health can help.

2. Decide what happens to every page

Go down the list and give each page one of three outcomes:

• Keep. It moves to the new site, with the same content or better. Pages that bring in visits belong here almost by default.
• Merge. Two or three thin pages on the same subject become one stronger page.
• Remove. It’s out of date, or covers a service you no longer offer.

Be careful with “remove”. A dull-looking page that still brings in steady visits is doing a job, and a redesign is an easy moment to lose it without noticing. The same goes for the words on pages you keep. If a service page ranks well with, say, 600 words of useful detail, replacing it with a slick 80-word version is a content change, not just a design change.

Done when: every URL on your list has an outcome.

3. Build the redirect map

A 301 redirect is a permanent forwarding instruction: ask for the old address and the server replies “moved permanently” and sends you to the new one. A redirect map is a two-column list of old URLs and the new URL each one goes to. The rules:

• Every kept or merged page gets a redirect to its closest equivalent. The old boiler repair page goes to the new boiler repair page, not to the homepage or a general services page. Merged pages all point to the page that combines them. Google’s own troubleshooting list says, “We frequently see people redirecting to the wrong (non-existent) URLs”, so check every destination actually exists.
• Pages you’re genuinely removing, with nothing to replace them, should return a 404 (“not found”) or 410 (“gone”). That’s Google’s instruction for deleted content in its site-move guide, and its Page indexing help notes that 404s “are not necessarily a problem, if the page has been removed without any replacement.” Don’t send every retired page to the homepage just to avoid a 404.
• Include more than pages. Google’s guide mentions images, PDFs and other files, so if you have price lists or brochures that people link to or find in search, map those too.
• Avoid chains. Old address to new address in one step. Google advises against chains of redirects (A to B to C), which can creep in if your current site already has redirects from an earlier redesign. Point those older addresses straight at the final new page.

Worried that redirecting throws away the value a page has built up? Google says “301 and other permanent redirects don’t cause a loss in PageRank.”

Done when: you have a written redirect map covering every URL on your list, and each new URL on the right-hand side exists on the new site.

4. Keep the staging site out of Google

A new site is often built on a staging site: a working copy at a temporary address (something like new.yoursite.co.uk) where you can review it before launch. It needs to stay out of Google, or a half-finished copy of your site could turn up in search.

Google’s guidance on blocking search indexing gives two ways:

• A noindex rule, either as a tag in each page’s code or as an X-Robots-Tag: noindex header sent by the server. Both have the same effect: Google can visit the page but won’t show it in results.
• A password, so nobody, Google included, can see the site without logging in.

What doesn’t work is relying on robots.txt, the small file that tells search engines which parts of a site they may crawl. Google’s robots.txt introduction says it “is not a mechanism for keeping a web page out of Google”; a blocked page can still be indexed if other sites link to it. Combining the two backfires too: if robots.txt blocks a page, Google never sees its noindex rule.

Done when: you’ve checked that the staging site uses noindex or a password, and your designer has a written note of exactly what needs removing at launch.

5. Carry over everything Google reads

Google reads text, titles, links and code, not the design. Check these survive the move:

• Page titles and headings on the pages that rank. Improve them by all means, but keep the words that say what the page is about.
• Mobile content. Google uses the mobile version of your site for indexing and ranking, and says your mobile site should contain the same content as the desktop one. If the new design hides sections on phones to look cleaner, that content may effectively disappear for Google.
• Internal links. Menus and in-text links should point straight at the new URLs, not rely on redirects. Google can only discover links that are proper HTML links (an <a> element with an href), so if the new menu is built in JavaScript, check with your designer that it still produces them.
• Structured data. This is code that describes your business to search engines in a standard format: your name, address, opening hours, FAQs. Google suggests testing it with its Rich Results Test during development and checking again after launch, because structured data “might break after deployment” when templates change.
• Tracking and verification. Google’s site-move guide says to make sure your Search Console verification keeps working and to run analytics on the new site, so your data doesn’t go dark just when you need it.

A faster site is a fair goal; just don’t count on speed alone to lift you. Google says Core Web Vitals (its speed and stability measures) “are used by our ranking systems”, but good scores don’t guarantee your pages will rank at the top.

Done when: you’ve compared your top pages on the old and new site, on a phone as well as a computer, and the words, titles and business details are all there.

6. Plan the switch-over

Google recommends preparing the live site’s robots.txt in advance, along with a list of pages that need noindex removed. It also suggests timing a move to coincide with lower traffic: if your business has a busy season, launching just before it leaves little room to fix a problem.

Done when: you have a launch date and a written list of what gets switched on, switched off and checked.

Launch day

1. Switch on the redirects, as permanent server-side redirects

Google recommends permanent HTTP redirects, meaning 301 or 308 status codes set up on the server, as the method it’s most likely to interpret correctly. Redirects done with JavaScript or a timed page refresh are a fallback. Your hosting company or platform will have its own way of adding them.

Watch for temporary redirects (302 or 307). Google treats them as “this page has moved for now” and shows the old address in results, which is the opposite of what you want after a redesign.

2. Remove the staging blocks

Take off the noindex rules or password, and put the launch robots.txt in place. Given that this tops Google’s list of common mistakes, check it on the live site rather than taking it on trust.

3. Test a sample of old addresses

Type a selection of old URLs into your browser, starting with your most visited pages. Each should land on the right new page in one hop. A made-up address should show a proper “not found” page.

Google’s site-move guide names the URL Inspection tool in Search Console as one way to check redirects. Try it on your homepage and a few key service pages.

4. Submit the new sitemap

Add your new sitemap in Search Console. Google calls submitting a sitemap “merely a hint” rather than a guarantee, but it points Google at your new URLs.

5. Update the links you control

• Google Business Profile. If your website address has changed, update it on your profile. Google’s instructions for editing your profile say to enter the full URL, including https://, and to make sure Googlebot isn’t blocked on your site. Google reviews edits first, which it says usually takes up to 10 minutes but can take up to 30 days. Our Google Business Profile guide covers the rest of the profile.
• Your other profiles and ads. Google’s site-move guide also mentions social profile links and ad campaigns. Directory listings you manage are worth checking too.
• The Change of Address tool: domain moves only. It’s for moving from one domain or subdomain to another, not for switching to https, adding or removing www, moving pages within your site or changing hosting. If you are changing domain, Google asks you to keep redirects for at least 180 days and recommends paying for the old domain for at least a year.

Done when: redirects work in one hop, the live site is open to Google, the sitemap is submitted and your Business Profile points to the right address.

The first few weeks

What’s normal

Expect movement. Google’s site-move guide says to “expect temporary fluctuation in site ranking during the move”, and that “a small to medium-sized website can take a few weeks for most pages to move, and larger sites take longer.” Some searches may dip or jump while Google swaps old addresses for new ones.

Search Console’s Page indexing report shows which of your pages Google has indexed and why others aren’t. Old URLs will appear there as “Page with redirect”. That’s expected: Google indexes the new page instead.

Our guide to how long SEO takes explains more about why Google works to its own timetable.

What’s a problem

Check Search Console weekly for these, and act on them:

• Pages marked “noindex” or “Blocked by robots.txt” that you want in Google. Something from staging was left behind.
• “Not found (404)” on old URLs that used to get visits. A redirect is missing or wrong. Add it to the map and fix it.
• “Soft 404”. Google thinks a page looks empty or like an error page even though the server says it’s fine. Check what’s on it.
• A sustained fall in clicks to specific pages. In the Performance report, use Compare to set the weeks since launch against the same period before, then look page by page. A general wobble is expected; one important page falling away while others hold is worth checking for a missing redirect or lost content.

Re-test your structured data too, and check contact forms and phone links work. Enquiries lost to a broken form won’t show in any ranking report.

Keep the redirects

Google’s advice is to “keep the redirects for as long as possible, generally at least 1 year”, and for visitors’ sake to consider keeping them indefinitely, so old links in emails, directories and bookmarks keep working. The 180-day figure you may see quoted applies only to domain moves using the Change of Address tool.

Done when: a few weeks after launch, Page indexing shows no unexpected noindex, robots.txt or 404 problems on pages you care about, and any important page that has fallen away against your baseline has been looked into.

How we did it on our own site

In September 2026 we moved getfound.co.uk from an old WordPress site to a new one on a different platform. The domain stayed the same but many page addresses changed: the second row of the table above. Here’s what we did:

• Listed the old site’s URLs from its sitemap.
• Mapped all 95 old addresses. Seventy-four redirect to their nearest new page: /google-my-business goes to our local SEO page, for example, and /website-maintenance to our web design page. Eight of those go to the homepage because it genuinely is the nearest match (the old home, about, company and general digital marketing pages). The other 21 were pages for services we no longer offer, such as video production and animation. Rather than redirect them to the homepage, we have them return 410 to tell Google they’ve gone.
• Added three pattern redirects that send whole groups of old WordPress addresses (dated archive pages, tag, category and author pages, and the old feed) to the blog.
• Set the redirects up on the server as permanent 301 rules, rather than relying on a plugin or JavaScript. Checks on the live site on 28 September 2026 found sample old addresses reaching their new page in a single redirect, retired service pages returning 410, and a made-up address returning a genuine 404.
• Kept the staging site out of Google. We built and reviewed the new site on a separate staging address that sends a noindex header, so Google is told not to index it. We chose that over a password, which would also have worked.
• Kept an archive of the old site so we could roll back if something went badly wrong.
• Submitted the new sitemap in Search Console.

We’re not quoting before-and-after traffic. It’s too early to say anything useful, and one site’s result wouldn’t tell you much about yours. What it does show is that these steps are practical on a small business site.

Questions to ask your web designer

If someone else is building your site, you don’t have to do these steps yourself, but you do need to know they’re being done. Ask:

1. Will any page addresses change, and can I see the redirect map before launch? (You’re looking for each old page going to “the closest matching new page”, not “the homepage”.)
2. Will the redirects be permanent 301s, set up on the server?
3. How will you keep the staging site out of Google, and who removes that at launch? (Listen for noindex or a password, not robots.txt alone.)
4. Will the pages that bring in enquiries keep their content, on mobile as well as desktop?
5. Will my business details markup, analytics and Search Console verification carry over?
6. What will you check on launch day, and who’s watching Search Console afterwards?
7. How long will the redirects stay in place? (Google’s general guidance is at least a year.)

Be wary of anyone who promises your rankings will stay exactly the same, or rise. Google itself says to expect fluctuation. Our guide to choosing an SEO agency covers more of the warning signs.

If you’d rather hand it over

Get Found is a local SEO, AI SEO and web design agency on Foregate Street in Worcester, with a second office in Stockport. We have 22 years’ experience, work across the UK and don’t tie clients into long contracts. When we design a new website or redesign an existing one, we start by checking what your current site ranks for, keep the pages and content that are working, redirect the old URLs, and keep an eye on Search Console after launch. Working with another designer? A free visibility audit shows where your site stands before anything changes, or you can get in touch with questions.