Scanner
Stale Content Scanner
An assistant quotes your page with total confidence, including the part written three years ago. This finds the sentences that carry an expiry date so you can fix them before they are quoted back to a customer.
- Finds expiring claimsYears, prices, counts
- Flags roadmap language“Coming soon” ages badly
- Paste, never fetchNothing leaves the page
Check it
Paste it here
Result
- Old year references —
- Prices or currency amounts —
- Roadmap or soon language —
- Time-relative words —
- Counts that drift —
- Highest risk —
Not everything flagged is wrong. A price is fine if it is current; the point is that an assistant cannot tell, and will quote it either way.
What the result means
“Coming soon” has no expiry date
Written once, it stays true-looking forever. An assistant will tell a customer a feature is coming soon three years after it shipped, or after it was cancelled.
A price on a page is a promise to a retriever
Assistants quote prices with no hedging. If an old pricing page is still indexed, somebody is being quoted last year's number right now.
Anchor time-relative words to a date
“Currently” means nothing to a model reading a fragment. “As of March 2026” means something, and lets the assistant tell the reader how old the claim is.
Counts drift silently
“Trusted by 200 companies” was true once. Either update it on a schedule or write it in a form that does not decay.
Questions
No. A current price is fine. The point is that a retriever cannot tell current from stale, so anything with an expiry date needs an owner and a review date.
Either update the claim, anchor it to a date, or remove the page from what the assistant is allowed to read. All three are valid.
No. It finds the mechanical signals of decay. Judging whether a claim is still true is a job for someone who knows the answer.
Want this run against your whole site?
Tell us the page your assistant lives on and the questions you care about. A person runs them and sends back the raw answers.