foley.io — AI Site Grade

Analysis

Foley — AI-Visibility Audit

The site operates a two-domain architecture (foley.io for the SaaS platform, foleyservices.com for content marketing) that creates a fragmented AI surface — the cold-knowledge model knows about "Foley Compliance Score" and ELD integration, neither of which actually appear on the live site.

Crawler Access

All major AI crawlers — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, ChatGPT-User, OAI-SearchBot, Applebot-Extended, Bytespider, anthropic-ai — receive full 200 responses with identical byte payloads (497 KB) from Cloudflare. No UA-based blocking exists. The robots.txt on both domains explicitly Allow: / for every AI bot listed, with only HubSpot CMS preview paths disallowed. The llms.txt files on both domains are present, well-structured, and link to authoritative product and regulatory pages — a rare and strong signal.

Cold-Knowledge Gap

The LLM's prior knowledge contains two significant hallucinations. It claims Foley offers a "Foley Compliance Score" proprietary metric and ELD data integration. Neither exists on the site. The homepage, platform page, and pricing page make no mention of a compliance score or ELD integration. The site focuses on DOT drug testing, driver qualification files, MVR monitoring, CSA monitoring, background checks, and the new Navigator AI assistant. The model also places Foley's founding in the "mid-2010s" — the site states founded 1992 (33+ years in business). This gap means AI-generated summaries about Foley will cite features the company does not offer and miss its actual 30-year heritage.

Schema Posture

The homepage carries rich JSON-LD (Organization, WebSite, WebPage, SoftwareApplication, EducationalOccupationalCredential, Service, Person) with BBB and PBSA credentials, CEO Joel Sitak, founding date 1992, and service areas (USA, Canada, Mexico). However, subpages (Navigator, Pricing, Platform, About, Customers, Resources) contain zero JSON-LD — only the homepage has structured data. The SoftwareApplication schema on the homepage is truncated in the fetch and may be incomplete. The foleyservices.com domain has its own Organization schema naming "Foley Carrier Services LLC" — a separate legal entity name not used on foley.io.

Dual-Domain Fragmentation

The two domains serve distinct roles but cross-reference inconsistently. Foley.io (the SaaS platform) links to foleyservices.com for login (login.foleyservices.com), initiatives, and some external resources. Foleyservices.com (the content hub) links back to foley.io for the platform and demos. The sitemap on foley.io lists 933 URLs (articles, guides, webinars, case studies) while foleyservices.com lists 112 URLs — yet the robots.txt on foley.io points its sitemap to foleyservices.com/sitemap.xml rather than its own. The llms.txt on foley.io references foleyservices.com as the "regulatory reference" domain. An AI crawler ingesting both domains would need to reconcile two brand identities ("Foley" vs. "Foley Carrier Services") and two separate URL trees.

External Signals

The homepage claims "#1 DOT Compliance Provider" with 1,124 Trustpilot reviews at 4.3 stars and "50,000+ customers." The DNS TXT records confirm OpenAI, Anthropic, and Apple domain verification — the brand has proactively registered for AI crawler trust signals. LinkedIn, Facebook, Glassdoor, Crunchbase, and BBB profiles are all linked in schema. However, web searches for "Foley DOT compliance" return zero organic results in the search tool used — the brand has minimal third-party press or independent review coverage outside its own properties.

Findings

1. LLM cold knowledge hallucinates non-existent features High

   The LLM prior knowledge incorrectly claims Foley offers a 'Foley Compliance Score' and ELD data integration, neither of which appear on the site. The model also misstates the founding year as mid-2010s instead of 1992.

   What to change: Add pages or content that clearly describe the actual features (DOT drug testing, driver qualification files, MVR monitoring, CSA monitoring, background checks, Navigator AI) and prominently display the founding year 1992 to correct the record.

2. Dual-domain architecture fragments AI surface High

   Foley operates two domains (foley.io for SaaS, foleyservices.com for content) with inconsistent cross-references and separate brand identities ('Foley' vs. 'Foley Carrier Services'). The sitemap on foley.io incorrectly points to foleyservices.com's sitemap.

   What to change: Consolidate AI-facing content onto a single domain or clearly define the relationship between the two domains in llms.txt and schema. Fix the sitemap reference on foley.io to point to its own sitemap.

3. Subpages lack JSON-LD structured data High

   Only the homepage contains JSON-LD schema. Key subpages (Navigator, Pricing, Platform, About, Customers, Resources) have zero structured data, limiting AI understanding of their content.

   What to change: Add appropriate JSON-LD schema (e.g., SoftwareApplication, Product, FAQPage, Article) to all subpages to match the homepage's structured data coverage.

4. Homepage SoftwareApplication schema may be incomplete Medium

   The SoftwareApplication schema on the homepage is truncated in the fetch and may lack required properties like applicationCategory or offers.

   What to change: Review and complete the SoftwareApplication schema to include all recommended properties (applicationCategory, offers, operatingSystem, etc.).

5. Minimal third-party press and independent reviews Medium

   Web searches for 'Foley DOT compliance' return zero organic results outside the brand's own properties. Despite claiming 1,124 Trustpilot reviews, no independent review coverage was found in search results.

   What to change: Build third-party press mentions, guest posts, and independent review profiles to increase external signals and AI citation sources.

6. Brand identity mismatch between domains Medium

   Foleyservices.com uses 'Foley Carrier Services LLC' in its Organization schema, while foley.io uses 'Foley'. This creates confusion for AI crawlers trying to reconcile the two entities.

   What to change: Align the legal entity name across both domains or use sameAs relationships in schema to clarify the relationship.

What's working

• All major AI crawlers fully allowed — Robots.txt on both domains explicitly allows all major AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.) with no UA-based blocking. All bots receive full 200 responses.
• llms.txt files present on both domains — Both foley.io and foleyservices.com serve well-structured llms.txt files that link to authoritative product and regulatory pages, providing a strong signal for AI crawlers.
• Homepage has rich JSON-LD with credentials and history — The homepage includes comprehensive JSON-LD with Organization, WebSite, SoftwareApplication, and Person schemas, including BBB and PBSA credentials, CEO name, founding date 1992, and service areas.
• DNS TXT records verify domain for AI crawlers — DNS TXT records confirm domain verification for OpenAI, Anthropic, and Apple, indicating proactive registration for AI crawler trust signals.
• Extensive resource library with 933 URLs — The sitemap on foley.io lists 933 URLs including articles, guides, webinars, and case studies, providing substantial content for AI crawlers to index.