The “Datetime property is missing a timezone” warning is one of the more common structured data issues reported in Google Search Console.
It often appears against the uploadDate property in video structured data, but it can also affect event start times, article publication dates, job postings, sale periods and live-stream information.
Because Google usually classifies it as a non-critical issue, it is easy to ignore. However, leaving it unresolved can cause problems. A date without a timezone can be interpreted incorrectly, sometimes by as much as a day. This can lead to Google showing the wrong date or time in search results.
Fixing the problem usually involves changing how your website handles dates. In many cases, one incorrect setting or line of code is responsible for hundreds or thousands of warnings.
This guide explains what the warning means, why it matters and how to fix it across your website. It is written for SEO and marketing teams responsible for Search Console, developers who manage website templates, and content teams who publish videos, events and articles.
I’ll also cover an issue that quick fixes often miss: the change between Greenwich Mean Time (GMT) and British Summer Time (BST).
1. What Happened? Datetime Property Is Missing a Timezone in Google Search Console: How to Fix It
Google has found a date or date-time value in your structured data that doesn’t include a timezone.
Without a timezone, Google cannot tell exactly when the event happened or when the content was published.
Google’s Search Console Help documentation explains that the fix is to include a timezone in the date-time value so that Google can interpret it correctly.
For example, consider this value:
2026-01-05T08:00:00
It tells Google that something happened at 8am on 5 January 2026. But it doesn’t say where that 8am applies.
Is it 8am in London, New York or Mumbai? These locations have different timezones, so the actual moment can be several hours apart.
A complete date-time value needs to include the timezone.
What a Correct Date-Time Value Looks Like
Structured data uses the ISO 8601 date-time format. A complete value includes the date, time and timezone.
Here are some examples:
| Value | Valid? | What it means |
|---|---|---|
2026-01-05 | Depends on the property | A date without a time or timezone. This is acceptable for some properties, but can trigger warnings for others, such as uploadDate |
2026-01-05T08:00:00 | No | The time is included, but there is no timezone |
2026-01-05T08:00:00Z | Yes | 8am UTC. The Z means UTC, also known as Zulu time |
2026-01-05T08:00:00+00:00 | Yes | 8am in London during winter (GMT) |
2026-07-05T08:00:00+01:00 | Yes | 8am in London during summer (BST) |
2026-01-05T08:00:00-05:00 | Yes | 8am in New York during winter |
2026-01-05T08:00:00+05:30 | Yes | 8am in India |
2026-01-05T08:00+0100 | Avoid | The timezone offset is missing the colon |
2026-01-05 08:00:00Z | Avoid | Uses a space instead of T between the date and time |
The standard format is:
YYYY-MM-DDThh:mm:ss followed by either Z or a timezone offset, such as +01:00.
Seconds and fractions of a second are optional.
Which Structured Data Properties Commonly Trigger This Warning?
The warning can affect several different structured data properties.
| Property | Where it appears | Common problem |
|---|---|---|
uploadDate | VideoObject, including video rich results and key moments | The video’s publication date is taken from a date-only field |
startDate, endDate | Event and BroadcastEvent for live-stream badges | An event time is entered without a timezone |
datePublished, dateModified | Article, NewsArticle and BlogPosting | The database date is output without a timezone |
datePosted, validThrough | JobPosting | A job listing has a date without the required time or timezone |
validFrom, validThrough | Offer and merchant listing structured data | A sale’s start or end time is missing its timezone |
expires | VideoObject | A date is provided without the expected time information |
Why Does This Happen?
There are several common reasons.
1. The CMS only stores a date
Some content management systems store a date without a time.
For example, a video upload date might be stored as:
2026-01-05
If the structured data template outputs that value without adding the required time and timezone, Google may report a warning.
2. Database times are not converted
Databases often store dates and times without including a timezone in the value.
A template that outputs the raw database value might generate something like:
2026-11-04 10:15:00
The time is there, but the timezone is missing.
3. Plugins and apps use the wrong date format
Some plugins and apps generate structured data using date formats that leave out the timezone.
For example, these formats look complete but don’t include a timezone:
- PHP:
Y-m-d\TH:i:s - JavaScript:
YYYY-MM-DDTHH:mm:ss
The result is a date-time value that Google cannot interpret precisely.
4. Dates are entered manually
Events, webinars and other scheduled activities are sometimes entered into custom fields or pasted directly into JSON-LD.
A value such as 19:30 doesn’t tell Google which timezone applies.
5. Third-party tools generate their own structured data
Video players, event widgets and other embedded tools can add structured data to a page.
If they output incomplete date values, the warning may appear even when the main website template is correct.
How Is This Different From “Invalid Datetime Value”?
Another related Search Console warning is “Invalid datetime value for ‘property name'”.
This usually means that an important part of the date-time value is missing. In many cases, the time itself is missing.
For example, video structured data might use:
2026-01-05
This value contains a date but no time or timezone.
It can therefore trigger both warnings.
The fix is to make sure the relevant property contains a complete and correctly formatted date-time value.
2. Why Does It Matter? Datetime Property Is Missing a Timezone in Google Search Console: How to Fix It
The missing timezone warning is usually classified as a non-critical issue in Google Search Console. It doesn’t necessarily stop a page from appearing with a rich result.
Google may use its own estimate when the timezone is missing.
The bigger problem is accuracy.
If Google cannot work out which timezone applies, it may show the wrong date or time in search results. For content where timing matters, that can be a serious problem.
Where Can a Missing Timezone Cause Problems?
| Content type | What can go wrong |
|---|---|
Videos (uploadDate) | The publication date shown beside a video can be a day early or late. This can also make freshness information less reliable |
Live streams (BroadcastEvent start and end) | The LIVE badge may appear too early, too late or not at all because Google cannot identify the exact start time |
Events (startDate, endDate) | Event times can appear at the wrong hour. An evening event close to midnight could even appear on the wrong day |
Articles (datePublished, dateModified) | The publication or updated date shown in search results could be incorrect, which matters for news and time-sensitive content |
Job postings (datePosted, validThrough) | Job listings could appear to expire earlier or later than intended |
Sale periods (validFrom, validThrough) | A sale price could appear before the sale starts or remain visible after it ends, creating a mismatch with the price shown on the page |
Why UK Businesses Need to Pay Particular Attention
The UK changes between two timezones during the year:
- GMT: UTC+00:00 during winter.
- BST: UTC+01:00 during summer.
British Summer Time normally starts in late March and ends in late October.
One common mistake is to add Z to every date-time value.
This can work during winter when UK time is the same as UTC. However, it creates an incorrect time during summer.
For example, an event scheduled for 7pm in London during BST should be written as:
2026-07-05T19:00:00+01:00
If you write it as:
2026-07-05T19:00:00Z
Google will interpret it as 7pm UTC, which is 8pm in London during summer.
That is an hour out.
For a webinar, product launch, live stream or event, this difference matters.
Why Fix the Warning If Google Calls It Non-Critical?
There are several reasons to deal with this issue rather than leave it in Search Console.
It is often a template problem
One incorrect date format can affect every video, event or article on your website.
Search Console might show hundreds or thousands of affected URLs, even though the underlying problem comes from one line of code.
It makes Search Console reports easier to manage
A report full of non-critical warnings makes it harder to spot more serious problems when they appear.
Cleaning up unnecessary warnings makes ongoing monitoring easier.
Accurate dates help Google understand your content
Google’s guidance on article bylines encourages websites to provide clear and accurate dates.
This is particularly important for publishers, news websites and businesses that regularly publish time-sensitive content.
Dates also matter in AI search
AI-powered search features and assistants increasingly answer questions about when something happened or will happen.
Examples include:
- When does an event start?
- When was this video published?
- When does the sale end?
- When was this article last updated?
Accurate dates make it easier for search engines and AI systems to understand when your content is relevant.
The technical fix is usually relatively small, particularly when the issue comes from one template. That makes it a worthwhile improvement for most websites affected by the warning.
3. Who Is Affected?
Any website that uses dates in structured data can experience this issue.
It is particularly common when dates come from basic CMS fields, plugins use incomplete date formats, or a website serves users in different timezones.
Which Industries Are Most Likely to Be Affected?
| Industry | Where the missing timezone usually appears |
|---|---|
| Publishers, news and media | datePublished and dateModified on articles, uploadDate on embedded videos, and live-stream start times |
| Video-led brands, education and e-learning | uploadDate on lesson, tutorial and product video pages |
| Events, venues, ticketing and conferences | startDate and endDate on event pages, including manually entered doors-open and performance times |
| B2B, SaaS and professional services | Webinar and online event structured data, product demo videos and dates generated by marketing automation landing pages |
| Ecommerce | Sale start and end dates (validFrom and validThrough), product videos and product launch countdowns |
| Recruitment and careers websites | datePosted and validThrough on job listings, often imported from applicant tracking systems |
| International brands | One website template serving several countries, where a single hard-coded timezone is incorrect for some locations |
Which Platforms Are Most Likely to Have This Problem?
The cause often depends on how the website generates its structured data.
| Platform | Typical cause |
|---|---|
| WordPress with SEO plugins | Video structured data uses a date-only field, custom code leaves out the timezone, or the website uses a fixed UTC offset instead of a named city |
| Shopify | Theme or app JSON-LD outputs a date without its timezone. Video and event apps may also generate incomplete structured data |
| Headless and custom websites | Dates are passed from an API or database as strings without conversion, or JavaScript date formatting is configured without a timezone |
| Video hosting embeds and players | The player adds VideoObject structured data with a date-only uploadDate |
| Event and webinar platforms | Embedded widgets or landing page builders output local times without a timezone |
| Applicant tracking systems and job feeds | Imported job listings contain dates without the required time or timezone |
How to Understand the Warning in Search Console
The way the warning appears can help you identify where the problem is coming from.
- The same property is affected across many URLs: For example,
uploadDateappears on every video page. This usually points to a template or plugin setting. Fixing the shared output should resolve the issue across those pages. - Only individual, manually created pages are affected: The problem may come from custom fields or JSON-LD added directly to those pages. Fix the way the dates are entered rather than correcting each page separately.
- Dates look correct in winter but wrong in summer: This often points to a hard-coded
Zor+00:00instead of a timezone-aware conversion that accounts for summer time.
4. What Should Businesses Do?
Every structured data date-time value should include the correct timezone.
The important part is to use a timezone-aware conversion rather than simply adding Z or +00:00 to the end of a date.
Set the rule once in each template, test it during both GMT and BST, and add a check to make sure the problem does not return.
Who Is Responsible for Fixing It?
This is a shared task between marketing, SEO, development and content teams.
| Team | Responsibility | Expected outcome |
|---|---|---|
| Marketing and SEO | Identify affected properties and templates, agree on the timezone rules and check the results in Search Console | A list of affected URLs by property and a clear date rule for each template |
| Development | Fix date output in templates, plugins and apps, account for summer time and add automated checks | Updated templates and plugins, tests for GMT and BST, and a check before release |
| Content | Enter complete dates, times and the correct timezone for events, webinars and scheduled videos | Complete date and time information without manually typing values into free-text fields |
Step 1: Find Out Where the Problem Is Coming From
Responsible team: Marketing and SEO
Start by identifying which structured data properties are affected.
- In Google Search Console, open the report showing the warning. This might be Videos, Events, Job postings, Merchant listings or another structured data report.
- Select the issue labelled “Datetime property ‘…’ is missing a timezone”. The property name tells you which date field is affected.
- Export the affected URLs and group them by template. For example, separate video pages, event pages and articles.
- Test a sample of affected URLs using Google’s Rich Results Test. Check the exact date-time value Google receives.
- Look for common problems, such as a date without a time, a time without an offset, or a space instead of
Tbetween the date and time. - Check whether the same URLs also have the “Invalid datetime value” warning. If they do, the template may be outputting a date without a time.
The aim is to identify whether the problem comes from a shared template, plugin, app or manually entered value.
Step 2: Agree on the Timezone Rules
Responsible teams: Marketing, SEO and Development
Before changing the code, agree on how dates should be handled across the website.
I recommend the following rules.
Convert the date properly. Don’t simply add a timezone
Start with the actual moment an event happens or content is published. Convert it into the correct timezone and then format it for structured data.
Never add Z to a local time just to make the warning disappear.
Use a named timezone rather than a fixed offset
For a UK website, configure Europe/London rather than using a fixed offset such as +00:00 or +01:00.
A named timezone automatically accounts for GMT and BST. A fixed offset does not change when the clocks change.
Use the event venue’s timezone
For in-person events, use the timezone of the venue.
For example, an event in Manchester uses UK time, while a conference in Berlin uses German time, even if the website is managed from the UK.
For online events, any correctly specified timezone can represent the actual moment. However, using the organiser’s timezone is usually the clearest option because it matches the time shown on the event page.
Convert date-only values into midnight in the correct timezone
Where a property requires a date-time but the source only contains a date, use midnight in the relevant timezone.
For example, a UK website operating in winter could output:
2026-01-05T00:00:00+00:00
This is preferable to treating the date as midnight UTC and then converting it to local time, which could move it into the previous or following day.
Make sure structured data matches what visitors see
The date and time in your structured data should match the information displayed on the page.
If the event page says 7pm London time, the structured data should represent that same moment.
Step 3: Implement the Fix
Responsible team: Development
The implementation depends on your website platform.
WordPress: Check the Website Timezone
Start by checking the WordPress timezone setting.
Go to:
Settings > General > Timezone
Choose a city, such as London, rather than a manual offset such as UTC+0.
A city-based timezone automatically accounts for BST and GMT. A fixed offset does not.
This is a common cause of dates appearing correctly during winter but being an hour out during summer.
WordPress: Fix Article Publication and Update Dates
For article publication and modification dates, use WordPress’s built-in ISO 8601 output.
For example:
'datePublished' => get_the_date( 'c' ),
'dateModified' => get_the_modified_date( 'c' ),The c format produces an ISO 8601 date-time value that includes the site’s timezone offset.
For example:
2026-07-05T10:15:00+01:00
WordPress: Fix Custom Fields That Store Only a Date
Some custom fields store only a date. This is common with video upload dates and event dates.
The solution is to interpret the date in the website’s timezone before formatting it.
You can use a function like this:
function sd_iso_datetime( $value ) {
if ( empty( $value ) ) {
return null;
}
try {
return ( new DateTimeImmutable( $value, wp_timezone() ) )->format( 'c' );
} catch ( Exception $e ) {
return null; // Omit the property rather than output a bad value
}
}Examples:
// sd_iso_datetime( '2024-01-05' )
// → 2024-01-05T00:00:00+00:00 (London site)
// sd_iso_datetime( '2024-07-05 14:30' )
// → 2024-07-05T14:30:00+01:00The function also handles values that already include a timezone offset. DateTimeImmutable respects an existing offset, which makes it suitable for fields containing a mixture of date formats.
WordPress: Fix the Rank Math Video Schema Warning
Rank Math video structured data can trigger this warning when uploadDate is output as a date without a time or timezone.
A common fix is to use a filter that adds a time and timezone to the upload date.
However, some versions of this approach use strtotime() and wp_date(). This can create another problem because WordPress runs PHP in UTC.
For example, strtotime( '2024-01-05' ) interprets the date as midnight UTC. When wp_date() converts it to the website’s timezone, the date can move backwards or forwards.
On a New York website, this could produce:
2024-01-04T19:00:00-05:00
That is the previous calendar day.
On an Indian website, it could produce 05:30 instead of midnight.
UK websites happen to avoid this particular date shift during winter, but that doesn’t make the approach suitable for every timezone.
The safer option is to interpret the original date in the website’s timezone using the sd_iso_datetime() function above.
You can then use the following Rank Math filter:
add_filter( 'rank_math/snippet/rich_snippet_videoobject_entity', function ( $entity ) {
if ( empty( $entity['uploadDate'] ) || false !== strpos( $entity['uploadDate'], 'T' ) ) {
return $entity; // Empty, or already a full date-time
}
$iso = sd_iso_datetime( $entity['uploadDate'] );
if ( $iso ) {
$entity['uploadDate'] = $iso;
}
return $entity;
} );Before using this code, confirm that the filter name matches your installed Rank Math version.
Also check the settings and available filters in your other SEO or structured data plugins, including Yoast and All in One SEO.
Shopify: Fix Date Formatting in Liquid
Shopify themes use Liquid to output structured data.
The Shopify date filter accepts formatting codes. The %:z code adds the timezone offset with a colon.
For example:
"datePublished": {{ article.published_at | date: '%Y-%m-%dT%H:%M:%S%:z' | json }},The output should include the correct timezone offset.
Also check the timezone in Settings > General.
Test the changes in a preview theme before publishing them. Remember to check whether video or event apps generate their own structured data, as fixing the theme alone may not resolve every affected URL.
Headless and Custom Websites: Fix Date Formatting in JavaScript
For custom websites and headless builds, the correct approach depends on how the date is stored.
If you have a genuine timestamp, this JavaScript method produces a UTC value ending in Z:
new Date(value).toISOString()However, if you need to output local time with its correct timezone offset so that it matches the time displayed on the page, you need a timezone-aware formatter.
The following function uses built-in browser and Node.js features:
function toIsoWithZone(date, timeZone = 'Europe/London') {
const p = Object.fromEntries(new Intl.DateTimeFormat('en-GB', {
timeZone,
hourCycle: 'h23',
year: 'numeric',
month: '2-digit',
day: '2-digit',
hour: '2-digit',
minute: '2-digit',
second: '2-digit'
}).formatToParts(date).map(x => [x.type, x.value]));
const local = Date.UTC(
+p.year,
+p.month - 1,
+p.day,
+p.hour,
+p.minute,
+p.second
);
const offMin = Math.round(
(local - Math.floor(date.getTime() / 1000) * 1000) / 60000
);
const sign = offMin >= 0 ? '+' : '-';
const a = Math.abs(offMin);
return `${p.year}-${p.month}-${p.day}T${p.hour}:${p.minute}:${p.second}` +
`${sign}${String(Math.floor(a / 60)).padStart(2, '0')}:${String(a % 60).padStart(2, '0')}`;
}Example outputs:
// January in London:
// 2026-01-15T09:00:00+00:00
// July in London:
// 2026-07-15T10:00:00+01:00
// India:
// 2026-01-15T14:30:00+05:30We tested this approach across the 2026 clock changes on 29 March and 25 October, using London, New York and India time. The timezone offset changed at the correct time in each test.
Python Backends: Use Timezone-Aware Dates
If your website uses Python on the backend, use timezone-aware date-time objects.
For example:
from datetime import datetime
from zoneinfo import ZoneInfo
datetime.now(ZoneInfo("Europe/London")).isoformat()This returns a date-time value with the correct timezone offset.
Events and Webinars: Stop Using Free-Text Time Fields
For manually entered events and webinars, the best solution is to change how the information is collected.
Instead of asking editors to type a date and time into a free-text field, provide separate fields for:
- Event date.
- Event time.
- Timezone.
The website should then generate the structured data automatically from those fields.
This reduces the risk of editors entering incomplete or incorrectly formatted dates.
Step 4: Test and Validate the Changes
Responsible teams: Development, followed by Marketing and SEO
Don’t release the changes across the entire website without testing them first.
Use the following process:
- Test on staging. Choose at least one page from each affected template and run it through Google’s Rich Results Test. You can use the code snippet option for pages that haven’t been published.
- Test both seasons. Check a winter date using the UK offset of
+00:00and a summer date using+01:00. If both dates produce the same offset, the website may not be applying summer time correctly. - Compare the dates. Make sure the date and time in the structured data match what visitors see on the page.
- Release the changes. Once the tests are successful, publish the changes.
- Run a live test. Use URL Inspection in Google Search Console to check a sample of affected pages.
- Validate the fix. Return to the relevant Search Console report and select Validate fix.
The warning should clear as Google recrawls the affected pages. This can take days or weeks.
Step 5: Stop the Problem From Returning
Responsible teams: All teams
Once the warning has been fixed, add checks to your website’s development and publishing processes.
Development: Add an automated date check
Add a release check that reads the JSON-LD on each template and confirms that every date-time value follows the expected format.
For example:
const ISO_WITH_ZONE = /^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}(:\d{2}(\.\d+)?)?(Z|[+-]\d{2}:\d{2})$/;This check accepts values such as:
2026-01-05T08:00:00Z2026-01-05T08:00:00+01:00- Values that include fractions of a second.
It rejects:
- A date without a time.
- A date-time without a timezone.
- A timezone offset without a colon.
- A space instead of
Tbetween the date and time.
Apply the check to the relevant properties, including:
uploadDate, startDate, endDate, datePublished, dateModified, datePosted, validFrom, validThrough and expires.
Development: Check after updates
Run the date validation after plugin, app and theme updates.
Also include it in the release process before the clock changes in March and October.
Marketing and SEO: Monitor Search Console
Include the Videos, Events and other relevant enhancement reports in your monthly Search Console review.
Content: Enter complete dates and times
Make sure editors always provide the correct event time and timezone.
Use scheduled publishing features rather than changing publication dates manually. Also make sure events outside the UK use the correct local timezone.
Implementation Checklist
Use this checklist to make sure the issue has been fixed across the website.
- Export affected URLs and group them by structured data property and page template.
- Set the WordPress or platform timezone to a named city rather than a fixed offset.
- Replace date-only and timezone-free outputs with correctly formatted ISO 8601 values where required.
- Use the venue’s timezone for in-person events.
- Replace any approach that simply adds
Zor uses an incorrectstrtotime()conversion. - Test one winter date and one summer date for every affected template.
- Release the changes and run live tests on affected URLs.
- Select Validate fix in Google Search Console.
- Add automated ISO 8601 checks to the development release process.
5. What We’re Watching Next
Dates are becoming more important as search engines provide more information about events, live content, product launches and other time-sensitive topics.
We expect accurate, timezone-aware dates to become a basic requirement for websites that rely on these search features.
There are several developments worth watching.
More Search Features Depend on Exact Times
Live badges, event listings, limited-time offers and sale periods all depend on accurate start and end times.
As Google shows more information about what is happening now or what is ending today, an incorrect timezone can create more problems for businesses.
Accurate Dates Matter for AI Search
Google AI Overviews, AI Mode and other AI assistants increasingly answer questions about dates and times.
For example, a user might ask when an event starts, when a video was published or when a sale ends.
Clear and accurate dates make it easier for these systems to understand the information and provide the correct answer.
Google Could Become Stricter About Incomplete Dates
Google has previously changed how strictly it handles structured data values, including price formats.
It would not be surprising to see more attention given to incomplete date-time values, particularly for search features where timing is important, such as live streams and events.
Clock Changes Will Continue to Cause Problems
Every March and October, websites using hard-coded timezone offsets risk publishing times that are an hour out.
Businesses should include checks for clock changes in their development and release schedules rather than waiting for Search Console to report a problem.
International Businesses Need More Accurate Timezones
As UK businesses expand into other markets, they increasingly publish content, sell products and organise events across different timezones.
One fixed offset for an entire website is unlikely to be suitable for every market.
Websites serving multiple countries need to handle dates according to the location and time of the activity.
AI-Generated Structured Data Needs Checking
AI tools and website builders can generate structured data automatically.
However, the resulting markup may leave out timezone offsets or add Z to a local time incorrectly.
Automated validation is important wherever structured data is generated rather than maintained through carefully tested templates.
6. About Szymaniak Digital
Szymaniak Digital is an Enterprise AI SEO Consultancy helping brands improve their visibility across Google and AI search platforms.
We also help businesses fix technical SEO issues that affect how their websites are understood and displayed in search results.
Our structured data audits cover the templates and systems that generate schema across a website. This includes less obvious problems such as incorrect summer-time offsets, missing timezones and dates that shift into the wrong day.
If Google Search Console is reporting datetime warnings across your website, or the dates shown in search results don’t match the information on your pages, we can investigate where the problem is coming from and help your development team implement and test the fix.
The aim is simple: make sure your structured data gives Google accurate information, rather than creating more problems for your SEO team.
