Article page has no date
article_no_dateShort answer
The page is an article (Article/NewsArticle schema or article-like markup) but has neither datePublished/dateModified in its structured data nor a date Glimana could read. Google uses dates for freshness and shows them in results and Discover. Add both schema dates and a visible date.
Why it matters
Google determines a page's date from several signals and recommends a visible date plus datePublished and dateModified in structured data that agree with each other. Articles without dates are harder to place in time, less likely to surface in Discover and Top stories, and look untrustworthy to readers.
How Glimana detects it
For pages Glimana classifies as articles, the rule fires when neither datePublished nor dateModified is present in the structured data and no publication date was found in the markup.
How to fix it
- Find the affected pages in Glimana. Open Issues › Article page has no date. Every affected page is a row; open one to see the evidence Glimana recorded for it (the measured value, the offending element or the target URL). The same list sits on the task card under Tasks, and the page's own detail view under Pages shows its full signals.
-
Apply the fix on your platform.
SEO plugins output Article schema with dates automatically for posts; a missing date means the post type is not treated as an article (set it under Search Appearance → Content types → Schema) or the theme hides the date — enable it in the theme's post settings.
Blog articles get
datePublishedthrough the theme's JSON-LD; check thearticleobject in the theme's structured-data snippet and show{{ article.published_at | date }}.Add
datePublishedanddateModified(ISO 8601 with time zone) to the Article JSON-LD and print the same date in the template; updatedateModifiedonly on real edits. -
Publish and clear caches. Save and publish, then make sure the crawler will see the new version: WordPress — clear the page cache in your cache plugin and purge the CDN; Shopify — theme and content changes go live on save, but purge any CDN in front of the store; custom code — deploy and purge the edge cache. Check in a private window or with
curl -s https://your-domain/page | grep -i '<title\|canonical\|robots'that the live HTML has changed; Glimana reads what the server sends, not what your browser has cached. - Verify in Glimana. Open the task under Tasks and click Mark as done. The affected pages are queued for a verification crawl within a few hours, and the task closes when a date is present in the schema or markup. If the check still fails, the task returns to New with a note; when it passes, the task is listed under Resolved technical issues on Impact reports. To check sooner, use Re-crawl affected pages on the issue.
How the fix is verified
Re-crawl; the task closes when a date is present in the schema or markup.