Article Schema Markup for
Blogs & Publishers
Whether you run a niche content blog, a multi-author magazine, or a news site, Article schema is how you tell Google what a piece is, who wrote it, when it was published, and who stands behind it. In an era where Google weighs experience and authorship heavily, and where AI systems decide which sources to cite, that authorship and freshness signal is no longer optional.
Get Started FreeWhat is Article schema?
Article schema is structured data describing an editorial page. The vocabulary is a small hierarchy: Article is the parent, with BlogPosting for blog-style content and NewsArticle for journalism. Each carries the same core properties: headline, image, author, publisher, datePublished, and dateModified. Picking the right subtype tells Google what kindof content it's looking at.
The point of this markup isn't a flashy rich card. It's clarity: Google reads it to attribute the piece to a real author, tie it to a publishing organization, and understand how fresh it is, all inputs into how your content is evaluated and surfaced.
Why blogs and publishers need Article schema
Google's quality systems reward content with clear experience and authority. Marking up author as a real Person, with a profile URL and sameAs links to their credentials, connects your content to an identifiable, trustworthy source rather than an anonymous byline.
datePublished and dateModified tell Google when a piece was written and last updated. For fast-moving topics, an accurate dateModified signals that a page is maintained.
For news publishers, NewsArticle markup with correct dates is part of qualifying for Google News and Top Stories treatment.
Answer engines synthesizing a response to an informational query need to know who said something and whether it's current. Clean authorship and date signals make your content more attributable, and a source that can be attributed is a source that can be cited.
A complete Article JSON-LD example
Here's correct BlogPosting markup with a real author and publisher entity:
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"@id": "https://example.com/blog/local-seo-guide#article",
"headline": "The 2026 Guide to Local SEO",
"image": "https://example.com/images/local-seo.jpg",
"datePublished": "2026-02-10T08:00:00+00:00",
"dateModified": "2026-05-04T10:15:00+00:00",
"author": {
"@type": "Person",
"@id": "https://example.com/author/jane-doe#person",
"name": "Jane Doe",
"url": "https://example.com/author/jane-doe",
"sameAs": ["https://www.linkedin.com/in/janedoe"]
},
"publisher": {
"@type": "Organization",
"name": "Example Media",
"logo": {
"@type": "ImageObject",
"url": "https://example.com/logo.png"
}
},
"mainEntityOfPage": "https://example.com/blog/local-seo-guide"
}author as a Person (not a plain string) with a url and sameAs: this is your authorship and E-E-A-T signal.
datePublished / dateModified in ISO 8601 format, reflecting the real publish and update times.
publisher with a valid logo, required for many article rich treatments.
headline kept concise (long headlines can be truncated or ignored).
News publishers: use NewsArticle
If you publish journalism, switch the type to NewsArticle. This is the signal that tells Google your content belongs in the news ecosystem, and it's part of qualifying for Google News and Top Stories. News content is judged harder on freshness and accuracy, so precise ISO 8601 datePublished/dateModified values matter even more here, and a clear publisher identity is essential. A general blog and a news site can share the same site, but each piece should carry the subtype that matches what it actually is.
Author and publisher entities
The highest-leverage move on this page type is treating your authors as entities, not text. Give each author a profile page, a stable @id, and sameAslinks to their professional profiles or published work. Do the same for your publishing organization. Over time this builds an author knowledge graph that reinforces every article they write, exactly the kind of experience-and-authority signal Google's systems look for.
A note on FAQ, Q&A, and comment sections
Publishers often bolt an FAQ section onto posts, so it's worth being precise about where each question-oriented type stands.
FAQPage(where you publish your own questions and answers) lost its Google rich result on May 7, 2026. The markup is still valid, still unpenalized, and still parsed by Bing and AI crawlers, but it no longer produces a dropdown in Google. AI Schema Gen can still auto-detect and generate it, just don't expect a SERP feature. We covered the full picture in Is FAQ Schema Dead?
Q&A and Discussion forum are a different story, and this is where publishers leave value on the table.Both remain fully supported in Google's structured data gallery. If your site has genuine community-submitted answers, an active comment section with substantive discussion, or a forum area, that content may qualify for a rich result that your Article markup alone won't get you. Many publishers mark these pages up as FAQPage or leave them bare when Q&A or Discussion forum is the accurate (and still-rewarded) type.
The rule is the same as always: use the type that honestly describes the page. A question you wrote and answered yourself is FAQPage. A question your readers answered is Q&A.
How to add Article schema in WordPress
Manual markup doesn't scale across a growing archive, and static dates go stale the moment you update a post. Your options:
Per post: unworkable at volume.
Basic Article output is common, but author-entity handling and subtype control are often shallow.
Builds Article/BlogPosting/NewsArticle markup with proper author and publisher entities, keeps dateModified accurate, and auto-detects FAQ content.
See the AI Schema Gen vs Yoast comparison for specifics.
The flow:
- 1Install the plugin and connect your free account.
- 2AI Schema Gen reads each post's author, dates, and content.
- 3It generates the correct subtype with real Person and Organization entities.
- 4Auto-apply keeps dateModified and content in sync on every edit.
- 5Validate before publishing.
Details in the documentation.
Common mistakes that undercut Article markup
Instead of a Person entity: you lose the authorship signal entirely.
So Google can't tell a page is maintained.
Missing, or not meeting the expected format.
That gets truncated.
(or vice versa), muddying how Google classifies the piece.
On the page: a policy violation.
Article schema and AI search
Informational search is the heart of AI Overviews and answer engines, and those systems are selective about attribution: they surface sources they can identify and trust. Content with clear authorship, a real publisher entity, and accurate dates is inherently more citable than an anonymous, undated post. Building author and publisher entities isn't just tidy SEO housekeeping. It's how you make your journalism and blogging legible to the systems now deciding which sources get quoted. The same entity discipline benefits recipe creators and local businesses alike.
Frequently Asked Questions
Give every post the signals search and AI reward
Free plan includes 30 AI generations per month. No credit card required.
Explore more use cases.