GEO for Insurance

TL;DR

Insurance is a YMYL vertical regulated state by state, so AI engines apply higher authority bars before citing. The six highest-use moves are: (1) licensed authors with Person schema and visible state license / NPN numbers, (2) an explicit state and product taxonomy (auto, home, life, disability, umbrella), (3) InsuranceAgency plus Service and FAQPage schema, (4) claims-process and head-to-head comparison content tuned to AI query patterns, (5) NAIC- and state-DOI-aligned disclosures. (6) a regulatory review cadence keyed to state filing windows.

Why insurance is a regulated YMYL vertical

Insurance is regulated primarily at the state level in the US, coordinated through the National Association of Insurance Commissioners (NAIC). Producers (agents and brokers) carry state-issued licenses tracked via NPN identifiers, and product availability and pricing vary by state filing.

For GEO, that creates four pressures:

• AI engines preferentially cite content that demonstrates licensure and jurisdictional accuracy.
• Generic, state-agnostic content gets out-cited by state-specific pages on local-intent queries.
• Misstating coverage, exclusions, or claim procedures creates real consumer harm — AI engines and reviewers heavily downweight imprecise insurance content.
• Compliance review is non-negotiable; advertising rules vary by state DOI.

The framework

1. Licensed authorship

For every consumer-facing insurance article, attach a real, licensed author or a clearly named licensed reviewer:

• Person schema with jobTitle, worksFor, and sameAs links to NIPR / state DOI lookups.
• Visible license display: NPN, resident state, license types (P&C, Life, Health), and expiration where shown.
• Bio block noting years licensed, lines of authority, and any CPCU, CLU, ChFC, or AAI designations.
• Compliance reviewer line for any rate, exclusion, or claim-procedure content.

Example (JSON-LD snippet, simplified):

{
"@type": "Person",
"name": "Author Name",
"jobTitle": "Licensed P&C Agent",
"identifier": {
"@type": "PropertyValue",
"propertyID": "NPN",
"value": "1234567"
},
"sameAs": [
"https://nipr.com/help/look-up-your-npn",
"https://www.linkedin.com/in/example"
]
}

Licensure is verifiable through public registries — that is the trust premise that AI engines and reviewers look for.

2. State and product taxonomy

Insurance content rarely earns citations without a clear taxonomy. Build out:

• One canonical hub per product line (auto, home, renters, life, disability, umbrella, business, health).
• One state-modifier page per state you write in (e.g. "California auto insurance", "Texas home insurance").
• One product-by-state matrix page for high-volume comparisons.
• Internal linking that ladders state pages up to the product hub and back to the section hub.

Avoid fake state coverage — only publish state pages where the carrier or broker is actually licensed.

3. Structured data layer

Use the most specific schema types your content supports:

• InsuranceAgency for the carrier or brokerage entity, with areaServed, hasCredential, and address.
• Service for each product line, with provider set to the agency and areaServed per state.
• FAQPage for question-led articles (claims, eligibility, policy mechanics).
• Article with author, reviewedBy, and lastReviewed.
• BreadcrumbList to make state-product hierarchy explicit.

Validate every JSON-LD block with the Rich Results Test before publishing.

4. Claims-process and comparison content

High-volume insurance queries fall into three buckets, each with a content shape:

• Mechanic queries ("how does umbrella insurance work") — long-form explainer with FAQPage schema and a glossary.
• Comparison queries ("term vs whole life", "HMO vs PPO") — head-to-head table with explicit pros, cons, and typical buyer profile.
• Procedural queries ("how to file a homeowners claim", "what to do after a car accident") — step-by-step with HowTo schema.

Each page should answer the query in the first 60-100 words, then expand. Avoid bait-and-switch lead-gen pages — AI engines deprioritise them quickly.

5. Disclosures and compliance language

NAIC and state DOI rules govern advertising language. Treat the following as table stakes:

• Producer identity at the top or bottom of every page (legal entity, NPN or license number, jurisdictions).
• No-guarantee language for rates and availability ("Coverage availability and pricing subject to state filing and underwriting").
• Plain-language disclaimers for product comparisons, with a clear "this is not a substitute for advice from a licensed agent".
• Affiliate / commission disclosures where applicable.
• State-specific addenda for any state with stricter advertising rules (e.g. CA, NY).

Make disclosures visible to humans and machines — plain text in the body, not hidden in a footer.

6. Regulatory review cadence

Insurance product detail changes with state filings. Run a quarterly review on top-cited pages:

• Cross-check rate ranges, exclusions, and underwriting against the latest filings.
• Verify that license numbers, NPN, and resident-state details are current.
• Bump dateModified and lastReviewed on substantive changes.
• Pull through any new NAIC model regulation language where adopted.

A 90-day cycle is the minimum for citation retention; tighter cycles (30-60 days) help on rate-sensitive pages.

Common AI query patterns to cover

Common mistakes

• Anonymous authors on rate, claim, or coverage detail pages. AI engines downweight; compliance flags possible.
• State-agnostic content competing on local-intent queries. Out-cited every cycle.
• Schema declared but not validated, or InsuranceAgency with missing areaServed.
• Stale rate ranges or expired filings. Citation churn at next refresh.
• Generic disclaimers that miss state DOI requirements (notably CA, NY, FL).
• Claim procedures that contradict the actual carrier handbook. Real consumer harm risk.

FAQ

Q: Do I need to display NPN on every page?

A: At minimum once per producer-facing page (a footer block is acceptable), and on any page that quotes coverage detail or rates. NPN display is one of the cheapest, highest-use trust signals for insurance GEO.

Q: Can I publish a state page if my carrier is not licensed there?

A: No. Publishing rate or product content for a state where the producer is not appointed is both an AI-citation liability and a compliance risk under most state DOI advertising rules.

Q: How fresh do rate references need to be?

A: Treat anything older than 12 months as suspect; 6 months is safer for rate-sensitive product lines (auto, home). Always pair rate language with a no-guarantee disclaimer and link to the live quote flow.

Q: Is InsuranceAgency enough, or do I also need Service?

A: Use both. InsuranceAgency describes the entity; Service describes each product line with its areaServed. Together they make the agency-product-state hierarchy explicit, which AI engines parse for state-modified queries.

Q: Does AI cite carrier sites or independent broker sites more?

A: It depends on the query. Mechanic and comparison queries skew toward independent or editorial sources; carrier-specific procedural queries (claims, account changes) skew toward the carrier site. Brokers should lean into mechanic, comparison, and "do I need" queries where independent stance is a citation advantage.