Skip to content
Search Experts

Cross-industry case study

Rebuilding a Website Without Throwing Away the Search Equity It Already Earned

Website redesigns create an unusual SEO risk. The site may look better after launch while performing worse in search.

URLs change. Content disappears. Internal links move. Page intent shifts. Redirects are missed. Navigation authority changes.

This case study documents the methodology we use when improving a website while protecting the search equity already attached to its existing architecture.

Discuss a situation like this

Migration framework

  1. Inventory
  2. Map
  3. Preserve
  4. Redirect
  5. Launch
  6. Validate
  7. Monitor
Written by
The Search Experts team
Reviewed by
Search Experts search strategy review
Published
Updated

The client is not identified. Names, screenshots and figures are published only with explicit written approval and verified source data.

The problem

Redesign Decisions Can Become SEO Decisions

Most migration damage is not caused by a single catastrophic error. It accumulates from small choices made for design reasons with search consequences nobody priced in.

Old site

  • URLs
  • Content
  • Internal links
  • Rankings
  • Backlinks

Redesign

New site

Risk points

  • URL removed
  • Content shortened
  • Title changed
  • Internal link removed
  • Redirect missing
A redesign changes several ranking inputs at once. Each one is a decision, whether or not anyone made it deliberately.

Principle

We Treat Existing URLs as Assets

Before changing an established URL, we evaluate what it currently carries.
  • Rankings it currently holds
  • Traffic it currently receives
  • Backlinks pointing to it
  • Internal links pointing to it
  • The search intent it satisfies
  • Its historical value over time
  • The replacement destination, if any

Framework

Inventory, Map, Preserve, Redirect, Launch, Validate, Monitor

  1. Inventory

    Every existing URL, with its rankings, traffic, links and internal-link position recorded before anything changes.

  2. Map

    Each old URL assigned a destination on the new architecture, matched on intent rather than on visual similarity.

  3. Preserve

    Content, headings and depth that earned the ranking are carried across instead of trimmed for layout reasons.

  4. Redirect

    Permanent redirects implemented for every changed URL, with chains and loops removed before launch.

  5. Launch

    Release with crawl access, canonicals, sitemaps and robots directives verified rather than assumed.

  6. Validate

    Post-launch crawl and index checks against the inventory: every mapped URL resolves where it should.

  7. Monitor

    Indexation, rankings and errors tracked against the pre-launch baseline for long enough to catch delayed effects.

Each stage has an exit condition. A migration that skips validation is discovered by the rankings, not by the team.

Internal links

Internal Links Need to Move With the Architecture

A page that loses its inbound internal links loses the signal that made it important, even when the URL itself survives the migration.
  1. Record which pages link to each important URL before the rebuild.
  2. Rebuild those links on the new templates, not only in navigation.
  3. Re-point contextual links inside body content to the new destinations.
  4. Check for orphan pages that exist but are no longer linked from anywhere.
  5. Confirm the new navigation still routes authority to commercial pages.
Implementation detail lives in technical SEO.
Observation
New templates dropped contextual body links that previously supported key pages.
Decision
Treat internal links as part of the migration map rather than as design decoration.
Implementation
Link inventory rebuilt on the new templates and contextual links restored to their mapped destinations.
Result
Awaiting verified data before publication.
Observation
Some legacy pages had no place in the new navigation and would have been orphaned.
Decision
Either give the page a home in the new structure or consolidate it into the page that owns the intent.
Implementation
Orphan candidates were re-linked or redirected, with no page left reachable only by sitemap.
Result
Awaiting verified data before publication.

Sequence

How the Engagement Progressed

Dates are published only where they have been confirmed. The sequence matters because it separates deliberate strategy from coincidental movement.

  1. Baseline

    Full URL, ranking, link and traffic inventory captured.

  2. Audit

    Intent and value assessed for every established URL.

  3. Architecture

    New structure mapped against the existing inventory.

  4. Implementation

    Content preserved, redirects built, internal links rewired.

  5. Search response

    Post-launch crawl, index and ranking behavior validated.

  6. Measurement

    Retention and recovery measured against the baseline.

Results

What Happened After Implementation

Indexed-URL stability, organic traffic retention, ranking retention, technical error changes and post-migration growth are published only once measured against the recorded pre-launch baseline.

The evidence

Verified performance data is being prepared for publication.

This case study documents the diagnosis, the decisions and the implementation. Results are published only once the underlying figures have been exported from the measurement system, checked against a matching baseline period and approved for release by the client.

Lessons

What Other Businesses Can Learn

These generalize from the case. They are not a promise that another business will see the same outcome.

  1. Inventory before design

    You cannot preserve what you never recorded. The baseline has to exist before the first template is approved.

  2. Map on intent, not on layout

    The right redirect destination is the page that answers the same question, not the page that looks most similar.

  3. Internal links are part of the migration

    Rankings often fall because supporting links disappeared, not because the URL changed.

  4. Validation is a deliverable

    Launch is the middle of the project. The post-launch crawl against the inventory is what proves the work.

  5. Monitor longer than feels necessary

    Migration effects surface over weeks. A single good week after launch is not confirmation.

Case study FAQs

Because a redesign changes several ranking inputs simultaneously — URLs, content depth, internal links, titles and page intent. Any one of them can reduce visibility, and when they change together the cause is hard to isolate afterwards.

Bring Us a Situation Like This One.

Describe your market and current architecture, and we will walk through how we would diagnose it.

Contact Search Experts