SwiftSchemaGenerate
    Schema stack

    Beta / Early Access Stack

    Beta program pages with Event, Offer, FAQs, and breadcrumbs.

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

    When to use this stack

    • Early access signup pages
    • Beta program enrollment pages
    • Product preview waitlists with timelines
    Composition

    What is included

    • Event

      Represents the beta program timeline and participation window.

    • Offer

      Captures the beta enrollment offer or access tier.

    • Frequently Asked Questions

      Answers eligibility, access timing, and feedback questions.

    • Breadcrumb

      Provides navigation context for the beta program 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
    • itemListElement[].name
    • mainEntity[].@type=Question
    • mainEntity[].acceptedAnswer.text
    • name
    • price
    • priceCurrency
    • startDate
    • url

    Recommended properties

    • category
    • description
    • endDate
    • eventAttendanceMode
    • eventStatus
    • itemListElement[].item
    • location.name
    • 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": "Event",
    "@id": "https://www.example.com/beta#event",
    "name": "Widget Pro Beta Program",
    "startDate": "2025-06-01",
    "endDate": "2025-08-31",
    "eventStatus": "https://schema.org/EventScheduled",
    "eventAttendanceMode": "https://schema.org/OnlineEventAttendanceMode",
    "location": { "@type": "VirtualLocation", "name": "Online" }
  },
  {
    "@context": "https://schema.org",
    "@type": "Offer",
    "@id": "https://www.example.com/beta#offer",
    "name": "Early Access Enrollment",
    "description": "Apply for early access and provide feedback to shape the product.",
    "price": "0.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "url": "https://www.example.com/beta#apply",
    "priceValidUntil": "2025-07-15"
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "Who can join the beta?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Applicants must be over 18 and agree to provide product feedback."
        }
      },
      {
        "@type": "Question",
        "name": "When will access be granted?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Accepted participants receive access within 3 business days of approval."
        }
      },
      {
        "@type": "Question",
        "name": "What feedback is required?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "We request a short survey after two weeks and optional interviews."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Beta Program", "item": "https://www.example.com/beta" }
    ]
  }
]
    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

    Should I include NDA requirements?

    If an NDA is required, mention it in the page copy and reflect it in the FAQ answers.

    How do I show a waitlist?

    Use Offer availability and a clear description of the waitlist steps in the FAQ.

    Primary sources

    References