Article and BlogPosting schema is structured data that labels your content as an article and spells out its key facts — headline, author, publish and update dates, publisher, and main image — in a machine-readable format. Adding it does not magically rank your post, but it gives search engines and AI assistants an unambiguous, trustworthy summary of what the page is, who wrote it, and when it was last updated. Those are exactly the signals AI engines lean on when deciding which source to cite, so marking up your articles removes guesswork and makes your content easier to attribute correctly.

What Article schema tells a machine

When an AI assistant reads a page, it has to infer a lot from messy HTML: is this an article or a product page? Who is the author? Is this current or five years old? Article schema answers those questions directly instead of leaving them to be parsed out of your layout. The core properties do most of the work:

BlogPosting is a more specific subtype of Article; use it for blog posts and reserve Article or NewsArticle for editorial and news content. Functionally they carry the same properties, so pick the one that best describes the page and stay consistent across your site.

Why this matters for AI citation

AI answer engines want to cite sources they can trust and describe accurately. Two of the strongest trust signals are a clear author and a clear timestamp, and Article schema hands both to the engine on a plate. A well-marked-up author connects to the broader question of E-E-A-T and author signals — assistants increasingly prefer content attributed to a real, identifiable person over anonymous text. Meanwhile, an explicit dateModified feeds directly into how engines judge freshness; our piece on content freshness and lastmod explains why a page that proves it is current gets cited more often than one that hides its age.

Getting attributed correctly is half the battle in AI search. If you have read how ChatGPT chooses which websites to cite, you will recognize the pattern: clarity and verifiable metadata win. Article schema is one of the cheapest ways to supply that clarity, because it states the facts an engine would otherwise have to guess.

Implementing it without common mistakes

Write your Article schema as JSON-LD in a script block; it does not change how the page looks and is the format engines prefer. Then avoid the handful of errors that quietly break it:

If JSON-LD is new to you, start with our practical guide to JSON-LD and Schema.org, then layer Article markup onto every post as part of your template so new content is covered automatically.

Roll it out across your content

The highest-leverage move is to bake Article or BlogPosting schema into your CMS template so every post generates correct markup from its existing fields — title, author, and dates you already store. Validate a few pages, confirm the markup matches the rendered content, and then let the template carry it forward. From there, keep author profiles genuine and update timestamps only on real revisions, and your archive steadily becomes easier for AI engines to trust and cite.

Want to confirm your articles are actually exposing this metadata to bots and AI crawlers? Run the free CheckMy.site scanner to see how your pages appear to the engines deciding whether — and how — to cite you.