Article missing a publication date: fix freshness and E-E-A-T

What it means

This page is marked up as an article or blog post — its structured data declares Article, BlogPosting, or NewsArticle — but it carries no publication date: no datePublished (or dateModified) in the JSON-LD and no visible date in the body. For content that makes time-sensitive claims or gives advice, the absence of a date removes a signal both readers and Google use to judge whether the information is current.

Why it matters

Google's quality systems treat freshness as part of assessing content, especially for topics where information changes — software instructions, legal requirements, medical guidance, financial data. Article schema supports datePublished and dateModified; supplying them gives Googlebot a machine-readable statement of when the content was written and last reviewed, which feeds the freshness ranking system and lets Search and Discover show a date next to your result. Missing dates are also a hallmark of scaled content operations, where maintaining publish/update dates across thousands of pages is editorial discipline that mass output tends to skip. This check is scoped tightly to article-typed pages, so product, category and home pages are never flagged.

How to fix it

1. Add a visible publication date near the article headline — plain text such as "Published 12 July 2026" or "Last updated June 2026" is enough.
2. Add datePublished (and dateModified for updated posts) to the page's Article JSON-LD, using ISO 8601 format: "datePublished": "2026-07-12".
3. Set dateModified to the last substantive editorial review, not a trivial formatting change.
4. Validate the markup with Google's Rich Results Test.

Example

<!-- article body has no visible date, and JSON-LD omits it -->
{
  "@type": "Article",
  "headline": "2026 Guide to Index Funds",
  "author": {"@type":"Person","name":"Lee Park"}
}

<!-- visible "Published May 2, 2026" in the body, plus: -->
{
  "@type": "Article",
  "headline": "2026 Guide to Index Funds",
  "author": {"@type":"Person","name":"Lee Park"},
  "datePublished": "2026-05-02",
  "dateModified": "2026-06-18"
}

Show a visible published date in the body and add Article.datePublished (and dateModified when you update it). Freshness is an E-E-A-T signal, especially for time-sensitive topics.

When it's not a problem

This is scoped to article-typed pages. Evergreen utility content — calculators, glossaries, tool landing pages — legitimately has no date; if such a page carries Article schema by mistake, correcting the schema type is the right fix. A page with a clearly visible date but no structured date is not flagged, because the check accepts either signal.

How Crawlinx detects it

This fires only on article-typed pages (Article/BlogPosting/NewsArticle) that carry no publication date at all — no datePublished/dateModified in JSON-LD and no visible <time> or date pattern in the body. Non-article pages are exempt.

How common is it?

145 audited sites in our corpus currently show this issue. The breakdowns below show which platforms, gatekeepers, verticals and countries are most exposed.

FAQ

Does a publication date affect SEO?

It's a freshness and trust signal, not a direct ranking factor. For time-sensitive queries (news, guides, prices) Google favors demonstrably fresh content, and a missing date reads as scaled or neglected.

Should I show datePublished or dateModified?

Both when relevant: datePublished for the original, dateModified when you make a substantive update. Don't fake dateModified on trivial edits — Google can detect gaming of freshness.

Is a JSON-LD date enough without a visible one?

Show a visible date too. Readers and Google both value a human-visible published date; the schema date reinforces it but shouldn't be the only place the date exists.

Related guides

• E-E-A-T SEO: Experience, Expertise, Authority, Trust