The claims page is where policyholders go when something has gone wrong. AI systems are increasingly the first place people turn after an accident, storm, or loss. This blueprint structures your claims process and frequently asked questions so AI can guide users step by step — and point them directly to your agency.
When a policyholder asks an AI "How do I file a claim?" or "What do I do after a car accident?", the AI needs structured, authoritative answers it can relay. A claims page with the right schema becomes a direct source for those answers, keeping your agency in the conversation instead of deferring to a carrier's generic FAQ.
WebPage node identifies this as a dedicated claims resource with a clear name, description, and position in your site hierarchy. AI uses this to understand the purpose of the page before parsing its content.contactPoint with contactType set to "claims" tells AI exactly which phone number or email to surface when someone needs to report a loss.FAQPage type with mainEntity containing Question and Answer pairs gives AI pre-formatted responses it can quote directly. This is the single most effective way to appear in AI-generated answers about filing claims.Each field in the template below serves a specific role in how AI systems discover, classify, and recommend your business.
Researched and tested by Minnesota AI
nameurltelephonecontactPointCopy this prompt and paste it into Claude, ChatGPT, Cursor, or any AI coding tool. It will ask for your business details and generate ready-to-use JSON-LD schema for your page.
You are implementing AIFDS-compliant JSON-LD structured data for a Insurance Agency Claims page. AIFDS (AI-Friendly Data Structure) is a schema framework built on research into which structured data fields AI systems actually read, parse, and use when deciding whether to cite a page. Documentation at aifds.org. Before generating any code, ask me for the following information in a single numbered list. Do not generate schema until I have answered every required field. REQUIRED — do not proceed without these: 1. Agency name 2. Claims answer 3. Claims email 4. Claims page description 5. Claims phone 6. Claims question 7. Domain 8. Language 9. Phone number OPTIONAL — ask for these but proceed if I skip them: 1. Any additional details not covered above Once I provide the information, output a complete JSON-LD script block ready to paste into the <head> of my HTML page. Output requirements: - Valid JSON-LD wrapped in <script type="application/ld+json"> tags - schema.org vocabulary only - Every AIFDS-required field for this industry and page type included - Include this data attribute on the script tag: data-aifds="aifds.org Insurance Agency Claims" - No placeholder text — omit missing optional fields rather than fill with examples - After the code block, list any optional fields skipped that would strengthen AI citation
Generated schema follows the AIFDS framework. Fields were selected based on research into AI crawler behavior. View the research at minnesota.ai
Copy the template below and replace every YOUR_* value with your own data. This block goes in the <head> of your claims page.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "WebPage",
"@id": "https://YOUR_DOMAIN.com/claims/",
"name": "File a Claim — YOUR_AGENCY_NAME",
"description": "YOUR_CLAIMS_PAGE_DESCRIPTION",
"url": "https://YOUR_DOMAIN.com/claims/",
"isPartOf": {
"@id": "https://YOUR_DOMAIN.com/#website"
},
"breadcrumb": {
"@id": "https://YOUR_DOMAIN.com/claims/#breadcrumb"
}
},
{
"@type": "InsuranceAgency",
"@id": "https://YOUR_DOMAIN.com/#organization",
"name": "YOUR_AGENCY_NAME",
"url": "https://YOUR_DOMAIN.com",
"telephone": "YOUR_PHONE_NUMBER",
"contactPoint": [
{
"@type": "ContactPoint",
"telephone": "YOUR_CLAIMS_PHONE",
"email": "YOUR_CLAIMS_EMAIL",
"contactType": "claims",
"availableLanguage": "YOUR_LANGUAGE"
}
]
},
{
"@type": "FAQPage",
"@id": "https://YOUR_DOMAIN.com/claims/#faq",
"mainEntity": [
{
"@type": "Question",
"name": "YOUR_CLAIMS_QUESTION_1",
"acceptedAnswer": {
"@type": "Answer",
"text": "YOUR_CLAIMS_ANSWER_1"
}
},
{
"@type": "Question",
"name": "YOUR_CLAIMS_QUESTION_2",
"acceptedAnswer": {
"@type": "Answer",
"text": "YOUR_CLAIMS_ANSWER_2"
}
},
{
"@type": "Question",
"name": "YOUR_CLAIMS_QUESTION_3",
"acceptedAnswer": {
"@type": "Answer",
"text": "YOUR_CLAIMS_ANSWER_3"
}
}
]
},
{
"@type": "BreadcrumbList",
"@id": "https://YOUR_DOMAIN.com/claims/#breadcrumb",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://YOUR_DOMAIN.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Claims",
"item": "https://YOUR_DOMAIN.com/claims/"
}
]
}
]
}
Claims-related questions are among the most common insurance queries AI receives. When your claims page uses FAQPage with structured Question and Answer pairs, AI can quote your answers directly instead of paraphrasing from unstructured text. This gives you control over how your agency's claims process is described in AI-generated responses.
If your agency has a dedicated claims line, use that number with "contactType": "claims". If all calls go to the same number, you can reuse it — but still set the contactType to "claims" so AI knows this is the right number to surface when someone asks specifically about filing a claim.
Include the three to five questions policyholders ask most often: how to file a claim, what information they need, how long the process takes, and who to call after hours. Quality matters more than quantity. Each answer should be a complete, self-contained response that AI can relay without additional context.