Use explicit review dates—not incidental years
A page may mention 2026 in a forecast, historic table or product name. That does not prove it was published or reviewed in 2026. A defensible freshness system calculates age only from explicit structured or meta publication and modification dates. Keep the exact extracted value and evidence class beside the calculation.
If no explicit date is available, report freshness as unverified. Do not label the page stale and do not reward it for a year found in body copy. The correct action is to expose a truthful visible publication or last-reviewed date and align it with structured metadata after an accountable review.
Apply disclosed content policies
Different evidence moves at different speeds. IndexHalo uses operational defaults: 120 days for volatile decision content such as pricing, tax, law, regulation, incentives, news, tariffs and rates; 365 days for research, datasets, reports and claim-dense evidence; and 730 days for standard evergreen pages. These are planning controls, not universal legal requirements.
A customer may need stricter policies for medicine, finance, law or regulated communications. The report should always show the assigned content class, maximum age, rationale, explicit review date, age, next due date and exact acceptance test. A hidden composite freshness score is not enough.
Measure claim support and source movement separately
Connect exact public claims to adjacent sources through the evidence graph. Distinguish adjacent evidence, page-level evidence and unsupported claims. Then compare exact public source links across consecutive crawls. Show which links were retained, gained or removed and which pages currently use each source.
A removed source link is an observed page change. It does not prove that the source is broken, that the claim is false, or that the publisher acted incorrectly. A human must inspect the claim and current primary evidence.
A material regression occurs when source links disappear or new claims appear without corresponding evidence growth. The action should name the exact page, removed URLs, added claims, current support states and minimum completion threshold. Avoid vague instructions such as “add more citations.”
Join renewal risk to exact URL exposure
Renewal priority should reflect consequence as well as age. Join Search Console, Bing and analytics rows only where the landing page matches the measured URL. Preserve impressions, clicks, sessions, conversions and revenue in their original evidence classes. Join timestamped answer citations only by the exact returned URL.
This reveals the difference between an overdue page with no measured exposure and an overdue canonical owner cited across several monitored responses with material revenue. It does not turn search impressions into AI demand or prove that freshness caused performance.
Build an operational renewal calendar
Group pages into overdue, next thirty days, thirty-one to ninety days, later and date-unverified. Within each window, rank exact URLs by evidence regression, unsupported claims, high-severity findings and connected value. Assign research, regional, legal, editorial or publishing owners according to the content risk.
The calendar must preserve current strengths. A page with a current method, adjacent provenance, stable source ledger and strong measured outcomes belongs in a protection register. Its evidence should not be rewritten merely because a scheduled review arrived.
Verify renewal automatically
A complete renewal test should require a safely parseable public date within the saved policy, a minimum source count for claim-bearing content, and the absence of date-missing and source-gap findings. Claim-specific work should also require adjacent evidence for the exact claim fingerprint.
Changing a date alone cannot pass when the source or claim conditions remain weak. When the task is marked ready, a fresh crawl should evaluate the saved thresholds, preserve evidence of failure, and reopen the work automatically if a later crawl regresses.
Preserve original-language evidence
Dates, claims, URLs, source labels and review decisions must remain in the page’s original language. Multilingual keyword rules can help assign volatile content policies, but they do not translate evidence or replace regional subject-matter review. Jurisdiction, currency, terminology and legal scope remain local responsibilities.
The bottom line
Evidence freshness is not a cosmetic date field. It is a governed relationship between the current claim, its public source, the page owner, the review policy, the business exposure and the next proof. A premium GEO platform should show all six—then make the next crawl verify the repair.