Article markup and visible dates disagree

Why it matters

Google recommends consistent equivalent dates in visible content and structured data.

What to do

1. Read both original date values, their roles, source locations and possible time intervals.
2. Correct the mismatched value using the actual publication or update history; keep those two roles separate.
3. Include a timezone when it is known, then run a new full audit.

When to leave it as it is: A confirmed same-role difference within the 48-hour tolerance is clean; a comparison that crosses the threshold is unverified.

What we read

We read a complete original 200 HTML response and its JSON-LD, microdata and RDFa. Only one primary Article or its official schema.org 30.1 subtypes counts, explicitly tied to this page by url, mainEntityOfPage or the current WebPage mainEntity; a URL path or template is not used to guess that a page is an article.

The static local header must belong to one explicit main or article region and contain one headline, or a bounded metadata prefix around it before the first body paragraph. Metadata before the header and after a headline-only header is included. Known hidden, inert, inline-style, citation and form content is excluded; external CSS is not evaluated.

A versioned source-owned grammar recognizes ISO text and bounded English/Ukrainian labels and month formats. IANA validates the original declared language only; it does not supply date formats or byline patterns.

Only the primary Article datePublished/dateModified is paired with the same Published/Updated role in its local visible text. A generic unlabeled date or another entity date does not supply a pair.

Zoned timestamps are exact instants. A timezone-less day, month, year or datetime in markup covers every instant allowed by the existing grammar, including offsets up to 23:59 in either direction. No timezone is guessed.

A finding requires the minimum possible gap to exceed 172800 seconds. Clean requires the maximum possible absolute gap to be at most 172800 seconds; otherwise the comparison is unverified. Equal date-only text can remain unverified because the unknown timezones can differ.

Example & evidence

Illustrative same-role conflict beyond 48 hours.

"datePublished": "2026-10-01T12:00:00Z"
<p>Published: 2026-10-10T12:00:00Z</p>

Both exact instants describe publication, and they are nine days apart. Correct the erroneous value using the actual page history.

Confirm & check again

Check for yourself: Check both source values and their roles; publication and update dates are different questions.

Check again: Full audit — Run a full audit. A complete same-role comparison wholly within tolerance can close the finding. Deleting a date, losing its role or Article association, conflicting duplicates or leaving an interval that straddles the tolerance does not prove a fix.

Limits & sources

No rendered-page or language-model inference is used. Ambiguous headers, source loss, unsupported formats or language, unresolved entity links and incomplete markup are unverified rather than treated as checked absence.

The check does not establish how Google will display or judge the page.

Confidence: Medium The interval arithmetic is exact, while the primary entity and visible role remain bounded source-qualified static facts.

Sources

• Google, Influence your byline dates in Google Search — Recommends consistency between equivalent user-visible and structured dates. Checked 7 October 2026.
• IANA, Language subtag registry — Validates declared language tags; not a visible-date or author-pattern dataset. Checked 3 October 2026.
• IANA, Language tag extensions registry — Validates declared language tags; not a visible-date or author-pattern dataset. Checked 3 October 2026.

Editorial review: 10 October 2026