What Survives the Launch: A Ninety-Day Audit of Inherited Content on Rebuilt UK Sites

A rebuild is rarely the moment a UK site becomes new. More often, it is the moment an old content estate acquires a new front end, a refreshed redirect map and a set of templates that make inherited copy look more current than it is. The launch is visible; the inheritance is not. That gap is where search equity, editorial credibility and commercial intent are quietly lost.

The practical problem is not that legacy pages exist. It is that nobody can say, with evidence, which ones still belong. Pages may have survived the migration untouched, been rewritten by a delivery team under time pressure, or been carried over despite describing a proposition the business no longer sells. A ninety-day inheritance audit gives the organisation a defensible account of what it now owns.

Launch day is not the audit

Most rebuild assurance stops at redirect coverage, status codes and template rendering. These are necessary checks, but they answer an engineering question: did the old URLs resolve? They do not answer the editorial question: should the destination page exist in its current form?

The distinction matters because UK rebuilds commonly compress content decisions into a design programme. Legacy URLs are mapped to their nearest new equivalent, metadata is inherited from a spreadsheet, and body copy is retained because removing it feels riskier than keeping it. By launch, the site may be technically coherent and editorially unresolved.

The first ninety days should therefore be treated as an inheritance period, not a victory lap. The objective is to establish three inventories: pages that survived, pages that were materially rewritten, and pages whose claims now conflict with current positioning. Each inventory requires a different response.

Build the inheritance register

Start with a complete URL-level register rather than a sample. For each pre-launch URL, record the final status, the destination URL, the number of hops, the canonical target, the indexability state and the template family. Then add three editorial fields: whether the content is unchanged, revised or newly written; whether the page still reflects current products, services or policies; and whether it retains meaningful search demand or internal links.

This register should be owned jointly by SEO, content and the rebuild delivery lead. A purely technical register will miss positioning drift; a purely editorial register will miss redirect chains and orphaned pages. The value comes from combining both views on one row per URL.

Where a legacy URL has been redirected to a category page, do not assume equivalence. A redirected product page may have carried comparison intent that a category template cannot satisfy. Where a legacy page has been rewritten, compare the pre- and post-launch copy at section level. Silent rewrites are common in rebuilds: an old service page becomes a generic capability page, losing the specific terms, proof points and local references that earned it visibility.

Score for keep, rewrite or retire

A simple scoring model makes the first ninety days manageable. Score each URL from one to five across five dimensions, then weight according to the site's commercial model. A reasonable starting weighting for a UK lead-generation or ecommerce estate is:

• Demand evidence (30%): impressions, clicks, conversions or qualified enquiries attributable to the URL or its query cluster.
• Positioning accuracy (25%): whether the page describes what the business currently offers, in the language it currently uses.
• Search equity (20%): external links, internal links, historical rankings and redirect integrity.
• Conversion fit (15%): whether the page's intent matches an available next step, from enquiry to purchase to dealer locator.
• Risk (10%): regulatory, legal, pricing or reputational exposure if the page remains live.

Multiply each score by its weight and rank the estate. The output is not a mandate but a triage. High-demand, high-accuracy pages are keepers. High-demand pages with weak positioning are rewrite candidates. Low-demand, low-equity pages with weak conversion fit are retirement candidates, subject to redirect and internal-link remediation. High-risk pages should be reviewed immediately, regardless of traffic.

Treat redirects as editorial decisions

Redirect maps are often built by matching URL patterns rather than user intent. That is understandable during a rebuild, but it produces inheritance debt. A redirect from an old buying guide to a product category may satisfy a status-code test while failing the searcher. The audit should sample redirect destinations by template and intent type, not merely by volume.

For each redirect, ask whether the destination page would satisfy the query that the old URL served. If it would not, the correct action may be to rebuild a small number of high-equity pages rather than redirect them. In other cases, a redirect to a closely matching page is appropriate, but the destination should be strengthened with the old page's unique proof points, terminology and internal links.

Also check for chains and loops introduced by successive campaigns, locale changes or abandoned microsites. A rebuild is an opportunity to flatten redirect paths, but only if someone owns the map after launch.

Metadata is where positioning drift shows

Title tags and meta descriptions are frequently inherited wholesale. That preserves continuity but also preserves outdated propositions. A page may still rank for a term the business no longer prioritises, or describe a service in language that conflicts with the current sales conversation.

Audit metadata alongside body copy. Flag pages where the title, H1 and opening paragraph disagree about the offer. These are not cosmetic issues. They affect click-through, landing-page confidence and the consistency of the brand across paid and organic search.

Run the ninety days as a managed programme

Weeks one to two: complete the register and identify high-risk contradictions. Weeks three to six: score the estate and publish a keep, rewrite and retire list with owners. Weeks seven to ten: execute the highest-value rewrites, redirect fixes and retirements. Weeks eleven to thirteen: re-crawl, re-measure and hand the register into business-as-usual governance.

The final deliverable should be a living inheritance register, not a slide deck. It should show which pages survived, which were changed without documentation, and which were retired with a deliberate redirect. That record is the difference between a rebuild that launched and a content estate that was actually audited.