SwiftSchemaGenerate
    Schema stack

    Travel Insurance Claim Stack

    Travel insurance claim submission pages with WebApplication + Service context, FAQs, and breadcrumbs.

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

    When to use this stack

    • Online travel insurance claim submission portals
    • Claim intake pages for trip interruption or cancellation
    • Insurance claim pages with upload instructions and FAQs
    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
    • serviceType
    • url

    Recommended properties

    • description
    • itemListElement[].item
    • mainEntity[].acceptedAnswer.text
    • mainEntity[].author.name
    • mainEntity[].name
    • offers.url
    • softwareVersion
    • url
    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/insurance/claims/travel#app",
    "name": "Travel Insurance Claim Portal",
    "description": "Submit travel insurance claims and upload supporting documents.",
    "applicationCategory": "InsuranceApplication",
    "operatingSystem": "Any",
    "url": "https://www.example.com/insurance/claims/travel"
  },
  {
    "@context": "https://schema.org",
    "@type": "Service",
    "@id": "https://www.example.com/insurance/claims#service",
    "name": "Travel Insurance Claim Submission",
    "serviceType": "InsuranceClaim",
    "provider": { "@type": "Organization", "name": "Northwind Travel Insurance" },
    "areaServed": { "@type": "Country", "name": "United States" },
    "description": "Submit claims for trip cancellation, delays, and medical expenses.",
    "url": "https://www.example.com/insurance/claims/travel"
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "What documents do I need?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Provide receipts, booking confirmations, and any medical documentation tied to the claim."
        }
      },
      {
        "@type": "Question",
        "name": "How long does processing take?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Most claims are reviewed within 10 to 15 business days."
        }
      },
      {
        "@type": "Question",
        "name": "Can I upload documents later?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes. You can return to the portal to upload additional documents at any time."
        }
      }
    ]
  },
  {
    "@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": "Claims", "item": "https://www.example.com/insurance/claims" },
      { "@type": "ListItem", "position": 4, "name": "Travel Claim", "item": "https://www.example.com/insurance/claims/travel" }
    ]
  }
]
    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 claim status links?

    If the page links to a claim status portal, reference it in the WebApplication description or FAQ answers.

    How do I show required timelines?

    Add timeline rules to the FAQ answers and match any filing deadlines shown on the page.

    Primary sources

    References