Keep, fix, merge, or retire

Content Refresh & Consolidation

A useful refresh leaves no module in limbo. The record shows what still earns its place, what needs correction, and what no longer has a job.

Each page is checked against current facts, current audience questions, and its neighbors. Every module then receives a documented decision: preserve, correct, merge, expand, or retire. Content owners managing an aging library who need a documented reason behind every page that stays, merges, or goes.

Every page in the library gets a written keep, fix, merge, or retire decision, backed by the evidence that drove it.

Specialist sorting page modules into preserve, correct, merge, expand, and retire decisions

Some of the 500+ brands we've worked with

See all references
  • BMW
  • Mustela
  • Yemek.com
  • Madame Coco
  • Obilet
  • Aksigorta
  • AVVA

From frozen baseline to release

The evidence behind every keep, merge or retirement

Published claims are checked against approved facts before we examine new questions or overlap elsewhere in the library. Editorial owners decide wording. Domain owners settle facts, while SEO and technical owners approve merges and retirements.

How we hold ourselves to it

  • One decision per module
  • A date is not freshness
  • Merges need an approved destination
  • External movement measured separately

  1. Freeze the current page and its job

    The exact version under review becomes the baseline. Later edits can then be judged against the page's original job and the value it already carried.

    A versioned baseline of the live page, its primary intent, protected modules, links, and first-party signals.

    AI assist
    Captures current content, internal links, headings, structured elements, and change history without editing the source.
    Human gate
    The content owner confirms the page job and the modules that need explicit protection.

  2. Diff published claims against approved facts

    The published claim, current approved source, original wording, and review date remain visible in the same comparison.

    A claim-and-source freshness diff with correct, stale, disputed, and unverifiable states.

    AI assist
    Extracts claims, dates, and sources from the current version and flags mismatches without rewriting them.
    Human gate
    The domain owner confirms the authoritative fact set and whether each discrepancy is material.

  3. Identify new questions and evidence gaps

    Current search, support, sales, and product evidence shows which questions are genuinely new.

    A question-and-evidence-gap map with audience, intent, proof need, and proposed destination.

    AI assist
    Clusters documented question inputs by intent and separates a new need from semantic similarity or competitor length.
    Human gate
    The strategist approves question validity, priority, and whether this page should answer it.

  4. Choose preserve, correct, merge, expand, or retire

    Every module receives one decision and a written reason. When the current version still works, the ledger records the evidence for leaving it alone.

    A module decision ledger with preservation notes, merge targets, and retirement dependencies.

    AI assist
    Compares overlap, dependencies, historical value, and reversibility across the available options.
    Human gate
    Content, SEO, technical, and client owners approve the page job and intervention for each module.

  5. Draft the smallest defensible change

    The revision closes the verified gap. Untouched claims stay untouched, and a new section appears only when a documented question requires one.

    An annotated revision with source, reason, owner, and acceptance check for every material edit.

    AI assist
    Produces a source-bound diff and flags any connective wording that adds unsupported meaning.
    Human gate
    Domain, editorial, legal, and brand owners approve changes inside their boundary.

  6. Release, annotate, and run regression checks

    Factual, link, extraction, accessibility, and page-job checks run again before we start watching external outcomes, which are measured over their own separate period.

    A post-refresh validation report with accepted changes, defects, confounders, and the next review date.

    AI assist
    Replays fixed checks, compares first-party results, and annotates documented platform or campaign confounders.
    Human gate
    An independent reviewer decides accept, correct, or roll back without changing the frozen baseline.

The decisions and the record

A handoff built for the next publishing decision

Publishers receive the decision, its evidence, and the frozen baseline in one place. The same record also shortens the next review.

  • Evidence-led refresh brief

    Page-by-page instructions saying which claim or module to preserve, correct, merge, expand, or retire, and why.

    Accepted when

    Lets the team spend review and production time only where the maintenance need is proven.

    Cadence: Reason documented

  • Reviewed content and consolidation specification

    Approved copy, canonical destinations, merge instructions, internal-link changes, redirect requirements, and unresolved claims that still need evidence.

    Accepted when

    Lets publishers release corrections and lets technical owners merge or retire pages without losing a validated user path.

    Cadence: Copy approved

  • Freshness, coverage, and preservation measures

    These measures tell us whether the refresh solved the actual maintenance need. Traffic and citation movement stay in a separate report.

    Accepted when

    Documented measurement rule: fact freshness, validated new-question coverage, preserved useful modules, and unsupported expansion. The scope, the pages it is counted against, and the time window are all fixed before any comparison.

    Cadence: Scope fixed pre-test

  • Post-refresh issue report

    The accepted changes, the defects that surfaced, the confounders we could name, and the next review date. It gets rebuilt at every affected release, with due or disputed claims reviewed monthly and page jobs, owners, and retirement candidates reassessed quarterly.

    Accepted when

    Supports acceptance, a targeted correction, or rollback without attributing platform movement to the refresh by default.

    Cadence: Reviewed quarterly

When aging pages need real decisions

Aging content needs a documented decision for every page

Bring this method into libraries where pages have aged, begun to overlap, or accumulated sections without a clear job. A current page that only needs a better opening answer calls for a smaller edit.

A good fit when

  • A page looks current and reads out of date — Product facts change and sources age while the publish date still looks recent.
  • Refresh means a new date and more words — The team expands pages without a documented question, a source, or a reason the section belongs on this URL.
  • Several URLs are doing one page job — Useful material sits across overlapping URLs, and nobody can say which page stays, which absorbs the rest, or what redirects.
  • The working record already exists somewhere — Live pages, approved facts, old versions, and the questions behind the review are available.
  • Published claims need checking against policy — We check each material fact, cited source, and regulated statement against its review date and owner.
  • Coverage expands only on a validated question — A search, sales, support, or product question needs evidence behind it before we expand the page.
  • Every module carries one named treatment — Preserve, correct, consolidate, expand, or retire, with its evidence and an owner who can reject the call.
  • Every change records where it came from — We record what changed, why, from which source, and how the released version performed against the original page job.

Better handled as other work when

  • You want length added for its own sake — Length alone earns nothing, so useful modules stay protected and expansion needs a documented question with evidence.
  • A newer date is expected to prove freshness — A recent timestamp is metadata. Freshness means the material claims, sources, and page job have actually been reviewed.
  • You want post-refresh movement credited — Ranking, citation, referral, and conversion move for other reasons, so none of it excuses a factual or usability defect.

People who watch how AI cites a brand

GEO work starts with recording what AI answers actually say about a brand today, then moves to the parts you can influence. The consultants below work on the specific capability this page covers.

Tools we use

Tools behind this work

  • Screaming Frog

    checks every page against its neighbors in one pass, the overlap this method decides on

  • Google Search Console

    the traffic history this page's own FAQ says is evidence, but not a keep decision on its own

  • Airtable

    holds the named treatment for every page alongside the evidence behind it

A recent date is not evidence of freshness

Put the next content decision on record

Share the current library, its approved facts, and the questions reaching your team. The review will show what stays, what needs correction, and where an approved merge path exists.
Review your content library

Questions we hear

We look at the page's current job, factual freshness, question coverage, overlap with its neighbors, and any proven first-party value. The evidence may support an update, a merge, retirement, or a documented decision to leave the module alone.