SwiftSchemaGenerate
    Schema stack

    Insurance Claim Submission Stack

    Claims intake portals with Service + WebApplication context, FAQs, and breadcrumb navigation.

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

    When to use this stack

    • Insurance claim submission portals
    • Claims intake pages for auto/home/health insurance
    • Pages where FAQs clarify documentation and timelines
    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
    • areaServed.name
    • itemListElement[].name
    • mainEntity[].@type=Question
    • mainEntity[].acceptedAnswer.text
    • name
    • operatingSystem
    • provider.name
    • url

    Recommended properties

    • description
    • itemListElement[].item
    • mainEntity[].acceptedAnswer.text
    • mainEntity[].author.name
    • mainEntity[].name
    • offers.price
    • offers.priceCurrency
    • offers.url
    • serviceType
    • 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": "Service",
    "@id": "https://www.example.com/insurance/auto#service",
    "name": "Auto Insurance Claims",
    "serviceType": "Auto Insurance",
    "provider": { "@type": "Organization", "name": "Example Insurance Co." },
    "areaServed": { "@type": "AdministrativeArea", "name": "US" },
    "offers": {
      "@type": "Offer",
      "price": "0.00",
      "priceCurrency": "USD",
      "url": "https://www.example.com/insurance/auto/claims"
    }
  },
  {
    "@context": "https://schema.org",
    "@type": "WebApplication",
    "@id": "https://www.example.com/insurance/auto/claims#app",
    "name": "Auto Claim Submission Portal",
    "description": "Submit and track auto insurance claims online.",
    "applicationCategory": "FinanceApplication",
    "operatingSystem": "Any",
    "url": "https://www.example.com/insurance/auto/claims",
    "offers": {
      "@type": "Offer",
      "url": "https://www.example.com/insurance/auto/claims"
    }
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "What documents do I need?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Provide photos of the damage, a police report if applicable, and your policy number."
        }
      },
      {
        "@type": "Question",
        "name": "How long does processing take?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Most claims are reviewed within 3-5 business days after submission."
        }
      },
      {
        "@type": "Question",
        "name": "Can I update my claim later?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes. You can upload additional documents from your claim dashboard."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Insurance", "item": "https://www.example.com/insurance" },
      { "@type": "ListItem", "position": 3, "name": "Submit Claim", "item": "https://www.example.com/insurance/auto/claims" }
    ]
  }
]
    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 multiple claim types?

    If the page supports multiple claim types, add a Service entry for each line of coverage.

    Can the portal link to a third-party system?

    Yes. Keep the WebApplication URL on your page and link out in offers.url if needed.

    Primary sources

    References