Why does Google show the wrong date for my page?
Rubric check: visible date that disagrees with the structured data (check id date_mismatch)
Often because the date on the page and the date in your structured data disagree. Rubric flags pages where the visible date differs from datePublished or dateModified in the markup.
Why it matters for SEO
Google picks the date it shows from several signals, including the visible date and the structured data. Its guidance is to keep them consistent. When they disagree, Google may show an old date, or not trust either one.
A wrong date makes a fresh page look stale in the results, and fewer people click it.
Does this matter for ChatGPT and AI Overviews?
AI tools often favour recent sources and may state a page's date in the answer. If your markup and your page disagree, the tool may report the wrong date, or treat an updated page as old.
The effect is hard to measure, but a single consistent date removes the doubt.
How Rubric scores it
StandardStandard checks are the baseline every other tier is measured against.
Why this tier: Conflicting dates confuse freshness.
It is judged on every page Rubric scores.
Every Rubric score starts at 100. When this check fails, it takes up to 12 points off. Even one failing page costs at least 6 points (half of the most), and the rest comes off as the share of affected pages grows. A warning costs less than a failure.
This check doesn't cap your score. It only takes off its own points.
From the engine's scoring files, scoring 2026-v2.1 (engine d5c591d).
How common it is
Found on 7 of 196 sites where Rubric could judge it (3.6%). That is 5 of 187 judged sites in Rubric's 313-site test set and 2 of 9 sites audited on Rubric between 11 Nov 2026 and 17 Nov 2026 under the current check rules (scoring 2026-11k or later). Measured 17 Nov 2026 with scoring 2026-v2.1.
How accurate the check is
Lab test: passed. On test pages built with this problem, it caught 3 of 3. On clean test pages, it stayed quiet 2 of 2 times. (Engine build bbcec7c.)
Real sites: people checked 5 of its findings by hand and 3 were wrong (60%). Last checked 14 Nov 2026. That's a small sample, so treat the rate as rough.
Holdout test 5 (sites the check had never seen): 0 of 3 findings judged wrong.
Lab as of 16 Nov 2026; judged findings as of 15 Nov 2026.
How to fix it
WordPress
- Check what your theme shows: the publish date, the updated date, or both.
- Yoast and Rank Math fill
datePublishedanddateModifiedfrom the post's real dates. If the visible date is typed by hand or comes from a custom field, make the theme show the post date instead. - If you show "Updated" on the page, make sure the theme prints the modified date (
get_the_modified_date()), not the publish date.
Shopify
- Blog articles show the published date set in the article editor, and the theme's markup uses the same field.
- If your theme or an app adds its own article markup, check it reads
article.published_atandarticle.updated_atand not a hard-coded or different date. - Edit the article's date in Content > Blog posts if it was set wrong.
Webflow
- On CMS templates, bind the visible date and the date in your schema embed to the same CMS field (for example Published On or a custom date field).
- Check the JSON-LD in your page's custom code uses that field, not a typed date.
- Publish.
Custom code
Print both from the same variable:
<time datetime="2026-11-10">10 November 2026</time>
<script type="application/ld+json">
{"@context":"https://schema.org","@type":"Article","datePublished":"2026-11-10","dateModified":"2026-11-10"}
</script>When you update a page, change the visible "updated" date and dateModified together.