What date markers are
Date markers are the visible and machine-readable signals that tell a system when a page was published and when it was last meaningfully updated. That includes the human-readable byline date, the datePublished and dateModified fields in your structured data, and supporting hints like <time> elements, Open Graph article:published_time, and sitemap lastmod values. When those are missing or contradict each other, you have a date-marker problem.
The check flags a page that shows no date context at all, or shows dates that disagree across the on-page byline, the schema, and the sitemap. Both cases leave a reader, a crawler, or an AI assistant unable to judge how current the content is.
Why currency signals matter for search and AI
Freshness is not a ranking bonus you sprinkle on everything. It matters in proportion to how time-sensitive the query is. For "best laptop 2026" or "current mortgage rates," a 2019 undated page is a liability. For "how photosynthesis works," the date barely matters. The problem with missing markers is that you remove the system's ability to make that judgment at all, so it defaults to caution.
- Search results. Google can show a date next to your result when it can determine one confidently. A clear published or modified date can influence whether a user clicks, especially on news, pricing, guides, and anything with a year in the query.
- AI answers and GEO. Generative engines and answer boxes lean on recency to decide which sources to trust and cite. A page with an explicit, credible modified date is easier to select than one that looks undated or abandoned.
- Trust. A visitor who cannot tell whether advice is from last month or last decade bounces. Date context is part of the credibility of the page, not decoration.
One caution worth stating plainly: do not fake it. Bumping dateModified to today without changing anything is a habit Google has warned against, and it trains your own analytics to lie to you. Update the date when you update the content.
The signals and where they live
How to detect missing or conflicting dates
| Tool | What to check |
|---|---|
| Rich Results Test / Schema validator | Confirm Article schema exists and carries valid datePublished and dateModified in ISO 8601 format. |
| Screaming Frog | Custom extraction on the byline and on schema date fields, plus the sitemap crawl, to spot pages with no date or mismatched dates at scale. |
| Search Console URL Inspection | See how Google rendered the page and whether it parsed the dates you intended. |
| View source | Check the on-page <time> element and Open Graph tags against the visible byline. |
| Sitemap review | Confirm lastmod reflects genuine changes and is not stamped to "now" on every crawl. |
How to fix it, step by step
- Show a real date to readers. Put a visible published date on evergreen and article content. If the page has been genuinely revised, add an "Updated" date next to or in place of it.
- Wrap it in a machine-readable element. Use
<time datetime="2026-07-01">July 1, 2026</time>so the value is unambiguous, not just prose. - Add Article structured data. Populate
datePublishedanddateModifiedin ISO 8601, and make them match the visible dates. Do not invent a modified date that never happened. - Align the sitemap. Set
lastmodto the real last-substantive-change date, and only bump it when content actually changes. - Update dates only on real updates. When you revise a page, change the content first, then update the modified date and the sitemap together. Consistency across all three surfaces is the goal.
DO
- Show a real published date on articles and guides
- Add an updated date when you genuinely revise
- Keep on-page, schema, and sitemap dates in agreement
- Use ISO 8601 in
<time>and structured data - Bump
dateModifiedonly when content really changed
DON'T
- Ship time-sensitive content with no date at all
- Fake a fresh modified date to look current
- Let schema dates contradict the visible byline
- Auto-stamp
lastmodto now on every deploy - Hide the date so far down nobody can find it
What "good" looks like
A reader lands and immediately sees when the piece was published and, if relevant, when it was last updated. The Rich Results Test parses matching datePublished and dateModified. The sitemap lastmod lines up with the last real edit. When you revise the article, all three move together, and only then. The result is a page a person trusts and an AI system can confidently cite as current.
FAQ
Do I need both a published and a modified date?
Will adding a recent date boost my rankings?
Should evergreen pages show a date?
My schema date and my byline disagree. Which wins?
<time> element, the schema, and the sitemap all show it. Conflicting signals dilute trust and can suppress the date in search results.Wondering how many of your pages look undated or stale to Google and AI?
An audit will flag every page with missing, hidden, or conflicting date signals across on-page markup, structured data, and your sitemap, and tell you which ones actually matter.
Claude Vincent is a technical SEO consultant focused on crawlability, rendering, and AI-search visibility. He writes the field guides and case studies at SEO ProCheck, with a bias toward the durable, unglamorous work that decides whether search engines and AI answer engines can actually read and cite a site.
About SEO ProCheck
Technical SEO consulting and GEO strategy with 20 years of enterprise experience. Case studies, resources, and tools for search and AI visibility.
Work With Me
Technical SEO audits, GEO strategy, site migrations, and international SEO. Hourly consulting for teams who need hands-on support, not just reports.
Subscribe to our newsletter!
