Freshness conflicts: When your pages disagree about what is current

How do you settle a freshness conflict?

Name one source of truth per fact

Pick the page that owns each fact: pricing owns prices, the docs own limits, the changelog owns dates. Every other page either links to the owner or states the fact with the same value and the same date.

Update in place, with a visible date

Change the stale copy where it lives, and put a "Last updated" date on the page that is true. Do not move the date without changing the content; that settles nothing and Google's guidance treats dates as a description of real updates.

Rewrite the shape, not just the cell

If a comparison page is what the engines quote, fix the comparison page as a comparison: each row states what is live, what is coming, and when it was checked. A corrected fact buried in a paragraph below a stale table is still a conflict.

Remove what has no value left

An old announcement whose only content is a superseded fact can be removed. Let the URL return a plain not found and link your other pages to the current owner. A stale copy that stays live keeps voting.

Fix the copies you do not own

Review sites, directories and partner pages carry your old facts long after you change them. Update the listings you control and send the editors of the rest one line: the current fact and the page it lives on.

What does settling one conflict look like?

Take one fact through the whole process. Say the fact is "which plan includes AI crawler analytics".

Search. A search of the site finds it stated in five places: the pricing page, the feature page, the docs, an old launch post and a comparison page.

Compare. Three say "Growth and above". The comparison page, written before the feature shipped, says the feature does not exist. The launch post says "coming soon" with no date.

Check what the engines read. The comparison question is where the fact matters, and the comparison page is the one the answers cite. So that page is the urgent fix, and the launch post is the second.

Name the owner. The docs own the fact. Every other page states it in the same words, or links to the docs.

Fix. The comparison page's row is rewritten to state the fact as a sentence, with the date it was checked. The launch post gets a dated line at the top saying the feature shipped and linking to the docs. Nothing else needs to change.

Measure. The comparison question is re-read in the weeks after the fix, and the count of answers that repeat the old claim is compared with the count before.

Most conflicts are like this one: one urgent page, one or two stragglers, and a handful of pages that were already right. The work is finding which page is which, and that only takes an afternoon per fact once you know where engines are reading.

How do you keep conflicts from coming back?

Conflicts are created every time a fact changes and only one page is updated. The fix is a habit, not a project:

• When a fact changes, search for it before you ship. Every page that states the old value changes in the same release.
• Date every fact that will age. "As of" beside prices, limits and competitor facts.
• Re-read your own pages on a schedule. Attensira keeps a version of each page it knows about and re-reads it after 7 days, or about daily while an open suggestion targets it. A re-read that finds the page changed records the change, so you can see when a stale version went live or came back.

How does Attensira handle freshness conflicts?

A freshness conflict reaches buyers as a wrong claim, so that is where Attensira looks. For every question you track, on ChatGPT, Perplexity, Claude and Google AI, with Gemini from Growth, it records which of your pages each answer cited and pulls out the factual claims the answer makes about you. Every night it checks those claims against the facts you confirmed in your brand profile, and a claim your facts contradict is flagged once, with the pages the answer attached to it: usually the place the stale copy lives. You, or an automation listening for wrong claims, can then have the crew draft the change to that page and put it in your inbox as a pull request or a CMS draft. A change that states a price, a number or a competitor's name waits for your yes in every mode. After it ships, the questions attached to it are re-read at +7, +14 and +30 days, and the result is reported with its sample size.

That is the service of an SEO agency at the price of a tool: someone who reads your site the way the engines do, every day, and fixes what disagrees. If you want to see which of your pages the engines lean on today, start with the free audit, or read how ChatGPT reads and indexes content.