News Media Organization Schema — Establish Publisher Identity

Generate valid NewsMediaOrganization JSON‑LD for your publisher/about pages. Clarify brand, logo, profiles, and contact details so articles map to the right publisher.

Try the NewsMediaOrganization Generator

Why many publisher pages underperform

Pain points we solve

• Articles aren’t consistently attributed to the right publisher in search.
• Logos appear inconsistently due to missing or unclear markup.
• Multiple domains/editions dilute brand signals and confuse crawlers.
• Manual JSON‑LD drifts across templates and is hard to maintain.

How SwiftSchema helps

Solution

Our generator focuses on the essentials that clarify publisher identity: name, canonical URL, logo/image, address, contactPoint, and official profiles via sameAs.

It outputs clean, copy‑ready JSON‑LD you can paste on your publisher or about page, complementing Article and NewsArticle markup to strengthen brand association.

How it works

How it works

1. Choose NewsMediaOrganization in the generator below.
2. Enter organization name, canonical site URL, and a high‑quality logo image.
3. Add address (if applicable), contactPoint (telephone + contactType), and sameAs profiles (site, app, socials).
4. Copy JSON or Script and paste it on your publisher/about page.
5. Validate in the Rich Results Test and keep details in sync across editions.

Generate NewsMediaOrganization JSON‑LD

Paste on your publisher or about page. Validate. Ship.

What is NewsMediaOrganization structured data?

NewsMediaOrganization is an Organization subtype tailored for news publishers and media outlets. It captures the brand’s name, canonical URL, logos, addresses, contact points, and official profiles, and complements Article/NewsArticle schema to reinforce publisher relationships.

Eligibility & Status

This markup improves brand understanding and publisher associations but does not directly provide a standalone rich result. It supports identity features (including logo usage) when policies and requirements are met. Use it on your about/publisher pages to give crawlers a canonical view of your newsroom.

Why publisher markup matters

• Brand consistency: Ensures search engines use the right name, URL, and logo across your articles.
• Trust signals: Official addresses, contact points, and profiles reassure readers and partners.
• Multi-edition clarity: Disambiguate regional/vertical editions while tying them back to the parent brand.
• Operational control: Centralized JSON-LD prevents drift during redesigns or rebrands.

Essential properties to include

• name
  : Official newsroom name (use
  alternateName
  for abbreviations).
• url
  : Canonical publisher site.
• logo
  /
  image
  : High-resolution ImageObject served from a stable CDN.
• address
  : PostalAddress for HQ or mailing address.
• contactPoint
  :
  contactType
  +
  telephone
  /
  email
  for press, reader services, etc.
• sameAs
  : Official profiles (apps, social, Google News, Apple News, Wikipedia).
• foundingDate
  ,
  parentOrganization
  ,
  memberOf
  : Context about your history and ownership.
• areaServed
  : Regions or audiences you cover.

Preparing publisher data before generating schema

1. Confirm branding: Validate the canonical name, tagline, and logos with leadership.
2. Gather contact info: Press, advertising, subscriptions, or corrections lines.
3. Inventory editions: List regional domains/verticals and their relationship to the main brand.
4. Collect profile links: Apps, newsletters, social channels, podcast hubs.
5. Document history: Founding year, awards, ownership; reuse this content on the page to avoid thin copy.
6. Plan updates: Define who updates schema during rebrands or leadership changes.

Implementation workflow inside SwiftSchema

1. Select NewsMediaOrganization in the generator.
2. Enter
   name
   ,
   alternateName
   ,
   url
   , and
   logo
   .
3. Add
   image
   ,
   address
   , and
   contactPoint
   entries with
   contactType
   +
   telephone
   .
4. Populate
   sameAs
   with official profiles; include
   parentOrganization
   if applicable.
5. Export JSON-LD, embed it on your about/publisher page, and optionally include in the site footer template.
6. Validate using the Rich Results Test; archive validation URLs for compliance.

Troubleshooting & QA

• Inconsistent naming: Align schema
  name
  with Business Profiles, News Publisher Center, and site headers.
• Broken logos: Logos must be publicly accessible; avoid querystrings that expire.
• Multiple editions: If each edition has its own domain, ensure each has accurate
  url
  and references the parent organization.
• Outdated contacts: Monitor when phone numbers/emails change; update schema immediately.
• Missing sameAs: Without official profile links, search engines may misattribute your brand.

Automate QA by storing publisher metadata in a CMS or config file. When marketing updates branding or contact info, regenerate the schema automatically.

Maintenance and governance

• Update schema during rebrands, mergers, or logo changes across all templates.
• Audit quarterly to confirm logos, addresses, and contact points still match your public pages.
• Keep
  lastReviewed
  metadata current and document schema ownership (comms, product, or engineering).
• Maintain a publisher metadata registry (spreadsheet or CMS entry) feeding SwiftSchema.

Common Errors & Fixes

• Inconsistent naming/URLs: use a single canonical brand name and URL across pages.
• Logo issues: provide a crawlable, high-quality image at a stable URL.
• Missing profiles: add official profiles via
  sameAs
  (site, apps, social, newsstand).
• Weak contact data: include
  contactPoint
  with
  contactType
  and
  telephone
  .

{
  "@context": "https://schema.org",
  "@type": "NewsMediaOrganization",
  "name": "The Example Times",
  "url": "https://www.exampletimes.com"
}