Will a website redesign lose our Google rankings? What we learned moving 310 pages

The new design is approved. Then someone asks the question that stops the meeting: what happens to our Google rankings? The pages that bring in enquiries took years to earn their places.

A redesign does not lose rankings by itself. Rankings fall when the move breaks what Google had learned about the site: old addresses that stop working, useful pages dropped, or a launch that shuts crawlers out. Some movement is normal even when the work is done well. Google's guidance on site moves (updated August 2026) tells site owners to expect temporary ranking fluctuation during a move, and says "a small to medium-sized website can take a few weeks for most pages to move, and larger sites take longer."

Whether to rebuild at all is a different question, answered in should we redesign our website or keep improving the one we have. This guide assumes the decision is made and sets out the page-by-page method we use for the move itself. We used it on the arum rebuild: "310 pages rebuilt across three regions, in weeks." "215 articles, research pieces and news items moved across, going back to 2014." "Every old address redirected, so years of rankings carried over."

#Why do websites lose rankings after a redesign?

Because the new site breaks the connections Google had made between an address, what the page says and where it ranks. In our experience, four failures cause most of the damage:

• Addresses that stop working. A new platform changes /services/tax-advice.html to /what-we-do/tax, and without a redirect the old ranking and its links are lost.
• Content dropped or cut down. A page that ranked for years is trimmed to fit a template, or left out because nobody knew it brought in enquiries.
• Temporary redirects. Google's guidance on redirects (April 2026) says that with a temporary redirect (302 or 307) the indexing pipeline "doesn't use the redirect as a signal that the redirect target should be canonical". A permanent redirect (301 or 308) does.
• Crawlers shut out at launch. A robots.txt block or "noindex" rule left from the test site, or new hosting that blocks AI crawlers.

#Which parts of a redesign put rankings at risk?

The risk depends on what changes. A new look on the same addresses carries little risk. A new domain, a new platform and a new structure all at once carries the most.

Google's Change of Address tool is only for moves between domains or subdomains, and each new page should carry a self-referencing canonical tag. Google recommends moving a small or medium site all at once; larger sites can move a section at a time.

#How do we move a site without losing rankings?

Work page by page, in this order. Most of the work happens before anyone sees the new design.

#Step 1: Crawl and list every old address

List every address in use, not only the pages in the menu. Google suggests starting from your sitemaps, server logs, analytics and the links report in Search Console. Add a crawl of the live site, then record for each address: visits in the last twelve months, enquiries or downloads, links from other sites, the searches it ranks for and when it was last updated. Include PDFs, images and old campaign pages, which often carry links from other sites.

#Step 2: Decide every page: keep, merge or retire

Give each address one decision and write it down. For TCC Group, a regulatory compliance group, the work was "624 pages reviewed, each given a decision: migrate, merge or retire." A written decision stops pages vanishing by accident and ends the debate about each one.

Merging matters as much as keeping. TCC's old site had "pages that half-answered the same question so neither was cited", and a rebuild is the cheapest moment to fix that. Our guide to why ChatGPT ignores sites with hundreds of pages covers how to spot them.

#Step 3: Map redirects one to one

Add the new address to each row of the spreadsheet. Every kept or merged page gets a server-side permanent redirect to its closest new page. Google says: "Don't redirect many old URLs to one irrelevant single URL destination, such as the home page of the new site", and warns this "might be treated as a soft 404 error", which means Google treats the old page as gone.

Two details catch most teams. First, redirects left from earlier moves: update them to point straight at the final page, because Google advises "redirecting to the final destination directly" rather than through a chain. Second, internal links: change every link on the new site to the new address, so the site does not send its own visitors through redirects.

#Step 4: Keep what ranks

The safest redirect is the one you do not need, so keep an address unchanged wherever the new structure allows. Where a page ranks, keep what earns the ranking: the question it answers, its headings, its facts and figures, and its depth. Improve the page around that core rather than rewriting it from memory. Keep honest dates as well: an article from 2019 should still say 2019, with an "updated" date only where the content really changed.

#Step 5: Move the content before the design

Put the real words into the new templates early, then review working pages instead of mock-ups. Mock-ups hide the problems that cost rankings: a long page squeezed into a short layout, a table turned into an image, text that only appears after a script runs. The main AI crawlers, GPTBot, ClaudeBot and PerplexityBot, fetch pages but do not run JavaScript (Vercel and MERJ, December 2024), so key text must be in the page's HTML. On arum, whose CEO and Executive Chair is Jamie Waller: "No workshops and no weekly status meetings. Jamie reacted to real, working pages within weeks."

#Step 6: Run the launch checks

On launch day, test rather than assume:

1. Every row of the redirect map returns a permanent redirect to the right page in one step.
2. Retired pages return a 404 or 410 error, not the home page.
3. Robots.txt and "noindex" rules from the test site are gone. Google lists them among the common mistakes in site moves.
4. AI crawlers can get in. To appear in ChatGPT search a site must allow OAI-SearchBot (OpenAI), and Cloudflare changed its default setting in July 2025 to block AI crawlers, so check that setting if your new hosting sits behind Cloudflare.
5. The new sitemap is submitted in Search Console and in Bing Webmaster Tools, since Bing's index feeds Copilot. See does ChatGPT use Google or Bing.
6. Canonical tags, structured data, analytics and every enquiry form work on the new pages.

Our technical checklist for an AI-ready website covers the crawler checks in more detail.

#Step 7: Recheck at one, four and twelve weeks

At one week, look for errors: old addresses that return a 404 and should not, forms that fail, pages missing from the new sitemap. Google suggests submitting both the old and new sitemaps and watching indexing move from one to the other. At four weeks, compare rankings and visits for the pages that mattered most in Step 1. At twelve weeks, compare enquiries by page with the same period before launch.

If a dip is not closing by week four, check your server logs for old addresses still returning errors, and compare each page that lost ground with its old version. In our experience the cause is usually a missing redirect or missing content.

#Step 8: Baseline AI answers, then recheck

Before launch, record what AI assistants say about you: a fixed list of 20 to 50 buyer questions, each asked several times in a clean session in ChatGPT, Gemini, Copilot and Perplexity. Search Console's generative AI performance reports, available to all sites since August 2026, add your impressions in AI Overviews and AI Mode. Run the same questions again at four and twelve weeks. Assistants that search the web live can reflect the new site within weeks; answers drawn from a model's memory change only when it is retrained, which takes months. Our guide to finding out whether ChatGPT recommends your firm sets out the method.

#What mistakes cost the most rankings?

These are the ones to rule out in writing before launch:

#What did moving 310 pages for arum teach us?

That a large move is a list-keeping exercise more than a design exercise. arum advises banks, governments and major brands on collections technology, and its site ran as "3 regional versions: UK and Europe, North America, Australia and New Zealand." The rebuild delivered "Proper structure and markup on every page, a plain summary AI assistants can read, facts stored once so two pages never disagree, and every old address redirected so years of rankings carry over."

The last stage was as disciplined as the first: "When arum's team sent a final list of 77 changes, we checked each one against the live site before touching a word." Jamie Waller put it this way: "For most people, our website is the first time they meet arum. It now does us justice."

The method does not need us to run it. TCC Group took "1 week to a plan TCC's own team built the new site from", and "TCC chose to build it with its own team, and the new tcc.group is live, built to the plan, with nothing about it depending on Fortitude."

#What to do this month

1. Export every old address into one spreadsheet, with visits, enquiries and links for each.
2. Mark the twenty pages that matter most by enquiries and links, and agree that their addresses and core content do not change without a reason.
3. Add a decision column and give every address keep, merge or retire before design work goes further.
4. Ask your developer how redirects will be set up: server-side, permanent, one step, and kept for at least a year.
5. Record your baseline: rankings for key pages, enquiries by page and your buyer questions in the main AI assistants.
6. Put the launch checks in the project plan with a named owner and dates for the one, four and twelve week reviews.

#Frequently asked questions

#How long does it take for rankings to recover after a redesign?

Google says a small to medium-sized site can take a few weeks for most pages to move, and larger sites longer. If the redirects and content are right, most dips close within that window. If rankings are still down after four to six weeks, look for missing redirects or cut content before blaming the design.

#Should we keep the same page addresses?

Wherever you can, yes. An address that does not change needs no redirect and carries no risk. Change addresses only where the new structure is clearly better for buyers, such as grouping services the way clients buy them, and then redirect each old address to its new one.

#Do we need to redirect pages that get no traffic?

Redirect any page with links from other sites or recent visits, even a few. A page with neither can be retired, and Google says retired addresses should return a 404 or 410 error. Do not point them at the home page to tidy up.

#How long should redirects stay in place?

Google says "generally at least 1 year", and as long as possible. Links from other sites, old emails and bookmarks keep sending people to old addresses for years, so we keep redirects indefinitely where the platform allows.

#Will a redesign change what ChatGPT says about us?

It can, in either direction. Assistants that search the web live can pick up the new pages within weeks, so a clearer site can help. If crawlers are blocked or key text only appears after scripts run, the same assistants may lose sight of pages they used to cite. Baseline before launch and recheck after.

#We are changing our domain name as well. What changes?

Everything above still applies, plus Google's Change of Address tool in Search Console. Keep the old domain registered and redirecting, update your directory listings, and ask the sites that link to you most to update their links. If the firm's name changes too, read why ChatGPT describes a firm wrongly.

A redesign should keep what your site has earned and add to it. If you are planning a rebuild, Website That Sells is how we build sites that carry their history across, and a free Growth Review will tell you in writing which three things to fix first.

#Sources