SwiftSchemaGenerate
    Schema stack

    SaaS Downtime Credit Stack

    SaaS downtime credit pages with Service + Offer context, FAQs, and breadcrumb navigation.

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

    When to use this stack

    • Downtime credit policy pages for SaaS platforms
    • Service credit request or eligibility landing pages
    • Pages where FAQs clarify timelines and claim steps
    Composition

    What is included

    • Service

      Captures the SaaS service covered by the downtime credit policy.

    • Offer

      Represents the credit or compensation offer terms.

    • Frequently Asked Questions

      Answers questions about eligibility, proof, and processing times.

    • Breadcrumb

      Provides navigation context for the downtime credit page.

    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
    • availability
    • itemListElement[].name
    • mainEntity[].@type=Question
    • mainEntity[].acceptedAnswer.text
    • name
    • price
    • priceCurrency
    • provider.name
    • url

    Recommended properties

    • description
    • eligibleRegion
    • itemListElement[].item
    • mainEntity[].acceptedAnswer.text
    • mainEntity[].author.name
    • mainEntity[].name
    • priceValidUntil
    • 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://www.example.com/legal/downtime-credits#service",
    "name": "Example Cloud Platform",
    "serviceType": "SaaS",
    "provider": { "@type": "Organization", "name": "Example Cloud Co." },
    "areaServed": { "@type": "AdministrativeArea", "name": "Global" },
    "url": "https://www.example.com"
  },
  {
    "@context": "https://schema.org",
    "@type": "Offer",
    "@id": "https://www.example.com/legal/downtime-credits#offer",
    "name": "Service Downtime Credit",
    "description": "Account credit applied when uptime falls below the monthly SLA.",
    "price": "0.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "eligibleRegion": "Worldwide",
    "priceValidUntil": "2026-12-31",
    "url": "https://www.example.com/legal/downtime-credits#claim"
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "When am I eligible for a credit?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Credits apply when monthly uptime drops below 99.9% for your paid plan."
        }
      },
      {
        "@type": "Question",
        "name": "How do I request a credit?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Submit a request within 30 days of the incident with timestamps and account details."
        }
      },
      {
        "@type": "Question",
        "name": "How are credits issued?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Approved credits are applied to your next invoice as a service credit."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Legal", "item": "https://www.example.com/legal" },
      { "@type": "ListItem", "position": 3, "name": "Downtime Credits", "item": "https://www.example.com/legal/downtime-credits" }
    ]
  }
]
    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 different tiers for each plan?

    If downtime credits vary by plan, add separate Offer entries tied to each plan’s terms.

    Do I need to list excluded incidents?

    Yes. Document exclusions in the page content so FAQ answers and offers align with policy.

    Primary sources

    References