SwiftSchemaGenerate
    Schema stack

    Support Status Stack

    Status pages with WebPage + Service context, FAQs, and breadcrumb navigation.

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

    When to use this stack

    • Service status overview pages listing system health
    • Support hubs with uptime metrics and incident summaries
    • Pages where FAQs clarify updates, SLAs, and notifications
    Composition

    What is included

    • Web Page

      Defines the status page and summary description.

    • Service

      Represents the service being monitored for status updates.

    • Frequently Asked Questions

      Answers update cadence, notifications, and support questions.

    • Breadcrumb

      Provides navigation context to the status hub.

    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

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

    Recommended properties

    • availableChannel
    • dateModified
    • inLanguage
    • itemListElement[].item
    • mainEntity[].acceptedAnswer.text
    • mainEntity[].author.name
    • mainEntity[].name
    • serviceType
    • url
    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://status.example.com#page",
    "name": "Service Status",
    "description": "Live system status, uptime history, and incident summaries.",
    "url": "https://status.example.com",
    "inLanguage": "en",
    "dateModified": "2025-04-22"
  },
  {
    "@context": "https://schema.org",
    "@type": "Service",
    "@id": "https://status.example.com#service",
    "name": "Example Cloud Platform",
    "serviceType": "SaaS Platform",
    "provider": { "@type": "Organization", "name": "Example Corp" },
    "areaServed": { "@type": "AdministrativeArea", "name": "Global" },
    "url": "https://www.example.com"
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "How often is the status updated?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "We update this page within 5 minutes of any incident or maintenance change."
        }
      },
      {
        "@type": "Question",
        "name": "How do I subscribe to updates?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Subscribe by email, SMS, or webhook from the status page notifications menu."
        }
      },
      {
        "@type": "Question",
        "name": "Where can I find SLA information?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "SLA details are linked from the status page and the support portal under Service Terms."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Support", "item": "https://www.example.com/support" },
      { "@type": "ListItem", "position": 3, "name": "Status", "item": "https://status.example.com" }
    ]
  }
]
    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 list every component?

    List key components on-page and consider additional Service objects if you show distinct component statuses.

    How do I handle maintenance windows?

    List maintenance windows in the page copy and add them to FAQ answers if they are recurring.

    Primary sources

    References