Organizations › Services › InsuranceAgency

Homepage Blueprint — Insurance Agency

The homepage is the identity anchor for an insurance agency website. It tells AI systems who the agency is, what lines of coverage it offers, where it operates, and how clients can reach it. This blueprint provides the complete JSON-LD graph your homepage needs so AI can classify, cite, and recommend your agency with confidence.

View Prompt View JSON

What this page needs

The homepage is the single most important page for AI discoverability. It is where AI systems look first to understand who your agency is and whether it is worth recommending to someone shopping for insurance. Every other page on the site inherits credibility from what the homepage declares. Without structured data here, AI may index deeper pages but still lack the identity anchor needed to surface your agency.

InsuranceAgency identity. The InsuranceAgency node declares your agency's name, logo, address, contact information, founding date, and social profiles. This is the canonical record AI uses to identify your business across the web.
WebSite declaration. The WebSite node anchors your entire site graph. It gives AI a root-level reference that every other page can point back to with isPartOf.
Search action for sitelinks. A SearchAction inside potentialAction tells search engines and AI systems that your site has internal search, which can trigger a sitelinks search box in results.
Service overview. The WebPage node with an about reference to the InsuranceAgency connects the homepage to the entity it represents, closing the loop between the page and the business.

Why these fields matter to AI

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

InsuranceAgency

name: Non-negotiable. AI cannot cite or recommend an unnamed entity.
url: AI needs a stable URL to attribute recommendations and route users correctly.
telephone: AI won't recommend a business it can't confirm is reachable. Phone is the primary trust signal for service businesses.
email: Secondary contact signal. Supports AI responses to queries about how to reach the business.
address: AI needs a verifiable address before recommending local services. Used for coverage zone inference and location-based queries.
geo: AI uses coordinates to confirm service coverage and answer location-specific queries. Without geo, AI guesses your location from address alone.
areaServed: AI filters service recommendations by coverage zone. Without this, AI may recommend you for queries outside your area or exclude you from local queries.
sameAs: AI cross-references sameAs links to confirm the business exists outside its own domain. One link minimum.
logo: Visual identity signal. AI uses logo presence to assess institutional legitimacy before recommending a service.
contactPoint: AI needs a customer service path before recommending a service from an unfamiliar provider.

WebSite

@id: All other schema nodes reference this ID. Without it the graph is disconnected and AI sees isolated, unrelated data.

Use This Prompt to Implement Your Schema

Copy 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 Homepage 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 description
2. Agency name
3. City
4. Company
5. Domain
6. Email
7. Employee count
8. Faq answer
9. Faq question
10. Founding year
11. Homepage title
12. Latitude
13. Logo
14. Longitude
15. Maps cid
16. Page
17. Phone number
18. Primary state
19. Site name
20. State
21. Street address
22. 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 Homepage"
- 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

Template — fill in your values

Copy the template below and replace every YOUR_* value with your own data. This block belongs in a <script type="application/ld+json"> tag in the <head> of your homepage.

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "InsuranceAgency",
      "@id": "https://YOUR_DOMAIN.com/#organization",
      "name": "YOUR_AGENCY_NAME",
      "url": "https://YOUR_DOMAIN.com",
      "logo": "https://YOUR_DOMAIN.com/YOUR_LOGO.png",
      "email": "YOUR_EMAIL",
      "telephone": "YOUR_PHONE_NUMBER",
      "description": "YOUR_AGENCY_DESCRIPTION",
      "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"
      },
      "areaServed": [
        {
          "@type": "State",
          "name": "YOUR_PRIMARY_STATE"
        }
      ],
      "sameAs": [
        "https://www.linkedin.com/company/YOUR_COMPANY",
        "https://www.facebook.com/YOUR_PAGE",
        "https://www.google.com/maps?cid=YOUR_MAPS_CID"
      ],
      "contactPoint": {
        "@type": "ContactPoint",
        "telephone": "YOUR_PHONE_NUMBER",
        "email": "YOUR_EMAIL",
        "contactType": "customer support"
      },
      "foundingDate": "YOUR_FOUNDING_YEAR",
      "numberOfEmployees": {
        "@type": "QuantitativeValue",
        "value": "YOUR_EMPLOYEE_COUNT"
      }
    },
    {
      "@type": "WebSite",
      "@id": "https://YOUR_DOMAIN.com/#website",
      "name": "YOUR_SITE_NAME",
      "url": "https://YOUR_DOMAIN.com",
      "potentialAction": {
        "@type": "SearchAction",
        "target": "https://YOUR_DOMAIN.com/?s={search_term_string}",
        "query-input": "required name=search_term_string"
      }
    },
    {
      "@type": "WebPage",
      "@id": "https://YOUR_DOMAIN.com/#webpage",
      "url": "https://YOUR_DOMAIN.com/",
      "name": "YOUR_HOMEPAGE_TITLE",
      "isPartOf": {
        "@id": "https://YOUR_DOMAIN.com/#website"
      },
      "about": {
        "@id": "https://YOUR_DOMAIN.com/#organization"
      }
    },
    {
      "@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"
          }
        }
      ]
    }
  ]
}

Frequently asked questions

Why use InsuranceAgency instead of a generic Organization type?

Schema.org defines InsuranceAgency as a specific subtype of FinancialService and LocalBusiness. Using it tells AI exactly what kind of business you are, which means you show up for insurance-related queries instead of being lumped into generic service results. The more precise your type, the better AI can match you to the right questions.

Do I need the SearchAction if my site does not have search?

No. The SearchAction inside potentialAction is only useful if your site has a working internal search. If it does not, remove the entire potentialAction block. Including a broken search URL can hurt rather than help.

Should I list every state I am licensed in under areaServed?

List the states where you actively write policies and want to be recommended. If you are licensed in 20 states but primarily serve three, list those three. AI uses areaServed to decide whether your agency is relevant to a user's location, so precision matters more than completeness.