Article Schema

TL;DR — Article schemaArticle schema (Article, NewsArticle, or BlogPosting) is structured data marking up a written piece's headline, author, and dates — Google labels it the \"Article rich result,\" but it's a better-displayed existing result, not a distinct new card, and it isn't required for Top Stories or Discover eligibility. is a small block of code you add to a blog post or news article that labels the basics for search engines — “this is the headline,” “this is the author,” “this is when it was published,” “this is the main image.” It helps Google show those details more nicely in search results. Google’s own docs call this the “Article rich result,” but it doesn’t create a flashy new-looking card the way Recipe or Video does — and it isn’t a requirement for getting into Google News or Discover. And — despite what you may have read — it does not require AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories..

What Article schema is

When you read an article, you can tell the headline from the author byline from the date just by looking. A search engine sees plain text and has to work it out. Article schema spells it out in code, using the shared schema.org vocabulary, so Google knows exactly which part is the headline, who wrote it, when it was published, and which image is the main one.

It’s almost always written as JSON-LDJSON-LD (JavaScript Object Notation for Linked Data) is a script-based structured data format, typically paired with the schema.org vocabulary to describe page content for search engines and AI systems. Google recommends it over Microdata and RDFa because it's the easiest format to implement and maintain at scale — but all three work, and structured data isn't a ranking signal. — a small block of code that sits in the page without changing how the page looks. You’ll see it as Article, NewsArticle, or BlogPosting. All three are valid, and Google covers them in a single guide. Evidence for this claim Schema.org defines Article and the more specific BlogPosting and NewsArticle types. Scope: Schema.org vocabulary; type validity is separate from Google search-feature eligibility. Confidence: high · Verified: 2026-07-14 Schema.org: Article You don’t have to agonize over the choice (more on that in the Advanced tab).

Why it’s worth doing

Here’s the part most guides overstate, so let me be plain: Article schema does not give you a flashy new result card the way a Recipe or a Product might. What it does is quieter but real:

• It helps Google show better title text, a better image, and clearer date information for your article in normal search results — Google’s own docs actually label this the “Article rich result.” Evidence for this claim Google says Article structured data can help it understand article pages and show better title, image, and date information. Scope: Google Search Article documentation; markup does not guarantee a particular appearance. Confidence: high · Verified: 2026-07-14 Google: Article structured data
• Google News and Discover can read this markup to understand your content better, but neither one requires it — Discover in particular says it needs no special tags or structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. at all.

So the payoff is a better-displayed version of your existing result, not a distinct new-looking card. Anyone promising you an “article carousel rich result” — or implying the markup is what gets you into Top Stories or Discover — is overstating it.

The good news: nothing is required

Google’s Article guide is refreshingly relaxed: there are no required properties. You add the ones that apply to your content. In practice you’ll want:

• headline — the article’s title (keep it concise; Google trims long ones).
• author — a real person or organization, with a name that matches the byline.
• datePublished and dateModified — when it went live and when it last changed.
• image — the lead image (Google likes at least 50,000 pixels, in a few sizes/shapes: 16x9, 4x3, 1x1).

The myths to ignore

Two things you may have read that are simply out of date or wrong:

• “Article schema requires AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories..” It doesn’t. Google’s current Article guide doesn’t mention AMP at all.
• “More properties always help.” Google explicitly says add only what applies — there’s no checklist you have to fill to “win.”

And one that’s always true: valid markup makes you eligible, not guaranteed. Google still decides whether to use it.

Want the full version — the Article vs. NewsArticle vs. BlogPosting question, how to fill the recommended properties well, the common implementation mistakes, and how this connects to Top Stories and Discover without overpromising? Switch to the Advanced tab.

TL;DR — Article structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. (Article, NewsArticle, or BlogPosting — all valid; Google documents them in one guide) marks up a written page’s headline, author, datePublished/dateModified, and image. It has no required properties — Google’s guidance is to “add the properties that apply to your content.” Google’s own docs label this the “Article rich result” — but unlike Recipe or VideoObject’s distinctive card, it manifests as a better-displayed version of your existing result (title text, image, date), not a separate snippet format. Article markup is not required for Google News features like Top Stories, and Discover’s own guidance says no special tags or structured data are needed at all — so it isn’t the eligibility switch some guides promise when they pitch an “article carousel.” And Google’s current Article guide does not mention AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories. anywhere — the old “Article schemaArticle schema (Article, NewsArticle, or BlogPosting) is structured data marking up a written piece's headline, author, and dates — Google labels it the \"Article rich result,\" but it's a better-displayed existing result, not a distinct new card, and it isn't required for Top Stories or Discover eligibility. requires AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories.” claim is stale. Valid markup only earns eligibility; Google still decides whether to use it, and it’s never a ranking factor.

What Article schema actually does (and doesn’t)

Let me correct the single most common overstatement up front, because everything else follows from it: Google’s own docs label this feature the “Article rich result,” but it is not a distinctive new-looking card the way Recipe markupRecipe schema (schema.org/Recipe) marks up a cooking recipe's image, name, ratings, times, ingredients, and nutrition so the page can earn Google's recipe rich result — a visual card with star ratings and cook time, plus carousel and recipe-filter eligibility. gives you a recipe card or VideoObject gives you a video thumbnail treatment. Article does not have an equivalent standalone visual snippet — the “rich result” here is your existing listing shown better. What it does is:

• Improve how existing results display — Google can show better title text, a better lead image, and clearer date information for the article.
• Help Google understand your content — but it is not a requirement for Google News features like Top Stories, and Google’s Discover guidance says eligible content needs no special tags or structured data at all. Article markup can make details more explicit; it doesn’t unlock either surface.

That’s a display-quality signal, not a distinct new snippet type or an eligibility switch. When you see a guide promising “Article schema unlocks Top Stories / article carousels,” read it as an overstatement — Google’s own framing is about helping it understand the page and show better title/image/date information, not about a card and not about flipping on News or Discover eligibility. (I’m treating that “better title text, images, and date information” phrasing as a paraphrase of Google’s framing, not a verbatim quote — see the Quotes tab for what’s confirmed word-for-word.)

Article vs. NewsArticle vs. BlogPosting — do you have to pick correctly?

Short answer: no, not agonizingly. All three types are valid, and Google’s guide covers Article, NewsArticle, and BlogPosting together with the same recommended properties. NewsArticle and BlogPosting are both subtypes of Article, so:

• Use NewsArticle for news content on a news site.
• Use BlogPosting for blog posts.
• Use Article as the safe general choice when neither fits neatly.

Pick the most specific type that honestly describes the page, but don’t lose sleep over it — the recommended property set is the same, and there’s no separate rich-result payoff riding on the choice. (Schema.orgSchema markup is code that uses the schema.org vocabulary to label what your content means so search engines can understand it and show rich results. It's most often written in JSON-LD, and it's not a direct ranking factor. itself defines a handful of further Article subtypes beyond these three — Google’s guide, and this article, cover the three it publishes a supported property set for.)

No required properties — a feature, not a gap

Google’s Article guide states plainly that there are no required properties; instead, add the properties that apply to your content. Evidence for this claim Google lists no required Article properties but recommends adding applicable author, date, headline, and image data. Scope: Google Search Article feature requirements; completeness and accuracy still matter. Confidence: high · Verified: 2026-07-14 Google: Article structured data That flexibility trips people up because they’re used to Product or Recipe markup with hard requirement lists. Here, the recommended properties are the ones worth filling well:

The temptation is to stuff in every property schema.org offers. Don’t. Google’s steer is to add what applies — there’s no bonus for hitting a longer list, and irrelevant or inaccurate properties are just risk.

Common implementation mistakes

• Author name mismatch. The most frequent one: author set to a generic or mismatched value (“Admin,” the site name, an editor who didn’t write it) instead of a real Person/Organization whose name matches the byline on the page.
• Overly long headline. Google trims and sometimes rewrites long headlines in display, so a bloated headline value doesn’t buy you anything and can look off.
• Stale or churning dateModified. Bumping it on every crawl (or never) both send the wrong signal. Move it when the content genuinely changes.
• A single low-quality image. Give Google a few sizes/ratios; a single tiny or awkwardly-cropped image limits what it can display.
• Chasing a card that doesn’t exist. Google calls this feature the “Article rich result,” but there’s no distinctive new-looking snippet to chase — you’re buying a better-displayed existing result, nothing more.

TIP Build Article markup around display quality, not a fake checklist

Article has no required fields, so this review focuses on malformed values and the recommended fields that improve title, image, date, and author context.

Draft and inspect Article JSON-LD field by field with my free Schema Markup Generator Free

1. Match the schema headline and author to the visible article.
2. Use absolute image and canonical URLs, and add genuine published or modified dates.
3. Treat recommended-field notices as editorial prompts, not permission to invent missing data.

Tap to enlarge

The Article form reports no required properties, four recommended fields not yet supplied, a headline longer than 110 characters, and a canonical URL that is not a valid absolute URL. The JSON-LD preview updates beside the form.

How it connects to Top Stories, News, and Discover — without overpromising

This is the part worth being precise about, because Google is explicit here and the two surfaces aren’t the same: Article markup can make your article’s details more explicit for Google to understand, but Google says it is not required for Google News features like Top Stories, and its Discover guidance says eligible content needs no special tags or structured data at all. So Article schema doesn’t unlock either surface — it’s markup that can help Google understand a page it’s already considering, not a switch. What actually gets you into Top Stories or Discover is being a qualifying publisher plus content quality, freshness, and Google’s own systems deciding you’re worth showing.

Two adjacent points worth a mention rather than a deep dive:

• Paywalled content should add paywalled-content structured data separately — that’s its own markup, not part of Article, and it matters for how Google treats subscription pages.
• The author and date fields are worth getting right for the same reasons a real, consistent author identity matters for the broader E-E-A-T signals discussed elsewhere on this site — I’m not aware of current evidence that this markup itself is a direct E-E-A-T input, just that getting authorship right is good practice either way.

Structured data isn’t a ranking factor

Worth restating because it underpins all of this: structured data — Article included — is not a ranking factor. As John Mueller has said repeatedly, it affects rich-result and display eligibility, not rankings directly. You add Article schema to help Google understand and display your content, not to move up the results. That’s exactly why I still think it’s worth adding: even without a distinctive new card, it improves how your articles show up. I’m a fan of schema markupSchema markup is code that uses the schema.org vocabulary to label what your content means so search engines can understand it and show rich results. It's most often written in JSON-LD, and it's not a direct ranking factor. as long as it gets you a search feature — and Google’s own “Article rich result” label for cleaner titles, images, and dates clears that bar on its own, without needing to lean on unproven News or Discover eligibility claims.

Where Article sits in the wider structured-data picture

Article is one of the Creative Works types in schema.org, alongside siblings like AudioObject, Book, Course, Dataset, Movie, Recipe, and VideoObject — the Creative Works hub this article nests under groups them together. Several of those (Recipe, VideoObject) do have dedicated rich-result cards, which is precisely why it’s worth being clear that Article does not. For the broader vocabulary and how JSON-LDJSON-LD (JavaScript Object Notation for Linked Data) is a script-based structured data format, typically paired with the schema.org vocabulary to describe page content for search engines and AI systems. Google recommends it over Microdata and RDFa because it's the easiest format to implement and maintain at scale — but all three work, and structured data isn't a ranking signal. fits, see the Schema Markup and Structured Data hubs above this article.

AI summary

A condensed take on the Advanced version:

• What it is: schema.orgSchema markup is code that uses the schema.org vocabulary to label what your content means so search engines can understand it and show rich results. It's most often written in JSON-LD, and it's not a direct ranking factor. Article markup (implemented as Article, NewsArticle, or BlogPosting — all valid; Google documents them together), usually JSON-LDJSON-LD (JavaScript Object Notation for Linked Data) is a script-based structured data format, typically paired with the schema.org vocabulary to describe page content for search engines and AI systems. Google recommends it over Microdata and RDFa because it's the easiest format to implement and maintain at scale — but all three work, and structured data isn't a ranking signal., labeling a written page’s headline, author, datePublished/dateModified, and image.
• No required properties. Google says add the properties that apply to your content — there’s no requirement list and no bonus for a longer one.
• Google labels it the “Article rich result” — but unlike Recipe or VideoObject, there’s no distinctive new-looking card. It’s your existing result shown better: better title text, image, and date information.
• Not a Top Stories or Discover switch. Google says Article markup is not required for Google News features like Top Stories, and Discover’s guidance says eligible content needs no special tags or structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. at all. The markup can help Google understand a page; it doesn’t unlock either surface.
• Competitor overstatement to ignore: claims that Article schemaArticle schema (Article, NewsArticle, or BlogPosting) is structured data marking up a written piece's headline, author, and dates — Google labels it the \"Article rich result,\" but it's a better-displayed existing result, not a distinct new card, and it isn't required for Top Stories or Discover eligibility. “unlocks Top Stories / article carousels / a rich snippet” conflate Google’s understanding-only framing with an eligibility guarantee. Read them as overstated, not as a distinct visual format Article grants.
• No AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories. requirement. Google’s current Article guide does not mention AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories. anywhere — the widely-repeated “Article schema requires AMP” claim is stale.
• Type choice: NewsArticle for news, BlogPosting for blogs, Article as the safe general fallback (schema.org defines further subtypes; Google documents a supported property set for these three). Same recommended properties for all; no rich-result payoff rides on the choice.
• Recommended properties done well: author = a real Person/Organization with a matching name; concise headline (Google trims long ones); honest dateModified; representative, crawlable images at least 50,000 pixels in multiple ratios (16x9, 4x3, 1x1).
• Common mistakes: mismatched/generic author, overly long headline, churning or stale dateModified, single weak image, expecting a card that doesn’t exist.
• Adjacent: paywalled content needs separate paywalled-content markup; getting author/date fields right is good practice alongside the site’s broader E-E-A-T work, though this record doesn’t establish the markup itself as a direct E-E-A-T input.
• Eligibility ≠ display, and not a ranking factor: structured data affects rich-result/display eligibility, not rankings (Mueller, repeatedly). Valid markup only makes you eligible; Google decides whether to use it.

Official documentation

Primary-source documentation from the search engines.

Google — Article structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding.

• Article (Article, NewsArticle, BlogPosting) structured data — the single guide covering all three types, labeling the documented feature the “Article rich result,” the “no required properties” stance, the recommended properties (author, dateModified, datePublished, headline, image), and the minimum-50,000-pixel, multi-aspect-ratio image guidance. It also states Article markup isn’t required for Google News features like Top Stories. Note it does not mention AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories..
• General structured data guidelines — the content, technical, and quality policies that apply to all structured data, Article included.
• Subscription and paywalled content — the separate markup for subscription/paywalled articles (mentioned in the Article guide, implemented on its own).
• Rich Results Test — validate the markup and check what Google can read from it.
• Get on Discover (Google) — Discover’s own eligibility guidance, which says content needs no special tags or structured data at all.

Bing / Microsoft

• Marking up your site with structured data — Bing’s general structured-data support (schema.orgSchema markup is code that uses the schema.org vocabulary to label what your content means so search engines can understand it and show rich results. It's most often written in JSON-LD, and it's not a direct ranking factor., JSON-LDJSON-LD (JavaScript Object Notation for Linked Data) is a script-based structured data format, typically paired with the schema.org vocabulary to describe page content for search engines and AI systems. Google recommends it over Microdata and RDFa because it's the easiest format to implement and maintain at scale — but all three work, and structured data isn't a ranking signal. recommended), validated with Bing’s generic Markup Validator.

Quotes from the source

On-the-record statements from Google. Where a source page exposes the text, the link is a deep link that jumps to the quoted passage.

Google docs — no required properties

• “There are no required properties; instead, add the properties that apply to your content.” Jump to quote

On structured data and rankings (evergreen framing)

• Structured data is not a ranking factor — as John Mueller has said repeatedly, it affects rich-result and display eligibility, not rankings directly. (Paraphrased from Mueller’s consistent public statements across Search Central office-hours and social posts; treat as well-established framing rather than a single sourced transcript.)

Article schema myths and mistakes to avoid

Myth: “Article schemaArticle schema (Article, NewsArticle, or BlogPosting) is structured data marking up a written piece's headline, author, and dates — Google labels it the \"Article rich result,\" but it's a better-displayed existing result, not a distinct new card, and it isn't required for Top Stories or Discover eligibility. requires AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories..” False, and worth correcting directly because it’s still repeated in older guides. Google’s current Article guide doesn’t mention AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories. anywhere — there is no AMP requirement for Article treatment today. If a resource ties Article markup to AMP, it’s out of date.

Myth: “Article schema gives you a distinctive new-looking rich-result card.” It doesn’t. Google’s own docs do label the documented feature the “Article rich result,” but unlike Recipe or VideoObject, Article has no distinct visual snippet — it’s a better-displayed version of your existing result (title text, image, date). And it’s not required for Google News features like Top Stories, and Discover’s own guidance says eligible content needs no special tags or structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. at all. Guides promising an “article carousel rich resultA carousel rich result (Google calls it a \"host carousel\") is a horizontally scrollable row of cards, all from one site, built by wrapping two or more same-type items in an ItemList with position values. Only a short, shifting list of schema.org types qualifies — and a second, geographically limited beta carousel system now runs alongside the original.” from schema alone — I’ve seen this framed as a distinct format by Yoast, Semrush, and SEJ — are overstating what the markup does. Read those as overstated eligibility claims, not format or eligibility guarantees.

Myth: “More properties always help.” Google explicitly says to add only the properties that apply to your content. There’s no required list to hit and no bonus for a longer one — irrelevant or inaccurate properties are just risk, not a ranking or eligibility boost.

Myth: “Structured data will boost my rankings.” Structured data — Article included — is not a ranking factor (Mueller, repeatedly). It affects rich-result/display eligibility, not rankings. Add it to help Google understand and display your content, not to climb the results.

Mistake: a generic or mismatched author. Setting author to “Admin,” the site name, or an editor who didn’t write the piece undercuts the whole point. Reference a real Person or Organization whose name matches the visible byline.

Mistake: an overly long headline. Google truncates and sometimes rewrites long headlines in display. A bloated headline value buys nothing and can look wrong — keep it concise and aligned with the visible title.

Mistake: churning or stale dateModified. Bumping dateModified on every crawl (to fake freshness) or never updating it both mislead. Move it when the content genuinely changes.

Mistake: expecting Article schema to turn on Top Stories or Discover. Google says Article markup isn’t required for Top Stories, and Discover’s own guidance says eligible content needs no special tags or structured data at all. Those placements depend on being a qualifying publisher plus content quality, freshness, and Google’s own decisions. Clean markup can help Google understand a page; it doesn’t flip a switch.

Mistake: forgetting paywalled-content markup. Subscription/paywalled articles need separate paywalled-content structured data — it’s not part of Article, and skipping it can cause problems for how Google treats gated pages.

Generic vs. well-formed Article JSON-LD

Article has no required properties, so “broken” here rarely means “fails validation” — it means thin and unhelpful: markup that technically parses but gives Google little to work with, or values that don’t match the page.

A thin, generic snippet

Parses fine, but the author is generic, there’s a single low-quality image, and the dates and modification info are missing:

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "How To Implement Article Schema Markup For Better Search Visibility And Rich Results In Google Today",
  "author": {
    "@type": "Person",
    "name": "Admin"
  },
  "image": "https://example.com/img/thumb.jpg"
}

What’s weak:

• author.name: “Admin” — generic and doesn’t match any real byline. Use the actual writer.
• Overly long headline — Google will trim/rewrite it; it also won’t match the visible title.
• Single small image — one thumbnail limits what Google can display.
• No datePublished/dateModified — you’re leaving the date signal on the table.

The same article, well-formed

Specific BlogPosting type, a real matching author, multiple image ratios, and honest dates:

{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "How to implement Article schema markup",
  "author": {
    "@type": "Person",
    "name": "Patrick Stox",
    "url": "https://example.com/author/patrick-stox/"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Example",
    "logo": {
      "@type": "ImageObject",
      "url": "https://example.com/img/logo.png"
    }
  },
  "datePublished": "2026-07-01T09:00:00-04:00",
  "dateModified": "2026-07-01T09:00:00-04:00",
  "image": [
    "https://example.com/img/article-1x1.jpg",
    "https://example.com/img/article-4x3.jpg",
    "https://example.com/img/article-16x9.jpg"
  ]
}

Why it’s better:

• @type: "BlogPosting" — the most specific type that honestly describes the page (a valid Article subtype).
• Real, matching author with a url to an author entity.
• headline concise and aligned with the visible title.
• Both dates present, in ISO 8601 with a timezone.
• Three image ratios (16x9, 4x3, 1x1) so Google can pick the best fit per surface.

Note there’s no “required” property being satisfied here — every field is recommended. The difference between the two snippets isn’t pass/fail; it’s how much Google can do with what you gave it.

Test yourself: Article Schema

Five quick questions on Article, NewsArticle, and BlogPosting markup, what it does (and doesn’t) do, and the myths worth ignoring. Pick an answer for each, then check.

The standing KPIs for Article schema

Article schemaArticle schema (Article, NewsArticle, or BlogPosting) is structured data marking up a written piece's headline, author, and dates — Google labels it the \"Article rich result,\" but it's a better-displayed existing result, not a distinct new card, and it isn't required for Top Stories or Discover eligibility. doesn’t have its own rich-result report in Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. the way Recipe or Product do, so the useful KPIs here are the ones that reflect what the markup actually does: better display quality for your existing result. Track these quarter over quarter rather than chasing a single number after publishing.

Top Stories / Discover search-appearance impressions

Metric: impressions and clicks where Search ConsoleGoogle's free tool for monitoring crawling, indexing, and search performance.’s Search appearance breakdown shows “Top stories” or where the separate Discover report shows activity. What it tells you: whether Google is surfacing your Article-marked pages in those surfaces — but remember Article markup isn’t required for either one (Google says no markup is required for Top Stories, and Discover needs no special tags or structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. at all), so a low number here doesn’t necessarily mean broken markup, and a strong one shouldn’t be credited to the markup alone. How to pull it: Search Console → Performance → Search appearance filter (or the dedicated Discover reportThe Discover report — Google's own label is 'Performance report (Discover)' — is a separate tab in Google Search Console's Performance section showing how your content performed in the Google Discover feed: impressions, clicks, and average CTR by page, country, date, and appearance type. It only appears once a property has crossed a minimum Discover-impression threshold., if your property has enrolled traffic to show one). Benchmark / realistic range: there’s no cross-site benchmark — Top Stories and Discover eligibility depend heavily on publisher status, niche, and freshness, so establish your own baseline per section and watch the trend rather than comparing to an outside number. Cadence: monthly, or after any change to your Article markup or publishing cadence.

Valid structured data rate across article templates

Metric: the share of Article-templated pages that parse clean with no missing recommended fields. What it tells you: whether a CMSA content management system (CMS) is software that lets users create, manage, and publish digital content — like blog posts and pages — without writing raw code. WordPress, Drupal, and Joomla are the most common open-source CMS platforms. update, theme change, or template edit broke the markup site-wide, since a single template bug can silently drop author or image from every article. How to pull it: spot-check a sample of URLs with the Schema Markup Validator or the Rich-Result Eligibility Checker; Search Console’s structured-data warnings can also flag pages Google failed to parse. Benchmark / realistic range: this is a hygiene metric, not a curve — the honest target is 100% of templated pages carrying the recommended fields, since there’s no upside to partial coverage. Cadence: immediately after any template or CMS change; otherwise a quarterly spot check is enough.

Displayed title, image, and date accuracy

Metric: whether the headline, image, and date Google actually shows in search results match what you set in headline, image, and datePublished/dateModified. What it tells you: this is the direct, observable version of “better display quality,” which is the main thing Article schema does — if Google is substituting its own guessed title or a different image, the markup isn’t doing its job for that page. How to pull it: use the URL Inspection toolA Google Search Console feature that reports how Google sees one specific URL on a property you own. By default it shows the last-indexed snapshot; a separate \"Test live URL\" mode fetches the current version.’s rendered preview, the Rich ResultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. Test, or a manual SERP check for the article’s target queries. Benchmark / realistic range: no percentage to hit — this is a pass/fail read per page you check, so treat any mismatch as a signal to revisit that page’s author, headline, or image values. Cadence: spot-check important pages shortly after publishing, then occasionally on older content that’s been updated.

Tools for building and checking Article schema

Three of my own free tools cover the full loop for Article schemaArticle schema (Article, NewsArticle, or BlogPosting) is structured data marking up a written piece's headline, author, and dates — Google labels it the \"Article rich result,\" but it's a better-displayed existing result, not a distinct new card, and it isn't required for Top Stories or Discover eligibility. — generating it correctly, validating what you already have, and confirming exactly which recommended fields you’re still missing.

Generate the markup with the Schema Markup Generator

The Schema Markup Generator builds Article, NewsArticle, or BlogPosting JSON-LDJSON-LD (JavaScript Object Notation for Linked Data) is a script-based structured data format, typically paired with the schema.org vocabulary to describe page content for search engines and AI systems. Google recommends it over Microdata and RDFa because it's the easiest format to implement and maintain at scale — but all three work, and structured data isn't a ranking signal. from a form instead of hand-writing it. It gets the nesting right for the parts people typically get wrong — a proper author as a Person or Organization object rather than a bare string, a publisher with a nested ImageObject logo, and an image array so you can supply the 16x9/4x3/1x1 ratios Google recommends — and exports in six formats you can drop straight into the page.

Validate existing markup with the Schema Markup Validator

The Schema Markup Validator checks JSON-LDJSON-LD (JavaScript Object Notation for Linked Data) is a script-based structured data format, typically paired with the schema.org vocabulary to describe page content for search engines and AI systems. Google recommends it over Microdata and RDFa because it's the easiest format to implement and maintain at scale — but all three work, and structured data isn't a ranking signal. you already have — paste the code or a full HTML page — with severity-tiered results against both the schema.orgSchema markup is code that uses the schema.org vocabulary to label what your content means so search engines can understand it and show rich results. It's most often written in JSON-LD, and it's not a direct ranking factor. vocabulary and Google’s recommended properties for Article. It’s particularly useful for the author-mismatch mistake covered in the Advanced tab: its cross-block @id graph checks will flag an author reference that doesn’t resolve to a real Person or Organization entity elsewhere on the page.

Check field-by-field eligibility with the Rich-Result Eligibility Checker

The Rich-Result Eligibility Checker is the fastest way to see, per field, whether your Article markup covers the recommended set — headline, author, datePublished, dateModified, and image — with a clear checkmark, an X for something missing, or a warning for a recommended-but-optional field. Since Article has no required properties, this is the tool for deciding which recommended fields are worth adding rather than guessing.

Google’s own validator, for a second opinion

Google’s Rich Results Test is worth running after the tools above, since it shows exactly what Google’s own parser reads from the page rather than a third-party interpretation of the spec — useful as a final check before you ship a template change site-wide.

Resources worth your time

From around the industry

Article schemaArticle schema (Article, NewsArticle, or BlogPosting) is structured data marking up a written piece's headline, author, and dates — Google labels it the \"Article rich result,\" but it's a better-displayed existing result, not a distinct new card, and it isn't required for Top Stories or Discover eligibility. is a topic where several well-known guides overstate what the markup buys you on Top Stories and Discover, so I’m listing a few of those as examples of the overstatement this article corrects — read them against Google’s own docs, which do label this the “Article rich result” but frame the benefit as better display of your existing result plus understanding, not a distinct new card or an eligibility switch:

• Article (Article, NewsArticle, BlogPosting) structured data (Google Search Central) — the authoritative reference: no required properties, recommended fields, minimum-50,000-pixel multi-ratio images, no markup requirement for Top Stories, and notably no mention of AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories..
• Get on Discover (Google) — states Discover eligibility needs no special tags or structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. at all.
• General structured data guidelines (Google) — the policies that apply to all structured data.
• Subscription and paywalled content (Google) — the separate markup for gated articles.
• Structured data / schema ultimate guide (Yoast) — useful general reference, but note it frames Article schema as enabling rich resultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. like Top Stories and article carousels; Google’s own docs say the markup isn’t required for either surface.
• Schema markup guide (Semrush) — similarly presents Article schema as making pages “eligible for a rich snippet,” which conflates News/Discover eligibility with the markup itself; treat it as an overstated eligibility claim.
• What Is Schema Markup? How to Add It & Why It Matters (Ahrefs) — a solid general schema guide with a useful AI-agent/machine-readability angle.

Article Schema

Article schema (Article, NewsArticle, or BlogPosting) is structured data marking up a written piece's headline, author, and dates — Google labels it the "Article rich result," but it's a better-displayed existing result, not a distinct new card, and it isn't required for Top Stories or Discover eligibility.

Related: Schema Markup, Structured Data, Rich Results, Product Schema

Article Schema

Article schema is the schema.orgSchema markup is code that uses the schema.org vocabulary to label what your content means so search engines can understand it and show rich results. It's most often written in JSON-LD, and it's not a direct ranking factor. structured-data markup — implemented as Article, NewsArticle, or BlogPosting (all three are valid, and Google’s own guide covers them together) — that tells search engines the key facts about a piece of written content: its headline, author, datePublished/dateModified, and lead image. It’s almost always written as JSON-LDJSON-LD (JavaScript Object Notation for Linked Data) is a script-based structured data format, typically paired with the schema.org vocabulary to describe page content for search engines and AI systems. Google recommends it over Microdata and RDFa because it's the easiest format to implement and maintain at scale — but all three work, and structured data isn't a ranking signal..

Google’s own docs label this the “Article rich result,” but unlike Recipe or VideoObject, Article does not produce a distinctive new-looking visual snippet — it’s a better-displayed version of your existing result (better title text, images, and date information). Article markup can help Google understand a page, but Google says it is not required for Google News features like Top Stories, and Discover’s own guidance says eligible content needs no special tags or structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. at all — so it doesn’t unlock either surface.

There are no required properties; Google’s guidance is to add the properties that apply to your content, including representative, crawlable images at least 50,000 pixels across multiple aspect ratios (16:9, 4:3, 1:1). And despite widely-repeated older advice, Google’s current Article guide does not mention AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories. anywhere — there is no AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories. requirement for Article treatment today. Valid markup only makes a page eligible; Google still decides whether and how to use it.

Related: Schema Markup, Structured Data, Rich Results, Product Schema

Changelog