Article schema markup.
Article, NewsArticle, and BlogPosting schemas describe editorial content to search engines. The property set is consistent across the three subtypes; the differentiation is in rich-result eligibility on specific surfaces. The load-bearing property for E-E-A-T is the author nesting, which grounds the named-author claim in a Person entity with a verifiable identity chain.
Article schema is one of the smallest implementation surfaces and one of the most consequential trust signals. Natural SEO Services wires the author Person node to LinkedIn and the author page on every editorial publication.
Headline, datePublished, dateModified, author, image, publisher.
Headline is the article title as the user reads it. Google's documentation recommends keeping the headline under 110 characters to prevent truncation in rich-result surfaces. The headline must match the visible page title; mismatches between the schema headline and the rendered headline trigger the consistency-requirement penalty.
datePublished and dateModified should be ISO 8601 timestamps with timezone. datePublished is the original publication; dateModified is the latest substantive content update. Both feed freshness signals and influence Top Stories eligibility on news-shaped content. The published anti-pattern: updating dateModified without making substantive content changes (the spam policies cover this).
Author is the property that carries the E-E-A-T signal. Nest author as a Person object with name, url (pointing to the author's profile page on the site), and sameAs (an array of external identity surfaces like LinkedIn, Wikipedia, or institutional profiles). The deterministic linking is what makes the named-author claim machine-readable and reconcilable with the Knowledge Graph.
Image is the primary visual associated with the article. Google's documentation requires the image and recommends multiple aspect ratios (1:1, 4:3, 16:9) so the rich result can adapt to different surface placements. Publisher is the Organization node that owns the publication, typically referenced by @id to the standalone Organization node defined at the site level.
Person with name, url, sameAs, and the Knowledge Graph reconciliation that follows.
The author Person node is the surface that grounds the named-author claim. The properties matter: name (the author's full name as it appears in the byline), url (the canonical URL of the author's profile page on the site, typically /author/[slug]/), and sameAs (an array of external identity surfaces). The sameAs chain is what enables Knowledge Graph reconciliation: LinkedIn profile, institutional page, professional credentialing body, Wikipedia entry where one exists.
The standalone Person node pattern keeps the author entity addressable as @id at the site level. The Article's author property then references the Person by @id rather than re-declaring the node inline on every article. The single source of truth for the author entity is the standalone node; the per-article reference is a pointer. This pattern simplifies maintenance and makes the entity claim consistent across the site.
For YMYL topics where E-E-A-T thresholds are heightened, the author Person nesting carries additional weight. jobTitle, worksFor (Organization), knowsAbout (array of expertise topics), and alumniOf where relevant let the crawler read the credentialing surface that the YMYL Quality Rater Guidelines treat as load-bearing for trust. The named author claim becomes a machine-readable entity claim that the ranking systems can evaluate against the topic the article addresses.
What operators ask about Article schema markup before the implementation work starts.
- 01.Which Article subtype should the page use?
- Three subtypes exist: Article (the general parent), NewsArticle (for news publication content), and BlogPosting (for blog-style editorial content). The choice affects rich-result eligibility on specific surfaces (Top Stories prefers NewsArticle), but the underlying property set is consistent across the three. For most editorial content that is not strict news publication, BlogPosting is the conventional choice. NewsArticle is reserved for content from publishers that qualify for Google News inclusion.
- 02.What are the required properties?
- Google's documentation names headline (the article title) and image (the primary image associated with the article) as required for rich result eligibility. The documentation also strongly recommends author, datePublished, and dateModified. The author property nesting is the load-bearing surface for E-E-A-T: the author should be a Person node with name, url pointing to the author page, and sameAs linking external identity surfaces like LinkedIn.
- 03.How does Article schema interact with E-E-A-T?
- The author property nesting is the entity-reconciliation surface. When the Article's author is a Person node with a verifiable url and sameAs chain, the crawler reconciles the author claim with the Knowledge Graph. This deterministic linking lets the ranking systems attribute content to a known entity rather than relying on lexical extraction of the author name from byline text. The named-author claim becomes machine-readable. For YMYL topics where E-E-A-T thresholds are heightened, the schema-grounded author entity is one of the load-bearing surfaces.
- 04.What about datePublished and dateModified?
- Both should be ISO 8601 format with timezone. datePublished is the original publication timestamp; dateModified is the latest substantive content update. The dates feed freshness signals and influence Top Stories eligibility on news-shaped content. Updating dateModified without making substantive content changes is a documented anti-pattern that Google's spam policies cover. The dates should reflect actual publication and update events.
If you want Article schema implemented as a load-bearing E-E-A-T surface rather than a checkbox, see how we work.
Two-week diagnostic. The Article schema work sits inside the broader EEAT operationalization program, alongside the named-author surface, the credentialing layer, and the editorial-publication signals the integrated core ranking systems reward.