Schema stack

    Carbon Footprint Calculator Stack

    Carbon footprint calculators with WebApplication context, FAQs, and breadcrumb navigation.

    Included schema
    Web Application
    Frequently Asked Questions
    Breadcrumb
    Fit

    When to use this stack

    • Personal or business footprint calculators
    • Sustainability tools with inputs for travel, energy, and waste
    • Pages where FAQs clarify methodology and emissions factors
    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
    • url

    Recommended properties

    • description
    • featureList
    • itemListElement[].item
    • mainEntity[].acceptedAnswer.text
    • mainEntity[].author.name
    • mainEntity[].name
    • operatingSystem
    • provider.name
    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/carbon-calculator#app",
        "name": "Carbon Footprint Calculator",
        "url": "https://www.example.com/tools/carbon-calculator",
        "applicationCategory": "EnvironmentalApplication",
        "operatingSystem": "Web",
        "description": "Estimate household emissions based on travel, energy use, and consumption.",
        "featureList": [
          "Travel emissions calculator",
          "Electricity and gas inputs",
          "Downloadable footprint report"
        ],
        "provider": { "@type": "Organization", "name": "Northwind Climate" }
      },
      {
        "@context": "https://schema.org",
        "@type": "FAQPage",
        "mainEntity": [
          {
            "@type": "Question",
            "name": "What data do I need?",
            "acceptedAnswer": {
              "@type": "Answer",
              "text": "Provide annual mileage, energy bills, and approximate household size for the most accurate estimate."
            }
          },
          {
            "@type": "Question",
            "name": "How are emissions calculated?",
            "acceptedAnswer": {
              "@type": "Answer",
              "text": "We apply regional emissions factors based on your location and input values."
            }
          },
          {
            "@type": "Question",
            "name": "Do you store my inputs?",
            "acceptedAnswer": {
              "@type": "Answer",
              "text": "No. Inputs are processed in your session unless you opt in to save results."
            }
          }
        ]
      },
      {
        "@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": "Carbon Calculator", "item": "https://www.example.com/tools/carbon-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

    Should I include regional emissions factors?

    Yes. Mention regional factors or defaults in the page copy so users understand assumptions.

    Can I link to methodology details?

    Yes. Link to a methodology page and keep the FAQ aligned with the calculations used.

    Primary sources

    References