executiveautogroup.com — AI Site Grade

Analysis

Cloudflare Wall Blocks All Crawlers, Site Renders Zero Content

Every AI crawler tested — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, ChatGPT-User, OAI-SearchBot, Applebot-Extended, Bytespider, and anthropic-ai — receives a 403 response from Cloudflare when requesting https://executiveautogroup.com. The homepage returns a 236KB HTML shell with zero visible text, no schema, no headings, and no links. The robots.txt and llms.txt endpoints also return 403. The site is functionally invisible to the AI ecosystem.

Crawler Access

The domain is hosted on Cloudflare (IP 74.119.99.3) behind a dealer website platform identified by the x-cars-signature-v1 header and the MX record pointing to tkcarsites.com. Every bot UA — including Browser UA — gets the same 403 with a JS-heavy HTML shell containing only font-face CSS and a <title>Dealer Website</title>. No robots.txt directives exist because the file itself is blocked. No llms.txt exists. The sitemap at /sitemap.xml also returns 403. The site has zero discoverable URLs.

Cold-Knowledge Gap

The LLM (DeepSeek) describes Executive Auto Group as a "network of car dealerships primarily operating in the Midwest and Southeast U.S., selling new and used vehicles from brands like Ford, Chevrolet, Honda, and Toyota" with "community sponsorships and local charity events." This prior knowledge is entirely unverifiable from the live site. The site itself provides no brand name, no location, no inventory, no service information — nothing. The gap between what the model "knows" and what the site delivers is total: the model describes a real business, but the domain presents a locked door.

External Signals

No external search results were found for executiveautogroup.com or "Executive Auto Group" across multiple search queries. No Wayback Machine snapshot exists. No reviews, Reddit threads, press mentions, or directory listings surfaced. The brand has zero indexed external footprint — a striking absence for a dealership group the LLM describes as multi-location and multi-brand.

Schema Posture

The homepage contains zero JSON-LD schema of any type. No AutoDealer, Organization, LocalBusiness, or Product schema is present. No FAQPage, HowTo, or Product structured data exists anywhere on the site. The heading structure is empty. The site has no answer-format signals (no FAQ, no tables, no comparison language, no lists). An AI engine attempting to extract inventory, location, or pricing data finds nothing.

Findings

1. Cloudflare wall blocks all AI crawlers with 403 responses High

   Every AI crawler tested receives a 403 response from Cloudflare when requesting the homepage. The site is hosted on Cloudflare and returns a 236KB HTML shell with zero visible text, no schema, no headings, and no links.

   What to change: Configure Cloudflare to allow AI crawler user agents (e.g., GPTBot, ClaudeBot) by creating a WAF rule or bypassing the JS challenge for known bot IP ranges. Alternatively, serve a static HTML version of the homepage to bots.

2. Robots.txt returns 403, preventing any crawl directives High

   The robots.txt endpoint returns a 403 response, meaning no crawl directives can be communicated to any bot. This prevents the site from allowing or disallowing specific crawlers.

   What to change: Ensure robots.txt is publicly accessible and returns a 200 status. Include directives to allow AI crawlers like GPTBot and ClaudeBot.

3. Sitemap returns 403, blocking URL discovery High

   The sitemap at /sitemap.xml returns a 403 response, preventing search engines and AI crawlers from discovering the site's URLs.

   What to change: Make sitemap.xml publicly accessible and ensure it lists all important pages.

4. No llms.txt file exists for AI guidance Medium

   The llms.txt endpoint returns a 403, meaning the site provides no guidance to AI crawlers about which pages to prioritize or how to interpret content.

   What to change: Create an llms.txt file that lists key pages (e.g., inventory, about, contact) and provides hints for AI consumption.

5. Homepage returns empty JS shell with no visible content High

   The homepage returns a 236KB HTML shell with only font-face CSS and a title 'Dealer Website'. No visible text, headings, links, or schema are present. This is likely a JavaScript-rendered page that fails to load for bots.

   What to change: Implement server-side rendering (SSR) or static prerendering for the homepage so that bots receive meaningful HTML content without requiring JavaScript execution.

6. No URLs discoverable via sitemap or crawling High

   The sitemap is blocked, and no internal links are present in the homepage HTML. The site has zero discoverable URLs, making it impossible for crawlers to find any pages.

   What to change: Ensure the sitemap is accessible and that the homepage contains internal links to key pages (inventory, about, contact).

7. No JSON-LD schema present on the homepage High

   The homepage contains zero JSON-LD structured data. No AutoDealer, Organization, LocalBusiness, or Product schema exists, preventing AI engines from extracting entity information.

   What to change: Add JSON-LD schema for AutoDealer, Organization, and LocalBusiness with name, address, phone, inventory URL, and operating hours.

8. Zero external search results or backlinks found High

   Multiple web searches for the domain and brand name returned zero results. No Wayback Machine snapshot exists. The brand has no indexed external presence, which severely limits AI knowledge grounding.

   What to change: Build external signals by claiming business listings (Google Business Profile, Yelp, DealerRater), earning press mentions, and encouraging customer reviews.

9. LLM prior knowledge of the dealership is unverifiable from the site Medium

   The LLM describes Executive Auto Group as a multi-location dealership group, but the live site provides no brand name, location, or inventory to confirm this. The gap between model knowledge and site content is total.

   What to change: Ensure the homepage clearly states the brand name, locations, and inventory in visible text and schema to align with AI knowledge.

10. No FAQ, tables, or list content for AI answer extraction Medium

    The site lacks FAQPage schema, tables, comparison language, or list structures that AI engines use to extract answers for featured snippets or direct answers.

    What to change: Add an FAQ section with common questions (e.g., financing, trade-in) and mark it up with FAQPage schema. Use tables for inventory comparisons.