In short. Article structured data describes article details that Google uses to understand pages and support search presentation.

Definition: Article structured data is machine-readable markup that describes an article using Schema.org's Article type or a subtype such as NewsArticle or BlogPosting. It identifies article details, including the headline, authors, images and publication dates.

Key facts

As of October 2026, Google's Article documentation supports Article, NewsArticle and BlogPosting, with recommended properties and no required properties.
Schema.org's Article definition includes articleBody for the article text and articleSection for a publication section, such as Sports.
Google's general structured data guidelines recommend JSON-LD as a markup format and require the data to represent the page content accurately.
Google's AI features guidance says AI Overviews and AI Mode require no special Schema.org markup. A supporting page must be indexed and eligible to appear in Search with a snippet.

Which properties does Google support?

Google's Article property table lists the following recommended fields. Applicable information comes from the article itself.

Property	Meaning and implementation detail
`headline`	The article title. Google recommends a concise title because some devices truncate long titles.
`author`	A `Person` or `Organization` describing the author.
`author.name`	The author's name. Publisher names and job titles belong in separate properties.
`author.url`	A page uniquely identifying the author, such as a biography or social profile. Google also accepts `sameAs` for author identification.
`datePublished`	When the article is first published, expressed in ISO 8601 date and time format. Timezone information is recommended.
`dateModified`	When the article is most recently modified, using the same date and time format.
`image`	An article-relevant image URL or `ImageObject`. Image URLs must be crawlable and indexable.

The same documentation recommends including every author shown on the page, with a separate author object for each person. It recommends author profile page markup when author.url points to an internal profile.

What does the markup look like?

Google's JSON-LD example embeds the article data in a script element. The following shortened adaptation retains its example headline, dates and author; these values are placeholders from the documentation.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "NewsArticle",
  "headline": "Title of a News Article",
  "image": [
    "https://example.com/photos/1x1/photo.jpg",
    "https://example.com/photos/4x3/photo.jpg",
    "https://example.com/photos/16x9/photo.jpg"
  ],
  "datePublished": "2024-01-05T08:00:00+08:00",
  "dateModified": "2024-02-05T09:20:00+08:00",
  "author": [{
    "@type": "Person",
    "name": "Jane Doe",
    "url": "https://example.com/profile/janedoe123"
  }]
}
</script>

Google's placement guideline puts structured data on the page it describes. Its content guidelines require the marked-up information to be visible to readers.

What does Google use it for, and how is it checked?

Google's implementation guide describes Article markup as helping it understand article pages and present title text, images and dates in Search and other properties, including Google News. Article markup is optional for eligibility for Google News features such as Top stories. Search appearance remains subject to Google's selection systems.

The guide recommends validating the code with the Rich Results Test and fixing critical errors. After deployment, the URL Inspection tool checks how Google sees the page. Google needs access without robots.txt blocking, a noindex directive or a login requirement. The Rich Results Test omits warnings for the optional publication and modification dates, so a clean test alone is insufficient to check their presence.

FAQ

Must I add every recommended property?

Google's Article guidance says there are no required properties. You can add the recommended properties that apply to your content.

Does the whole article text belong in the markup?

Schema.org defines articleBody as the actual body of the article. Google's recommended Article property table focuses on fields such as the headline, author, images and dates; articleBody is outside that table.

Can I put Article markup on content readers cannot see?

Google's content guidelines require the marked-up content to be visible to readers. Your markup must accurately represent the page.

Sources

Check how a page reads to answer engines. Open the GEO score analyzer