Last updated 2026-06-10
Here is the pattern we have been called in to repair too many times: a company launches a beautiful new site, and weeks later organic traffic is down hard and nobody can say why. The why is almost never the design. It is that URLs changed without redirects, pages that quietly earned rankings were dropped or rewritten into something else, and internal links that told search engines what mattered were reshuffled. The equity was attached to specific URLs and specific content, and the relaunch threw it away without noticing it existed.
Our position is blunt: a redesign is a migration, and migrations are run with inventories, mappings, and baselines, not enthusiasm. This is a craft we practice with conviction because we practice it on our own properties, the same protocol, the same discipline, every time. Preservation and improvement are not in tension; the protocol below is exactly what frees a redesign to be ambitious safely.
AI earns its place in this work at the unglamorous layer: crawling and diffing every URL at scales manual review cannot reach, checking content parity between old and new pages, and validating redirect maps before launch. What AI does not decide is what each page is worth, that ranking comes from your traffic, rankings, and backlink data, read by an analyst. The build standard for the new site itself is covered under AI-ready website development.
What the engagement includes
Full URL inventory and equity ranking
Every URL on the current site crawled and scored by traffic, rankings, and backlinks, so nothing of value gets dropped by accident.
Keep, redirect, or retire mapping
Each URL assigned a fate on the new site, with one-to-one 301 mapping reviewed page by page for everything that earns.
Content parity on pages that rank
The topics, headings, and answers that earned each page its position carried forward deliberately, then improved, never accidentally deleted.
Pre-launch baseline
Rankings, organic traffic, and index coverage recorded before cutover, so post-launch performance is measured instead of debated.
Staged cutover and redirect validation
The full redirect map tested before launch and the new site crawled against the plan, so the first thing search engines meet is order, not 404s.
Post-launch monitoring
Index coverage, ranking movement, and crawl errors watched closely through the weeks after launch, with regressions triaged while they are still cheap.
Why redesigns lose rankings
Search equity lives in specifics. A URL accumulates years of backlinks, ranking history, and trust; a page holds the exact content that matched a query's intent; the internal link structure tells crawlers which pages the site itself considers important. A typical redesign changes all three at once, new URL scheme, rewritten pages, reorganized navigation, and then adds a new template's rendering and performance behavior on top. Search systems re-evaluate the whole site as the sum of those changes, and what reads to the team as a facelift reads to the machine as a different website wearing the same domain.
None of this argues against redesigning. Sites genuinely need rebuilding: design ages, platforms hit ceilings, and the structural standards that earn visibility in AI answers did not exist when most current sites launched. It argues for treating the equity as a first-class deliverable, with the same rigor as the design itself.
The preservation protocol
The sequence is fixed. Inventory: crawl everything, then rank every URL by the equity evidence, traffic, rankings, backlinks. Bucketing: each URL is kept and refreshed, redirected to its nearest surviving equivalent, or consciously retired, and money pages get their content parity checked so the substance that earned the ranking survives the redesign. Baseline: rankings and traffic recorded before anything changes. Cutover: redirects validated pre-launch, the new site crawled against the map, and launch staged rather than flipped blind. Then weeks of deliberate monitoring, because the work is not done when the site is live, it is done when the data says the equity transferred.
AI is woven through each step: full-site diffing that compares thousands of old and new pages for parity, log and crawl analysis that spots what search engines are actually hitting, anomaly detection on the post-launch metrics. The protocol used to be so labor-intensive that agencies skipped it and hoped. Now skipping it is purely a choice, and the wrong one.
A redesign should be an upgrade, not a gamble
Run this way, a redesign becomes the moment to bank improvements the old site could never ship: performance budgets met from day one, semantic structure and schema that machine readers parse cleanly, measurement wired through every conversion path, and templates built so the conversion testing program that follows can move fast. The protocol is not a tax on ambition; it is what lets you change boldly because you know exactly what must carry over.
We will also be honest about the floor: even careful migrations can dip briefly while search systems re-process the site. The difference is between a managed dip, planned for, monitored, recovering on schedule, and an unexplained collapse that takes quarters to diagnose. If a redesign is on your roadmap, book a call before the design work starts. A senior analyst will spend 30 minutes on what your current site has earned and what it will take to keep it.