Cookies & analytics

    We use cookies for analytics and to serve ads. Accept to enable Google Analytics and AdSense. You can decline to stay opt-out.

    SwiftSchema Logo

    SwiftSchema

    Intuitive Schema Generation at Your Fingertips

    AboutLearnContact
      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

      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

      What's included

      • Defines the affected service with provider and status context.

      • Documents the incident detail/postmortem with headline and dates.

      • Frequently Asked Questions
        Open generator

        Answers customer-impact and remediation questions.

      • Breadcrumb
        Open generator

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

      Recommended properties (stack union)

      about.@id
      author.name
      dateModified
      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": "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" }
          ]
        }
      ]

      Implementation steps

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

      Common errors and fixes

      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.

      References