Article Schema

What is Article Schema?

Article¹ is the schema.org JSON-LD type for editorial content: news pieces, blog posts, long-form essays, and informational guides. It captures the metadata that bare HTML doesn't: who wrote it, when it was published, when last modified, what publication it belongs to, and what topical scope it covers.

A typical Article payload includes:

• headline: the article title
• author: a Person object with name + URL
• datePublished and dateModified: ISO date strings
• publisher: an Organization object
• image: main image URL with dimensions
• mainEntityOfPage: the canonical URL of this article

Google's Article rich-result eligibility covers three schema.org types: Article itself, NewsArticle (journalistic content with a date hook), and BlogPosting (blog-format posts; BlogPosting inherits transitively from Article via SocialMediaPosting in schema.org, but Google treats it as a first-class Article subtype)². Other Article descendants like ScholarlyArticle and TechArticle exist in schema.org but aren't part of Google's Article rich-result eligibility set. Most editorial sites use Article as the safe default unless one of the supported subtypes is a stronger match.

Status in 2026

Foundational and broadly expected. Article schema is the baseline metadata layer for any publication that wants accurate authorship and freshness attribution in AI search results². The fields it exposes (datePublished, dateModified, author) are commonly hypothesized to feed Google's E-E-A-T inference and AI engines' citation-eligibility decisions, though no major engine has publicly confirmed how heavily these specific fields weight. Empirically, sites that ship Article schema and sites that don't both get indexed and cited; whether the schema fields independently move the needle beyond what engines could derive from the visible page is not isolated by public study. The practical case for shipping it is low-cost hygiene: most CMSes generate it automatically, and citations that do credit authorship tend to draw on the structured author field rather than guessing from prose.

A worthwhile counterweight: independent SEO consultant Jono Alderson (formerly at Yoast SEO, widely respected on structured data) framed the broader limit honestly in a November 2024 piece on his blog: "Maybe Schema.org is 'just' labels and connections. Maybe we don't get any magic powers from it right now. Maybe we were over-sold by Google."³ The same caution applies here: shipping author and datePublished does not make a low-authority, stale, or thin article cite-able. Article schema improves machine-readability for editorial content that already deserves citation; it does not create citation-worthiness from nothing.

Note on this entry's territory (paired with the FAQ schema, DefinedTerm schema, HowTo schema, BreadcrumbList, and JSON-LD entries as schema cluster siblings): Article as a schema.org type is vendor-canonical. Schema.org maintains the vocabulary, and Google Search Central documents rich-result eligibility (Article + NewsArticle + BlogPosting). The application to AI search engine citation behavior (whether the author / datePublished / headline fields independently weight in citation selection versus being machine-readable convenience metadata derivable from visible content) is non-vendor-canonical because no major engine publishes Article-specific weighting. The content-side application (filling author with a Person object, keeping dateModified honest, matching headline to H1) sits in practitioner-discipline territory: writers can directly verify schema validity via Google's Rich Results Tester and schema.org's validator. Paired with the other schema cluster anchors: each declares a different facet of a page; Article declares the editorial-metadata facet, who wrote it, when, and where it belongs in the publication.

How to apply

Article schema is one of the cheapest schema additions to ship. Most static-site frameworks and CMSes generate it automatically from frontmatter. Three concrete moves:

• Wire author to a real Person schema, not a freeform string: "author": "Jane Doe" is parseable, but "author": { "@type": "Person", "name": "Jane Doe", "url": "/about/jane-doe" } lets engines build a richer entity record. Google's Article documentation recommends Person or Organization with a url for this reason; whether engines independently weight Person-typed vs string authors is a common practitioner hypothesis but is not vendor-documented as a ranking or citation signal.
• Bump dateModified only on legitimate updates: search and AI systems may discount or ignore freshness signals when the visible update date does not match substantive content changes. Detection mechanisms (content-diff inspection for crawl-based systems, re-embedding cycles for retrieval-based AI engines) are plausible but not vendor-documented. No engine has published a specific date-spoofing penalty policy, but practitioners report excessive date-bumping correlates with reduced citation over time. Update the date when you genuinely revise the content; keep it stable otherwise.
• Match headline to the visible <h1>: Google's Article documentation requires headline to correspond to the visible page title and caps it at 110 characters; titles longer than this should be trimmed in the schema field even if the H1 retains the full string. Whether mismatch independently suppresses rich-result eligibility or reduces AI citation is plausible but not vendor-documented as a specific penalty.

What to skip: Article schema on glossary entries (use DefinedTerm), product pages (use Product), or pages that are really FAQs masquerading as articles. Schema type should match content type as a readability principle; whether mismatched types actively harm citation more than no schema is not vendor-documented, but Google's "Spammy structured markup" manual action does target deliberate misuse.

How it relates to other concepts

• Foundational metadata layer paired with FAQ schema (for Q&A structure; note that FAQPage rich results were fully deprecated for all sites on May 7, 2026) and HowTo schema for content-heavy pages.
• Provides a structured input channel for E-E-A-T authorship inference via the author property. Whether engines independently weight Article's author field beyond what they could infer from the visible byline + linked author page has not been isolated by public study.
• Sibling to DefinedTerm schema: Article for editorial content, DefinedTerm for terminology entries; they coexist on glossary-with-blog sites.
• Foundational for GEO. Article metadata is what makes content cite-able as a discrete editorial piece rather than as a domain-level mention.