chucknashchevroletbuickgmc.com — AI Site Grade

Analysis

Complete AI-Visibility Blackout Behind Cloudflare

Every AI crawler — GPTBot, ClaudeBot, Google-Extended, PerplexityBot, Applebot-Extended, OAI-SearchBot, and all others tested — receives a 403 Forbidden from Cloudflare on the homepage, robots.txt, llms.txt, and sitemap.xml. No bot has ever received a single byte of real content from the live domain. The site is a JS-rendered shell behind a WAF that blocks all non-browser traffic indiscriminately.

Crawler Access

The robots.txt and llms.txt both return 403 with Cloudflare's HTML error page — they are inaccessible, not merely absent. The sitemap.xml is also 403. The domain resolves to a single IP (54.243.57.127) behind Cloudflare, hosted on Bobcat Host. The compare_bot_access test confirmed all 11 major AI user-agents get the same 403 response (4,564 bytes of Cloudflare block page). No bot can discover any URL, inventory page, or service page on this domain.

Cold-Knowledge Gap

The LLM model describes Chuck Nash Chevrolet Buick GMC as a "family-owned and operated" San Marcos dealership with "community involvement in Hays County" and "mixed online reviews." The Wayback snapshot of the live site (January 2025) confirms the address (3209 N Ih 35), phone numbers, and three-brand inventory. However, the model's knowledge is entirely pre-2025 — it references no current inventory, no current specials, and no recent reputation signals. The live site's 2024-2025 model-year clearance sale, EV inventory (Blazer EV, Hummer EV, Sierra EV), and specific financing offers (2.9% APR, 90-day deferral) are completely absent from the model's knowledge. The gap is total: the model knows the brand exists but has zero access to any current page content.

Schema Posture

The Wayback snapshot reveals a rich AutoDealer schema block with Organization, WebSite, WebPage, AutoPartsStore, AutoRepair, and department-level OpeningHoursSpecification. The schema includes telephone, address, price range, and department-specific hours. This schema is only visible in the Wayback Machine — it is never served to live bots because Cloudflare blocks all non-browser requests before the page renders. The live site returns zero JSON-LD types to any crawler.

External Signals

No external mentions, reviews, Reddit threads, or press coverage were found in web search results for the domain name, brand name, or address. The brand has zero indexed external citations in current search results. The Wayback Machine shows 253 captures since April 2010, indicating the domain has existed for 15+ years, but none of that historical content is accessible to AI crawlers today. The google-site-verification TXT record confirms Google Search Console was once configured, but the current Cloudflare block prevents Googlebot from indexing any page.

Findings

1. Cloudflare WAF returns 403 Forbidden to all AI crawlers High

   Every major AI user-agent (GPTBot, ClaudeBot, Google-Extended, etc.) receives a 403 Forbidden response from Cloudflare on the homepage, robots.txt, llms.txt, and sitemap.xml. No bot can access any page content.

   What to change: Configure Cloudflare WAF to allow AI crawler user-agents (e.g., GPTBot, ClaudeBot, Google-Extended) by creating a firewall rule that permits these bots based on user-agent string.

2. Robots.txt returns 403, blocking crawler directives High

   The robots.txt file is served as a Cloudflare error page (403), making it impossible for any crawler to read crawl directives. This prevents even well-behaved bots from discovering allowed paths.

   What to change: Ensure robots.txt is publicly accessible and returns a 200 OK with appropriate directives. Remove any WAF rule that blocks access to this file.

3. Sitemap.xml returns 403, preventing URL discovery High

   The sitemap.xml is blocked by Cloudflare (403), so crawlers cannot discover any URLs on the site. This eliminates the primary mechanism for bot discovery of inventory and service pages.

   What to change: Make sitemap.xml publicly accessible and submit it to Google Search Console and Bing Webmaster Tools.

4. LLMs.txt returns 403, missing AI discovery file Medium

   The llms.txt file returns a 403 error, preventing AI crawlers from discovering a curated summary of the site's content. This file is increasingly used by LLMs to understand site structure.

   What to change: Create a publicly accessible llms.txt file that lists key pages (inventory, specials, service) and a brief description of the dealership.

5. Zero URLs indexed in search engines High

   Web search for site:chucknashchevroletbuickgmc.com returned zero results, confirming that no pages are indexed by Google or Bing. The Cloudflare block prevents all crawling and indexing.

   What to change: Remove the blanket bot block and allow Googlebot and Bingbot to crawl the site. Submit the sitemap to search consoles.

6. LLM knowledge of dealership is stuck in 2024 High

   The LLM model describes the dealership with pre-2025 information, missing current inventory (Blazer EV, Hummer EV, Sierra EV), current specials (2.9% APR, 90-day deferral), and recent reputation signals. The model knows the brand exists but has zero access to current page content.

   What to change: Allow AI crawlers to access the site so that LLMs can ingest current inventory, specials, and service information.

7. Zero external citations or reviews found in search results Medium

   Web searches for the dealership name, address, and domain returned no results for reviews, news, or any external mentions. The brand has no indexed external signals to support AI visibility.

   What to change: Encourage customers to leave reviews on Google, Yelp, and DealerRater. Ensure the dealership is listed on major directories with consistent NAP (name, address, phone).

8. Rich AutoDealer schema exists but is never served to crawlers High

   The Wayback snapshot shows a comprehensive AutoDealer schema block with Organization, WebSite, WebPage, AutoPartsStore, AutoRepair, and department hours. However, this schema is only visible in the Wayback Machine — live bots receive a 403 and never see the structured data.

   What to change: Ensure the schema is present on the live site and that AI crawlers can access the page to read it. Verify schema validity with Google's Rich Results Test.

9. Google Search Console verification exists but site is blocked Medium

   A google-site-verification TXT record exists, indicating past Search Console setup, but the current Cloudflare block prevents Googlebot from indexing any page, rendering the verification useless.

   What to change: Re-verify Search Console ownership and remove the bot block. Monitor crawl stats to confirm Googlebot can access the site.

10. No AI-specific directives or files (llms.txt, AI robots rules) Medium

    The site lacks any AI-specific configuration such as llms.txt or user-agent rules for AI bots in robots.txt. Combined with the blanket block, this leaves no path for AI crawlers to access content.

    What to change: Create a robots.txt that allows AI crawlers (e.g., GPTBot, ClaudeBot) and add an llms.txt file summarizing the site's key pages.

What's working

• Comprehensive AutoDealer schema exists in historical snapshot — The Wayback Machine snapshot shows a detailed AutoDealer schema with Organization, WebSite, WebPage, AutoPartsStore, AutoRepair, and department-specific opening hours. This schema is well-structured and covers key entity types.
• Domain has 15+ years of history with 253 Wayback captures — The domain has been active since at least 2010, with 253 captures in the Wayback Machine, indicating a long-standing online presence and historical content that could be restored.
• Google Search Console verification TXT record is present — A google-site-verification TXT record exists in DNS, indicating past or intended use of Search Console, which can be leveraged once bot access is restored.