Article schema generator
Build Article, NewsArticle or BlogPosting markup that tells Google who wrote the piece, when it was published and updated, and which images represent it.
All Google-required properties present. That makes the page eligible, not guaranteed. Google's docs
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "How we cut our product page weight by 60%",
"description": "A walkthrough of the image, font and script changes that made our store load in under two seconds on 4G.",
"url": "https://example.com/blog/page-weight",
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://example.com/blog/page-weight"
},
"image": [
"https://example.com/img/page-weight-16x9.jpg",
"https://example.com/img/page-weight-1x1.jpg"
],
"datePublished": "2026-09-14T09:00:00",
"dateModified": "2026-09-20T16:30:00",
"author": [
{
"@type": "Person",
"name": "Maya Okafor",
"url": "https://example.com/team/maya"
}
],
"publisher": {
"@type": "Organization",
"name": "Example Outfitters",
"logo": {
"@type": "ImageObject",
"url": "https://example.com/logo.png"
}
}
}
</script>When to use Article markup
- News stories, blog posts, how-to guides and opinion pieces.
- Any page whose main content is a single piece of editorial writing.
- Not for category pages, product pages or pages that list many articles.
Getting it right
- Google lists no required properties for Article, so completeness is about the recommended set: headline, image, datePublished, dateModified and author.
- Give each author their own object with a name and a url pointing to a bio page; don't put "By Jane and John" in one name.
- Provide images in 16:9, 4:3 and 1:1 crops when you have them; Google picks the one that fits the surface.
- Include a time-zone offset in dates. Without it, Google assumes Googlebot's time zone.
- Only change dateModified when the content meaningfully changes.
Source: Google Search Central, Article structured data documentation, and schema.org/Article.
Google's property list
| Property | Google says |
|---|---|
| No required properties for this type. | |
author | recommended |
author.name | recommended |
author.url | recommended |
dateModified | recommended |
datePublished | recommended |
headline | recommended |
image | recommended |
Example output
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "How we cut our product page weight by 60%",
"description": "A walkthrough of the image, font and script changes that made our store load in under two seconds on 4G.",
"url": "https://example.com/blog/page-weight",
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://example.com/blog/page-weight"
},
"image": [
"https://example.com/img/page-weight-16x9.jpg",
"https://example.com/img/page-weight-1x1.jpg"
],
"datePublished": "2026-09-14T09:00:00",
"dateModified": "2026-09-20T16:30:00",
"author": [
{
"@type": "Person",
"name": "Maya Okafor",
"url": "https://example.com/team/maya"
}
],
"publisher": {
"@type": "Organization",
"name": "Example Outfitters",
"logo": {
"@type": "ImageObject",
"url": "https://example.com/logo.png"
}
}
}Article schema questions
Should I use Article, NewsArticle or BlogPosting?
All three are treated the same way by Google's Article documentation. Use the most specific one that is honest: NewsArticle for journalism, BlogPosting for blog entries, Article for everything else.
Does Article markup give me a rich result?
It helps Google show the right title, image and date in Top stories, Discover and other surfaces, but no markup guarantees a particular appearance.
Is the publisher property required?
No. Google's current Article documentation doesn't list publisher among its recommended properties, though schema.org supports it and it does no harm.