AEO · Content and answer readiness · 5 credits
Content Freshness Checker: Date Signals
Find missing or conflicting date signals and review whether dated claims need a substantive update.
Content Freshness Checker 1.1.1 · price f23-v1 · retrieved at run time · Run it from an AI agent
Loading tool
What the Content Freshness Checker checks
Inspect dates in JSON-LD, meta tags, microdata, time elements and visible labels for conflicts or impossible values. Older dates and title years are prompts for editorial review.
- Dates in JSON-LD, meta tags and microdata
- HTML time elements and visible date labels
- Conflicting or impossible dates
- Older dates and title years worth an editorial review
What it does not do
- Deciding what content to update
- Rewriting content
- Tracking changes over time
Questions about the Content Freshness Checker
- Should I change the date to make content look fresh?
- No. Change dateModified only when the content changes substantively. A new date on unchanged content can conflict with other signals and mislead readers.
- Does an old date hurt a page?
- Not by itself. The checker treats older dates and years in titles as prompts to review whether the content still holds, not as errors.
- Why do conflicting dates matter?
- When markup, meta tags and the visible label disagree, search engines and AI systems have to guess which date is right, and may show the wrong one.
- How much does the Content Freshness Checker cost?
- 5 credits per run, shown before the run starts. An AI agent can run the same tool over the REST API or MCP with a workspace API key.
