Article Schema Generator

100% private — runs on your device, never uploaded. Works offline once loaded.

Fill in a short form and get clean Article, BlogPosting or NewsArticle JSON-LD you can paste straight into your page head. Everything is generated in your browser.

What Article structured data does

Article schema is a block of JSON-LD that describes a piece of editorial content — its headline, author, publisher, publication dates and lead image — in a vocabulary search engines understand. Adding it to a page makes your content eligible for enhanced presentation in Google Search and Google News, including the article carousel, Top Stories and richer snippets with a visible byline and date.

Under the hood the markup uses schema.org types. The three variants this tool produces — Article, BlogPosting and NewsArticle — are subtypes of one another, so they share the same properties and are largely interchangeable. Pick the one that best labels your content and the crawler does the rest.

The fields that matter

A minimal but well-formed Article needs a headline. Beyond that, the properties Google actively uses are author, publisher (with a logo), datePublished, dateModified, image and the canonical URL expressed through mainEntityOfPage.

  • headline — the article title, ideally under 110 characters.
  • author — a Person object with the writer's name.
  • publisher — an Organization with a name and a logo ImageObject.
  • datePublished / dateModified — ISO dates so freshness is unambiguous.
  • image — a high-resolution lead image improves eligibility for large thumbnails.
  • mainEntityOfPage — the canonical URL the markup belongs to.

When to use it and common mistakes

Add Article markup to any standalone editorial URL: blog posts, guides, news pieces and long-form explainers. Do not add it to category or tag listing pages, which are not articles.

The most frequent errors are markup that describes content not visible on the page, a logo that is not a real, crawlable image URL, and dates in a non-ISO format. Keep the JSON-LD in sync with what a reader actually sees — mismatches can cause Google to ignore the markup or issue a structured-data warning in Search Console.

Validate before you ship

Generating valid JSON-LD is only half the job. After pasting the block into your head, run the live URL through Google's Rich Results Test and the Schema Markup Validator to confirm there are no errors or warnings. Both tools read the rendered page, so they also catch problems your CMS might introduce during templating.

Frequently asked questions

Where do I put the generated code?

Paste the entire <script type="application/ld+json"> block into the <head> of the article's HTML, or into the body — both are valid. Most CMS and SEO plugins have a field for custom head markup.

Should the dates include a time and timezone?

The date picker outputs a plain ISO date (YYYY-MM-DD), which is valid. If you need higher precision you can extend it to a full ISO 8601 timestamp with an offset, for example 2026-08-07T09:30:00-05:00.

Do I need both datePublished and dateModified?

datePublished is the more important of the two. Add dateModified only when the article has genuinely been updated; setting it equal to the publish date is harmless but pointless.

Can I have more than one author?

Yes in schema.org — author can be an array of Person objects. This tool captures a single author to keep the form simple; you can duplicate the author object by hand for co-authored pieces.

Will adding this schema guarantee rich results?

No. Valid markup makes a page eligible for rich results, but Google decides whether to show them based on content quality, page experience and its own algorithms. Schema is a strong signal, not a switch.

What is the difference between headline and name?

For Article types Google reads the headline property specifically. name also exists on the type but headline is the one used for the rich result title, which is why this generator emits headline.

Advertisement