SwiftSchemaGenerate
    Schema stack

    Status Incident Detail Stack

    Incident detail pages with Service context, Article-style incident post, FAQs, and breadcrumb navigation.

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

    When to use this stack

    • Status/incident detail pages for outages or service disruptions
    • Postmortems or RFO pages linked from a status hub
    • Pages where FAQs clarify impact, remediation steps, and timelines
    Composition

    What is included

    • Service

      Defines the affected service with provider and status context.

    • Article

      Documents the incident detail/postmortem with headline and dates.

    • Frequently Asked Questions

      Answers customer-impact and remediation questions.

    • Breadcrumb

      Provides navigation context from 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
    • datePublished
    • description
    • headline
    • itemListElement[].name
    • mainEntity[].@type=Question
    • mainEntity[].acceptedAnswer.text
    • name
    • provider.name
    • url

    Recommended properties

    • about.@id
    • author.name
    • dateModified
    • 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": "Service",
    "@id": "https://status.example.com/incidents/2025-02-redis#service",
    "name": "Core API",
    "serviceType": "SaaS API",
    "provider": { "@type": "Organization", "name": "Example Corp" },
    "areaServed": { "@type": "AdministrativeArea", "name": "Global" },
    "url": "https://status.example.com"
  },
  {
    "@context": "https://schema.org",
    "@type": "Article",
    "@id": "https://status.example.com/incidents/2025-02-redis#article",
    "headline": "Incident: Elevated Errors on Core API",
    "description": "We observed elevated 5xx errors due to a Redis cluster failover. Service is restored.",
    "datePublished": "2025-02-14T16:20:00Z",
    "dateModified": "2025-02-14T17:05:00Z",
    "author": { "@type": "Organization", "name": "Example SRE" },
    "about": { "@id": "https://status.example.com/incidents/2025-02-redis#service" },
    "url": "https://status.example.com/incidents/2025-02-redis"
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "What was the impact?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "API error rates peaked at 7% between 16:05 and 16:25 UTC. No data loss occurred."
        }
      },
      {
        "@type": "Question",
        "name": "How was it mitigated?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "We promoted a standby Redis node, rebalanced connections, and increased circuit-breaker backoffs."
        }
      },
      {
        "@type": "Question",
        "name": "What’s next?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "We are adding automated failover simulation tests and expanding headroom by 30% for cache clusters."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Status", "item": "https://status.example.com" },
      { "@type": "ListItem", "position": 3, "name": "Incident 2025-02 Redis", "item": "https://status.example.com/incidents/2025-02-redis" }
    ]
  }
]
    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 all impacted services?

    Yes. Add one Service object per impacted service if multiple are affected and visible on the page.

    How do I handle updates over time?

    Update dateModified on the Article when you add remediations. Keep FAQ answers aligned to the latest state.

    Primary sources

    References