Using Article and NewsArticle Schema Correctly for Publishers

1. Why publishers need article schema at all

For editorial content, structured article schema is not a nice to have, it is the technical baseline requirement for an entire set of visibility formats that are simply not accessible without it. That includes Top Stories, the Google News carousel, non AMP display of author name and publish date directly in the search result, and eligibility for Google News overall, which is not even evaluated without correct schema.

Especially for time sensitive content, where freshness is a decisive ranking factor, the difference between visibility and invisibility often comes down not to content quality but to technical markup. An excellent article without or with broken schema simply does not compete in Top Stories, while an average article with clean schema at least gets a shot at visibility.

2. Article versus NewsArticle versus BlogPosting: the differences

Article is the most general of the three schema types and fits editorial content without a specific news angle, such as guides or background pieces without time pressure. NewsArticle is a subtype of Article specifically meant for actual news content and supports additional, news specific properties like dateline, which states the location and time of reporting. BlogPosting is also a subtype of Article, intended for blog posts in the classic sense, meaning opinion driven or more personal content.

In practice, choosing the right type is less about technical capability, since all three support similar fields, and more about content honesty toward Google. A company publishing genuine news updates daily should use NewsArticle, while a blog with opinion pieces or how to guides is better served by BlogPosting. Choosing the wrong type does not necessarily trigger a penalty, but it lowers the odds of getting the matching rich result format.

3. Required fields for Google News eligibility

For inclusion in Google News and Top Stories, Google requires a set of fields that go beyond the basic requirements of Article. These include headline with a concise, not overly long title, datePublished and preferably also dateModified in ISO 8601 format, image with at least one image at sufficient resolution, and complete linking of author and publisher as their own structured objects.

Beyond pure schema markup, actual inclusion in Google News requires separate registration through Google Publisher Center and compliance with editorial policies, for example around authorship transparency and corrections. Schema alone therefore does not guarantee News eligibility, but it is a mandatory prerequisite without which Google does not even consider the content for review in the first place.

4. Author linking with Person schema and sameAs

The author should not be marked up as a plain text string but as a standalone Person object that ideally includes a name, a URL to an author page, and via sameAs, links to external profiles like LinkedIn or an official author biography. This linking helps Google identify an author consistently across multiple articles and, ideally, across multiple publications, which contributes to establishing authority over time.

In larger newsrooms with many authors, a central author database that automatically generates the Person objects is preferable to entering them manually per article, since inconsistent data, for example different spellings of the same name, is a common problem here. If author is missing entirely, or only a generic editorial byline without a Person object is used, that lowers the transparency assessment that is particularly relevant for News eligibility.

5. Publisher linking with Organization schema

The publisher field expects an Organization object with a name and a logo field, which in turn should be marked up as an ImageObject with concrete width and height values. Google uses this logo among other things for display in Top Stories and the News carousel, which is why the image resolution and aspect ratio should follow Google's documented recommendations to avoid a distorted or cropped display.

A common mistake is phrasing the publisher object slightly differently on each page, for example with varying name spellings or different logo URLs depending on the subpage. This inconsistency makes it harder for Google to reliably attribute all articles to the same publisher, which is why a central, technically reusable publisher definition included identically across all article pages is recommended.

{
  "@context": "https://schema.org",
  "@type": "NewsArticle",
  "headline": "New EU Product Labeling Regulation Takes Effect",
  "image": [
    "https://www.mironsoft.de/media/news/eu-regulation-1x1.jpg",
    "https://www.mironsoft.de/media/news/eu-regulation-16x9.jpg"
  ],
  "datePublished": "2026-08-05T08:00:00+02:00",
  "dateModified": "2026-08-05T10:30:00+02:00",
  "author": {
    "@type": "Person",
    "name": "Julia Vogt",
    "url": "https://www.mironsoft.de/authors/julia-vogt",
    "sameAs": ["https://www.linkedin.com/in/julia-vogt-example"]
  },
  "publisher": {
    "@type": "Organization",
    "name": "Mironsoft",
    "logo": {
      "@type": "ImageObject",
      "url": "https://www.mironsoft.de/media/logo/mironsoft-logo.png",
      "width": 600,
      "height": 200
    }
  }
}

6. Common validation errors in practice

By far the most common error is a headline that is too long, which Google tolerates technically in the Rich Results Test but truncates in display, which is why a concise formulation well under the technical limit is recommended. Also common is a missing or too small image that falls short of Google's documented minimum width and resolution and therefore gets ignored for Top Stories.

A third, often overlooked error is a mismatch between the datePublished stated in the schema and the actually visible publish date on the page, for example when an article gets updated but the schema is not followed up with a new dateModified. Google treats such inconsistencies as a quality signal and can, in doubt, exclude affected articles from freshness sensitive formats like Top Stories.

7. The Rich Results Test as a diagnostic tool

Google's Rich Results Test should be a fixed part of every publishing workflow, ideally integrated automatically into the publication pipeline rather than only checked manually on a spot check basis. The test surfaces not only hard errors that block rich result display but also warnings for recommended, non mandatory fields whose addition improves display quality.

For newsrooms with a high publishing frequency it also pays to use the Search Console API to monitor the validation status of hundreds of articles automatically instead of checking each article individually in the test. That way systematic errors, for example after a CMS template update, get caught broadly and quickly, before they silently affect the entire article library for weeks.

8. Maintaining image and date fields correctly

For the image field, Google recommends providing multiple aspect ratios, typically 16:9, 4:3 and 1:1, so the image can get cropped appropriately depending on the display format without cutting off important content. A single square image is enough for basic functionality but limits display options in certain formats.

For the date fields, beyond correct ISO 8601 formatting, timezone matters too, since an article without a stated timezone can get interpreted differently by Google depending on server location. Publishers operating internationally should therefore state the timezone explicitly and consistently across all articles, to avoid ambiguity in temporal classification, particularly for time sensitive news content.

9. How it all ties into Google News and Top Stories

Even with technically perfect schema, keep in mind that inclusion in Google News and Top Stories is ultimately an editorial decision by Google, which alongside schema also weighs content quality, freshness, originality and the domain's overall trustworthiness. Schema markup opens the technical door but does not replace any of the content requirements Google sets for these particularly visible formats.

Publishers looking to newly get into Google News should therefore review editorial policies alongside the technical schema implementation, for example around a clear separation of advertising and editorial content and traceable authorship. Only the combination of clean schema and content requirements reliably leads, in practice, to visibility in these freshness sensitive search formats.

10. Summary

11. FAQ: Article and NewsArticle Schema: Key Takeaways