SwiftSchemaGenerate
    Schema stack

    Publisher Schema Stack

    NewsArticle + Breadcrumb + Speakable + SubscriptionAndPaywall signals for publisher pages that need clarity, eligibility, and access control.

    Open generatorValidate in Rich Results Test
    Included schema
    News Article
    Breadcrumb
    Speakable
    Subscription and Paywall
    Fit

    When to use this stack

    • News or longform articles with metered or hard paywalls
    • Publisher sections that need breadcrumb clarity and speakable selectors
    • Articles where eligibility and access signals reduce paywall confusion
    Composition

    What is included

    • News Article

      Primary article entity with headline, dates, author, and publisher.

    • Breadcrumb

      Clarifies article location within the site structure.

    • Speakable

      Defines speakable sections for voice surfaces.

    • Subscription and Paywall

      Marks paywall accessibility and paywalled sections for Google guidance.

    Data contract

    Properties across the bundle

    Nested properties keep their parent path, such as offers.priceCurrency. Only publish values that match visible page content.

    Required properties

    • author.name
    • datePublished
    • hasPart.cssSelector
    • hasPart.isAccessibleForFree
    • headline
    • image
    • isAccessibleForFree
    • itemListElement[].name
    • speakable.cssSelector
    • url

    Recommended properties

    • dateModified
    • description
    • hasPart.url
    • itemListElement[].item
    • mainEntityOfPage
    • publisher.name
    • speakable.xpath
    Copy-ready example

    Combined JSON-LD

    Paste this as one script tag, then replace every example value with data from the live page.

    Validate
    [
  {
    "@context": "https://schema.org",
    "@type": "NewsArticle",
    "@id": "https://www.example.com/news/ai-adoption-report#article",
    "headline": "AI Adoption Report 2026: Enterprises Accelerate Deployment",
    "description": "Key findings from the 2026 enterprise AI adoption survey across 1,200 organizations.",
    "datePublished": "2026-02-10T13:00:00Z",
    "dateModified": "2026-02-11T09:00:00Z",
    "url": "https://www.example.com/news/ai-adoption-report",
    "mainEntityOfPage": "https://www.example.com/news/ai-adoption-report",
    "image": [
      "https://www.example.com/images/ai-report-hero.webp"
    ],
    "author": {
      "@type": "Person",
      "name": "Casey Lin",
      "url": "https://www.example.com/authors/casey-lin"
    },
    "publisher": {
      "@type": "Organization",
      "name": "Example News",
      "url": "https://www.example.com",
      "logo": {
        "@type": "ImageObject",
        "url": "https://www.example.com/images/logo-120x60.png"
      }
    },
    "isAccessibleForFree": false,
    "hasPart": {
      "@type": "WebPageElement",
      "isAccessibleForFree": false,
      "cssSelector": ".paywall",
      "url": "https://www.example.com/news/ai-adoption-report/preview"
    },
    "speakable": {
      "@type": "SpeakableSpecification",
      "cssSelector": [
        "article h1",
        "article h2.lede"
      ]
    }
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "News", "item": "https://www.example.com/news" },
      { "@type": "ListItem", "position": 3, "name": "AI Adoption Report", "item": "https://www.example.com/news/ai-adoption-report" }
    ]
  }
]
    Workflow

    Implement and verify

    1. 01

      Start with the live page

      Confirm titles, prices, availability, policies, and visible FAQ content before generating markup.

    2. 02

      Add one JSON-LD script

      Use the combined example as a template in the document head or before the closing body tag.

    3. 03

      Complete regional details

      Fill shipping destinations and timing for every region the page actually serves.

    4. 04

      Link the return policy

      Use a stable MerchantReturnPolicy URL and keep its terms synchronized with the page.

    5. 05

      Match visible answers

      Add only FAQs that users can read on the same page, with identical answers.

    6. 06

      Validate after changes

      Run Rich Results Test after implementation and whenever price, availability, or policy data changes.

    Quality check

    Common errors and fixes

    • Missing currency or availability

      Use ISO currency codes and complete schema.org availability URLs in Offer data.

    • Incomplete shipping details

      Include shippingDestination.addressCountry and deliveryTime.transitTime with units.

    • Return policy is not connected

      Reference MerchantReturnPolicy from the Offer and provide a stable public policy URL.

    • FAQ answers differ from the page

      Keep structured FAQ answers identical to visible answers.

    Questions

    Stack FAQs

    Do I need both speakable and paywall markup?

    If you support voice surfaces and a paywall, yes—speakable clarifies which content is eligible for voice, and paywall markup clarifies access.

    Should I use Article or NewsArticle?

    Use NewsArticle for news/publisher content that meets freshness and E-E-A-T expectations; otherwise use Article.

    Primary sources

    References