Why does my page show a date in the future?
Rubric check: publish or update date in the future (check id date_future)
Usually a time zone setting, a scheduled post, or a template that prints the wrong date field. Rubric flags pages whose publish or update date is later than today, in the visible text or the structured data.
Why it matters for SEO
Google picks a date to show from the page and its markup. A date that hasn't happened yet looks wrong, and Google may ignore it or show a different one. It can also make readers doubt the rest of the page.
Does this matter for ChatGPT and AI Overviews?
AI tools that weigh how recent a source is read the same dates. A future date is an obvious error, so it may be ignored, and it doesn't make a page look fresher. The effect is small, but the fix is usually one setting.
How Rubric scores it
MinorMinor checks cost a quarter to a half of a standard check when they fail.
Why this tier: Future dates look wrong.
It is judged on every page Rubric scores.
Every Rubric score starts at 100. When this check fails, it takes up to 6 points off. Even one failing page costs at least 3 points (half of the most), and the rest comes off as the share of affected pages grows. A warning costs less than a failure.
All the minor checks share one limit: together they can take off at most 25 points, however many of them fail.
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 0 of 196 sites where Rubric could judge it (0%). That is 0 of 187 judged sites in Rubric's 313-site test set and 0 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 2 of 2. On clean test pages, it stayed quiet 2 of 2 times. (Engine build bbcec7c.)
Lab as of 16 Nov 2026; judged findings as of 15 Nov 2026.
How to fix it
WordPress
- Check Settings > General > Timezone matches where you publish.
- Open the post and check the Publish date in the editor's sidebar. Scheduled posts aren't public, so a future date on a live post is usually a typo.
- If the date comes from an events or custom-field plugin, check which field the template prints as the post date.
Shopify
- Check Settings > General > Store defaults > Time zone.
- Open the blog post and check its Visibility date.
- If a theme or app adds a date to the structured data, check it uses
article.published_at.
Webflow
- Open the CMS item and check its date fields.
- Check the page binds the right field (for example a publish date, not an event date) to the visible date and to any JSON-LD in Page settings > Custom code.
- Publish.
Custom code
Store dates in UTC, print them with the right offset, and never output a date later than now:
<time datetime="2026-11-16T09:00:00+00:00">16 November 2026</time>