Schema stack

    Free Tool Stack

    Free tool/calculator pages with WebApplication context, FAQs, and breadcrumb navigation.

    Included schema
    Web Application
    Frequently Asked Questions
    Breadcrumb
    Fit

    When to use this stack

    • Standalone free tools or calculators offered for lead-gen
    • Product marketing pages that embed a free app experience
    • Pages where FAQs clarify limits, data handling, and upgrades
    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.

    [
      {
        "@context": "https://schema.org",
        "@type": "WebApplication",
        "@id": "https://www.example.com/tools/roi-calculator#app",
        "name": "ROI Calculator — Example",
        "description": "Estimate ROI using your current costs and projected savings.",
        "applicationCategory": "BusinessApplication",
        "operatingSystem": "Any",
        "softwareVersion": "2025.02",
        "url": "https://www.example.com/tools/roi-calculator",
        "offers": {
          "@type": "Offer",
          "price": "0.00",
          "priceCurrency": "USD",
          "availability": "https://schema.org/InStock",
          "url": "https://www.example.com/tools/roi-calculator"
        }
      },
      {
        "@context": "https://schema.org",
        "@type": "FAQPage",
        "mainEntity": [
          {
            "@type": "Question",
            "name": "Is the tool really free?",
            "acceptedAnswer": {
              "@type": "Answer",
              "text": "Yes. The calculator is free to use. No signup is required to get results."
            }
          },
          {
            "@type": "Question",
            "name": "Do you store my inputs?",
            "acceptedAnswer": {
              "@type": "Answer",
              "text": "Inputs stay in your browser session unless you choose to save or email your report."
            }
          },
          {
            "@type": "Question",
            "name": "How accurate are the estimates?",
            "acceptedAnswer": {
              "@type": "Answer",
              "text": "Estimates are illustrative. For a custom quote, contact sales with your usage details."
            }
          }
        ]
      },
      {
        "@context": "https://schema.org",
        "@type": "BreadcrumbList",
        "itemListElement": [
          { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
          { "@type": "ListItem", "position": 2, "name": "Tools", "item": "https://www.example.com/tools" },
          { "@type": "ListItem", "position": 3, "name": "ROI Calculator", "item": "https://www.example.com/tools/roi-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

    Can I include a paid upsell?

    Yes. Link the upsell in offers.url or the page body. Keep the free tool URL and pricing at 0.00 for the free experience.

    How do I handle localization?

    Localize text and currency on-page and in JSON-LD; adjust priceCurrency accordingly if you localize offers.

    Primary sources

    References