A redesign that keeps every URL can still lose rankings. Google's John Mueller has said that a layout change alone can affect rankings even when URLs and content stay the same, and that a redesign tends to cause more fluctuation than moving a site one to one to a new domain (Search Engine Journal, 2020). The losses come from a short list of changes made quietly during design and build, and each has a check that catches it before launch.
This guide covers website redesign and SEO for B2B marketing sites: the nine ways a new site loses rankings, what Google's documentation says about each, and the fix. Redirect mapping gets one section here because our Website Migration Without Losing Rankings guide covers it in full.
Why a redesign moves rankings even with the same URLs
Google ranks pages from what it can crawl and render: the HTML, the links between pages, headings and copy, images and alt text, structured data and indexing rules. A redesign rewrites most of those at once, even when the brief only says "new look".
What Mueller described. Asked about three revamps that had all lost rankings, Mueller said nothing on Google's side penalises a revamp as such. The things to keep stable are the URLs, the internal linking, and each page's content and layout. If those line up, Google mostly sees a faster site. If they all change, Google treats it as a new website and starts over. Even moving a paragraph from a prominent position to a side note can change how Google reads a page, a little.
Timing confuses the diagnosis. A launch can coincide with a core update, Mueller noted, which hides whether the redesign or Google caused a drop. Google's guide to traffic drops recommends avoiding radical changes to pages that already perform well, and notes that a misplaced noindex causes a slower decline than an outage, because it takes effect page by page as Google recrawls.
One change at a time. Google's site move documentation advises against changing the domain, the CMS and the layout together. Mueller said the same on Reddit: if everything changes at once, you will not know what to fix.
| # | What changes | What Google loses | Check before launch |
|---|---|---|---|
| 1 | URLs change without redirects | The link from old rankings to new pages | Every old URL with clicks or links 301s to its closest match |
| 2 | Pages are cut | Content that ranked | Each page with clicks is kept, merged and redirected, or removed on purpose |
| 3 | Titles, headings and copy are rewritten | The words the page ranked for | Title, H1 and opening copy compared on pages that earn clicks |
| 4 | Navigation links are trimmed | Crawl paths and anchor text | Internal links per page, live against staging |
| 5 | Content moves behind clicks or scripts | Text Google never renders | Primary copy present in the HTML |
| 6 | Staging rules ship to production | Indexing itself | No stray noindex or disallow; canonicals on the live domain |
| 7 | Structured data and meta tags are dropped | Rich results and snippet control | Structured data types and descriptions per template |
| 8 | Images become CSS backgrounds or lose alt text | Image search traffic | Content images are img elements with alt text |
| 9 | The new design is slower | Page experience | Core Web Vitals per template, before and after |
Source: Google Search Central documentation; John Mueller via Search Engine Journal, 2020 and 2021; the checks are our own
1 and 2: Changed URLs and cut pages
These two cause the large drops, and they are the easiest to prevent.
Changed URLs. Mueller's view, reported by Search Engine Roundtable in September 2022, is that changing URLs for SEO reasons alone very rarely helps and will probably hurt until Google reprocesses the site. Google's site move guide asks for server-side permanent redirects (301 or 308) per page, no chains, internal links and the sitemap updated, and redirects kept for at least a year. The redirect map itself is covered in our Website Migration Without Losing Rankings guide.
Cut pages. Redesigns often shrink a site. Old articles, thin service pages and resource libraries get dropped because nobody wants to restyle them. Every dropped page with clicks or links takes its rankings with it, unless it is merged into a page answering the same query and redirected there.
What it costs. Seer Interactive, an agency that sells recovery work, publishes two cases. A consumer goods company redesigned, moved CMS, changed its URLs and information architecture, and lost 26% of its traffic; the audit found about 90,000 404 pages, mostly URLs missed in the redirect map, which Seer cut by 94% to about 5,000. An ecommerce redesign meant mainly to move to HTTPS deleted key pages, changed the URL structure and created duplicates, and organic traffic fell 75%. These are vendor case studies, but the causes match Google's own troubleshooting list: redirects to wrong or missing URLs, crawl errors and stale sitemaps.
3 and 4: Rewritten words and trimmed links
Titles and headings. Google builds title links from several sources: the title element, the main visual title and headings, og:title, other prominent text, and anchor text pointing at the page. Redesigns change all of them. New templates apply a boilerplate title pattern, the H1 becomes a slogan, and a second large heading competes with it. Google asks for a distinct, descriptive title on every page and one main heading that stands out; when several look equally prominent, it may use the first. Reprocessing takes a few days to a few weeks.
Copy. Copy written to fit the design, shorter and more abstract, removes the phrases a page ranked for. Asked in a 2020 office hours session whether a new layout could matter with unchanged URLs and content, Mueller said yes, because the layout carries the titles, the internal linking and the context around the content. Rewrite copy against the queries each page already earns in Search Console, not against a blank page.
Internal links. Google reliably follows a link only when it is an a element with an href attribute; buttons with click handlers and styled span elements are not parsed as links. According to the HTTP Archive Web Almanac 2025, the median page has 43 links to its own site on desktop and 39 on mobile, rising to 174 and 161 at the 90th percentile. Replacing a mega menu with five items, or a long footer with a short one, removes most of those paths in one release.
5: Content Google cannot see
Google indexes the mobile version of a page. Its mobile-first guide asks for equivalent primary content and headings on mobile and desktop, and says Google will not load content that requires a swipe, a click or typed input. Accordions and tabs are fine when the content is already in the page; content fetched only when a tab opens is not.
JavaScript adds a step. Google crawls the HTML, queues the page for rendering in headless Chromium, which can take seconds or longer, then indexes the result. Google still recommends server-side rendering or pre-rendering, since not every bot runs JavaScript. The Web Almanac 2025 found the median home page has 18% more words after rendering than in raw HTML on desktop, and 16% more on mobile. For a marketing site the test is short: view the source of each staging template and confirm the main copy, headings and links are there.
6 and 7: Staging leftovers and dropped markup
Indexing rules. Staging sites are rightly blocked with noindex tags, a disallow-all robots.txt, or canonicals pointing at the staging host. Google's site move guide lists forgotten noindex and robots.txt blocks as the first common mistake. Canonicals are the quieter version: 68% of desktop pages and 67% of mobile pages declare one, and 0.7% have mismatched values (Web Almanac 2025). A template that hard-codes the staging host or the homepage as canonical tells Google every page is a copy.
Structured data and meta tags. 50% of pages carry structured data, and only 2% add it with JavaScript (Web Almanac 2025). It lives in old templates, plugins or hand-written embeds, so a rebuild drops it unless someone lists it first. Meta descriptions, on 67.7% of desktop pages, go the same way. Google's mobile-first guide asks for the same structured data and metadata on every version of a page; the logic holds between old and new templates.
| Signal | Share of pages, 2025 | Redesign risk |
|---|---|---|
| title element | 98.62% desktop, 98.54% mobile | Rewritten to a boilerplate pattern |
| Non-empty H1 | 66% | Replaced by a slogan or image |
| rel=canonical | 68% desktop, 67% mobile | Hard-coded to staging or the homepage |
| Structured data | 50% | Left behind with old templates |
| Meta description | 67.7% desktop, 67.2% mobile | Not carried over |
| Images with alt attribute, median mobile page | 60% | Lost when images are uploaded again |
Source: HTTP Archive Web Almanac 2025, SEO chapter
8 and 9: Images and speed
Images. Google indexes images in the src attribute of an img element, including inside picture, and does not index CSS background images. Backgrounds are fine for decoration, but screenshots, diagrams and team photos that earn image search traffic should stay img elements with descriptive alt text and filenames, each referenced by the same URL consistently. On the median mobile page, 60% of images had an alt attribute and 15% a blank one (Web Almanac 2025). Uploading every image again to a new CMS is when alt text disappears.
Speed. Google says good Core Web Vitals align with what its core ranking systems reward. The targets are Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint under 200 milliseconds and Cumulative Layout Shift under 0.1. About 60% of desktop pages and just over 50% of mobile pages pass, and Largest Contentful Paint passes on only 55% to 60% of mobile pages (Web Almanac 2025). Autoplay video, extra font families and a heavy animation library can tip a passing site into failing. Record field data per template before design starts and set the budget then.
How to use this on your redesign
Write down what the new site must keep before the first wireframe:
- Crawl the live site: URLs, titles, H1s, canonicals, structured data types, internal links per page and word counts.
- Pull 12 months of Search Console clicks and decide for each page that earns them: keep, merge with a redirect, or remove on purpose.
- Give designers the constraints: one H1 per page, content images as img elements, primary copy in the HTML, navigation that reaches every page that matters.
- Crawl staging, compare it field by field with the live crawl, and fix every difference nobody chose.
- At launch, remove staging rules, publish redirects, submit the sitemap and spot-check the top pages; then watch Search Console for 30 days.
We build marketing sites in Webflow on a four-week process, and we redesigned the USLege legal-tech site. On a redesign we would run the crawl and content inventory in week one, before design, because every check above depends on them. Our Webflow SEO Checklist covers the platform settings. Our marketing websites service page explains how we scope a redesign.
