Article and BlogPosting schema

What it does for AI citation

Freshness and authorship are two of the signals that decide whether an assistant will cite a page or pass over it. dateModified in particular is how a model tells a current answer from a stale one, and it is routinely wrong or absent.

A working example

Paste this into a <script type="application/ld+json"> tag in your page head and replace the values. It is valid as written.

{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "How assistants choose which sources to cite",
  "datePublished": "2026-08-01T09:00:00Z",
  "dateModified": "2026-08-20T14:30:00Z",
  "author": {
    "@type": "Person",
    "name": "Jane Example",
    "url": "https://example.com/about"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Example Co",
    "logo": { "@type": "ImageObject", "url": "https://example.com/logo.png" }
  },
  "mainEntityOfPage": "https://example.com/blog/how-assistants-cite"
}

What actually goes wrong

These are the errors that show up repeatedly on real sites, in rough order of how often we see them.

• dateModified bumped on every deploy. If it always says today, it carries no information and looks like manipulation.
• author as a bare string instead of a Person with a url. The url is what lets the author be resolved to an entity.
• headline that disagrees with the visible H1.
• Missing dateModified entirely, which leaves an assistant to guess whether a two-year-old page is current.

Markup is necessary, not sufficient

Valid Article does not buy you a citation. It makes your page legible, which is the precondition. Whether an assistant names you when a buyer asks also turns on your content, how current the page is, and who else on the web corroborates you. Any tool that tells you markup alone will get you cited is overselling.

Other types