XooCode(){

NewsMediaOrganization

NewsMediaOrganization is an Organization subtype for news publishers, broadcasters, and news agencies. It is the most property-rich Organization subtype, with 10 properties focused on editorial transparency and trust. Google News reads these as publisher credibility signals when evaluating eligibility for Top Stories and Google News surfaces.

This type pairs naturally with NewsArticle: the NewsArticle's publisher should be typed as NewsMediaOrganization. The trust properties on the publisher strengthen the credibility of every article it publishes.

Full example of schema.org/NewsMediaOrganization json-ld markup

The markup is verified as valid with Rich Results Test from Google.

Highlight legend:Required by GoogleRecommendedOptional
schema.org/NewsMediaOrganization
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@id": "https://dunmoreherald.com#publisher",
  "@type": "NewsMediaOrganization",
  "name": "Dunmore Herald",
  "description": "Independent local newspaper covering Dunmore, Scranton, and Lackawanna County since 1892. Daily print edition and digital news.",
  "url": "https://dunmoreherald.com",
  "logo": {
    "@type": "ImageObject",
    "url": "https://dunmoreherald.com/images/herald-logo.png",
    "width": "600",
    "height": "60"
  },
  "foundingDate": "1892",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "150 Elm Street",
    "addressLocality": "Dunmore",
    "addressRegion": "PA",
    "postalCode": "18512",
    "addressCountry": "US"
  },
  "areaServed": {
    "@type": "AdministrativeArea",
    "name": "Lackawanna County, Pennsylvania"
  },
  "ethicsPolicy": "https://dunmoreherald.com/ethics",
  "masthead": "https://dunmoreherald.com/staff",
  "correctionsPolicy": "https://dunmoreherald.com/corrections",
  "verificationFactCheckingPolicy": "https://dunmoreherald.com/fact-checking",
  "unnamedSourcesPolicy": "https://dunmoreherald.com/unnamed-sources",
  "noBylinesPolicy": "https://dunmoreherald.com/no-bylines",
  "actionableFeedbackPolicy": "https://dunmoreherald.com/feedback",
  "missionCoveragePrioritiesPolicy": "https://dunmoreherald.com/mission",
  "diversityPolicy": "https://dunmoreherald.com/diversity",
  "diversityStaffingReport": "https://dunmoreherald.com/diversity-report-2025",
  "sameAs": [
    "https://twitter.com/dunmoreherald",
    "https://www.facebook.com/dunmoreherald"
  ]
}
</script>

The 10 editorial trust properties

All 10 accept a URL or CreativeWork object pointing to the relevant policy page:

  • ethicsPolicy - editorial ethics and standards
  • masthead - editorial staff listing
  • correctionsPolicy - how corrections and retractions are handled
  • verificationFactCheckingPolicy - fact-checking methodology
  • unnamedSourcesPolicy - rules for using anonymous sources
  • noBylinesPolicy - when and why articles are published without a byline
  • actionableFeedbackPolicy - how readers can report errors or submit feedback
  • missionCoveragePrioritiesPolicy - editorial mission and coverage priorities
  • diversityPolicy - newsroom diversity commitments
  • diversityStaffingReport - published diversity data (accepts Article or URL)

Which trust properties matter most

Google News documentation specifically references ethicsPolicy and masthead as signals it evaluates. correctionsPolicy and verificationFactCheckingPolicy are also read by fact-checking systems. The other six are less commonly checked by automated systems but signal thoroughness to human reviewers. At minimum, include ethicsPolicy and masthead. Ideally, include all that your newsroom has published.

IFCN verification

For fact-checking organizations, linking to your International Fact-Checking Network (IFCN) signatory page via sameAs strengthens the connection between your NewsMediaOrganization and your ClaimReview markup. Google cross-references IFCN membership when evaluating fact-check rich result eligibility.

Minimal valid version

The smallest markup that still produces a valid NewsMediaOrganization entity. Use it as the floor. Reach for the advanced example above when you want search engines and AI agents to understand more about your content.

schema.org/NewsMediaOrganization (minimal)
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "NewsMediaOrganization",
  "name": "Dunmore Herald",
  "url": "https://dunmoreherald.com"
}
</script>

Google rich results this unlocks

Markup matching this example makes your page eligible for the following Google Search rich results. The primary target drives the required / recommended property classification in the advanced code block above.

Common NewsMediaOrganization mistakes

Mistakes that pass validation but silently fail to earn rich results or mislead consumers walking the graph. Avoid these and your markup will be ahead of most sites in the wild.

  1. 01

    Using Organization for a news publisher

    Wrong
    "@type": "Organization" as the publisher of NewsArticle blocks
    Right
    "@type": "NewsMediaOrganization"

    NewsMediaOrganization carries trust properties that Google News reads when evaluating publisher eligibility. Using generic Organization for a news publisher means Google cannot read your editorial policies, which weakens your credibility signals for Top Stories and Google News.

  2. 02

    Missing ethicsPolicy and masthead

    Wrong
    NewsMediaOrganization with name and url but no trust properties
    Right
    At minimum: "ethicsPolicy": "https://...", "masthead": "https://..."

    Google News documentation specifically mentions ethicsPolicy and masthead as evaluated signals. A NewsMediaOrganization without them provides minimal benefit over generic Organization. If you only add two trust properties, make them these two.

  3. 03

    Trust properties pointing to non-existent pages

    Wrong
    "ethicsPolicy": "https://example.com/ethics" (returns 404)
    Right
    Only include trust properties that point to real, published policy pages

    Google and fact-checking systems follow these URLs. A 404 or placeholder page is worse than omitting the property. It signals that the publisher claims to have policies it has not actually published, which undermines trust rather than building it.

  4. 04

    Duplicating the NewsMediaOrganization in every NewsArticle

    Wrong
    Full NewsMediaOrganization object repeated in every article's publisher property
    Right
    Define the NewsMediaOrganization once (on the homepage) with an @id, then reference it: "publisher": { "@id": "https://dunmoreherald.com#publisher" }

    The full organization block with all trust properties only needs to appear once. Every article should reference it via @id. Duplicating 15+ properties in every article bloats the markup and creates maintenance burden when policies change.

Schema properties in this example

NewsMediaOrganizationnamedescriptionurllogoImageObjectfoundingDateaddressPostalAddressareaServedAdministrativeAreaethicsPolicymastheadcorrectionsPolicyverificationFactCheckingPolicyunnamedSourcesPolicynoBylinesPolicyactionableFeedbackPolicymissionCoveragePrioritiesPolicydiversityPolicydiversityStaffingReportsameAs

About the example data

The Dunmore Herald is the fictional local newspaper that published the NewsArticle about Xoo Code Shop's opening. Here it gets its own standalone NewsMediaOrganization block with all 10 editorial trust properties. The @id matches the publisher reference in the NewsArticle example.

Comments

Loading comments...

Leave a comment