pedderautogroup.com — AI Site Grade

Analysis

Pedder Auto Group — AI-Visibility Audit

The most consequential finding is a geographic hallucination gap: a frontier LLM queried cold describes Pedder Auto Group as a Houston, Texas dealership group selling Ford and Chevrolet, when the site is in fact a Southern California group (Riverside/San Diego counties) selling Nissan, Hyundai, Chrysler, Dodge, Jeep, and Ram — zero overlap on location or brands.

Crawler Access

All major AI crawlers — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Bytespider, Applebot-Extended — receive a 200 status with full HTML content (~535KB) from the homepage. No UA-based blocking exists. The site runs on Google Frontend infrastructure (Google Cloud / App Engine) with a Content-Security-Policy restricting frames to app.ridemotive.com and related subdomains. The robots.txt has a Crawl-delay: 10 for * and blocks dotbot and MotoMinerBot entirely, but no AI crawler is explicitly named in any directive. The sitemap.xml contains ~2,030 URLs and is well-formed.

llms.txt and Content Signals

The site has an llms.txt (rare for automotive groups) at /llms.txt returning 200 with 6,827 bytes — but every inventory entry uses the identical description "New quality vehicles in your area." The llms.txt also contains a malformed address line ("located at , , ,"). The blog at /blog returns "No blogs available" — a dead content channel. The homepage has 342 words of visible text, two H1s (a structural error), and no FAQ schema. The AutoDealer schema on the homepage and about-us page contains "streetAddress": "undefined" — a broken address field that will confuse knowledge graph parsers.

Cold-Knowledge Gap

The cold LLM response places the group in Houston, Texas, lists Ford and Chevrolet as franchise brands, and describes a "decades" history. The actual site: founded in 2008 in Hemet, California, with Nissan, Hyundai, Chrysler, Dodge, Jeep, Ram — no Ford or Chevrolet. The cold model also describes a "strong local reputation in Houston" — a city where the group has zero presence. This is a complete geographic and brand hallucination, likely because the name "Pedder" is rare and the model conflates it with unrelated Texas dealership groups.

Schema and Structured Data

Inventory detail pages carry rich Car schema with VIN, mileage, pricing, fuel efficiency, engine specs, and dealer information — strong for individual vehicle pages. However, the top-level AutoDealer schema across the homepage, about-us, and career pages is broken: streetAddress is "undefined", openingHoursSpecification is an empty nested array [[]], and department is an empty array. The WebSite schema with SearchAction is correctly configured. No LocalBusiness or Organization schema with proper address is present on any page.

External Signals

The group operates eight individual dealer-branded domains (e.g., racewaynissan.com, hemetcdjr.com, powayhyundai.com) that link back to the main site for service scheduling. Web search returned zero indexed results for "Pedder Auto Group" queries — the brand has essentially no discoverable external press, reviews, or Reddit mentions. This absence of off-domain signals means AI engines have almost no corroborating data to correct the geographic hallucination.

Findings

1. Frontier LLMs hallucinate Pedder Auto Group as a Houston, Texas Ford/Chevrolet dealer High

   A cold LLM query describes Pedder Auto Group as a Houston, Texas dealership group selling Ford and Chevrolet, with a 'decades' history. The actual group is based in Hemet, California, founded in 2008, and sells Nissan, Hyundai, Chrysler, Dodge, Jeep, and Ram. No Ford or Chevrolet franchises exist. This complete geographic and brand hallucination is likely due to the rare name 'Pedder' being conflated with unrelated Texas dealerships.

   What to change: Publish a comprehensive 'About' page with exact location, founding year, and franchise list. Add LocalBusiness schema with correct address on every page. Build external signals (press releases, Google Business Profile, dealer reviews) to provide corroborating data for AI engines.

2. AutoDealer schema contains undefined streetAddress and empty openingHoursSpecification High

   The AutoDealer schema on the homepage, about-us, and career pages has 'streetAddress' set to 'undefined' and 'openingHoursSpecification' as an empty nested array. This broken structured data will confuse knowledge graph parsers and may cause AI engines to ignore or misinterpret the entity.

   What to change: Fix the AutoDealer schema to include valid streetAddress, openingHoursSpecification, and department fields. Use a proper LocalBusiness or Organization schema with correct address on all pages.

3. No external signals found for Pedder Auto Group brand High

   Web searches for 'Pedder Auto Group' and related queries returned zero indexed results. The brand has no discoverable external press, reviews, or social mentions. This absence of off-domain signals means AI engines have no corroborating data to correct the geographic hallucination.

   What to change: Build external signals by creating and optimizing Google Business Profiles for each dealership, submitting press releases, and encouraging customer reviews on third-party platforms.

4. llms.txt contains malformed address and duplicate inventory descriptions Medium

   The llms.txt file returns 6,827 bytes but every inventory entry uses the identical description 'New quality vehicles in your area.' The file also contains a malformed address line 'located at , , ,' which will confuse AI parsers.

   What to change: Fix the llms.txt address line and provide unique, descriptive summaries for each inventory item. Consider adding a summary of the dealership group's locations and brands.

5. Blog page returns 'No blogs available' Medium

   The blog at /blog returns a page with only 81 words and the message 'No blogs available.' This dead content channel provides no value to AI crawlers and misses an opportunity to build topical authority.

   What to change: Either remove the blog page or populate it with regular, high-quality articles about vehicle maintenance, local driving tips, and dealership news.

6. Homepage has two H1 headings Low

   The homepage contains two H1 elements, which is a structural HTML error that can confuse search engines and AI crawlers about the page's primary topic.

   What to change: Ensure only one H1 per page. Convert the second H1 to an H2 or other heading level.

7. No FAQ schema on any page Low

   No FAQ schema was found on any page. FAQ schema can help AI crawlers extract common questions and answers, improving visibility in AI-generated answers.

   What to change: Add FAQ schema to pages with common customer questions, such as financing, service hours, and warranty information.

8. robots.txt does not explicitly name any AI crawler Low

   The robots.txt file has rules for general crawlers and blocks dotbot and MotoMinerBot, but no AI crawler (GPTBot, ClaudeBot, etc.) is explicitly named. While not blocking them, the lack of explicit allowance may cause some crawlers to be cautious.

   What to change: Add explicit Allow directives for major AI crawlers (GPTBot, ClaudeBot, PerplexityBot, etc.) to ensure they crawl the site without hesitation.

What's working

• All major AI crawlers receive 200 status with full HTML content — All 11 tested AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Bytespider, Applebot-Extended) receive a 200 status with full HTML content from the homepage. No UA-based blocking exists.
• llms.txt file is present and returns 200 — The site has an llms.txt file at /llms.txt returning 200 with 6,827 bytes. This is rare for automotive groups and provides a direct channel for AI crawlers to consume structured content.
• Inventory detail pages carry rich Car schema with VIN, mileage, pricing — Individual inventory pages include detailed Car schema with VIN, mileage, pricing, fuel efficiency, engine specs, and dealer information. This helps AI crawlers understand vehicle specifics.
• Sitemap.xml is well-formed with ~2,030 URLs — The sitemap.xml contains approximately 2,030 URLs and is well-formed, helping crawlers discover all pages efficiently.
• WebSite schema with SearchAction is correctly configured — The WebSite schema includes a SearchAction property, enabling AI crawlers to understand the site's search functionality.
• Site runs on Google Frontend infrastructure with fast response — The site is hosted on Google Cloud / App Engine (Google Frontend), providing fast response times and reliable infrastructure for crawlers.