Fix Missing dateModified: Add a Freshness Signal
This page has no machine-readable dateModified value, so search engines and AI answer engines can't reliably tell when your content was last updated. Add an accurate dateModified in your Article or WebPage JSON-LD, keep it in sync with real edits, and mirror it in a visible timestamp. Done honestly, this restores a freshness signal that supports both classic ranking and AI citation.
What this means
The audit flagged that your page exposes no machine-readable "last updated" date. There's no dateModified property in your structured data (JSON-LD), and usually no article:modified_time Open Graph tag or <time>-marked visible timestamp either.
dateModified is a schema.org property that states, in a format machines can parse, when the content last meaningfully changed. It's distinct from datePublished, which records when the page first went live. Google, Bing, and AI crawlers can read dateModified to gauge recency without guessing from your HTML.
Without it, a crawler falls back to weaker heuristics: the HTTP Last-Modified header (often just a build or file timestamp, not a content edit), dates scraped from visible text, or nothing at all. A genuinely fresh, recently revised article can then look stale. This is a low-severity, notice-level issue. It won't sink your rankings on its own, but it removes a signal that supports E-E-A-T and freshness.
Why it matters
Freshness is a real ranking input for query-dependent topics. For time-sensitive queries (news, "best X in 2026", pricing, how-tos on fast-moving software, medical or financial guidance), Google applies a "query deserves freshness" model and can favor recently updated content. A trustworthy dateModified also lets Google show an "Updated" date in the SERP instead of the publish date, which can improve click-through and signals that you maintain the page.
dateModified feeds E-E-A-T too. Content that's demonstrably kept current reads as better maintained, which matters most for Your-Money-Your-Life topics where accuracy has consequences.
The answer-engine angle is where this increasingly bites. Tools like ChatGPT with browsing, Perplexity, Google AI Overviews, and Bing Copilot try to avoid quoting outdated facts, and an explicit, recent date is one signal they can use to judge recency. When two pages answer the same question, a clear dateModified makes yours a lower-risk citation than an undated competitor.
One caveat protects you: the date must be truthful. Google explicitly warns against artificially bumping dates without real content changes, and it can ignore dates that don't match what's actually on the page. The goal is an accurate freshness signal, not a fake-fresh one.
How to fix it
- 1
Add dateModified to your JSON-LD structured data
Expose the date in Article, BlogPosting, NewsArticle, or WebPage schema as JSON-LD. Include both datePublished and dateModified, and use full ISO 8601 with a timezone offset (for example 2026-07-07T09:30:00+00:00), not a bare date, so machines parse it unambiguously. Place the script in the page's head or body. This is the field Google's Article rich results and most AI crawlers read first.
- 2
Drive the date from your CMS's real edit timestamp
Wire dateModified to your CMS's genuine last-edited value so it changes only when content actually changes, never on every rebuild or a trivial whitespace edit. Do not bulk-stamp dates to today across your site to fake freshness; Google can detect the mismatch and may discount your dates. If a page truly hasn't changed, an older accurate dateModified beats a fabricated recent one.
- 3
Mirror the date in a visible timestamp and Open Graph
Show a human-readable "Updated on July 7, 2026" near the top of the article, and back it with a <time> element carrying a datetime attribute. Add article:modified_time and article:published_time Open Graph meta tags from the same source. When your visible date, <time datetime>, Open Graph tag, and JSON-LD all agree, Google is far more likely to trust and display the date than when sources conflict.
- 4
Keep datePublished and dateModified consistent
On a brand-new page the two dates can be equal. After any real revision, dateModified should be later than datePublished. A common bug is emitting dateModified earlier than datePublished, or setting it to the render time on every request. Both look wrong to validators and can suppress the "Updated" label. Pull the value from your database's modified field, not the current server time.
- 5
Validate and request re-crawl
Paste the URL into Google's Rich Results Test and the Schema Markup Validator (validator.schema.org) to confirm dateModified is present and well-formed. Fix any warnings, then use URL Inspection in Google Search Console and click Request Indexing so the updated markup gets picked up. Re-run your audit afterward to confirm the missing_date_modified flag clears.
Example
<!-- In <head> -->
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "How to Fix a Missing dateModified Freshness Signal",
"author": {
"@type": "Person",
"name": "Kaustav Basak"
},
"datePublished": "2026-06-12T08:00:00+00:00",
"dateModified": "2026-07-07T09:30:00+00:00"
}
</script>
<!-- Open Graph, same values -->
<meta property="article:published_time" content="2026-06-12T08:00:00+00:00" />
<meta property="article:modified_time" content="2026-07-07T09:30:00+00:00" />
<!-- Visible, human + machine readable, same date -->
<p>Updated on
<time datetime="2026-07-07">July 7, 2026</time>
</p>Article JSON-LD with an honest dateModified, plus matching Open Graph and a visible <time> element. Keep all three values in sync and driven by your real last-edited timestamp.
Platform-specific steps
Both Yoast SEO and Rank Math output datePublished and dateModified in their Article/WebPage JSON-LD, pulled from the post's real modified date, so the fix is usually just confirming schema output is enabled. In Rank Math, set the schema type on the post (Article or BlogPost) under the Schema tab. Many themes hide the visible updated date; add a template tag using get_the_modified_date() or a plugin like WP Last Modified Info so the on-page date matches the schema. Avoid plugins that rewrite modified dates in bulk.
Shopify's default article schema is thin and often omits dateModified. Edit your blog/article Liquid template (article-template.liquid or the relevant section) and add a JSON-LD block. Liquid exposes article.published_at reliably, but a true content-edit timestamp is less consistent, so store a real "last updated" value in a metafield you control and render it into dateModified so it only changes when you actually edit.
Wix blog posts include some structured data automatically but give you limited control over dateModified. For custom pages, inject an Article schema with an accurate dateModified via Settings > SEO > Advanced (custom header code) or the Velo API. Wix can also show a "last updated" label on blog posts through the blog element settings; enable it so a visible date exists alongside the markup.
Squarespace blog posts expose a publish date but not a separate machine-readable modified date by default. Add JSON-LD through Code Injection (per-page header or site-wide) containing an Article object with datePublished and dateModified. Because Squarespace doesn't surface a reliable per-post modified timestamp to inject automatically, update dateModified manually when you revise a post and keep it in sync with any visible "Updated" text.
Render a JSON-LD script (type="application/ld+json") in the page. In the App Router you can return it from generateMetadata or inline a script in the layout/page. Pull dateModified from your CMS or database updatedAt field and format it as ISO 8601 with an offset; never call new Date() at request time, or the value shifts on every render. Emit article:modified_time and a visible <time datetime> element from the same source so all three stay consistent.
Frequently asked
datePublished is when the page first went live and shouldn't change. dateModified is when you last made a meaningful content edit. Search engines use datePublished to establish original authorship and dateModified to judge freshness. Include both, and make sure dateModified equals or is later than datePublished.
Not dramatically on its own, which is why this is a notice, not a critical error. But for freshness-sensitive queries it lets Google assess recency and display an accurate "Updated" date, and it makes your page a stronger citation candidate for AI answer engines. The bigger win comes from genuinely updating the content and reflecting that in the date.
No, not without a real content change. Google warns against artificially freshening dates and can ignore or distrust dates that don't match actual edits, which can hurt more than help. Only update dateModified when you meaningfully revise the page, and keep the visible date matching the markup.
Ideally all three, in agreement. JSON-LD dateModified is what Google's rich results and most crawlers read. article:modified_time Open Graph reinforces it for social and some AI crawlers. A visible "Updated on" line with a <time datetime> element builds user trust and gives an on-page signal that matches. Consistency across all three is what earns trust.
Indirectly. These tools try to avoid citing outdated information, so a clear, recent, machine-readable date is one signal that makes your page a lower-risk source to quote. When competing pages answer the same question, an explicit dateModified can help yours get picked over an undated alternative.
Does your site have this issue?
Run a free, AI-powered audit and we’ll flag this and 150+ other checks in about a minute. No signup.