Stack

Pricing Calculator Stack

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

Open generator Validate in Rich Results Test

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

What's included

Web Application
Open generator
Defines the calculator tool as an app, including category and URL.
Frequently Asked Questions
Open generator
Answers how estimates are calculated, what inputs matter, and validity.
Breadcrumb
Open generator
Provides navigation context to the calculator page.

Required properties (stack union)

Ensure every applicable required property is present in your implementation. Nested props reference their parent objects (for example, `offers.priceCurrency`).

applicationCategory

itemListElement[].name

mainEntity[].@type=Question

mainEntity[].acceptedAnswer.text

name

operatingSystem

url

Recommended properties (stack union)

description

itemListElement[].item

mainEntity[].acceptedAnswer.text

mainEntity[].author.name

mainEntity[].name

offers.url

softwareVersion

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": "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" }
    ]
  }
]

Implementation steps

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

Common errors and fixes

Missing currency or availability: ensure `offers.priceCurrency` and `offers.availability` use ISO currency codes and schema URLs.
ShippingDetails missing destination or transit time: include `shippingDestination.addressCountry` and `deliveryTime.transitTime` with units.
MerchantReturnPolicy not linked: reference it from the Offer via `hasMerchantReturnPolicy` and provide a stable policy URL.
FAQ answers don't match the page: keep FAQ content identical to visible answers to avoid review or manual actions.

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.

SwiftSchema

Intuitive Schema Generation at Your Fingertips