SwiftSchemaGenerate
    Schema stack

    Waitlist Landing Stack

    Waitlist/early access 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

    • Early access or beta waitlist pages
    • Product launch signup pages with limited slots
    • Pages where FAQs clarify timing, eligibility, and invite flow
    Composition

    What is included

    • Web Page

      Declares the waitlist landing page and summary description.

    • Offer

      Describes the early access offer and signup URL.

    • Frequently Asked Questions

      Answers invite timing, access tiers, and eligibility questions.

    • Breadcrumb

      Provides navigation context to the waitlist 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/early-access#page",
    "name": "Join the Early Access Waitlist",
    "description": "Get early access to Example AI with priority onboarding and launch pricing.",
    "url": "https://www.example.com/early-access",
    "inLanguage": "en",
    "dateModified": "2025-03-08"
  },
  {
    "@context": "https://schema.org",
    "@type": "Offer",
    "@id": "https://www.example.com/early-access#offer",
    "name": "Early Access Waitlist",
    "description": "Free waitlist signup for early access invitations.",
    "price": "0.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "url": "https://www.example.com/early-access#signup"
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "When will invites be sent?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Invites roll out weekly starting in April. You will receive an email once your spot is available."
        }
      },
      {
        "@type": "Question",
        "name": "Is the waitlist free?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes. Joining the waitlist is free and does not require a credit card."
        }
      },
      {
        "@type": "Question",
        "name": "How is priority determined?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Priority is based on signup time and fit for current feature testing."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Early Access", "item": "https://www.example.com/early-access" }
    ]
  }
]
    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 the invite timeline?

    Yes. Match any public timelines on the page and mirror them in FAQ answers.

    How do I handle multiple access tiers?

    List each tier in the page content and add separate Offer objects if each tier has distinct terms.

    Primary sources

    References