A structured-data datetime omits its timezone
In the reportDate value has no timezone designator
structured_data_date_missing_timezone · Review item
A valid captured datetime has a time component and no timezone designator.
Severity: Notice. Review whether the intended time needs an explicit timezone.
Why it matters
Google’s Article guidance recommends timezone information for publication and modification datetimes to avoid a default interpretation.
What to do
- Check the intended local time and timezone for the reported value.
- Add Z for UTC or the correct offset, for example +02:00. Preserve the intended instant.
When to leave it as it is: Date-only values, durations and clock-time properties do not require a datetime timezone for this check. Review deliberately local datetimes before changing their meaning.
What we read
We read the page’s captured HTML and its JSON-LD, Microdata and RDFa declarations without executing JavaScript or fetching remote contexts. The finding preserves the property, validated value, original declaration and source byte positions.
Incomplete capture, an unresolved reference, contradictory values or a form outside the supported parser means not checked. It never demonstrates a correction.
We check recognized datetime strings on temporal properties. Calendar dates, durations and standalone clock times do not fire.
Example & evidence
Illustrative correction; this is not a live audit.
"datePublished": "2024-01-05T08:00:00""datePublished": "2024-01-05T08:00:00+08:00"Confirm & check again
Check for yourself: Compare the reported property with the HTML served at this URL. Validate the corrected markup with the appropriate structured-data test.
Check again: Full audit — Run another full site audit. A correction is confirmed only for the same page with sufficient captured coverage and no remaining violation. Missing coverage does not close the finding.
Limits & sources
This is a review notice, not proof of an invalid date or a ranking problem. Google’s cited default-timezone guidance specifically discusses Article dates; it does not prove that every structured-data consumer handles every datetime identically.
Confidence: High The finding records an exact offline validation reason. It does not establish Google indexing, ranking or rich-result display.
Sources
- Google, Article structured data — Recommends timezone information and explains the fallback for article datetimes. Checked 3 October 2026.
Editorial review: 2 November 2026