A redesign is not a migration, and treating it as a purely visual project is why so many sites lose traffic after one. The URLs may not change at all and the rankings can still fall, because what changed was the content and the markup rather than the addresses.
Why redesigns lose rankings
Content is cut for visual reasons
The most common cause by a distance. A cleaner design usually means less text, and pages that ranked on substance are rebuilt with a hero image and three lines of copy. The design improves and the page stops answering the query it used to rank for.
Heading structure is replaced by styling
Rebuilds frequently convert real headings into styled divs, or use heading levels for visual size rather than document structure. The page looks identical and reads as structureless.
Internal links disappear into navigation changes
Contextual links inside body copy are often casualties of a rewrite, and a simplified menu removes more. Pages that were well linked become hard to reach.
Text moves into images or scripts
Copy rendered inside images, sliders or scripted tabs may not be picked up as page content.
Page speed regresses
New designs tend to be heavier. Large hero images, web fonts and animation libraries push Core Web Vitals in the wrong direction.
Protecting rankings through a redesign
- Benchmark first. Record current rankings, traffic by page and word counts before anything changes. Without this you cannot tell what was lost.
- Identify your top pages by revenue and traffic and treat them as constrained. Their content should be preserved or extended, not trimmed.
- Keep the URLs unless there is a strong reason to change them. If they must change, the project is also a migration and needs a redirect map.
- Preserve title tags and meta descriptions. These are frequently regenerated by a new theme and quietly replaced with templated versions.
- Carry over the internal links, including in-body contextual links.
- Crawl staging against a crawl of the live site and compare titles, headings and word counts page by page. This one check catches most redesign damage before launch.
That final comparison is the highest-value step in the entire process and is almost never done.
What to check immediately after launch
- The staging robots.txt did not go live with the site.
- No pages carry a stray noindex from the build environment.
- Canonical tags point at live URLs, not staging ones.
- The sitemap regenerated and reflects the new site.
- Analytics and Search Console are still recording.
Frequently asked questions
Do I need redirects if the URLs did not change?
No, and confirm they genuinely did not change. Trailing slashes, case, and category prefixes shift more often than people expect during a rebuild.
How long after a redesign should I worry?
Minor fluctuation in the first two weeks is normal. A sustained decline beyond three to four weeks indicates something structural rather than settling. See SEO recovery.
Can I improve SEO during a redesign?
Yes, and it is the best opportunity you get. Fixing heading structure, internal linking and page speed is far cheaper during a rebuild than retrofitted afterwards.
Should the designer handle SEO?
Design and SEO requirements need to be agreed before the design is signed off, not negotiated after. Most damage comes from decisions made early that nobody flagged as having search consequences.
Consulting CTA
If a redesign is planned, book an SEO consultation during the design phase, while changes are still cheap.