How to fix non iso date on Webflow
Change all datePublished (and dateModified) values in your structured data from informal formats like "09/23/2019 00:00:00" to the ISO-8601 format "2019-09-23" so search engines can correctly read your content's publication date.
Steps for Webflow
- In the Webflow Designer, open the Page Settings for any page that has custom JSON-LD structured data added in the 'Custom Code' → 'Head Code' or 'Before </body> tag' sections.
- Locate any date fields in those JSON-LD blocks and correct the value to ISO-8601 format: '2019-09-23' or '2019-09-23T00:00:00Z'.
- For CMS-driven pages (Blog Posts, Products), open the CMS Collection schema under CMS → Collections, and check if you have a Date field connected to a JSON-LD embed in the Collection Template page.
- In the Collection Template page's custom code embed, use Webflow's CMS field binding to pull the date dynamically. Ensure the bound Date field outputs in ISO format — Webflow Date fields can be formatted; use the 'YYYY-MM-DD' format option in the embed binding dialog.
- If dates are hard-coded in embeds, update each one manually to the correct ISO format.
- Publish the site and test affected pages in Google's Rich Results Test.
{
"@context": "https://schema.org",
"@type": "WebPage",
"name": "My Product Page",
"datePublished": "2019-09-23",
"dateModified": "2024-03-15T09:30:00Z"
}What is non iso date?
Structured data (the behind-the-scenes code that tells Google what your page is about) includes date fields like `datePublished` and `dateModified`. These dates must be written in a specific international format called ISO-8601 — which looks like `YYYY-MM-DD` (for example, `2019-09-23`) or with a full timestamp like `2019-09-23T00:00:00Z`. When dates are written in a casual format like "09/23/2019 00:00:00" or "September 23, 2019", search engines cannot reliably parse them and may ignore them entirely. Think of it like filling out an official form: the field has a required format, and anything else gets rejected.
Google uses `datePublished` and `dateModified` to understand content freshness — a key signal for ranking pages in news, article, product, and general search results. If Google can't parse your date, it may estimate the wrong publish date or show no date at all in search results, making your listings look outdated or untrustworthy compared to competitors whose dates are formatted correctly. For Answer Engine Optimization (AEO), freshness signals help your content surface in AI-generated answers and featured snippets, where recency is often a deciding factor. A malformed date can also cause your structured data to fail Google's Rich Results Test, disqualifying your pages from rich result enhancements like breadcrumb trails, review stars, and FAQ dropdowns — all of which directly impact click-through rates and organic traffic.
See the complete Non iso date guide for every platform and the full background.
Not sure if your Webflow store has this?
Run a free SEOLZ audit — we’ll find non iso date and every other issue across your whole site.
Scan my site free