Your contact page is where AI looks to confirm that your agency is reachable. This blueprint makes your phone number, email, mailing address, and office hours machine-readable so AI systems can surface you as a trustworthy, contactable insurance provider.
Reachability is a trust signal. When AI evaluates whether to recommend your agency, it checks whether a real person can actually get in touch. A contact page without structured data forces AI to guess from raw HTML — and guessing means your agency gets skipped in favor of one that made its contact information explicit.
ContactPage as the page type tells AI this is the canonical contact destination for your agency. It distinguishes this page from a generic web page that happens to mention a phone number.InsuranceAgency node carries telephone, email, and a full PostalAddress. AI uses these fields to display your contact information directly in answers without requiring a click-through.latitude and longitude inside a GeoCoordinates node remove all ambiguity about where your office is located on a map.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
nameurltelephoneemailaddressgeoopeningHoursSpecificationcontactPointCopy 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 Contact 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. City 3. Close time 4. Domain 5. Email 6. Faq answer 7. Faq question 8. Language 9. Latitude 10. Longitude 11. Open time 12. Phone number 13. State 14. Street address 15. Zip 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 Contact" - 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 contact page.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "ContactPage",
"@id": "https://YOUR_DOMAIN.com/contact/",
"name": "Contact — YOUR_AGENCY_NAME",
"url": "https://YOUR_DOMAIN.com/contact/",
"isPartOf": {
"@id": "https://YOUR_DOMAIN.com/#website"
},
"breadcrumb": {
"@id": "https://YOUR_DOMAIN.com/contact/#breadcrumb"
}
},
{
"@type": "InsuranceAgency",
"@id": "https://YOUR_DOMAIN.com/#organization",
"name": "YOUR_AGENCY_NAME",
"url": "https://YOUR_DOMAIN.com",
"telephone": "YOUR_PHONE_NUMBER",
"email": "YOUR_EMAIL",
"address": {
"@type": "PostalAddress",
"streetAddress": "YOUR_STREET_ADDRESS",
"addressLocality": "YOUR_CITY",
"addressRegion": "YOUR_STATE",
"postalCode": "YOUR_ZIP",
"addressCountry": "US"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": "YOUR_LATITUDE",
"longitude": "YOUR_LONGITUDE"
},
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
"opens": "YOUR_OPEN_TIME",
"closes": "YOUR_CLOSE_TIME"
}
],
"contactPoint": {
"@type": "ContactPoint",
"telephone": "YOUR_PHONE_NUMBER",
"email": "YOUR_EMAIL",
"contactType": "customer support",
"availableLanguage": "YOUR_LANGUAGE"
}
},
{
"@type": "BreadcrumbList",
"@id": "https://YOUR_DOMAIN.com/contact/#breadcrumb",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://YOUR_DOMAIN.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Contact",
"item": "https://YOUR_DOMAIN.com/contact/"
}
]
},
{
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "YOUR_FAQ_QUESTION_1",
"acceptedAnswer": {
"@type": "Answer",
"text": "YOUR_FAQ_ANSWER_1"
}
},
{
"@type": "Question",
"name": "YOUR_FAQ_QUESTION_2",
"acceptedAnswer": {
"@type": "Answer",
"text": "YOUR_FAQ_ANSWER_2"
}
},
{
"@type": "Question",
"name": "YOUR_FAQ_QUESTION_3",
"acceptedAnswer": {
"@type": "Answer",
"text": "YOUR_FAQ_ANSWER_3"
}
}
]
}
]
}
Yes. AI crawlers do not always combine data across pages. The contact page should carry its own ContactPage and InsuranceAgency nodes so the reachability signals are self-contained on the page where a user — or an AI — expects to find them.
Include them if you have a registered office address. If your agency is fully virtual with no physical location, omit the geo node rather than using a fake coordinate. AI systems treat missing data as unknown, but incorrect coordinates actively mislead.
Create a separate contact page for each location, each with its own InsuranceAgency node containing that office's specific address, phone, hours, and coordinates. If you only have one contact page, list the primary office and use sameAs or subOrganization to reference branches.