Article Structured Data: Fields and Validation

Article markup describes article rich results in the pinned Atlas registry. Its recorded status is supported, which is a documentation and validation boundary rather than a promise of a particular search presentation.

Use Article schema only when the visible page actually contains and owns the entity or content being described. The reviewed page contexts are article, blog, homepage, other. A type can be valid vocabulary while remaining irrelevant, ineligible, misleading, or unsupported for a specific page.

Structured data should make an existing page easier to interpret. It should not introduce hidden reviews, ratings, products, people, events, jobs, services, questions, steps, or other facts that users cannot verify in the visible content.

The Atlas record lists these required fields for Article: headline. Required means the registry expects the property for the reviewed feature or vocabulary contract; it does not override stricter current documentation or page-specific policy.

Recommended fields are author, datePublished, image. Add them only when the page owns accurate values. Visibility requirements are headline, and the broader rule remains that material structured claims must match visible content.

• Confirm the page purpose is one of the reviewed contexts: article, blog, homepage, other.
• Inventory the required properties: headline.
• Compare visibility requirements with the page: headline.

Implement Article schema from the same content record that renders the page whenever possible. That ownership prevents a detached JSON-LD template from retaining an old title, entity, price, date, author, rating, location, or availability after visible content changes.

Use stable canonical identifiers for recurring entities, absolute URLs for public references, and correctly shaped values for dates, numbers, lists, and nested objects. Keep route-specific markup out of global shells that can duplicate it across unrelated pages.

• Add page-owned values for the required Article properties before optional enrichment.
• Review recommended properties without inventing absent facts: author, datePublished, image.
• Keep JSON-LD values consistent with the visible page and the current primary documentation.

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Visible headline value",
  "author": "Use the correctly typed visible entity",
  "datePublished": "2026-07-20"
}

Validate Article schema in the final deployed HTML. First parse the JSON, then check Schema.org vocabulary shape, then review feature-specific required properties and policy, and finally compare every material value with what a user can see on the canonical page.

The source record was reviewed on 2026-04-17. Recheck the primary documentation before a release when the feature, status, or Search presentation could have changed since that date.

• Parse the final deployed JSON-LD rather than a detached editor snippet.
• Review the Article record against its official documentation and Atlas status supported.
• Check that no hidden, misleading, expired, or unsupported values survive the render path.

A parser success does not establish feature eligibility or rich-result selection.

Article can be valid Schema.org vocabulary while having limited or no special Google Search presentation.

Do not mark a reference page like this one as Article merely because it discusses the type. This page is an Article about Article schema; its JSON-LD must describe the visible article, not impersonate the subject of the guide.

Claim boundary: Valid Article markup can establish technical eligibility only. It does not guarantee crawling, indexing, a rich result, ranking, impressions, or clicks.

1. Article structured data documentationGoogle Search Central / checked 2026-04-17

   Primary documentation referenced by the Atlas Article registry record.