SwiftSchemaGenerate
    Schema stack

    Pricing Calculator Stack

    Interactive pricing calculator pages with WebApplication context, FAQs, and breadcrumb navigation.

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

    When to use this stack

    • Self-serve pricing calculator tools for SaaS or services
    • Cost estimator pages where the app context should be explicit
    • Pages where FAQs explain inputs, rounding, and how quotes are honored
    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
    • itemListElement[].name
    • mainEntity[].@type=Question
    • mainEntity[].acceptedAnswer.text
    • name
    • operatingSystem
    • url

    Recommended properties

    • description
    • itemListElement[].item
    • mainEntity[].acceptedAnswer.text
    • mainEntity[].author.name
    • mainEntity[].name
    • offers.url
    • 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/pricing/calculator#app",
    "name": "Example Cloud Pricing Calculator",
    "description": "Estimate monthly costs for Example Cloud based on usage, seats, and regions.",
    "applicationCategory": "BusinessApplication",
    "operatingSystem": "Any",
    "softwareVersion": "2025.02",
    "url": "https://www.example.com/pricing/calculator",
    "offers": {
      "@type": "Offer",
      "url": "https://www.example.com/pricing#plans"
    }
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "How do you calculate usage?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "We multiply monthly active units by your selected tier rate and add any overage at published rates."
        }
      },
      {
        "@type": "Question",
        "name": "Are taxes or fees included?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Estimates exclude taxes and payment processing fees. Final totals at checkout may differ based on your billing country."
        }
      },
      {
        "@type": "Question",
        "name": "How long is the quote valid?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Quotes are indicative only. Plan pricing is governed by the live pricing page and your contract terms."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Pricing", "item": "https://www.example.com/pricing" },
      { "@type": "ListItem", "position": 3, "name": "Pricing Calculator", "item": "https://www.example.com/pricing/calculator" }
    ]
  }
]
    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 WebApplication for every calculator?

    Use WebApplication when the calculator is the primary interactive tool on the page. Otherwise, keep it to FAQ + Breadcrumb.

    Can I show multiple offers?

    Link to the main pricing/plan URLs in offers.url. If you expose multiple plan URLs, include one Offer per plan shown on the page.

    Primary sources

    References