AI Site Grade

principleauto.com — AI Site Grade

Principle Auto's Akamai WAF blocks every AI crawler except anthropic-ai, leaving the site invisible to search engines and AI retrieval bots.

Principle Auto's website is blocked by Akamai for all crawlers except anthropic-ai, has no search engine presence, and lacks server-side schema markup.

Findings
10
Evidence checks
48
Completed
30 May 2026

Analysis

The Akamai Wall That Only Lets Claude Through

Principle Auto Group's website at www.principleauto.com returns a 403 Access Denied to every browser and every major AI crawler tested — GPTBot, Google-Extended, PerplexityBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, and Applebot-Extended all hit the same Akamai block. The sole exception is anthropic-ai, which receives a 200 with 316KB of full HTML served from an nginx backend. This creates a bizarre asymmetry: Anthropic's training crawler can read the site in full, but ClaudeBot (the real-time retrieval bot) cannot.

Crawler Access

The robots.txt explicitly disallows GPTBot, OAI-SearchBot, ChatGPT-User, Claude-User, Claude-SearchBot, and PerplexityBot from accessing JS, CSS, JSON, and API paths — though the Akamai WAF makes those rules moot since all those bots are already blocked at the edge. No llms.txt file exists (returns connection refused). The sitemap.xml is accessible only to anthropic-ai and contains ~350 URLs with lastmod dates of 2026-05-30 (a future date), suggesting a CMS misconfiguration rather than actual freshness signals. The site runs on the DDC (Dealer.com) platform, a JS-heavy automotive CMS where visible text content is minimal in raw HTML — most content renders client-side.

Cold-Knowledge Gap

The LLM model knows Principle Auto as a privately held dealership group founded in 2005 by brothers Chris and Cary Prinster, operating Toyota, Honda, Nissan, Hyundai, and Kia franchises across Texas, Florida, and Tennessee. It also recalls a 2023 class-action lawsuit alleging deceptive add-on product fees. The actual website tells a different story: the homepage title lists INFINITI, Volkswagen, Volvo, MINI, Toyota, BMW, and Hyundai — no mention of Honda, Nissan, or Kia, and no reference to the Prinster brothers, the company's founding story, or any locations outside San Antonio. The site presents itself as a single multi-franchise dealership in San Antonio, TX, not a multi-state group. The about page (/about/index.htm) returns a 404 error, meaning the company's own origin story is inaccessible.

Schema Posture

The homepage HTML contains no JSON-LD schema in the raw server-rendered output. The DDC platform injects structured data client-side via JavaScript, meaning crawlers that cannot execute JS — including most AI training bots — see zero schema markup. No AutoDealer, Organization, or LocalBusiness schema is present in the initial HTML payload. The meta description tag is also absent from the homepage.

External Signals

Web search returns zero indexed results for principleauto.com, "Principle Auto", or any combination of the brand name with "San Antonio" or "dealership". The site has no visible presence in search engine indexes — likely a consequence of the Akamai WAF blocking Googlebot (confirmed: Google-Extended gets a 403). The class-action lawsuit that the LLM model knows about is entirely absent from the site's content and from search results, suggesting the brand's external reputation is shaped by sources the company does not control and cannot influence through its own web presence.

Findings

  1. Akamai WAF blocks all AI crawlers except anthropic-ai High

    The site returns 403 Access Denied to GPTBot, Google-Extended, PerplexityBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, and Applebot-Extended. Only anthropic-ai receives a 200 response with full HTML.

    What to change: Reconfigure the Akamai WAF to allow major AI crawlers (GPTBot, Google-Extended, ClaudeBot, etc.) to access the site, or serve a static HTML version to bots.

  2. Zero search engine indexed pages High

    Web searches for principleauto.com, 'Principle Auto', and related terms return zero results. The site has no presence in search engine indexes, likely due to the WAF blocking Googlebot.

    What to change: Allow Googlebot and other search engine crawlers through the WAF, and submit the sitemap to Google Search Console.

  3. No JSON-LD schema in server-rendered HTML High

    The homepage HTML contains no JSON-LD structured data. The DDC platform injects schema client-side via JavaScript, which is invisible to crawlers that do not execute JS.

    What to change: Include JSON-LD schema (AutoDealer, Organization, LocalBusiness) in the server-rendered HTML for all pages.

  4. About page returns 404 error Medium

    The /about/index.htm page returns a 404, making the company's origin story and background inaccessible to visitors and crawlers.

    What to change: Restore the about page with accurate company information, including founding story, leadership, and locations.

  5. Sitemap contains future lastmod dates Medium

    The sitemap.xml lists lastmod dates of 2026-05-30, indicating a CMS misconfiguration that undermines freshness signals for crawlers.

    What to change: Correct the CMS date configuration to output accurate lastmod dates.

  6. Homepage missing meta description tag Low

    The homepage HTML does not include a meta description tag, reducing click-through potential in search results.

    What to change: Add a descriptive meta description tag to the homepage.

  7. No llms.txt file available Low

    The llms.txt file is not accessible (connection refused), missing an opportunity to guide AI crawlers to key content.

    What to change: Create an llms.txt file at the root domain listing important pages for AI crawlers.

  8. JS-heavy content invisible to non-JS crawlers Medium

    The DDC platform renders most content client-side, so crawlers that do not execute JavaScript see minimal text content.

    What to change: Implement server-side rendering or pre-rendering for key pages to ensure content is available in the initial HTML.

  9. Robots.txt disallows multiple AI bots from JS/CSS paths Low

    Robots.txt explicitly disallows GPTBot, OAI-SearchBot, ChatGPT-User, Claude-User, Claude-SearchBot, and PerplexityBot from accessing JS, CSS, JSON, and API paths, though the WAF already blocks them.

    What to change: Review and simplify robots.txt to allow necessary resources for compliant crawlers.

  10. Class-action lawsuit absent from site content Low

    The LLM model recalls a 2023 class-action lawsuit against Principle Auto, but the site contains no mention of it, leaving the brand's reputation unmanaged.

    What to change: Consider adding a page or statement addressing the lawsuit to manage brand narrative.

What's working

  • Anthropic-ai crawler allowed full access — The anthropic-ai crawler receives a 200 response with full HTML, enabling Claude training to read the site content.
  • Sitemap accessible to anthropic-ai — The sitemap.xml is served to anthropic-ai, listing ~350 URLs for discovery.
  • Robots.txt accessible and well-structured — The robots.txt file is accessible and contains clear directives for various crawlers.
  • Contact page accessible and contains location info — The contact page loads successfully and includes address and phone number for the San Antonio dealership.
  • New inventory page accessible — The new inventory page loads and contains vehicle listings, though content is JS-rendered.

Track principleauto.com across AI search

This is one snapshot. Open the interactive report to inspect evidence, or grade another site free.

Open this AI Site Grade Grade another site Track your brand