Article & BlogPosting Schema Generator

Create valid Article, BlogPosting or NewsArticle JSON-LD structured data for your blog posts and news pages — instantly, in your browser, free of charge.

Schema type

Headline

Image URL (optional)

Date published (optional)

Date modified (optional)

Author type

Author name

Publisher name

Publisher logo URL (optional)

JSON-LD code

Fill in the required fields (headline, author, publisher) to generate the JSON-LD code.

Good to know: Google treats headline, image and dates as strongly recommended for article rich results. The tool only requires headline, author and publisher — but adding an image and the publication date makes your article much more likely to qualify for enhanced display in Google Search and Google News.

What is Article schema?

Article is a structured data type from schema.org that describes an editorial piece of content — its headline, author, publisher, publication date and lead image. Added to a page as JSON-LD, it helps Google understand who wrote the article, when it was published, and which image represents it. That understanding can lead to enhanced presentation in Google Search results, Top Stories and Google News, such as larger images and clearer headline and date display.

Article, BlogPosting or NewsArticle — which one?

All three types share the same properties; BlogPosting and NewsArticle are simply more specific subtypes of Article. Use BlogPosting for posts on a blog, NewsArticle for journalistic news content, and the generic Article when neither fits — for example evergreen guides or magazine-style pieces. Google explicitly supports all three for article structured data, so picking the most precise type is best practice rather than a ranking trick.

How to add the schema to your site

Copy the generated code and paste it into a script tag of type application/ld+json, placed in the head section of the article page it describes. The headline, author and dates in the markup must match what readers actually see on the page — structured data describes existing content, it does not replace it. A minimal example looks like this:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "How IBAN check digits work",
  "author": {
    "@type": "Person",
    "name": "Jane Miller"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Example Media Ltd."
  },
  "datePublished": "2026-07-10"
}
</script>

Frequently asked questions

What is the difference between Article and BlogPosting?: BlogPosting is a subtype of Article intended specifically for blog posts. Both share the same properties and are treated equally by Google for article rich results. Choose BlogPosting for blog content, NewsArticle for news, and the generic Article for everything else.
Which fields are required?: This tool requires a headline, an author name and a publisher name before it outputs code. Google itself has no strictly required properties for Article markup, but headline, image, dates, author and publisher are the recommended core set — the more of them you provide, the better.
Should the author be a Person or an Organization?: Use Person when a named individual wrote the article — this is the common case for blogs. Use Organization when the piece is published under the name of a company, newsroom or team without an individual byline.
What format do datePublished and dateModified use?: Both use ISO 8601 format, for example 2026-07-10. This tool outputs the plain date, which is valid; a full timestamp with time and timezone is also allowed. dateModified is optional and should only be set when the content was meaningfully updated.
Does Article markup guarantee a rich result?: No. Structured data makes your page eligible for enhanced display, but Google decides case by case whether to show it. Valid markup, a matching visible article and a good quality page together maximize your chances.