BlogPosting structured data

Definition: Schema.org defines BlogPosting as “A blog post.” It is a type of structured data, a standardized format for describing page content, that identifies an individual blog entry and its properties.

Key facts

• Schema.org's BlogPosting definition places the type beneath SocialMediaPosting, which is beneath Article in its hierarchy.
• As of 17 October 2026, Google's Article documentation accepts BlogPosting for Article objects and lists recommended properties without requiring particular properties.
• Google's general structured data guidelines call for the most specific applicable type and markup that accurately represents visible page content.

Which properties describe a blog entry?

Schema.org's property table includes properties inherited from broader types. Inheritance means that a subtype can use properties listed for its parent types. BlogPosting therefore has access to article fields and the more general properties of CreativeWork, the parent type for creative works.

articleBody contains the article's text. articleSection identifies an editorial section, with Sports and Lifestyle given as examples. wordCount records the number of words as an integer. headline holds the article heading.

author identifies a person or organization responsible for the content, while publisher identifies its publisher. datePublished records first publication; dateModified records the most recent modification. Schema.org allows dates or date-and-time values for these fields.

image accepts an image URL or an ImageObject, an object describing an image. mainEntityOfPage points to the page whose main subject is the post. isPartOf identifies a containing work; Schema.org's example uses a Blog object here. The inherited sharedContent property describes creative content shared within the posting, such as an image or video.

What does the markup look like?

The W3C defines JSON-LD as a JSON-based format for linked data. Schema.org's BlogPosting example embeds it in an HTML script element. This reduced extract preserves the example's type, headline, publication date and author details:

<script type="application/ld+json">
{
  "@context": "https://schema.org/",
  "@type": "BlogPosting",
  "headline": "Library Metadata Evolution: The Final Mile",
  "datePublished": "2019-05-14",
  "author": {
    "@type": "Person",
    "name": "Richard Wallis",
    "url": "https://dataliberate.com/author/richard-wallis/"
  }
}
</script>

The full example also connects the post to its publisher and containing blog. These relationships describe separate roles: the person writes the post, an organization publishes it, and the blog contains it.

How does Google document implementation and checks?

Google's Article guide recommends author, headline, image, datePublished and dateModified. Its date fields use ISO 8601 date-and-time values, and it recommends timezone information. Its author guidance calls for each visible author to have a separate author object, with a name and an identifying URL.

Google's general guidelines recommend JSON-LD and require the markup to describe the page on which it appears. A content review checks that the marked-up author and article information match what readers see. Image URLs must be crawlable and indexable.

The same guidelines identify the Rich Results Test and URL Inspection tool as technical checks. They also state that automated tools have limits when assessing content quality, so technical validation accompanies the review of visible content.

Related terms

• Structured data
• JSON-LD
• Article structured data
• Person structured data
• Article update dates

FAQ

Should a whole blog use BlogPosting?

Schema.org's BlogPosting definition describes an individual post. Its example uses Blog for the containing publication and connects the post through isPartOf.

Must every property be filled in?

Google's Article documentation lists no required properties. It recommends adding the properties that apply to your content.

Can the structured data replace the visible author information?

Google's content guidelines require markup to represent visible page content. Keep your displayed author information and the structured author object consistent.

Sources

1. Schema.org, "BlogPosting", undated
2. Google Search Central, "Article (Article, NewsArticle, BlogPosting) structured data", updated 8 September 2026
3. Google Search Central, "General structured data guidelines", updated 10 July 2026
4. W3C, "JSON-LD 1.1", 16 July 2020

---

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