Redesigns lose rankings when URLs, content or internal links change without a migration plan. Protect the equity with four disciplines: benchmark, map, redirect, monitor. Here is the checklist we run on every rebuild.
Before anything: benchmark what you are protecting
- Full crawl of the current site, every URL, title, meta and status
- Search Console export: queries, top pages, and which URLs earn the traffic
- Backlink inventory: which pages hold the external equity
- Analytics baseline: organic sessions and conversions per template
The URL decision, and the redirect map
Keeping URLs identical is the safest redesign there is. Where URLs must change, build a one-to-one redirect map: every old URL 301-ing to its most equivalent new page, never mass-redirected to the homepage. Redirect chains and wildcard shortcuts are where equity quietly dies; the map is boring work that saves months of recovery.
Content and template parity
Designers love minimalism; rankings love substance. Audit that the new templates preserve the content that earned positions: headings, copy depth, FAQs, internal links, schema. A page that shrinks from twelve hundred rendered words to two hundred will re-rank accordingly. Rebuild structured data deliberately; it rarely survives platform moves on its own.
Launch week and the month after
- Crawl the new site pre-launch on staging and fix 404s, chains and noindex leaks before DNS flips
- Submit fresh sitemaps; watch Search Console coverage and Core Web Vitals daily for the first weeks
- Track your benchmark keywords and top pages against the baseline; investigate any template-wide dip fast
- Expect small turbulence for a few weeks: real losses that persist past a month mean something in the checklist was skipped
Key takeaways
- Benchmark before touching anything, you cannot protect what you never measured.
- One-to-one 301 mapping is non-negotiable; homepage mass-redirects are equity bonfires.
- Content parity matters as much as redirects: thinner templates re-rank thinner.
Frequently asked questions
How much traffic drop is normal after a redesign?
With a proper migration, low single-digit turbulence for two to four weeks. Double-digit drops persisting past a month indicate redirect gaps, content loss or crawl issues, auditable and usually fixable.
Should I redesign and migrate platforms at once?
It compounds risk but is often practical. The checklist stays identical; the redirect map and pre-launch crawl just carry more weight. Never add a domain change to the same launch without strong reason.
Can VTurnU rescue a redesign that already tanked?
Yes, recovery audits are a service line. We diff old crawls (or archives) against the live site, rebuild the redirect map and restore content parity. Speed matters; equity fades with time.