SLA / Service Terms Stack
Service pages with Offer terms, FAQ coverage, and breadcrumb navigation for SLAs/contract terms.
When to use this stack
- Service SLA/terms pages outlining uptime, credits, and response times
- Customer-facing SLA/contract terms that pair the service entity with offers
- Pages where FAQs clarify coverage, regions, and how to claim credits
What is included
Declares the SLA/terms page itself.
Captures the service covered by the SLA.
Expresses the SLA terms as an offer with eligibility and link.
Answers coverage, credits, and claim process questions.
Provides navigation context for the SLA page.
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
- description
- itemListElement[].name
- mainEntity[].@type=Question
- mainEntity[].acceptedAnswer.text
- name
- price
- priceCurrency
- provider.name
- url
Recommended properties
- dateModified
- description
- eligibleRegion
- inLanguage
- itemListElement[].item
- mainEntity[].acceptedAnswer.text
- mainEntity[].author.name
- mainEntity[].name
- priceValidUntil
- serviceType
- url
Combined JSON-LD
Paste this as one script tag, then replace every example value with data from the live page.
[
{
"@context": "https://schema.org",
"@type": "WebPage",
"@id": "https://www.example.com/legal/sla#page",
"name": "Service Level Agreement — Example Cloud",
"description": "Uptime targets, response times, and credit policy for Example Cloud.",
"url": "https://www.example.com/legal/sla",
"inLanguage": "en",
"dateModified": "2025-02-14"
},
{
"@context": "https://schema.org",
"@type": "Service",
"@id": "https://www.example.com/legal/sla#service",
"name": "Example Cloud",
"serviceType": "SaaS",
"provider": { "@type": "Organization", "name": "Example Corp" },
"areaServed": { "@type": "AdministrativeArea", "name": "Global" },
"url": "https://www.example.com"
},
{
"@context": "https://schema.org",
"@type": "Offer",
"@id": "https://www.example.com/legal/sla#offer",
"name": "Example Cloud SLA",
"description": "99.9% uptime SLA with service credits for impacted customers.",
"price": "0.00",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"eligibleRegion": "Worldwide",
"url": "https://www.example.com/legal/sla"
},
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is the uptime commitment?",
"acceptedAnswer": {
"@type": "Answer",
"text": "99.9% monthly uptime. We measure across all production regions."
}
},
{
"@type": "Question",
"name": "How do I claim a service credit?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Submit a ticket within 30 days of the incident with timestamps and logs; credits apply to the next billing cycle."
}
},
{
"@type": "Question",
"name": "Are there exclusions?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Scheduled maintenance, force majeure, and customer network issues are excluded. See the SLA for details."
}
}
]
},
{
"@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": "SLA", "item": "https://www.example.com/legal/sla" }
]
}
]Implement and verify
- 01
Start with the live page
Confirm titles, prices, availability, policies, and visible FAQ content before generating markup.
- 02
Add one JSON-LD script
Use the combined example as a template in the document head or before the closing body tag.
- 03
Complete regional details
Fill shipping destinations and timing for every region the page actually serves.
- 04
Link the return policy
Use a stable MerchantReturnPolicy URL and keep its terms synchronized with the page.
- 05
Match visible answers
Add only FAQs that users can read on the same page, with identical answers.
- 06
Validate after changes
Run Rich Results Test after implementation and whenever price, availability, or policy data changes.
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.
Stack FAQs
Should I list multiple regions?
Yes, if the SLA differs by region. Add multiple eligibleRegion entries or separate Offer objects aligned to the page content.
Can I include paid support tiers?
If support tiers are part of the SLA page, include separate Offer objects with their URLs and terms.