SwiftSchemaGenerate
    Schema stack

    Appointment Booking Stack

    Booking pages with Service + WebApplication context, FAQs, and breadcrumb navigation.

    Open generatorValidate in Rich Results Test
    Included schema
    Service
    Web Application
    Frequently Asked Questions
    Breadcrumb
    Fit

    When to use this stack

    • Appointment booking pages with embedded schedulers
    • Service pages where scheduling is the primary CTA
    • Pages where FAQs clarify availability and cancellations
    Composition

    What is included

    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

    • applicationCategory
    • areaServed.name
    • itemListElement[].name
    • mainEntity[].@type=Question
    • mainEntity[].acceptedAnswer.text
    • name
    • operatingSystem
    • provider.name
    • url

    Recommended properties

    • description
    • itemListElement[].item
    • mainEntity[].acceptedAnswer.text
    • mainEntity[].author.name
    • mainEntity[].name
    • offers.price
    • offers.priceCurrency
    • offers.url
    • serviceType
    • softwareVersion
    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": "Service",
    "@id": "https://www.example.com/services/consulting#service",
    "name": "Strategy Consultation",
    "serviceType": "Business Consulting",
    "provider": { "@type": "Organization", "name": "Example Advisors" },
    "areaServed": { "@type": "AdministrativeArea", "name": "US" },
    "offers": {
      "@type": "Offer",
      "price": "0.00",
      "priceCurrency": "USD",
      "url": "https://www.example.com/services/consulting/book"
    }
  },
  {
    "@context": "https://schema.org",
    "@type": "WebApplication",
    "@id": "https://www.example.com/services/consulting/book#app",
    "name": "Consultation Scheduler",
    "description": "Book a 30-minute strategy consultation with our team.",
    "applicationCategory": "BusinessApplication",
    "operatingSystem": "Any",
    "url": "https://www.example.com/services/consulting/book",
    "offers": {
      "@type": "Offer",
      "url": "https://www.example.com/services/consulting/book"
    }
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "How do I reschedule?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Use the confirmation email link to reschedule up to 24 hours in advance."
        }
      },
      {
        "@type": "Question",
        "name": "What is your cancellation policy?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Cancellations within 12 hours may incur a fee. See full policy on the booking page."
        }
      },
      {
        "@type": "Question",
        "name": "Do you offer virtual appointments?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes. Virtual appointments are available for all consultation types."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Services", "item": "https://www.example.com/services" },
      { "@type": "ListItem", "position": 3, "name": "Book Consultation", "item": "https://www.example.com/services/consulting/book" }
    ]
  }
]
    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 multiple service types?

    If multiple services are bookable on one page, add a Service entry for each.

    Can I link to third-party scheduling?

    Yes. Keep the WebApplication URL on the booking page and include the scheduler link in offers.url.

    Primary sources

    References