Articles are dated

Does each article say when it was published?

Coverage · 10 of 100 in Coverage · yours to do · dates

What we look for

On the sampled pages that are articles, we look for any honest sign of when it was written, the machine-readable ones first: a datePublished in the page’s structured data, a <time datetime> element in the article’s header or byline, or first under its title (never one in a comment), a date in a meta tag (article:published_time, date, or a Dublin Core or Highwire date such as dc.date.issued, dcterms.created, or citation_publication_date), the entry for that page in your feed (your site’s, or the feed the page’s own head links), a date in the page’s address (/2026/nov/3/, /2026/11/03/), or a date a reader can see: under the title, or in an element marked as the date or byline. A modified date never dates a post: a dateModified, an article:modified_time, an og:updated_time, a Dublin Core modified date, or a “Last updated” says when the page changed, not when it was written; so does a <time> labelled “Updated” or “Last modified”, and a date on the line under such a label. A time of day that several pages share to the second, with modified dates that don’t differ, is the build’s stamp, not a date; one publishing time over modified dates that differ is real (a newspaper that publishes a day’s notices at 00:05). The score is the share of articles that have one, and the detail says which signals we found. If no sampled page is an article, we skip the criterion.

A page counts as an article only by its own content: it shows a date or a byline of its own, in the article or in the structured data that describes the page as one, or a feed has an entry for it (your site’s feed, when the page shows a date or a byline or sits under a section where writing lives, since a feed of program or landing pages is not a feed of posts; or the feed the page’s own head links). Or it has a place among your posts: an <article> at an address where writing lives, or a page an index of posts labels as an article; such a page counts with no date at all, and is the one we ask you to date. An <article> element alone, anywhere else, doesn’t make one, and an index, an archive of links, or a tool page never counts. We also check the two newest posts from your feed (or, with no feed, the two pages your sitemap says changed most recently); and when that still leaves fewer than two posts, the newest ones an index we read lists on your site, never a page on another site. A date counts only if it has a full four-digit year and is no more than a day in the future, so a bare time like 10:00 doesn’t count, and neither does a year mentioned in the prose. The detail names the newest date we found and the page it was on; when a page’s signals disagree, its structured date is the one we take.

The pages we sample include your two newest posts whenever your sitemap lists any; translations, logins, test pages, and legal pages are sampled only when nothing else is left.

We only ask sites that publish posts, and we find them in your sitemap first: a sitemap of posts (post-sitemap.xml, news-sitemap.xml), or addresses under a section where writing lives (/blog/, /posts/, /journal/, /articles/, /news/, /notes/, /writing/) or with a date in them (/2026/11/…). Then a feed with items on your site, then articles, posts, or episodes among the pages we read (in structured data, or a piece of writing that shows its date), and, when the pages we read are indexes (an archive, a list of posts), the newest posts an index lists on your site, each judged by its own page. A site that doesn’t publish posts skips this criterion. If we couldn’t read what would tell us (your sitemap didn’t answer, or the request budget ran out first), we say we couldn’t check, never that you don’t publish. Any kind of site that publishes posts is asked, a company with a blog or a changelog as much as a magazine; a page is a post only by its own content: it shows a date or a byline of its own (in the article itself, or in the structured data that describes the page as an article), or a feed that your site or the page itself links has an entry for it, or it has a place among your posts: an <article> at an address where writing lives (/blog/a-post, /2026/11/a-post), or a page one of your indexes of posts labels as an article. Such a page is a post even with no date and no byline, which is how we can tell you to put a date on it. A label alone, anywhere else, makes no post: not an <article> your template wraps around every page or around an intro paragraph, not og:type, not an author card every page carries in its footer, and not a date we judged a build’s stamp (such a page leaves the count; it is never an undated article). A page under your about section, or one your navigation lists as a product, tool, or landing page, is never a post, and neither is a page that only carries its own dateModified or a legal page’s “Last updated”: a modified date never dates a post. Never a post, whatever it carries: your about page, a press release, reference docs (/docs/, /help/, /guides/, /api/), a login, signup, cart, thank-you, or test page, a landing page your navigation lists as a section, a page of five or more dated entries, or the home page. A page’s date is its own publication date, in its structured data, its header or byline, a meta tag, your feed, its address, or alone under its title, and never a date in its prose.

Why it matters

An AI assistant weighing two sources wants to know which is newer, and whether advice still holds. An undated article is harder to trust and harder to place: is this from last week or ten years ago?

A date people can see counts, because a model reads the page much as a person does. But “last Tuesday” or a date in an image means nothing to it, and a date in a form built for AI is read with more confidence and less guesswork.

How to pass

  1. Put the publish date (and the last-updated date, if it changes) in each article’s structured data:
    <script type="application/ld+json">
    {
      "@context": "https://schema.org",
      "@type": "BlogPosting",
      "headline": "How we cut our prices",
      "datePublished": "2026-10-01",
      "dateModified": "2026-10-14"
    }
    </script>
  2. And show it by the byline, marked up so it can be read:
    <time datetime="2026-10-01">October 1, 2026</time>

Most blog platforms do both; check that the theme you use hasn’t removed them.

Evidence

  • Ahrefs · July 2025 · moderate

    AI assistants cite content about a quarter fresher than search results do; ChatGPT leans newest, and AI Overviews slightly older. A date is how a page says how fresh it is.

    About 17 million citations across AI assistants and search results. Ahrefs sells AI-visibility tracking.

Last changed .

The whole rubric