Article Schema: A Practical Implementation Guide

What it is and how it works

Article schema is a vocabulary from Schema.org that describes editorial content: news stories, blog posts, guides, and similar. You add it to a page as JSON-LD, a small block of structured data that lives in the HTML and is invisible to readers. Search engines and AI systems parse that block to understand who wrote the page, when it was published, who published it, and what image represents it.

The reason this matters is that a crawler reading raw HTML has to guess at these facts. A byline could be a real author or a category label. A date in the footer could be the publish date or a copyright year. Article schema removes the guesswork by stating each fact explicitly in a format machines read without ambiguity.

There are three common types you will choose between. Article is the general-purpose parent type and a safe default. NewsArticle is for time-sensitive journalism and is the type associated with Top Stories eligibility. BlogPosting is for blog content and behaves almost identically to Article. When in doubt, plain Article is rarely wrong.

Required and recommended properties

Google treats a small set of properties as required for rich result eligibility: headline, image (Google recommends multiple high-resolution images), and either datePublished or both dates. Strongly recommended properties include dateModified, author (with a nested @type of Person or Organization plus a name, and ideally a url), and publisher (an Organization with a name and logo). The more accurate detail you provide, the more confidently a search engine can attribute and display your content.

The SEO and visibility angle

Here is the honest version, because it gets oversold. Article schema is not a ranking factor. Adding it will not move a page up the results page on its own, and any tool that promises a ranking lift from markup alone is selling optimism.

What it actually does is two useful things. First, it clarifies entities: it connects your content to a named author and a known publisher, which supports the broader job of establishing who you are in Google's and AI systems' understanding of the web. Second, it is an eligibility gate. You cannot appear in Top Stories or earn certain rich features without valid markup. Schema does not win you the feature, but its absence can quietly disqualify you from being considered. Think of it as the entry form, not the prize.

Pros and cons

Use cases: who benefits most vs least

Benefits most: news publishers and time-sensitive sites that want Top Stories eligibility; multi-author blogs and editorial sites where author and publisher attribution matters; any content where freshness signals (an accurate dateModified) help. Benefits least: static pages that are not articles, such as product pages, service pages, or a homepage, which have their own more appropriate schema types. Forcing Article markup onto a non-article page adds noise without upside. If you publish help content or guides, pairing Article with FAQ schema and breadcrumb schema often does more than Article alone.

Implementation

Add the following JSON-LD inside a <script type="application/ld+json"> tag in the page head or body. Replace every value with your real data and make sure each one matches what a visitor sees on the page.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Article Schema: A Practical Implementation Guide",
  "image": [
    "https://example.com/images/article-1x1.jpg",
    "https://example.com/images/article-16x9.jpg"
  ],
  "datePublished": "2026-06-06T08:00:00+00:00",
  "dateModified": "2026-06-06T08:00:00+00:00",
  "author": {
    "@type": "Person",
    "name": "Jane Author",
    "url": "https://example.com/authors/jane-author"
  },
  "publisher": {
    "@type": "Organization",
    "name": "SEO ProCheck",
    "logo": {
      "@type": "ImageObject",
      "url": "https://example.com/logo.png"
    }
  },
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "https://example.com/schema-guides/article-schema/"
  }
}
</script>

For NewsArticle or BlogPosting, change only the @type value; the property structure is the same. If your CMS supports it, populate these fields from real post metadata so dates and authors update automatically. For deeper guidance on shaping pages so machines parse them cleanly, see our notes on structuring content for AI.

How to validate

Run every change through two tools before and after publishing. Google's Rich Results Test tells you whether the page is eligible for article rich results and flags missing required properties or errors. The Schema Markup Validator at validator.schema.org checks your markup against the Schema.org vocabulary itself, independent of any one search engine, which is useful for catching structural mistakes Google's tool may not surface. Test the live URL where possible so you validate the markup as it actually renders, not a draft you pasted in.

Common mistakes

• Headline mismatch: the headline value should match the visible page title or H1. A markup headline that differs from what readers see is the single most common warning.
• Missing or stale dateModified: if you update content, update this date. Claiming freshness you do not have, or omitting the field entirely, both undercut the signal.
• Fake or generic authors: "Admin" or an invented persona weakens the entity you are trying to build. Use a real, attributable author with a profile url where you can.
• Images that do not exist or do not match: the image URL must resolve and should reflect the article, not a generic placeholder.
• Markup that contradicts the page: every value in the JSON-LD should be visible or true on the rendered page. Hidden or invented data is the fastest way to have your markup ignored.

FAQ