Content freshness: show Google and AI engines your page is current
Contents
A page with no date is a page an engine has to guess about. Google estimates when a page was published or updated, and may show that date in results. AI tools that cite pages also read dates as one signal of whether a page is still worth quoting. This post covers what is documented, what is folklore, and which findable checks test dates.
Why do dates matter to search engines and AI tools?
Google's publication dates guidance says its systems use multiple factors to estimate a page date, because any single signal can be unreliable. When the estimate is useful, Google shows a date next to the result. A page that says "Updated March 2026" earns trust a dateless page cannot.
For AI citations, the evidence is thinner but points the same way. Ahrefs analyzed about 17 million cited URLs and reported that AI assistants cite somewhat fresher pages than Google's organic results, with the strongest recency preference in ChatGPT and little to none in AI Overviews. The same study found the average cited page was still years old. The lesson: dates help, stale facts hurt, and nothing here is a citation guarantee.
What does Google actually document?
Three things, all in the publication dates guide:
- Show a prominent, clearly labeled visible date, such as "Published February 4, 2019" or "Last updated: Feb. 14, 2018".
- Add structured data on a CreativeWork subtype such as Article or BlogPosting, with
datePublishedanddateModifiedin ISO format, ideally with a timezone. - Keep the visible date and the markup consistent, never use a future date, and date the page itself, not the event it describes.
Google also says it does not guarantee a date will appear, even when you follow all of this. See JSON-LD schema basics for how to add the markup.
Which date checks does findable run?
Six scored checks in the GEO family cover dates, plus one SEO schema check. The article checks skip themselves when the page is not an article, so a landing page is not punished for lacking a publish date.
| Check id | What it checks | Fix in one line |
|---|---|---|
geo_freshness | A time element, a recent year in text, or a schema dateModified | Show a real date somewhere |
geo_time_element | A <time> tag is present | Wrap dates in <time> |
geo_date_published | datePublished in schema or article:published_time | Declare the publish date |
geo_date_modified | dateModified in schema or article:modified_time | Declare the modified date |
geo_modified_after_published | Modified date is not earlier than publish date | Keep dates honest |
geo_visible_date | A visible published or updated date in the text | Show the date to readers |
article_dates | Article schema dates are valid ISO dates | Use ISO format in markup |
The full list with scores lives in every GEO check.
How should I mark dates in HTML?
Wrap visible dates in a time element with a machine-readable datetime attribute. It is valid HTML and makes the date unambiguous to any parser. Google does not document it as a date signal, but it does no harm and other readers use it.
<p>Published <time datetime="2026-11-05">November 5, 2026</time></p>In structured data, both properties together:
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "Example headline",
"datePublished": "2026-11-05T08:00:00+06:00",
"dateModified": "2026-11-05T09:20:00+06:00"
}The meta tags article:published_time and article:modified_time count for findable too, and some platforms read them, but Google's supported meta tags list does not include them. Schema markup is the documented path.
Does bumping the date alone work?
No. Google's sitemap docs are blunt about lastmod: it is used when it is consistently and verifiably accurate, and it should reflect a significant update, not a trivial change like a copyright-year refresh. The same honesty applies to dateModified. Engines can compare claims against what actually changed, and a page that claims freshness it does not have is a trust problem, the same way a mismatched canonical is.
Update the date when you update the facts. Then the signal and the page agree.
What is the quick fix list?
- Show a labeled visible date near the title, wrapped in
<time>. - Add
datePublishedanddateModifiedin ISO format to your article schema. - Keep the visible date and the markup identical.
- Update dates only with real changes, and fix what went stale while you are in there.
Then run findable and look for the checks above. For the wider picture of what makes a page worth citing, see SEO vs AEO vs GEO.
FAQ
- Does changing dateModified update my date in Google?
- Not by itself. Google estimates a page date from several signals and wants the visible date and the markup to match. It also does not promise to show any date.
- What does the geo_freshness check test?
- It passes when the page has a time element, a year from 2024 to 2029 in its text, or a schema dateModified. It is a pattern match that shows a signal exists, not that the date is true.
- Should every page show a visible date?
- Article-like pages should. Landing pages and evergreen product pages can skip them. The article date checks skip themselves when the page is not an article.
- Does sitemap lastmod help?
- Only when it is honest. Google says it uses lastmod when the value is consistently and verifiably accurate, and means a significant update, not a copyright-year bump.
- Do AI tools only cite fresh pages?
- No. In a large Ahrefs study the average cited page was still years old. Freshness is a relative advantage, strongest for time-sensitive topics.
How does findable score a page?
| Family | Weight | Question it asks |
|---|---|---|
| SEO | 50% | Can crawlers read and index this page? |
| AEO | 25% | Is it easy to lift an answer from this page? |
| GEO | 25% | Does the page give a generative model a reason to cite it? |
The hosted audit waits up to 10 s for a page and fetches at most 5 MB. It reads robots.txt and llms.txt up to 512 KB each.
More guides
- Every findable AEO Check ID and How to Fix It
- All 35 AEO checks in findable explained, from aeo_faq to aeo_summary. See what each id tests, how loose the test is and how to fix it. AEO is 25% of the score.
- Author Markup and E-E-A-T: Show Engines Who Wrote Your Page
- E-E-A-T lives in Google's rater guidelines, not its ranking code. See what author markup really does, what Google documents, and which findable checks test it.
- Canonical Tags and Duplicate Content: How to Get Them Right
- Use one canonical link per page that points to its own absolute URL. Learn the checks canonical, canonical_self and canonical_absolute and fix them.
- FAQ Schema for Answer Engines: Markup and Checks
- How to add FAQPage JSON-LD that answer engines can lift, and how findable tests aeo_faq, aeo_faq_count and faq_valid. Includes a working example.
- Get Findable in 15 Minutes: A Step by Step Checklist
- Install findable, audit a page and your site, fix the top failures, then add MCP, the web UI, the API and a CI gate. Every step has a copy-paste command.
- Every findable GEO Check ID, Plus AI Crawler Checks
- All 27 GEO checks in findable explained, plus the unscored Site checks for GPTBot, ClaudeBot and llms.txt. GEO is 25% of the score. Fixes included.
- Heading Structure for AI Answer Engines
- Write headings that AI answer engines can cite. Learn what aeo_question_headings, aeo_answer_after_question, aeo_section_length and five related checks test, and how to fix each one.
- Image Alt Text, Dimensions and Lazy Loading Explained
- Fix img_alt, img_dimensions, img_alt_quality, img_lazy_loading and img_modern_format. See what each image check in findable tests and how to pass.
- JSON-LD Schema Basics: What findable Checks and Why
- Learn what JSON-LD is, which schema.org types findable validates, and how to fix jsonld_valid, jsonld_context and empty or relative values.
- llms.txt: What It Is and How findable Checks It
- llms.txt is a plain Markdown file at your site root that points AI tools to your key pages. See the llms-txt check and how to write the file.
- How to Write a Meta Description That Passes findable
- Write a meta description of 120 to 160 characters, one per page, that matches the page. See the checks desc_exists, desc_length and desc_single.
- Open Graph and Twitter Cards: Fix Your Share Previews
- Add og:title, og:description, og:image, og:url and twitter:card so links unfurl well. See every social check findable runs and how to pass it.
- robots.txt and AI Crawlers: GPTBot, ClaudeBot, PerplexityBot
- How robots.txt rules decide whether GPTBot, ClaudeBot, PerplexityBot and Google-Extended can fetch your page, and how findable tests each one.
- Every findable SEO Check ID and How to Fix It
- A plain guide to all 98 SEO checks in findable, from title_length to csp. See what each id tests, when it passes and the fix. SEO is 50% of your score.
- SEO vs AEO vs GEO: The Difference in Plain Words
- SEO, AEO and GEO each target a different reader: a search crawler, an answer box, or a generative AI model. See what wins in each and how to check them.
- Why AI Answer Engines Skip Your Site and How to Fix It
- ChatGPT, Perplexity and Claude may ignore your pages for five fixable reasons, from robots.txt blocks to missing answers. Learn each cause and its check id.