Page & Bell

Article Schema Generator

Generate Article, NewsArticle, or BlogPosting JSON-LD with the properties Google actually evaluates: headline, images, author with profile URL, publisher with logo, and both dates. The output updates live as you type, validates every URL, and counts your headline against the 110-character truncation point. Because the JSON is built with JSON.stringify, quotes and em dashes in headlines never produce broken markup.

  • ✕ Headline is required.

Enter a headline (and fix any invalid URLs) to generate the JSON-LD markup.

How to use the article schema generator

  1. Pick the type: BlogPosting for blog content, NewsArticle for news publishers (it feeds Google News surfaces), Article when neither fits.
  2. Enter the headline exactly as it appears on the page — the counter warns past 110 characters.
  3. Paste one or more image URLs (one per line). Supplying 16:9, 4:3, and 1:1 crops gives Google a choice for each placement.
  4. Set the author (Person or Organization) with a link to their profile page, plus your publisher name and logo.
  5. Fill datePublished and dateModified, then copy the <script> block into the article’s <head> or body.

What Google requires vs. recommends for articles

Strictly speaking, article structured data has no required properties for basic eligibility — but every recommended property you skip removes a feature. headline drives the rich result title; image (high-resolution, multiple aspect ratios) drives visual treatments in Discover and Top Stories; datePublished/dateModified drive the date label; author.name plus author.url drive attribution. A worked example with everything in place:

{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "How We Cut Our Cloud Bill by 43% in One Quarter",
  "image": [
    "https://example.com/img/cloud-16x9.jpg",
    "https://example.com/img/cloud-1x1.jpg"
  ],
  "author": {
    "@type": "Person",
    "name": "Jane Smith",
    "url": "https://example.com/authors/jane-smith"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Acme Engineering Blog",
    "logo": { "@type": "ImageObject", "url": "https://example.com/logo.png" }
  },
  "datePublished": "2026-03-02",
  "dateModified": "2026-05-18",
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "https://example.com/blog/cloud-bill"
  }
}

Two pitfalls worth flagging. Dates here use the simple YYYY-MM-DD form, which is valid ISO 8601; if you add a time, you must also add a timezone offset (e.g. 2026-03-02T09:30:00-05:00) — a bare time without offset is the most common date error the Rich Results Test flags. And the markup must mirror the page: a schema headline that differs from the visible H1, or a datePublished that contradicts the visible byline date, reads as misleading structured data and can cost the page its enhancements.

Frequently asked questions

Article, NewsArticle, or BlogPosting — does the choice matter?

Less than most people think, but it is not zero. All three are eligible for the same article rich result treatment, and BlogPosting and NewsArticle are both subtypes of Article, so Google understands the hierarchy either way. Pick the most specific true type: NewsArticle signals journalistic content and is the conventional choice for publishers in Google News, BlogPosting fits editorial blog content, and plain Article covers everything else. Do not use NewsArticle on commercial blog content hoping for news treatment — type alone does not grant it.

Is the schema headline the same as my title tag?

No, and conflating them is a common mistake. The title tag is what shows as the blue link in search and is usually written for CTR at roughly 60 characters. The schema headline should be the on-page H1 — the actual headline of the article — and may run up to 110 characters before risking truncation in rich results. Google cross-checks markup against visible content, so a headline that matches your H1 is safer than one copied from a keyword-stuffed title tag.

Why does dateModified matter so much?

Two reasons. First, Google has stated it prefers dateModified for determining the date shown in search results when content is meaningfully updated — a 2022 article substantively revised last month can display the recent date, which measurably improves CTR for time-sensitive queries. Second, it is an honesty signal: sites that bump dateModified without changing anything get caught, because Google compares the claim against actual content changes between crawls. Update the date when you update the content, never otherwise.

What are the image requirements for article rich results?

Images must be crawlable and indexable (not blocked by robots.txt), at least 1200 pixels wide for the best treatment, and Google recommends providing the same image in 16:9, 4:3, and 1:1 aspect ratios so it can pick the right crop per surface — that is why this tool accepts multiple URLs. A wide hero image alone works, but the square crop is what Discover and mobile carousels often use, so omitting it leaves placements on the table.

Should the author be a Person or an Organization?

Use Person whenever a real human wrote the piece, and link the author URL to a profile page that demonstrates who they are — Google’s documentation explicitly recommends author.url to disambiguate authors, and named human authors align with the E-E-A-T signals quality raters are trained on. Reserve Organization for genuinely collective content like a company changelog or staff-written documentation. An author of “Admin” with no URL is technically valid markup and a wasted property.

Will article schema get me into Top Stories?

Markup alone, no. Top Stories eligibility depends on Google’s news content policies and overall site quality; since 2019 it no longer requires AMP, and valid NewsArticle markup with good images and accurate dates is part of the recipe — but it is the editorial signals that decide. What the markup reliably does for every site: correct dates in snippets, better image selection in Discover, and unambiguous bylines machine readers can attribute.

Related tools

Learn more