Article and BlogPosting schema: structured data for articles

By Articlate Team · · 2 min read · updated on

Structured data is a block of code that describes the page: who wrote it, when it was published, what the main image is. The format Google recommends is JSON-LD, placed in the page's HTML.

Article or BlogPosting?

BlogPosting is a more specific type of Article, used for blog posts. Either one works for articles. What matters is that the information matches what the visitor sees on the page.

Main fields

  • headline: the article title.
  • datePublished and dateModified: dates in ISO 8601 format.
  • author: a person or organization, with a name and, preferably, a URL.
  • image: one or more images of the article.
  • publisher and mainEntityOfPage: who publishes and the page's URL.

Example

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "Article title",
  "datePublished": "2026-01-15T09:00:00-03:00",
  "dateModified": "2026-02-01T10:30:00-03:00",
  "author": {"@type": "Person", "name": "Author name"},
  "image": ["https://yoursite.com/cover.jpg"],
  "mainEntityOfPage": "https://yoursite.com/article"
}
</script>

How to validate

Use Google's Rich Results Test and the Schema.org validator. They point out syntax errors and missing recommended fields.

What not to expect

  1. Structured data does not guarantee a highlight in the results and does not improve ranking on its own.
  2. Do not mark up information the visitor cannot see on the page.
  3. Some features, such as the ones for frequently asked questions, became restricted to certain types of sites. Check the current documentation before planning.

Conclusion

Marking up the article well is a simple step that makes the content clearer to the systems that process it. Do it together with the other technical adjustments, such as the heading structure.