Article Schema
Article schema is the schema.org/Article vocabulary you embed in a page's code, usually as JSON-LD, to state machine-readably that the page is an editorial article: headline, author, datePublished, dateModified, publisher. It labels what the article is, not how well it will rank or get cited — those depend on the content itself.
Why it matters
Crawlers and AI systems parse a page as data, not prose. Without markup they have to infer which string is the headline, who wrote it and when. Article schema states that directly, which makes the page easier to parse and its authorship and dates easier to extract. That is a real, if modest, benefit: it is an extractability aid, not a proven ranking or citation lever. Google has said no special schema is required for AI Overviews or AI Mode, and schema has not been a direct ranking factor since 2018. Treat article schema as good hygiene that removes ambiguity, not as a switch that turns visibility on.
How it works
You add a JSON-LD block to the page's source, invisible to readers but readable by crawlers. It holds field-value pairs: headline for the title, author for the writer (ideally linked to an author profile), datePublished and dateModified for freshness, and publisher, typically with a logo. You can write the block by hand, generate it with a CMS plugin, or template it across a content type. The one hard rule: every value in the markup must match what is actually visible on the page. Once it is live, run it through a validator that flags missing required fields or type errors before you consider it done.
Common mistakes
The most damaging mistake is markup that contradicts the visible page — an author name in the schema that appears nowhere in the byline, for instance. That reads as manipulation, and platforms may discard the markup rather than trust it. Just as common: missing required fields, a publisher with no logo, a datePublished that was never updated after a substantive rewrite, or the same article carrying two conflicting schema types. And some teams treat the schema as a one-time task, when in practice it needs to be revalidated every time the article's byline, date or structure changes. None of this will hurt you if you skip it entirely; it will only hurt you if you get it wrong and leave it wrong.
Relation to E-E-A-T and author profiles
Article schema's real value shows up alongside the things that establish trust: a real author profile, a byline that matches a person with demonstrable expertise, and a publisher that is a recognizable entity. The schema does not create authorship or credibility, it exposes credibility that already exists in a form machines can read reliably. Pair it with an author-profile page and consistent publisher information, and you have removed the ambiguity that would otherwise force a crawler or an AI system to guess. Skip the surrounding trust signals and the schema alone will not compensate.
Example
Picture a small tax advisory firm in Leipzig publishing a post on income-tax deadlines. Its CMS template embeds article schema automatically: headline holds the post title, author links to the named tax advisor's profile page, datePublished and dateModified are kept current, and publisher points to the firm with its logo. None of that guarantees the post gets cited by an AI assistant. It does mean that if the post is otherwise well-written and the advisor's expertise is genuinely documented elsewhere, a crawler parsing the page has no ambiguity left to resolve about who wrote it or when.
Common questions
Do I need programming skills to add article schema?
No. Most CMS platforms generate the JSON-LD block through a plugin or template. What matters more than the code itself is that every value in the markup matches the visible page, and that it gets updated when the byline or date changes.
Will article schema get my content cited by ChatGPT or included in AI Overviews?
Not by itself. Google states plainly that no special schema is required for AI Overviews or AI Mode, and schema stopped being a direct ranking factor in 2018. It helps machines parse authorship and dates correctly; it does not substitute for original, trustworthy content.