Stack

Support Status Stack

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

Open generator Validate in Rich Results Test

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

What's included

Web Page
Open generator
Defines the status page and summary description.
Service
Open generator
Represents the service being monitored for status updates.
Frequently Asked Questions
Open generator
Answers update cadence, notifications, and support questions.
Breadcrumb
Open generator
Provides navigation context to the status hub.

Required properties (stack union)

Ensure every applicable required property is present in your implementation. Nested props reference their parent objects (for example, `offers.priceCurrency`).

areaServed.name

description

itemListElement[].name

mainEntity[].@type=Question

mainEntity[].acceptedAnswer.text

name

provider.name

url

Recommended properties (stack union)

availableChannel

dateModified

inLanguage

itemListElement[].item

mainEntity[].acceptedAnswer.text

mainEntity[].author.name

mainEntity[].name

serviceType

url

Combined JSON-LD

Paste as a single script tag. Keep product details, offer data, shipping/returns, and FAQ answers in sync with the 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" }
    ]
  }
]

Implementation steps

Start from your live product detail page content; ensure titles, prices, and availability match the page.
Embed one JSON-LD script in the head or just before the closing body tag using the combined example as a template.
Fill shipping details for each region you serve and keep them aligned with on-page shipping tables.
Attach your canonical MerchantReturnPolicy URL and keep the policy text in sync with Merchant Center.
Add 3–6 FAQs that address purchase blockers (shipping, returns, compatibility) and keep answers consistent with visible content.
Validate in the Rich Results Test and revalidate after price/availability/policy changes.

Common errors and fixes

Missing currency or availability: ensure `offers.priceCurrency` and `offers.availability` use ISO currency codes and schema URLs.
ShippingDetails missing destination or transit time: include `shippingDestination.addressCountry` and `deliveryTime.transitTime` with units.
MerchantReturnPolicy not linked: reference it from the Offer via `hasMerchantReturnPolicy` and provide a stable policy URL.
FAQ answers don't match the page: keep FAQ content identical to visible answers to avoid review or manual actions.

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.

SwiftSchema

Intuitive Schema Generation at Your Fingertips