BlogPosting Schema Markup
BlogPosting is a subtype of Article for blog content. While Google treats it identically to Article for rich result purposes, using BlogPosting can help structure your content semantically and makes your markup more precise.
Eligible Rich Results
When to Use BlogPosting
Properties
| Property | Type | Status | Description |
|---|---|---|---|
| headline | Text | required | The blog post title. |
| image | URL or ImageObject | required | Featured image for the post. |
| datePublished | Date or DateTime | required | When the post was published. |
| dateModified | Date or DateTime | recommended | When the post was last updated. |
| author | Person | required | The blog post author. |
| publisher | Organization | recommended | The blog or publication. |
| description | Text | recommended | Post summary or excerpt. |
| articleBody | Text | optional | The full text content. |
| wordCount | Integer | optional | Number of words. |
| keywords | Text | optional | Comma-separated tags or keywords. |
JSON-LD Examples
Personal Blog Post
A simple blog post with author and basic metadata.
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "My Journey Learning React in 2024",
"image": "https://myblog.com/react-journey.jpg",
"datePublished": "2024-02-20",
"author": {
"@type": "Person",
"name": "Alex Developer",
"url": "https://myblog.com/about"
},
"description": "What I learned spending 3 months building React apps from scratch.",
"wordCount": 2500,
"keywords": "React, JavaScript, Web Development, Learning"
}Common Mistakes
Assuming BlogPosting gets different treatment from Article — Google treats them the same for rich results.
Not including publisher information — even personal blogs should have a publisher Organization.
Complete Guide to BlogPosting Schema Markup
BlogPosting is a more specific subtype of Article designed for blog content. While Google currently processes BlogPosting and Article identically for rich result eligibility, using the correct type makes your markup more semantically accurate and future-proof.
For bloggers and content creators, the markup implementation is identical to Article — you need headline, image, datePublished, and author at minimum. The main advantage of using BlogPosting is semantic clarity: it tells consuming applications (not just Google) that this content lives in a blog context.
A common question is whether to use Article or BlogPosting. The answer is simple: if the content is published on a blog, use BlogPosting. If it's a standalone article or news piece, use Article or NewsArticle. There's no SEO advantage either way — Google treats them identically.
One often-overlooked property is keywords. While Google doesn't use the meta keywords tag for ranking, the keywords property in structured data helps define the topical scope of your content. It can influence how Google categorizes your content for Google Discover recommendations.
Related Types
Ready to Create BlogPosting Markup?
Use our free generator to create valid BlogPosting JSON-LD markup with a visual form. No coding required.
Open Generator