kahligauto.com — AI Site Grade

Analysis

I have enough data now. Let me compile the audit.

Kahlig Auto Group — AI-Visibility Audit

The site's ads page lists specials starting May 2026 — dates that are still in the future — suggesting the content management system has a systemic date-entry error or the page template is pulling placeholder dates, which would confuse any AI crawler trying to determine content freshness.

Crawler Access

Every major AI crawler — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Bytespider, Applebot-Extended, anthropic-ai, ChatGPT-User — receives a full 200 response with identical byte payload (~1.1 MB) to a browser baseline. The robots.txt uses a permissive User-agent: * Allow: / with no AI-specific disallow rules. No AI bot is blocked at the UA level. The site runs on nginx with HSTS and X-Frame-Options: SAMEORIGIN but no CSP. /llms.txt returns a 404 — the site has no AI-friendly content map. The sitemap index references four gzipped sub-sitemaps (static, vehicle, vehicle images), but the gzip payloads are binary and not parseable via plain GET, which may limit crawler discovery of individual vehicle pages.

Cold-Knowledge Gap

The LLM's cold knowledge describes Kahlig Auto Group as selling Ford, Chevrolet, Toyota, and Honda — a generic mass-market picture. The actual site reveals a dramatically different portfolio: Lincoln, Audi, Lexus, Volkswagen, Subaru, Mazda, Jeep, Chrysler, Dodge, Ram, and Toyota across 18+ branded dealership locations including a Rio Grande Valley Lexus store and a Bluebonnet Ford Lincoln in New Braunfels. The model misses the luxury/premium concentration (Lexus, Lincoln, Audi) and the group's geographic reach beyond San Antonio proper. The cold knowledge also says "family-owned for decades" — the site itself never states founding year or ownership history, so that claim has no on-site corroboration.

Schema Posture

Every page carries AutoDealer and AutomotiveBusiness JSON-LD schema, but the schema is identical across all pages — always pointing to "North Park Lincoln" at 9207 San Pedro Ave. as the sole AutoDealer entity, with the same geo coordinates and price range ($10,238–$101,402). The schema does not reflect the group's actual multi-brand, multi-location structure. A page about military discounts at a Subaru dealership still schema-declares itself as North Park Lincoln. No ItemList or Vehicle schema types appear on inventory pages, and no FAQPage or Product schema exists anywhere.

External Signals

The domain has no indexed external mentions in search results — no reviews, no Reddit threads, no press coverage surfaced. The Wayback Machine has no snapshots of the site. DNS records show Microsoft 365 mail (protection.outlook.com), Google site verification, and Apple domain verification, indicating standard enterprise hosting but no notable third-party content footprint that would feed AI training corpora.

Findings

1. Ads page lists specials starting May 2026 High

   The used car ads page displays specials with dates in the future (May 2026), suggesting a systemic date-entry error or placeholder dates that confuse AI crawlers assessing content freshness.

   What to change: Correct the date entries on the ads page to reflect actual current specials, and audit the CMS for placeholder date logic.

2. Identical AutoDealer schema on every page points only to North Park Lincoln High

   All pages carry the same JSON-LD AutoDealer schema referencing only North Park Lincoln at 9207 San Pedro Ave., ignoring the group's 18+ dealerships across multiple brands and locations.

   What to change: Implement per-dealership schema with distinct AutoDealer entities for each location, and add Vehicle schema on inventory pages.

3. No llms.txt file for AI crawlers Medium

   The site returns a 404 for /llms.txt, providing no AI-friendly content map or structured overview for large language models.

   What to change: Create an llms.txt file listing key pages and a brief site description to guide AI crawlers.

4. Inventory pages lack Vehicle or ItemList schema Medium

   The used vehicles page and other inventory pages do not include Vehicle or ItemList structured data, missing an opportunity to provide detailed vehicle attributes to AI crawlers.

   What to change: Add Vehicle schema with make, model, year, price, and mileage to each vehicle listing, and ItemList schema on inventory pages.

5. No indexed external mentions or reviews Medium

   Web searches for the brand, reviews, and dealership locations returned zero results, indicating no third-party content footprint that would feed AI training corpora.

   What to change: Encourage customer reviews on third-party platforms and pursue local press coverage to build external signals.

6. No Wayback Machine snapshots of the site Low

   The Wayback Machine has no archived snapshots of the domain, limiting historical context for AI crawlers and reducing trust signals.

7. Gzipped sitemaps may hinder crawler discovery Low

   The sitemap index references gzipped sub-sitemaps whose binary payloads are not parseable via plain GET, potentially limiting crawler discovery of individual vehicle pages.

   What to change: Ensure sitemaps are served uncompressed or with proper Content-Encoding headers so crawlers can parse them.

8. LLM cold knowledge misrepresents brand portfolio Medium

   The LLM's cold knowledge describes Kahlig Auto Group as selling Ford, Chevrolet, Toyota, and Honda, but the actual site shows Lincoln, Audi, Lexus, Volkswagen, Subaru, Mazda, Jeep, Chrysler, Dodge, Ram, and Toyota — missing the luxury/premium concentration and geographic reach.

   What to change: Publish a clear 'About Us' page listing all brands and locations, and consider submitting structured data to knowledge panels.

What's working

• All major AI crawlers allowed and served full content — Every major AI crawler receives a 200 response with full page content; robots.txt has no AI-specific disallow rules.
• JSON-LD AutoDealer schema present on all pages — Every page includes AutoDealer and AutomotiveBusiness schema, providing a baseline of structured data.
• Sitemap index with multiple sub-sitemaps — The site has a sitemap index referencing static, vehicle, and vehicle image sitemaps, aiding crawler discovery.
• HSTS and X-Frame-Options headers set — The site uses HSTS and X-Frame-Options: SAMEORIGIN, providing basic security posture.