AnyTool
Your files never leave your device. All processing happens locally in your browser.

How do I generate Article schema (Article / NewsArticle / BlogPosting JSON-LD) for a blog post or news article?

Open AnyTool’s Article Schema Generator, choose the type (Article, NewsArticle or BlogPosting), then fill in the headline, author (Person or Organization, with an optional URL), publisher and logo, the publish and last-modified dates, one or more image URLs, a description, the article section, the canonical URL and keywords. It instantly builds a valid schema.org Article object, converts your dates to ISO 8601, omits any empty fields and wraps everything in a <script type="application/ld+json">…</script> block you can paste into your page. A live validation panel flags a missing headline, image, publish date or author, an over-long (>110-character) headline, non-ISO or modified-before-published dates, relative image or logo URLs and a missing publisher logo. Everything runs in your browser — nothing is uploaded. Google lists no strictly-required properties, but headline, image, datePublished and author are strongly recommended; article rich features and Top Stories lean toward news and recognized publishers, so test in the Rich Results Test.

  • Builds valid Article / NewsArticle / BlogPosting JSON-LD with headline, image, dates, author and publisher
  • Converts publish and modified dates to ISO 8601 and omits any empty fields
  • Outputs a copy-ready <script type="application/ld+json"> block plus the bare JSON
  • Live validation: missing headline / image / date / author, long headline, bad dates, relative URLs, missing logo
  • 100% client-side — your article fields never leave the browser; honest note on rich-result eligibility

What is

Article Schema (Article / NewsArticle / BlogPosting structured data)

Article schema is schema.org Article structured data — usually written as JSON-LD — that describes an article-style page using one of three types: Article (generic), NewsArticle (news) or BlogPosting (blog). It carries the headline, one or more image URLs, datePublished and dateModified in ISO 8601, an author (Person or Organization), a publisher (Organization with a logo), the canonical URL (mainEntityOfPage), a description, the article section and keywords. Google lists no strictly-required properties but strongly recommends headline, image, datePublished and author; the markup must match the visible article and can support article rich features and Top Stories.

SEO & Web

Related terms

JSON-LDStructured dataNewsArticleBlogPostingRich resultsschema.org

Frequently Asked Questions

Google lists no strictly-required Article properties, but headline, image, datePublished and author are strongly recommended and effectively needed for any article rich feature.

Google’s Article documentation says there are no required properties — you add the ones that apply to your content. In practice, headline, image, datePublished and author are strongly recommended: without an image the page cannot qualify for Top Stories or Discover, and Google uses the author, headline and dates for attribution and freshness. dateModified, publisher (with a logo), description, articleSection and keywords are also recommended. This tool treats a missing headline, image, publish date or author as an error so you don’t ship empty markup.

They are three schema.org types for the same kind of markup: Article is generic, NewsArticle is for news stories (and Top Stories), and BlogPosting is for blog posts. The properties are the same.

Article is the generic type for any article-style page; NewsArticle is the more specific type for news stories and is what Top Stories looks for (it needs a publisher with a logo); BlogPosting is for blog posts and personal articles. They share the same recommended properties — headline, image, datePublished, dateModified, author and publisher — so you can pick whichever best describes your content. The Article Schema Generator lets you switch between all three and updates the @type accordingly.

datePublished and dateModified must be in ISO 8601 — for example 2025-01-26 or 2025-01-26T12:00:00+00:00. This tool converts your dates automatically.

Article structured data requires dates in ISO 8601 format, such as 2025-01-26T12:00:00+00:00 (a date with time and timezone) or a plain 2025-01-26 date. The Article Schema Generator lets you pick the dates and converts them to valid ISO 8601 for you, and it warns if the last-modified date is earlier than the publish date. The dates in the markup should match the dates shown to readers on the page.

Not necessarily. The markup is valid and helps search and AI engines, but visible article rich features and Top Stories lean toward news and recognized publishers, so a normal blog may get no visible snippet.

Article structured data helps Google and AI answer engines understand your article — the headline, author, dates and publisher — and can support article rich features, Top Stories and Discover. However, those visible features lean heavily toward news sites and recognized publishers, so an ordinary blog often produces perfectly valid markup without any visible rich result. The markup is still worthwhile for understanding and attribution. The markup must match the visible article and use ISO 8601 dates; always test in Google’s Rich Results Test before relying on it.

Detailed Explanation

How It Works

What the Article Schema Generator Produces

The Article Schema Generator turns an article’s details into a valid schema.org Article object expressed as JSON-LD, using one of three types — Article (generic), NewsArticle (news) or BlogPosting (blog) — and wraps it in the <script type="application/ld+json">…</script> block ready to paste into a page. The object follows the documented shape: @context https://schema.org, the chosen @type, a headline, an image array of one or more URLs, datePublished and dateModified (converted to ISO 8601), an author (Person or Organization with an optional url), a publisher (Organization with an ImageObject logo), mainEntityOfPage (the canonical URL), a description, an articleSection and keywords. Empty fields are omitted entirely, so the JSON only carries properties you supplied. Both the wrapped script block and the bare JSON can be copied with one click, and the output updates live as you type.

  • Outputs valid Article / NewsArticle / BlogPosting JSON-LD with headline, image array, dates, author and publisher
  • Publish and modified dates are converted to ISO 8601 automatically
  • Empty fields are omitted; the </script> sequence is safely escaped
  • Wraps the JSON in a copy-ready <script type="application/ld+json"> block, and offers the raw JSON
  • All generation is pure client-side JavaScript — no server call, no CDN, no upload
Methodology

How It Validates the Article Markup

A pure engine (schemaEngine.ts) normalizes each field and runs a validation pass before and after building the schema. Google lists no strictly-required Article properties, but headline, image, datePublished and author are strongly recommended and effectively required for any article rich feature — so the tool treats a missing one of those as an error. It also warns on an over-long (>110-character) headline, on dates that are not valid ISO 8601 or a last-modified date earlier than the publish date, on image and publisher-logo URLs that are not absolute https:// URLs, and on a missing publisher or publisher logo (a logo is needed for NewsArticle Top Stories eligibility). Findings are ordered errors → warnings → notes → confirmation, with image-specific findings pinned to the offending image, and a final confirmation reports valid Article structured data.

  • Treats a missing headline, image, publish date or author as an error
  • Warns on a >110-character headline and non-ISO or modified-before-published dates
  • Flags relative image and logo URLs and a missing publisher logo (needed for Top Stories)
  • Findings ordered errors → warnings → notes → confirmation, pinned to each image
  • The same engine is reused across AnyTool’s structured-data tools
Use Cases

When Article Markup Gets a Visible Rich Result

The tool is honest that valid Article markup does not guarantee a visible rich result. Article structured data helps Google and AI answer engines understand the headline, author, dates and publisher, and can support article rich features, Top Stories and Discover — but those visible features lean heavily toward news sites and recognized publishers, so an ordinary blog often produces perfectly valid markup with no visible snippet. The markup is still worthwhile for understanding and attribution. Three rules are stressed: the markup must match the visible article (same headline, dates and author — never mark up hidden or different content), dates must be ISO 8601, and the headline should be ≤ 110 characters with a high-resolution image (≥ 1200px wide, ideally in 16x9, 4x3 and 1x1 aspect ratios). Always test in Google’s Rich Results Test.

  • Valid markup helps understanding and attribution but does not guarantee a rich result
  • Article rich features and Top Stories lean toward news and recognized publishers
  • Markup must match the visible article and never describe hidden or different content
  • Dates must be ISO 8601; headline ≤ 110 characters; use a high-resolution image (≥ 1200px)
  • Multiple aspect ratios (16x9, 4x3, 1x1) recommended; test in the Rich Results Test
Article schema generation: in-browser (AnyTool) vs typical online generators
CapabilityAnyToolTypical online generators
ProcessingRuns entirely in your browserOften server-side
Your contentNever uploaded, works offlineSometimes sent to a server
TypesArticle, NewsArticle and BlogPostingOften one type only
DatesConverted to ISO 8601 automaticallyOften manual / error-prone
Output<script> block and bare JSON, both copy-readyUsually one block only
ValidationMissing headline / image / date / author, long headline, bad dates, relative URLs, missing logoOften none
Honesty about rich resultsClear that rich features lean toward news publishersOften implies it always shows
Cost / signupFree, no signupOften gated or ad-heavy

AnyTool builds the Article JSON-LD locally and uploads nothing. Google lists no strictly-required properties, but headline, image, datePublished and author are strongly recommended; article rich features and Top Stories lean toward news and recognized publishers, the markup must match the visible article and use ISO 8601 dates, and it should be tested in the Rich Results Test. Comparison as of June 2026.