central-insurance.com — AI Site Grade

Analysis

Central Insurance: A 149-Year-Old Mutual with No AI Surface

The main site (central-insurance.com) has zero JSON-LD schema on any page — no Organization, InsuranceProduct, FAQPage, or LocalBusiness markup — despite being a $2B+ mutual insurer operating in 25 states since 1876.

Crawler Access

All major AI crawlers — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Bytespider, Applebot-Extended — receive 200 status with identical byte payloads as a browser. The site runs on Microsoft-IIS/10.0 with ASP.NET, no CDN or WAF layer. The robots.txt contains a single User-agent: * block with 30+ disallow paths (internal portals like /centralconnect/, /vpn/, /CentralInSite/) but no AI-bot-specific rules at all. No llms.txt exists (404). No sitemap.xml exists (404). The blog lives on a separate subdomain (blog.central-insurance.com) with proper WordPress schema (Article, WebSite, Organization, BreadcrumbList), but the main corporate domain has no discoverable URL index — no sitemap, no XML feed, no structured path listing.

Cold-Knowledge Gap

The LLM prior knows Central Insurance as a "regional" carrier based in Van Wert, Ohio, founded 1876, A+ rated by A.M. Best, policyholder-owned mutual. The actual site says "A" Excellent (not A+), describes operations in 25 states with regional offices in Boston, Atlanta, Dallas, Columbus, and Salt Lake City — a national footprint the model understates. The site also reveals a mutual holding company restructuring in the 2020s (detailed in the 150th-anniversary blog post), a structural change the cold model knows nothing about. The blog is actively publishing (February 2026 post about the 150th anniversary), but the main site's content pages carry no publication dates and no dateModified metadata.

Schema Posture

The main domain is a schema desert. The homepage, about page, product pages (home, auto, business), claims page, history page, awards page, and culture page all return zero JSON-LD blocks and zero schema.org types. No Organization schema with logo, social profiles, or A.M. Best rating. No Product or InsuranceProduct schema for the three policy tiers (Standard, Signature, Summit). No FAQPage despite detailed coverage descriptions that are inherently Q&A-shaped. The blog subdomain has proper schema but is not linked from the main site's schema graph — the main site has no schema at all to link from.

External Signals

The site has near-zero external discoverability in search results. DuckDuckGo returned zero results for multiple queries targeting the brand name, domain, and location. The DNS TXT records show verification tokens for Anthropic, Apple, Google, Atlassian, OneTrust, and Dynatrace — indicating the organization actively manages vendor integrations — but none of this verification translates into AI-visible content structure. The blog carries social profile links (Facebook, X, LinkedIn, Instagram, YouTube, Threads) but the main site has no sameAs schema to connect them.

Findings

1. Zero JSON-LD schema on any main domain page High

   No page on central-insurance.com contains any JSON-LD structured data. Missing Organization, InsuranceProduct, LocalBusiness, FAQPage, and other schema types that would help AI models understand the company's identity, products, and content.

   What to change: Add JSON-LD schema for Organization, InsuranceProduct, LocalBusiness, and FAQPage to all relevant pages. Include A.M. Best rating, social profiles, and product tiers.

2. No sitemap.xml or URL index exists High

   The site returns a 404 for sitemap.xml and has no XML feed or structured path listing. This prevents crawlers from discovering the full site structure efficiently.

   What to change: Generate and submit a sitemap.xml listing all public pages, and reference it in robots.txt.

3. No llms.txt file for AI crawler guidance Medium

   The site returns a 404 for llms.txt, missing an opportunity to provide AI crawlers with a curated summary and link list.

   What to change: Create an llms.txt file with a brief company description and links to key pages.

4. LLM prior knowledge understates company scale and structure Medium

   The cold LLM knowledge describes Central Insurance as a 'regional' carrier with A+ rating, but the site states 'A' Excellent rating, operations in 25 states with five regional offices, and a mutual holding company restructuring in the 2020s. This mismatch reduces the accuracy of AI-generated summaries.

   What to change: Add Organization schema with accurate rating, number of states, regional offices, and corporate structure details.

5. Main site content pages lack publication dates Low

   Pages like about, history, and awards have no visible publication or modification dates, reducing trust signals for AI crawlers that value freshness.

   What to change: Add datePublished and dateModified metadata in JSON-LD or visible page elements.

6. Near-zero external search discoverability High

   Multiple web searches for the brand name, domain, and location returned zero results on DuckDuckGo, indicating the site is not indexed or has very low visibility in search engines.

   What to change: Improve SEO fundamentals: ensure pages are indexed, build backlinks, and submit sitemap to search engines.

7. No sameAs schema linking social profiles Medium

   The main site has no sameAs schema to connect its social media profiles (Facebook, X, LinkedIn, Instagram, YouTube, Threads), which are present on the blog subdomain but not linked via structured data.

   What to change: Add sameAs property to Organization schema with URLs of all social profiles.

8. Robots.txt has no AI-bot-specific rules Low

   The robots.txt file contains a single User-agent: * block with disallow paths for internal portals, but no explicit rules for AI crawlers like GPTBot or ClaudeBot. While this allows access, it misses the chance to guide AI crawlers to valuable content.

   What to change: Consider adding AI-bot-specific directives to prioritize crawling of key pages.

9. Blog subdomain not linked from main site schema Medium

   The blog at blog.central-insurance.com has proper schema but is not connected to the main domain via any schema link, creating a disjointed knowledge graph.

   What to change: Add a sameAs or relatedLink schema property on the main site pointing to the blog, and vice versa.

10. No InsuranceProduct schema for policy tiers Medium

    Product pages describe three policy tiers (Standard, Signature, Summit) but lack InsuranceProduct or Product schema, making it harder for AI to extract coverage details.

    What to change: Add InsuranceProduct schema for each policy tier with name, description, and coverage details.

What's working

• All major AI crawlers receive full access — All 11 tested AI crawlers (GPTBot, ClaudeBot, PerplexityBot, etc.) receive 200 status with identical content as browsers, with no blocking or rate-limiting.
• Blog subdomain has proper schema markup — The blog at blog.central-insurance.com includes Article, WebSite, Organization, and BreadcrumbList schema, providing structured data for AI crawlers.
• Blog actively publishes with fresh content — The blog has a February 2026 post about the 150th anniversary, indicating regular content updates that can attract AI crawlers.
• DNS TXT records show vendor integrations — TXT records include verification tokens for Anthropic, Apple, Google, Atlassian, OneTrust, and Dynatrace, indicating active management of third-party services.
• No AI bots are blocked by robots.txt — The robots.txt does not disallow any AI crawlers, ensuring they can access all public content.