Article Schema: A Practical JSON-LD Template for Editorial Pages
A source-backed guide to Article structured data: key fields, common mistakes, and a repeatable approach to keep editorial schema correct as templates change.

Article schema is easiest to maintain when your CMS stores clean fields (title, author, dates) and templates output JSON-LD consistently.
TL;DR (Key takeaways)
- Google provides an Article structured data reference and examples. (Article structured data)
- Schema.org defines the underlying vocabulary (Article, NewsArticle, BlogPosting). (Schema.org: Article)
- Keep Article schema aligned with visible content and stable author identity.
- Validate with Rich Results Test and Schema Validator before and after template changes.
What we know (from primary sources)
Google’s documentation describes how to add Article structured data and provides required/recommended properties for eligibility. (Google: Article structured data)
Schema.org defines the Article type and related types (e.g., NewsArticle, BlogPosting), along with properties like author, headline, and datePublished. (Schema.org)
A practical “template” (fields to capture in your CMS)
You don’t need complicated schema logic. You need clean fields and consistent output. Capture these as first-class fields:
- headline (your H1)
- description (meta description / summary)
- datePublished and dateModified
- author (person or organization) with stable identity
- mainEntityOfPage / canonical URL alignment
- image (if you use featured images)
For author identity specifics, see Person & Author Markup.
Common mistakes
Schema drift (fields don’t match the page)
The most common issue is mismatch: a headline in schema that differs from the page, or an author in schema that doesn’t exist visibly. Treat schema as an extension of the page, not a separate marketing layer.
Broken JSON-LD after template changes
Any refactor (especially AI-assisted) can break JSON-LD generation. Add schema checks to your release checklist — see Schema Testing Workflow.
What’s next
- Pick 5 representative articles and validate with Rich Results Test. (Rich Results Test)
- Validate JSON-LD syntax with Schema Validator. (Schema Validator)
- Consolidate your overall schema plan in the hub playbook: Structured Data Playbook.
Why it matters
Article schema is a low-friction way to make your editorial metadata explicit to machines. It helps with rich result eligibility in classic search and strengthens entity clarity in AI-era discovery systems that reward stable authorship and well-structured sources.
For broader AI context, start with AI & SEO trends.
Sources
- Google Search Central: Article structured data
- Schema.org: Article
- Google Rich Results Test
- Schema Validator
Updated February 11, 2026.