SwiftSchemaGenerate
    Schema stack

    Newsletter Landing Stack

    Newsletter/signup landing pages with WebPage + Offer context, FAQs, and breadcrumb navigation.

    Open generatorValidate in Rich Results Test
    Included schema
    Web Page
    Offer
    Frequently Asked Questions
    Breadcrumb
    Fit

    When to use this stack

    • Newsletter signup pages for publications or products
    • Lead-gen newsletter hubs that need clear offer/value context
    • Pages where FAQs explain cadence, content types, and unsubscribe
    Composition

    What is included

    • Web Page

      Declares the landing page for the newsletter signup.

    • Offer

      Expresses the value/offer of the newsletter (free subscription) and target URL.

    • Frequently Asked Questions

      Answers cadence, content, and unsubscribe questions.

    • Breadcrumb

      Provides navigation context to the signup page.

    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

    • availability
    • description
    • itemListElement[].name
    • mainEntity[].@type=Question
    • mainEntity[].acceptedAnswer.text
    • name
    • price
    • priceCurrency
    • url

    Recommended properties

    • dateModified
    • description
    • eligibleRegion
    • inLanguage
    • itemListElement[].item
    • mainEntity[].acceptedAnswer.text
    • mainEntity[].author.name
    • mainEntity[].name
    • priceValidUntil
    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": "WebPage",
    "@id": "https://www.example.com/newsletter#page",
    "name": "Subscribe to the Example Weekly",
    "description": "A weekly roundup of product updates, growth tips, and upcoming events from Example.",
    "url": "https://www.example.com/newsletter",
    "inLanguage": "en",
    "dateModified": "2025-02-12"
  },
  {
    "@context": "https://schema.org",
    "@type": "Offer",
    "@id": "https://www.example.com/newsletter#offer",
    "name": "Example Weekly Newsletter",
    "description": "Free weekly newsletter with product updates, tutorials, and event invites.",
    "price": "0.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "url": "https://www.example.com/newsletter/subscribe"
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "How often do you send it?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Once per week on Tuesdays. We send special editions only for major launches."
        }
      },
      {
        "@type": "Question",
        "name": "What content is included?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Product updates, tutorials, customer stories, and invites to upcoming webinars and events."
        }
      },
      {
        "@type": "Question",
        "name": "How do I unsubscribe?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Every email includes a one-click unsubscribe link. You can also manage preferences in your account."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Newsletter", "item": "https://www.example.com/newsletter" }
    ]
  }
]
    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 an Offer for a free newsletter?

    Yes. Set price to 0.00 and availability to InStock. Link the signup URL in offers.url.

    Should I include language or geo?

    Include inLanguage and eligibleRegion if the newsletter is locale-specific; otherwise keep it global.

    Primary sources

    References