SwiftSchemaGenerate
    Schema stack

    Cloud Pricing Estimator Stack

    Cloud pricing estimators with WebApplication + Offer, FAQs, and breadcrumb navigation.

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

    When to use this stack

    • Cloud cost calculators for compute, storage, and networking
    • Estimator pages offering downloadable quotes or exports
    • Pages where FAQs clarify billing assumptions and rounding
    Composition

    What is included

    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

    • applicationCategory
    • availability
    • itemListElement[].name
    • mainEntity[].@type=Question
    • mainEntity[].acceptedAnswer.text
    • name
    • operatingSystem
    • price
    • priceCurrency
    • url

    Recommended properties

    • category
    • description
    • itemListElement[].item
    • mainEntity[].acceptedAnswer.text
    • mainEntity[].author.name
    • mainEntity[].name
    • offers.url
    • priceValidUntil
    • softwareVersion
    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": "WebApplication",
    "@id": "https://www.example.com/cloud/pricing#app",
    "name": "Cloud Pricing Estimator",
    "description": "Estimate monthly cloud costs for compute, storage, and bandwidth.",
    "applicationCategory": "FinanceApplication",
    "operatingSystem": "Any",
    "url": "https://www.example.com/cloud/pricing",
    "offers": { "@id": "https://www.example.com/cloud/pricing#offer" }
  },
  {
    "@context": "https://schema.org",
    "@type": "Offer",
    "@id": "https://www.example.com/cloud/pricing#offer",
    "name": "Estimator Report Export",
    "description": "Downloadable estimate summary and line-item breakdown.",
    "price": "0.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "url": "https://www.example.com/cloud/pricing#export",
    "category": "Estimate"
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "How accurate are the estimates?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Estimates are based on the inputs provided and may vary with usage spikes and regional pricing."
        }
      },
      {
        "@type": "Question",
        "name": "Do prices include taxes?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "No. Taxes and regulatory fees are calculated at checkout based on your billing address."
        }
      },
      {
        "@type": "Question",
        "name": "Can I save my estimate?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes. Export a PDF or save the estimate to your account for future updates."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Cloud", "item": "https://www.example.com/cloud" },
      { "@type": "ListItem", "position": 3, "name": "Pricing Estimator", "item": "https://www.example.com/cloud/pricing" }
    ]
  }
]
    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

    Do I need an Offer if the estimator is free?

    Yes. Set price to 0.00 and keep availability and URL aligned to the export or save flow.

    How do I handle regional pricing?

    Add eligibleRegion to the Offer or provide separate Offer objects per region shown on the page.

    Primary sources

    References