AI Site Grade
saffordauto.com — AI Site Grade
Safford Auto Group's Cloudflare configuration blocks all AI crawlers and human browsers with a 403, making the entire site invisible to search engines and AI systems.
Safford Auto Group's site is completely blocked by Cloudflare 403 for all user agents, resulting in zero search engine presence and no AI visibility despite having OpenAI verification.
- Findings
- 12
- Evidence checks
- 25
- Completed
- 30 May 2026
Analysis
I have everything I need. Here's the audit.
Cloudflare blocks every AI crawler — and every browser — with a 403
Every single request to saffordauto.com, regardless of user-agent (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, or a standard browser), returns HTTP 403 served by Cloudflare with a "Attention Required!" challenge page. The site is effectively invisible to the open web. No page — not the homepage, not /new-vehicles/, not /contact-us/, not /privacy-policy/ — returns any real content. The robots.txt and llms.txt endpoints also 403. The sitemap is unreachable. The DNS TXT record includes an openai-domain-verification key, indicating OpenAI has been granted some verified access, but in practice OAI-SearchBot and ChatGPT-User both receive the same Cloudflare 403 as everyone else.
Cold-Knowledge Gap
The LLM prior describes Safford Auto Group as a family-owned Mid-Atlantic dealer network serving Virginia, Maryland, and D.C. with brands like Honda, Hyundai, Kia, Mazda, and Subaru. The actual site (visible only via Wayback Machine) reveals a far larger operation: 30+ locations spanning Alfa Romeo, BMW, Maserati, Genesis, Chrysler/Jeep/Dodge/Ram/Fiat, Toyota, Nissan, Volkswagen, and multiple collision centers. The cold model knows nothing about the luxury brands (Maserati, Alfa Romeo, BMW, Genesis) the group actually sells, nor about the "Safford Brown" naming convention used across many locations. The model also has no awareness of the group's collision repair network (Owings Mills, Tysons, Winchester, Springfield).
Schema Posture
The Wayback snapshot shows a single AutoDealer schema block on the homepage with @type: AutoDealer, but the PostalAddress fields for streetAddress, addressLocality, and postalCode are all empty strings. The priceRange is set to $-$$. No AggregateRating schema, no Review schema, no FAQPage schema, no ItemList schema for the 30+ locations. Each individual dealership is listed in the HTML as an <h3> heading with a "Visit Website" link pointing to separate subdomain sites — but none of those subdomain relationships are expressed in structured data. The WebSite schema correctly names the entity "Safford Automotive Group."
External Signals
DuckDuckGo returns zero search results for "saffordauto.com," "Safford Auto Group," or any combination of the brand name with location terms. This is highly unusual for a 30-location dealer group and suggests the Cloudflare block has effectively deindexed the domain from at least one major search engine. The Wayback Machine has a snapshot from October 2025 showing the site was functional then, meaning the blanket 403 is a recent or intermittent configuration. The DNS includes verification tokens for Apple, Facebook, Google, and OpenAI, indicating the group has engaged with multiple platforms — but the actual access controls contradict those verification signals.
Findings
Cloudflare blocks all traffic with 403 challenge page High
Every request to saffordauto.com, regardless of user-agent (including GPTBot, ClaudeBot, Google-Extended, OAI-SearchBot, and standard browsers), returns HTTP 403 served by Cloudflare. No page returns real content.
What to change: Remove the blanket 403 block and allow legitimate crawlers (Googlebot, GPTBot, etc.) through Cloudflare. Configure Cloudflare to serve real content to verified bots while still protecting against abuse.
Robots.txt and llms.txt return 403 High
The robots.txt and llms.txt endpoints both return HTTP 403, preventing crawlers from learning which paths are allowed or disallowed. This further blocks any potential crawling.
What to change: Ensure robots.txt and llms.txt are publicly accessible and return 200. Add appropriate directives for AI crawlers.
Sitemap.xml returns 403 High
The sitemap.xml endpoint returns HTTP 403, preventing search engines from discovering the site's pages. This contributes to the site's deindexing.
What to change: Make sitemap.xml publicly accessible and ensure it lists all important pages.
Zero search results for brand and domain High
DuckDuckGo returns zero results for queries including 'saffordauto.com', 'Safford Auto Group', and brand-location combinations. This indicates the site has been deindexed from at least one major search engine, likely due to the Cloudflare block.
What to change: Resolve the Cloudflare 403 issue to allow search engines to crawl and index the site. Submit the sitemap to Google Search Console and Bing Webmaster Tools.
OpenAI domain verification present but ineffective High
DNS TXT records include an openai-domain-verification key, indicating OpenAI has been granted verified access. However, OAI-SearchBot and ChatGPT-User both receive the same Cloudflare 403 as everyone else, making the verification useless.
What to change: Configure Cloudflare to allow OAI-SearchBot and ChatGPT-User through, honoring the OpenAI verification. Alternatively, remove the verification token if not intended to be used.
LLM prior lacks knowledge of luxury brands and collision centers Medium
The LLM prior describes Safford as a Mid-Atlantic dealer with Honda, Hyundai, Kia, Mazda, and Subaru, but the actual site (via Wayback) shows 30+ locations selling Alfa Romeo, BMW, Maserati, Genesis, and other luxury brands, plus multiple collision centers. The cold model has no awareness of these.
What to change: Publish detailed, crawlable content about all brands and locations. Use structured data (AutoDealer, LocalBusiness) for each location and brand.
AutoDealer schema has empty PostalAddress fields Medium
The homepage's AutoDealer schema block contains empty strings for streetAddress, addressLocality, and postalCode. This provides no useful location data to search engines or AI systems.
What to change: Populate the PostalAddress fields with the correct physical address of the main dealership or headquarters.
Missing AggregateRating and Review schema Medium
The site lacks AggregateRating and Review structured data, which are important for rich snippets and AI visibility. Competitors often include these to enhance search presence.
What to change: Add AggregateRating and Review schema markup to the homepage and individual location pages, using real customer review data.
No ItemList schema for 30+ dealership locations Medium
The homepage lists each dealership as an h3 heading with a link, but no ItemList or CollectionPage schema groups these locations. This makes it harder for AI to understand the full scope of the dealer network.
What to change: Add ItemList schema to the homepage or a dedicated locations page, listing each dealership with its name, URL, and address.
Subdomain relationships not expressed in structured data Medium
Each dealership has a separate subdomain website, but the relationship between the main domain and subdomains is not expressed via schema (e.g., sameAs or parentOrganization). This fragments the entity understanding.
What to change: Use schema.org properties like sameAs, parentOrganization, or subOrganization to link the main site to each dealership subdomain.
PriceRange set to broad '$–$#039; Low
The AutoDealer schema's priceRange is set to '$–$
#039;, which is too vague to be useful. More specific pricing information would help AI systems and search engines.What to change: Update priceRange to reflect actual pricing tiers, e.g., '$–$$' or provide a more descriptive range.
No FAQPage schema on site Low
The site does not include FAQPage schema, which is commonly used by automotive dealers to answer common questions and appear in rich results.
What to change: Create an FAQ page with common questions (e.g., financing, service hours) and mark it up with FAQPage schema.
What's working
- WebSite schema correctly names the entity — The homepage includes a WebSite schema block that correctly identifies the entity as 'Safford Automotive Group', providing a consistent name for AI systems.
- AutoDealer schema present on homepage — The homepage includes an AutoDealer schema block, which is the correct type for a car dealership group. This provides a foundation for structured data.
- DNS verification tokens for major platforms — DNS TXT records include verification tokens for Apple, Facebook, Google, and OpenAI, indicating the group has engaged with multiple platforms for verification.
- Wayback Machine snapshot shows functional site — A Wayback Machine snapshot from October 2025 shows the site was functional with content, indicating the current 403 block is a recent configuration issue and not a permanent state.
Track saffordauto.com across AI search
This is one snapshot. Open the interactive report to inspect evidence, or grade another site free.