MigrateSpot
MigrateSpot

How to redesign a website without losing what it has earned

A redesign should change how a company is experienced, not erase years of search history. This is the working method we use to protect URLs, rankings and links while everything else changes.

, 5 min read, by MigrateSpot

Most established websites look older than the companies behind them. They also tend to be worth more than they look. Years of published pages, inbound links and search history have built up a kind of equity that does not show up on a balance sheet, and a careless redesign can spend it in a single afternoon.

The usual advice is to change as little as possible, so that “nobody notices”. We think that sets the bar too low. A redesign should be noticed. What it should not do is break the things search engines and returning visitors already rely on. The method below is how we separate the two.

Start with a complete URL inventory

Before anyone opens a design tool, list every URL the current site has ever exposed. That means more than the pages in the navigation. Combine the XML sitemap, a full crawl of the live site, the URLs Google reports in Search Console, the landing pages in your analytics and, where available, the target URLs of external links from a backlink tool.

Each source catches things the others miss. Crawls find orphaned templates and parameter variants. Search Console finds pages that are no longer linked internally but still receive impressions. Backlink data finds old campaign pages that nobody remembers but other websites still point to. The inventory is the single list against which every later decision is checked.

Read the data before deciding anything

Search Console keeps around 16 months of performance data. Export clicks and impressions per page and per query for the full period, so seasonal pages are not judged on a quiet month. In GA4, look at landing pages and the conversions or key events they lead to: a page with modest traffic can still be where most enquiries begin.

From these exports, three questions matter for each URL. Does it bring people in from search? Do other sites link to it? Does it contribute to enquiries, sign-ups or sales? A page that answers no to all three is a candidate for retirement. A page that answers yes to any of them needs a deliberate plan.

When the data is missing

Many sites we see have gaps, and it is better to say so than to pretend otherwise. Search Console may never have been verified, or only for one protocol or subdomain. Analytics history may have ended with Universal Analytics, whose data Google has since deleted. Sometimes the only record is the live site itself.

In those cases we lower our confidence rather than our standards. Verify a Search Console domain property immediately, because every week of data collected before launch helps. Use server logs if the host keeps them; they show which URLs are actually requested, by people and by crawlers. Use a backlink tool to find linked URLs. Where nothing tells us a page is unimportant, we redirect it to its closest equivalent instead of letting it fail.

Keep, improve, merge or retire

Every URL in the inventory gets one of four decisions. This is where a redesign becomes an editorial project rather than a technical one.

  • Keep: the page performs and its URL stays. The content moves into the new design with its substance intact.
  • Improve: the page has demand but the content is thin, dated or hard to use. It keeps its URL and gets rewritten.
  • Merge: several pages compete for the same intent. They become one stronger page, and the others redirect to it.
  • Retire: the page has no traffic, no links and no business role. It is removed and either redirected to the nearest relevant page or, if nothing fits, returns 404 or 410.

Map every redirect, one to one

Any URL that changes needs a permanent, server-side redirect (a 301 or 308) to its most relevant new equivalent. Google's guidance on site moves is explicit that redirects should map old URLs to their specific new counterparts and stay in place for a long time, generally at least a year.

Avoid two common shortcuts. Sending everything to the homepage tells search engines the old page has no real successor, and Google may treat such redirects as soft 404s. Chaining redirects (old to interim to new) slows crawling and dilutes the signal. Collapse every chain so each old URL resolves in a single hop, including URLs that were already redirecting before the project began.

Canonicals and structured data

Each new page should declare a self-referencing canonical URL that matches its final, redirected address, its sitemap entry and its internal links. Mixed signals, such as a canonical pointing to a URL that redirects elsewhere, are a frequent cause of slow re-indexing after launch.

Structured data deserves the same care. Carry over what was valid, such as Organization, Article or BreadcrumbList markup, and only describe what is visible on the page. Google's structured data policies are clear that markup must reflect the content users can see. A redesign is a good moment to fix markup that drifted out of date.

A launch checklist

  1. Crawl the staging site and confirm every page returns 200, carries the right canonical and is not blocked by robots rules or noindex tags that were only meant for staging.
  2. Run the full list of old URLs against the redirect rules and check that each resolves in one hop to a 200 page.
  3. Update internal links so they point directly to final URLs instead of relying on redirects.
  4. Publish a new XML sitemap and submit it in Search Console.
  5. Check that analytics, consent and conversion tracking fire on the new templates.
  6. Annotate the launch date in your reporting so later changes can be read in context.

The first 90 days

Some movement in rankings after a significant redesign is normal while search engines recrawl and reassess the site. The goal of monitoring is to tell ordinary turbulence from real problems early enough to act.

For the first weeks, check Search Console's page indexing report and crawl stats, the 404s appearing in server logs, and impressions for the pages that carried most value before launch. Compare like with like: the same pages, the same queries, the same weekdays. After that, a weekly review is usually enough until the 90-day mark. If an important page loses visibility and stays down, look first at what changed for that specific URL: its redirect, its content, its internal links.

Sources

Read next

Your next website starts with the one you already have.

Show us your current website. We'll explore what it could become.

Reimagine my website