longlewisauto.com — AI Site Grade

Analysis

I have enough data to write the audit. Let me compile the findings.

Cold-Knowledge Gap

The LLM's cold knowledge about Long Lewis Auto is significantly inaccurate. It states the group was founded in 1969 by Long Lewis Sr. and operates in Alabama and Georgia with "over 20 dealership locations." The site itself says the business traces to 1887 as a hardware store in Bessemer, Alabama, and that the Long-Lewis name first appeared on that hardware store. The founder was William J. Long, not "Long Lewis Sr." The group operates 12 dealership locations across Alabama only — not Georgia. The current ownership structure (Todd Ouellette as sole owner since 2020, with Allen Vines as partner) is entirely absent from the model's prior. The model also mentions a "Long Lewis Promise" lifetime powertrain warranty, but the site prominently features a 3-Day/300-Mile Money Back Guarantee and a Lease-to-Own program — neither mentioned by the model.

Crawler Access

Every major AI crawler — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Applebot-Extended, Bytespider, anthropic-ai — receives a 200 status with the same full HTML payload (2.39 MB) as a browser. No UA-based blocking exists. The robots.txt uses an unusual Content-Signal directive (ai-train=yes, search=yes, ai-input=yes) that explicitly grants permission for all AI uses, including training and input. This is a progressive but non-standard approach — most crawlers do not parse Content-Signal headers. No AI bot is mentioned by name in the robots.txt. The /llms.txt endpoint returns a 404 (serving the full SPA shell instead), meaning no AI-friendly content map exists.

Schema Posture

The homepage includes WebSite, WebPage, Organization, and ImageObject schema types via JSON-LD — but critically, no AutoDealer or LocalBusiness type is used. Vehicle detail pages do include Vehicle schema with VIN, mileage, brand, model, color, and price — this is strong. However, the Organization schema lacks address, telephone, geo coordinates, and areaServed — all standard fields for a multi-location dealership. The locations page has no LocalBusiness schema at all. No FAQPage, Product, Review, or AggregateRating schema appears anywhere on the site despite customer reviews being displayed on the homepage.

Content & Structure

The homepage is a single-page application (SPA) built on Sanity CMS (evidenced by cdn.sanity.io image CDN) served behind Cloudflare. The page delivers 716 words of visible text from a plain GET — not a JS shell, but the content is relatively thin for a group claiming to be "Alabama's oldest, largest, and most trusted automotive group." The H1 reads "NO Fees. NO Gimmicks. NO Games." — a strong value proposition but zero keyword relevance for organic search. The site has 3,886+ vehicles in inventory (per the shop page title) and a sitemap with 7,652+ URLs across 4 sub-sitemaps. The history page is rich and well-structured with a timeline from 1887 through 2026. No FAQ, comparison tables, or structured answer-format content exists anywhere.

External Signals

Web searches for "Long Lewis Auto Group reviews Alabama dealership" and "Long-Lewis auto group Alabama" returned zero results from DuckDuckGo — an unusual vacuum for a group claiming to be the largest dealer in Alabama. No Reddit threads surfaced. The site's external link profile is minimal: only worktrucksolutions.com (commercial fleet) and autogenius.io (a third-party review/lead platform). The DNS shows Microsoft 365 for email and Cloudflare for DNS/hosting. The site lacks security headers (no HSTS, no CSP, no X-Frame-Options).

Findings

1. LLM cold knowledge about Long Lewis Auto is significantly inaccurate High

   The LLM prior incorrectly states the group was founded in 1969 by Long Lewis Sr., operates in Alabama and Georgia with over 20 locations, and mentions a lifetime powertrain warranty. The site's actual history traces to 1887, founder William J. Long, 12 Alabama-only locations, and a 3-Day/300-Mile Money Back Guarantee.

   What to change: Publish structured data (Organization, LocalBusiness) with accurate founding date, founder, location count, and service guarantees. Consider an llms.txt file to provide verified facts to AI crawlers.

2. No LocalBusiness or AutoDealer schema on any page High

   The homepage uses WebSite, WebPage, and Organization schema but omits AutoDealer or LocalBusiness types. The locations page has no LocalBusiness schema at all. Organization schema lacks address, telephone, geo coordinates, and areaServed.

   What to change: Add AutoDealer or LocalBusiness schema with address, telephone, geo, and areaServed to the homepage and each location page.

3. No external search results for the dealership group High

   Web searches for 'Long Lewis Auto Group reviews Alabama dealership' and 'Long-Lewis auto group Alabama' returned zero results on DuckDuckGo. No Reddit threads or third-party review sites surfaced.

   What to change: Build a backlink profile through local citations, press releases, and partnerships. Encourage customer reviews on Google, Yelp, and DealerRater.

4. No llms.txt file for AI-friendly content map Medium

   The /llms.txt endpoint returns a 404, serving the SPA shell instead. This means no AI-friendly content map exists for crawlers to discover key pages efficiently.

   What to change: Create an llms.txt file listing key pages (history, locations, inventory, service) with brief descriptions.

5. Homepage content is thin for a major dealership group Medium

   The homepage delivers only 716 words of visible text. The H1 'NO Fees. NO Gimmicks. NO Games.' lacks keyword relevance for organic search. Despite 3,886+ vehicles, the homepage does not highlight inventory depth or location breadth.

   What to change: Expand homepage content to include location summaries, inventory highlights, and keyword-rich descriptions of services and history.

6. No FAQPage, Review, or AggregateRating schema despite customer reviews Medium

   Customer reviews are displayed on the homepage but no structured data marks them up. No FAQPage schema exists anywhere on the site.

   What to change: Add Review and AggregateRating schema to review sections, and FAQPage schema for common customer questions.

7. Robots.txt uses non-standard Content-Signal directive Low

   The robots.txt includes a Content-Signal directive (ai-train=yes, search=yes, ai-input=yes) that most AI crawlers do not parse. No AI bots are named explicitly, which could lead to inconsistent interpretation.

   What to change: Replace the Content-Signal directive with explicit allow rules for major AI crawlers (GPTBot, ClaudeBot, etc.) in robots.txt.

8. Site lacks security headers (HSTS, CSP, X-Frame-Options) Low

   The homepage response headers show no HSTS, Content-Security-Policy, or X-Frame-Options headers, which can affect trust signals for AI crawlers and users.

   What to change: Add HSTS, CSP, and X-Frame-Options headers to improve security posture.

What's working

• All major AI crawlers receive full HTML content — Every tested AI crawler (GPTBot, ClaudeBot, PerplexityBot, etc.) receives a 200 status with the same full HTML payload as a browser. No UA-based blocking exists.
• Vehicle detail pages include comprehensive Vehicle schema — Inventory detail pages include Vehicle schema with VIN, mileage, brand, model, color, and price, which helps AI crawlers understand vehicle listings.
• History page provides a well-structured timeline — The history page offers a detailed timeline from 1887 through 2026, providing rich content for AI crawlers to learn about the company's heritage.
• Large inventory with extensive sitemap coverage — The site lists 3,886+ vehicles and has a sitemap with 7,652+ URLs across 4 sub-sitemaps, ensuring good crawl coverage.
• Robots.txt explicitly grants AI training and search permission — The robots.txt includes a Content-Signal directive that explicitly allows AI training, search, and input, showing a forward-thinking approach to AI visibility.