Redesign without losing traffic
By Ismael · Reviewed
A redesign keeps its search signals when the URLs, content and internal links that earned them survive the visual and technical rebuild. SiteBienfait sequences a rebuild so the design changes after the URL contract is frozen. Google Search Central, updated 2026-08-20, advises changing one thing at a time, because combined changes make the cause of a fluctuation impossible to isolate.
Why does a redesign lose traffic?
Four causes, in order of frequency. URLs changed without a redirect map. Content was removed or rewritten so heavily that the page no longer answers the query it used to answer. Internal links were rebuilt by a new navigation and pages lost the links that reached them. And staging protections — noindex, basic auth, a robots block — shipped to production.
None of these is about the new design looking different. A redesign can change every pixel and keep its signals, as long as the contract underneath is preserved.
What should be frozen before design work starts?
Five things. The full URL list from the live site. The current titles and descriptions, so the new ones can be compared rather than guessed. The canonical rules, including trailing slash and protocol choices. The internal link graph, meaning which pages are linked from where. And a Search Console baseline: queries, pages, impressions, clicks and average position for the previous three months.
The freeze is not bureaucracy. It is the only way to answer the question a month after launch: did this page change for the better, or did it lose the links and text that made it rank?
When should the URLs change?
Only when the information architecture genuinely requires it. A rebuild that keeps content on the same paths is a hosting and template change, which Google Search Central separates from a site move. A rebuild that reorganises sections is a URL change, and it needs the full migration treatment: mapping, permanent redirects, canonical updates and a new sitemap.
Google Search Central, updated 2026-08-20, is explicit that 301 and other permanent redirects do not cause a loss in PageRank, and that redirects should stay in place for as long as possible, generally at least one year. The risk is not the redirect; the risk is the missing redirect.
In what order should a redesign be built?
First the content and URL contract: which pages exist, at which addresses, answering which queries. Then the new templates and styles, built against those addresses. Then redirects for anything that genuinely moved. Then launch, measurement, and iteration.
Doing it in that order means the new design is evaluated against a stable map. Doing it in the opposite order — design first, then discover the URL consequences — is how projects end up rebuilding the redirect plan on launch week.
What is checked after launch?
Index coverage for the new URLs. The internal link graph, to confirm no page became orphaned. Titles and descriptions on the rebuilt templates, because a new component often drops a field. Canonicals, because a rebuilt head is a common place for a wrong URL to appear. Core Web Vitals, because templates change images, fonts and scripts, and Google Search Central’s updated 2025-12-10 guidance on Core Web Vitals lists the targets to hold: LCP within 2.5 seconds, INP under 200 milliseconds, CLS under 0.1.
Then compare against the frozen baseline: the same queries, the same pages, the same window length. Keep the redirects live and keep the baseline until the comparison is done.
SiteBienfait’s rebuild route runs this as a sequence of approved change sets: URL contract first, then template work, then preview, then deploy with rollback available. The redirect map checker covers the case where a rebuild does change addresses and the mapping has to be proven. For the performance half of the launch, the guide on Core Web Vitals for small business turns the thresholds into a page-level checklist.
Sources
- Google Search Central, Move a site with URL changes, last updated 2026-08-20.
- Google Search Central, Changing your web hosting, last updated 2025-12-10.
- Google Search Central, Understanding Core Web Vitals, last updated 2025-12-10.
Questions
01 Why do redesigns lose search traffic?
Usually because URLs changed without redirects, content was cut, or staging rules such as noindex and password protection shipped to production. Visual redesigns that keep URLs, content and internal links do not have that failure mode.
02 Should a redesign change URLs?
Only when the information architecture genuinely requires it. Google Search Central, updated 2026-08-20, treats URL changes as a site move that needs a mapping and redirects kept generally at least a year.
03 What should be frozen before the design work starts?
The URL list, the title and description baseline, the canonical rules, the internal link graph and a Search Console baseline. Freezing them first means the redesign can be compared with the site that existed before it.
04 How long should a redesign be monitored?
Long enough for recrawling and reindexing to finish, which Google Search Central describes as a few weeks or more for a medium-sized site, updated 2026-08-20. A single week after launch is not a verdict.