Article Schema Implementation: The Complete 2026 Guide

Article schema is the single most impactful structured data type for content-driven websites. It tells search engines exactly what your page contains, who created it, and when it was published. A correctly implemented Article schema is the foundation for news rich results, author attribution in...

Understanding Article and Its Subtypes

Schema.org defines Article as a type of CreativeWork. Three specialized subtypes exist: NewsArticle for time-sensitive journalism, BlogPosting for blog entries, and ScholarlyArticle for academic papers. Each inherits all Article properties and adds domain-specific ones.

Google differentiates between these subtypes for rich result eligibility. A NewsArticle can appear in Top Stories and Google News. A BlogPosting may qualify for the general rich result carousel. Using the correct subtype matters (Google Search Central, "Article Rich Results," 2025).

Required Properties for Article Rich Results

Google requires three properties for a page to be eligible for Article rich results.

headline is the title of the article. It should match or closely approximate the visible <h1> on the page. Google does not require an exact match, but consistency improves confidence signals.

image is a representative image for the article. The image must be at least 1200 pixels wide, meet Google's content policy standards, and be declared using the image property with an ImageObject type or direct URL.

datePublished must be an ISO 8601 date string with or without time. Google also recommends dateModified for the last revision date, which can improve crawl freshness signals.

Complete JSON-LD Example

Here is a production-ready Article schema block:

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Article Schema Implementation: The Complete 2026 Guide",
  "description": "A complete technical guide to implementing Article schema with JSON-LD.",
  "image": "https://example.com/images/article-schema-guide.jpg",
  "datePublished": "2026-06-15T08:00:00+00:00",
  "dateModified": "2026-06-15T14:30:00+00:00",
  "author": {
    "@type": "Person",
    "name": "Alex Rivera",
    "url": "https://example.com/authors/alex-rivera"
  },
  "publisher": {
    "@type": "Organization",
    "name": "TechPub Inc.",
    "logo": {
      "@type": "ImageObject",
      "url": "https://example.com/logo.webp",
      "width": 600,
      "height": 60
    }
  },
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "https://example.com/article-schema-guide"
  }
}

This block declares the headline, image, publication date, author, publisher with logo, and the canonical page URL. Every single property uses a valid schema.org type.

Author and Publisher Markup Best Practices

The author property can be a Person or Organization. For multi-author publications, use an array of Person objects. Always include a url pointing to the author's biography or contributor page. Google uses this for author attribution in search results and for connecting entities in its knowledge graph.

The publisher property requires an Organization type with a logo. The logo must be at least 112 pixels wide, have a 1:1 or 4:3 aspect ratio, and be on a solid background. An Organization without a valid logo will fail the rich result eligibility check (Schema.org, "Article Type Definition," 2026).

Article Schema for AMP and News

AMP pages must include Article schema in the <head> as a JSON-LD block. The same properties apply. For NewsArticle specifically, Google recommends adding dateline for the location the news was reported and articleSection for the section or category.

News publishers should also include isAccessibleForFree with a boolean value to indicate paywall status and hasPart with WebPageElement for article sections in long-form journalism.

Common Article Schema Mistakes

Mismatched headline is the most common error. If the JSON-LD headline differs significantly from the HTML <title> or <h1>, Google may treat the markup as potentially misleading. Keep all three aligned.

Missing publisher logo blocks rich result eligibility even when all other properties are valid. The logo property is frequently omitted in automated implementations.

Incorrect date format causes silent validation failures. Always use ISO 8601 with timezone offset. Dates without timezone information are assumed to be UTC, which may or may not match your publishing workflow.

Audit Checklist

[ ] Article subtype matches content type (Article, NewsArticle, or BlogPosting)
[ ] headline matches or closely aligns with visible page title
[ ] image is at least 1200px wide and accessible via a public URL
[ ] datePublished uses ISO 8601 with timezone
[ ] publisher.logo.width is at least 112px
[ ] author.url points to an accessible author page
[ ] JSON-LD passes Rich Results Test
[ ] No Article markup on non-article pages (category pages, landing pages)

Conclusion

Article schema is a well-defined, well-documented type that rewards careful implementation. Use the correct subtype, provide every required property, and validate before deployment. The effort is minimal compared to the visibility gains from rich result eligibility and improved entity...

Ready to Build Your Dream Website?

Let's discuss your project and create something amazing together.