AI still cites your old page. How do you replace stale evidence without losing discovery?

Direct answer: treat a stale page as an evidence migration, not a copy edit. First identify the questions, links, citations, languages, and commercial outcomes the URL still serves. Then choose one of five actions: update in place, consolidate with a permanent redirect, keep only a canonical variant, archive with an explicit status, or retire with 404/410. Publish the successor before removing useful signals, update internal links, canonical, hreflang, structured data, and the sitemap, then observe discovery and conversion through at least one recrawl cycle.

This is a commercial problem. A service page may still promise an old scope, a comparison may cite a retired capability, and an AI answer may repeat a policy that changed. Publishing another page without reconciling the old one splits authority and leaves the buyer between two truths. The https://makinai.co/insights/en/company-search-absent-ai-answers-geo-plan explains how to establish initial visibility; this article addresses maintenance after public evidence already exists.

Use the Public Evidence Supersession Contract

• Original job — the question, decision, audience, language, market, and funnel stage that made the URL useful.
• Current state — which offers, claims, prices, policies, people, examples, and sources remain valid, changed, or expired.
• Successor — the URL and section that will answer now; no migration starts without a useful destination or explicit retirement decision.
• Action — update, consolidate and redirect, canonicalize, archive, or remove, with the reason recorded.
• Signals to preserve — backlinks, traffic, bookmarks, referrals, internal links, hreflang, schema, and commercial history.
• Effective dates — datePublished, dateModified, business effective date, accountable source, and next review.
• Tests — HTTP status, destination, self-canonical, locale alternates, sitemap, rendering, structured data, analytics, and rollback.
• Outcome — question answered, stale citation observed, qualified session, lead, and opportunity when measurement supports it.

Give the contract an owner. Content owns the assertion; the service or product owner confirms the offer; legal validates obligations; SEO/GEO designs the migration; engineering implements status, redirects, and markup; analytics preserves comparison; sales reports misaligned conversations. The https://makinai.co/insights/en/ai-marketing-copilots-inconsistent-answers-knowledge-layer covers internal source alignment; this project governs truth already published.

Choose the action by the job the page still performs

• Update in place when intent, offer, and audience remain the same and the URL holds discovery and links. Make a material correction and use an accurate dateModified.
• Consolidate with 301/308 when several pages compete for the same job and one successor is clearly stronger. Map each old URL to a relevant destination, not the home page.
• Use rel=canonical when truly duplicate or near-duplicate versions still need to exist. Canonical is a signal; it does not erase a stale promise or replace a redirect.
• Archive when historical, regulatory, or reference value is real. State clearly that the page is not the current offer and link to the current version.
• Return 404/410 when there is no successor and keeping the page creates risk or confusion. Remove it from internal links and the sitemap.

Google recommends permanent redirects for moved URLs, self-canonicals on successors, and avoiding irrelevant redirects. It also describes canonicalization as a signal rather than an absolute directive. Sitemap lastmod should represent a significant, verifiable update. Visible dates, datePublished, and dateModified should tell the same story in Article or BlogPosting markup. These steps reduce ambiguity; they do not force a search engine or AI system to refresh immediately.

Migrate the multilingual group, not one isolated page

If PT, EN, and ES represent the same article, make a decision for all three. Updating English alone can leave hreflang pointing to stale Portuguese or Spanish evidence. Each successor needs its own canonical, reciprocal alternates, and localized metadata. If an offer does not exist in one market, do not translate the promise: remove the relationship or publish an appropriate market explanation.

Illustrative example: a consulting offer changed scope

A hypothetical company has 26 pages about a service that no longer includes implementation. The inventory finds nine URLs with traffic, four material backlinks, three divergent translations, and two pages still producing leads that expect execution. These figures are illustrative, not a benchmark or MAKINAI client case.

The team keeps and materially updates the main URL, consolidates seven redundant articles with specific redirects, archives one contractual guide with historical status, removes three pages without successors, repairs hreflang and internal links, and separates successor visits from qualified leads. The job is not deleting content; it is aligning discovery and expectations with what the company can deliver now.

Run a six-week cluster pilot

• Week 1 — select one service cluster with 20–40 URLs and capture search, referral, lead, and sales-question baselines.
• Week 2 — inventory claims, sources, links, locales, backlinks, markup, sitemap entries, and conversions; classify risk and value.
• Week 3 — approve the URL→action→destination map with content, business, legal, SEO/GEO, engineering, and analytics.
• Week 4 — stage successors, redirects, canonicals, dates, hreflang, internal links, sitemap changes, and events.
• Week 5 — crawl the cluster, test statuses and variants, validate analytics, and rehearse rollback and no-successor cases.
• Week 6 — release, monitor Search Console, AI referrals, entry pages, and CRM, then repair, expand, or stop.

Cost grows with URL and locale count, CMS debt, redirect access, backlink value, regulated claims, fragmented owners, personalization, analytics history, and monitoring frequency. Updating preserves continuity but may obscure a material change; redirecting concentrates signals but removes specific coverage; archiving preserves transparency but remains discoverable; retirement reduces risk but can waste links without a relevant successor.

Measure supersession, not just recrawling

Track inventory coverage, decided URLs, redirect/canonical/hreflang errors, sitemap consistency, repair time, old-versus-successor impressions and clicks, observed AI citations, qualified sessions, leads, and misaligned sales conversations. OpenAI says allowing OAI-SearchBot makes content eligible for ChatGPT summaries and snippets and that referrals can be tracked in analytics. Eligibility does not guarantee inclusion, fast refresh, or causal attribution.

Models, indexes, and caches refresh at different speeds, and answers vary by prompt, market, and date. Fewer stale citations alongside successor growth is operational evidence, not proof of incremental revenue. The https://makinai.co/insights/en/measure-ai-search-visibility-pipeline-geo separates observation, referral, qualification, and pipeline; the https://makinai.co/insights/en/ai-referral-traffic-conversion-website-crm-routing carries context into CRM.

If stale pages still attract buyers to an offer that changed, bring MAKINAI at https://makinai.co/services/en/data-content-intelligence-systems one URL cluster, three outdated-answer examples, the locale map, and affected leads. We can scope the smallest supersession contract and pilot without turning it into a full-site redesign.