neilhuffman.com — AI Site Grade

Analysis

The tool truncates at 3223 bytes. I have enough data now. Let me compile the audit.

Here's what I know:

1. The site is completely blocked to browsers and most AI bots by Akamai — returns 403 for every UA except anthropic-ai which gets a 200 with full content (413KB). This is an extreme whitelist/blacklist configuration.

2. The robots.txt exists but is only accessible to anthropic-ai (everyone else gets 403). It has specific rules for GPTBot, OAI-SearchBot, ChatGPT-User, Claude-User, Claude-SearchBot, PerplexityBot, etc. — all disallow /*.js, /*.css, /*.json, /api/, /apis/, /pixall/, */pixall/. Notably, there's no Disallow: / for any AI bot — they're allowed to crawl the site content.

3. No llms.txt — returns 403 to all UAs.

4. The site is a multi-franchise auto group (Acura, Honda, Mazda, Chevrolet, Subaru, Nissan, Volkswagen, GMC) based in Louisville, KY, founded in 1969. The Wayback snapshot shows rich content: AutoDealer schema with reviews, address, brands, geo coordinates.

5. Cold LLM knowledge is zero — the model knows nothing about Neil Huffman.

6. No external search results — DuckDuckGo returns zero results for any query about the brand or domain.

7. The sitemap has ~300KB of URLs with lastmod dates of 2026-05-30 (future date, likely a placeholder).

8. The site runs on dealer.com (DDC platform) behind Akamai CDN.

Let me write the audit.

Neil Huffman Auto Group — AI-Visibility Audit

The site is entirely invisible to every AI crawler except Anthropic's, despite having a well-structured AutoDealer schema and rich content that would serve AI answers well.

Crawler Access

The Akamai WAF at neilhuffman.com returns 403 to every User-Agent except anthropic-ai, which receives a full 200 with 413KB of HTML. GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, PerplexityBot, Google-Extended, and even a standard browser all get blocked at the edge. The robots.txt is also 403'd to all non-Anthropic UAs, meaning most AI crawlers cannot even read the crawl rules. The robots.txt that does exist (visible only to anthropic-ai) contains permissive rules for AI bots — no Disallow: / — but the Akamai layer overrides those permissions with a blanket block. No llms.txt exists (403 to all).

Cold-Knowledge Gap

A frontier LLM queried cold about "Neil Huffman" returns zero knowledge — no awareness of the brand, its 50+ year history, its eight franchise brands, or its Louisville presence. This is a complete knowledge vacuum despite the site having been online since at least 2015 (Wayback Machine confirms snapshots back to 2015). The site's content — a multi-franchise auto group founded in 1969 with Acura, Chevrolet, GMC, Honda, Mazda, Nissan, Subaru, and Volkswagen — is entirely absent from the model's training data.

Schema Posture

The homepage carries a well-formed AutoDealer JSON-LD schema with address (4926 Dixie Hwy, Louisville, KY 40216), telephone, geo coordinates, eight brand entries, area served (Louisville, Clarksville, Frankfort, Lexington, Jeffersontown), and embedded customer reviews with 5-star ratings. This is strong structured data that would power rich AI answers — but no AI engine besides Anthropic can access it to index it.

External Signals

DuckDuckGo returns zero indexed results for neilhuffman.com, "Neil Huffman Auto Group", or any variant. The domain has no visible external mentions, reviews on third-party sites, Reddit threads, or press coverage surfaced by search. The only accessible record is the Wayback Machine snapshot from January 2025, which shows the site was fully functional with inventory, service scheduling, and testimonials. The DNS resolves to dealer.com infrastructure behind Akamai, and the site uses Barracuda email security — a standard automotive dealer tech stack that appears to have locked down access too aggressively.

Findings

1. Akamai WAF blocks all AI crawlers except Anthropic High

   The Akamai WAF at neilhuffman.com returns 403 to every User-Agent except anthropic-ai, which receives a full 200 response. GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, PerplexityBot, Google-Extended, and standard browsers are all blocked at the edge.

   What to change: Reconfigure the Akamai WAF to allow access for major AI crawler User-Agents (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, PerplexityBot, Google-Extended) to the site's content.

2. robots.txt inaccessible to most AI crawlers High

   The robots.txt file returns 403 to all User-Agents except anthropic-ai, preventing most AI crawlers from reading crawl rules. The file that is visible to anthropic-ai contains permissive rules (no Disallow: /), but the Akamai layer overrides those permissions.

   What to change: Ensure robots.txt is publicly accessible (200) to all User-Agents, and include clear rules for AI crawlers.

3. No llms.txt file published Medium

   The site does not serve an llms.txt file; requests return 403 to all User-Agents. This file would help AI crawlers discover key pages and content.

   What to change: Create and publish an llms.txt file at the root listing important pages (homepage, inventory, about, service) and any AI-specific instructions.

4. Zero cold knowledge of Neil Huffman in LLMs High

   A frontier LLM queried cold about 'Neil Huffman' returns no information about the brand, its 50+ year history, eight franchise brands, or Louisville presence. The site's content is entirely absent from the model's training data.

   What to change: Improve AI visibility by allowing crawlers access and ensuring content is indexed; consider submitting to AI training data sources.

5. No search engine indexing for domain or brand High

   DuckDuckGo returns zero results for queries including 'neilhuffman.com', 'Neil Huffman Auto Group', or any variant. The domain has no visible external mentions, reviews, or press coverage surfaced by search.

   What to change: Investigate why the site is not indexed; ensure no robots.txt or meta noindex blocks search engines, and build external backlinks and citations.

6. Sitemap contains future lastmod dates Low

   The sitemap lists lastmod dates of 2026-05-30, which is a future date and likely a placeholder. This may confuse crawlers about content freshness.

   What to change: Update the sitemap with accurate lastmod dates reflecting actual content update times.

7. About page returns 404 Medium

   The about page at /about/index.htm returns a 404 error when accessed as anthropic-ai, indicating a broken link or missing content.

   What to change: Restore the about page or implement a redirect to a working page.

8. No external citations or backlinks found Medium

   Web searches for the brand and domain returned zero results, indicating no external mentions, reviews, or backlinks that could boost AI visibility.

   What to change: Build external citations through local business directories, press releases, and social media profiles.

What's working

• Well-formed AutoDealer JSON-LD schema on homepage — The homepage includes a comprehensive AutoDealer schema with address, telephone, geo coordinates, eight brand entries, area served, and embedded customer reviews with 5-star ratings. This structured data would power rich AI answers if accessible.
• Anthropic crawler receives full 200 response with rich content — The anthropic-ai User-Agent receives a 200 response with 413KB of HTML, including inventory, service, and dealership information. This means Anthropic's models can index the site's content.
• Permissive robots.txt rules for AI bots (no Disallow: /) — The robots.txt file (visible to anthropic-ai) does not disallow any AI bot from crawling the site's content, only blocking static assets and API endpoints. This is a favorable starting point for AI access.
• Large sitemap with many URLs — The sitemap contains approximately 300KB of URLs, indicating a comprehensive listing of pages including inventory, service, and other sections. This helps crawlers discover content.
• Rich content including inventory and service pages — The site has detailed inventory and service pages with substantial HTML content (300KB+ each), providing valuable information for AI models.
• Staff page accessible with contact information — The staff page at /dealership/staff.htm returns 200 with 276KB of content, providing team member details that could be used for AI answers.