ZeroUtil

Article Schema Generator (JSON-LD)

Generate Article JSON-LD schema for blog posts, news pages and long-form guides.

Maintained by

Article Schema Generator (JSON-LD)

The Article schema generator builds a JSON-LD block that tells Google, Bing, and voice assistants this page is a long-form editorial piece. Populate headline, author, datePublished, and a high-resolution image and the generator emits an <script type="application/ld+json"> snippet you can paste straight into <head>. The tool runs entirely in your browser - nothing is uploaded or logged.

Which Article Variant Should You Pick?

Schema.org ships three article subtypes, and picking the right one affects what Google surfaces:

  • Article - the generic fallback for long-form content on a commercial or informational site. Use this when nothing more specific fits.
  • NewsArticle - a subtype reserved for publishers that follow editorial standards recognised by Google News. Using it on a marketing blog does not earn you Top Stories eligibility, but it can still clarify intent.
  • BlogPosting - blog posts on personal or company blogs. Most CMSes (WordPress, Ghost) emit this by default.

If you are unsure, start with Article. Only upgrade to NewsArticle if you control a publication indexed by Google News or hold a Publisher account in Search Console.

Required and Recommended Fields

Google documents the Article rich-result contract as a minimum of four fields. The generator exposes them plus the most commonly requested optional ones:

  • headline (required) - 110 characters or less per Google guidance. Longer values get truncated in search snippets.
  • image (required) - at least 1200px wide for Top Stories eligibility. Absolute HTTPS URL only; relative paths and data: URIs are silently dropped.
  • datePublished (required) - ISO 8601 with timezone, for example 2026-04-22T10:00:00+00:00.
  • dateModified (recommended) - update whenever you materially change the body. Articles with recent dateModified tend to re-rank for news-adjacent queries.
  • author (required) - an object with @type: Person or @type: Organization. The generator emits the Person form; edit the raw JSON if you need Organization authorship.
  • publisher (recommended) - the Organization behind the article; pair with a square logo at least 112x112 for NewsArticle eligibility.

Common Validation Errors

  • Missing logo on publisher - for NewsArticle Google requires publisher.logo as an ImageObject with width, height, and a url pointing to a PNG or JPG with a white background.
  • Date format drift - "2026-04-22" is accepted for Article but most validators flag it as a warning. Add a time component (T00:00:00+00:00) to silence it.
  • Mismatched headline - structured data must mirror what users see. If the visible <h1> reads "Claude 4.7 is Here" but your JSON-LD says "Why Claude 4.7 Matters", Google treats that as a policy violation.
  • Missing mainEntityOfPage - not required but strongly encouraged. Set it to the canonical URL so Google knows which page owns the entity when the same Article appears on syndicated copies.

How It Differs From the Generic Generator

The generic Schema Markup Generator supports eight schema types via a type picker. This Article-focused page loads the same underlying UI but pre-selects Article so you can land, paste, and copy without extra clicks. It also surfaces Article-specific copy - field requirements, NewsArticle considerations, author modelling - instead of generic structured-data background. For Product, FAQPage, or Organization schema, use the dedicated sub-pages or switch types in the picker.

Testing Before You Ship

Run the generated block through two validators before committing the change. Google's Rich Results Test reports rich-result eligibility (the feature that decides whether you get article carousels, Top Stories, or nothing). The Schema.org validator reports schema.org-level correctness - broader coverage, stricter about nonsense values. Clean on both, then paste into <head> and request a re-crawl via Search Console if the page is already indexed.

Frequently Asked Questions

Does Article schema directly improve my search ranking?

Not directly. Google's John Mueller has repeatedly said structured data is not a ranking signal. What Article schema does is make the page eligible for rich-result features: carousels, Top Stories, knowledge panel entries. Those features raise click-through rate by 20-30% for competitive queries, and CTR is a weak indirect ranking input. The uplift comes from CTR, not the schema itself.

Should I use NewsArticle or plain Article for my blog?

Use Article unless you publish under a recognised news brand. NewsArticle unlocks Top Stories eligibility and Google News surfaces, but both require you to be an approved publisher - typically a news organisation with editorial staff, correction policies, and a Google News Publisher profile. Marketing blogs using NewsArticle do not gain anything and may trigger "misleading structured data" warnings if Google decides the content is promotional.

Do I need <code>dateModified</code> if I never update old articles?

Not required, but recommended. Google uses <code>dateModified</code> as a freshness signal for news-adjacent queries where recency matters. If you update typos, add a note, or refresh a screenshot, bump <code>dateModified</code>. If the content is truly evergreen and the only changes are CSS tweaks, leave it off rather than emit a misleading recent date.

Can I have multiple authors on one Article?

Yes - <code>author</code> accepts an array of Person or Organization objects. Schema.org validators accept it, Google surfaces "By Alice and Bob" correctly in some rich-result layouts. The generator here produces a single author; edit the JSON to add more, following the pattern <code>"author": [{"@type": "Person", "name": "Alice"}, {"@type": "Person", "name": "Bob"}]</code>.

What image sizes does Google actually require?

For Top Stories eligibility, Google explicitly asks for at least 1200px wide and a 16x9, 4x3, or 1x1 aspect ratio (supply an array of three variants for best results). For plain Article rich results there is no strict minimum, but Google truncates smaller thumbnails into less-prominent SERP features. Use a 1200x675 WebP or JPEG at HTTPS; anything smaller loses rich-result slots.

Where should the JSON-LD block go in the HTML?

Both <code>&lt;head&gt;</code> and end-of-<code>&lt;body&gt;</code> are valid per Google's documentation. <code>&lt;head&gt;</code> is conventional and slightly faster for Googlebot to parse. End-of-body makes sense for very large FAQ or HowTo payloads where you do not want to bloat the head and slow time-to-first-byte. For Article schema, which is typically under 2 KB, head placement is fine.

Is this Article schema generator free?

Yes, fully free, no signup, no paywall. The generator runs in your browser with pure JavaScript; your input never leaves the page. There is no per-day limit, no watermark, and no premium tier. Same story for the other schema-type pages: Product, FAQPage, Organization. If you want deeper tooling (bulk schema across an entire site, automated validation in CI), combine this with <a href="/tools/structured-data-validator/">our structured data validator</a>.

What happens if I have invalid Article schema?

Google logs a parse error in Search Console but does not penalise the page's text ranking. The rich-result feature simply fails to trigger, and the page ranks normally on its body content. Invalid structured data is a dropped feature, not a negative signal. The exception is if the structured data contains policy violations (fake reviews, misrepresented content), which can lead to a manual action.

More SEO & Web Tools