SchemaValid
ENDE

Article & Blog Posting Schema Generator

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

Try an example

Article details

Author type

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.
What is Article schema markup, in plain terms?
It's a JSON-LD snippet based on the schema.org Article vocabulary that tells search engines the key facts about a piece of written content — headline, author, publisher and dates — without changing anything a reader sees on the page.
Does Google require a publisher logo?
If you include a publisher, Google recommends a square logo image, ideally at least 112×112 pixels, hosted on your own domain. This tool's publisher logo field is optional, but leaving it out means the publisher object won't include a logo at all.
Can I list more than one author?
Yes, schema.org allows the author property to hold an array of Person or Organization entries for pieces with multiple writers. This tool's form handles a single author for simplicity — for a multi-author byline, take the generated code and change author into an array of author objects.
When should I update an article's schema?
Update dateModified whenever you meaningfully revise the content, headline or image — a typo fix doesn't need it, but a substantive rewrite does. Keep the markup in sync any time the visible byline, publish date or headline on the page changes.
What are common mistakes when adding Article schema?
The most frequent ones are picking the wrong subtype (using NewsArticle for a blog post, for instance), pointing the image or logo at a broken URL, letting dateModified predate datePublished, and listing an author who doesn't actually appear as the byline on the page.
Can I combine Article schema with other schema types?
Yes, as long as each type genuinely applies to the page's content — for example adding FAQPage markup below an article that ends with a real Q&A section, or BreadcrumbList for the page's navigation path. Each type is its own JSON-LD block and they don't conflict.
Does Article schema help my content get picked up by Google Discover or Top Stories?
Valid markup with a strong image and accurate dates is one of the baseline requirements for those surfaces, but eligibility ultimately depends on Google's broader content-quality and E-E-A-T signals, which structured data alone can't substitute for.

Related tools