ecapital.com — AI Site Grade

Analysis

The llms.txt file at https://ecapital.com/llms.txt is published but entirely broken — every single URL it lists uses the local development domain ecapital.local instead of the live domain, rendering the file useless to any LLM that consumes it.

Crawler Access

The site runs on Cloudflare (verified via DNS A records pointing to 141.193.213.20/21 and server headers) and hosts on Azure DNS. robots.txt has a permissive User-agent: * Allow: / with no AI-bot-specific rules — no mention of GPTBot, ClaudeBot, Google-Extended, or any other AI crawler. compare_bot_access confirmed that GPTBot, ClaudeBot, Google-Extended, OAI-SearchBot, ChatGPT-User, and anthropic-ai all receive a full 200 with the same 811KB payload as a browser. However, PerplexityBot and Perplexity-User get a 403 (Cloudflare block, nginx error page, 146 bytes), and Bytespider also gets a 403 (4.5KB Cloudflare block page). The homepage returns rich HTML content (1,870 words extracted), not a JS shell — AI crawlers that get through can parse it.

llms.txt and Sitemap Issues

The llms.txt file (generated by Yoast SEO v27.2) exists and returns 200, but every link — pages, posts, financial terms, transactions — uses https://ecapital.local/ as the base URL. An LLM consuming this file would attempt to fetch ecapital.local (a local dev domain) and get nothing. The sitemap index at sitemap_index.xml is valid and contains 6 sub-sitemaps with ~1,574+ URLs across US, UK, and Canadian locale paths.

Cold-Knowledge Gap

The LLM prior knows eCapital as a factoring/ABL firm formed through mergers (Riviera Finance, APEX Capital), serving transportation/staffing/healthcare, headquartered in Miami, with ~700 employees. The site itself claims 850+ employees and 42K+ clients financed with $89B+ funded — figures the cold model does not cite. The Wikipedia page (which the site links to via sameAs schema) contains a negative industry review section citing a 2014 Truckers Report review with complaints about contract termination, escrow delays, and aggressive sales tactics. The site's own /reviews/ page shows only positive testimonials and links to Trustpilot, but the Wikipedia page preserves the negative historical context — a fragmentation that means AI engines retrieving Wikipedia may surface complaints the site itself does not address.

Schema and Content Structure

The homepage carries a Corporation schema type with name: "eCapital Corp.", telephone, sameAs links (Facebook, X, LinkedIn, YouTube, Wikipedia, Medium), and a 600+ word description. The WebSite schema includes SearchAction with proper target URL. However, the US /about-us/ path returns a 404 — the only working About page is the UK locale at /en-gb/about-us/. The /products/ page has a noindex, follow robots meta tag, meaning it is excluded from search engine indexes despite being a primary navigation destination. The blog is active with posts dated as recently as May 2026, and the homepage dateModified is set to April 2026 — content freshness is not a concern.

External Signals

The Wikipedia page is well-maintained (last edit May 2026) and provides the most complete public narrative: founded 2006 as Global Merchant Fund Corp., rebranded to eCapital in 2020 after acquiring the eCapital brand, 12+ acquisitions including Gerber Finance, Paragon Financial, Bibby Financial Services, UMB Bank's AR division, and CNH Finance. The DNS TXT records reveal integrations with Salesforce (Pardot), Mandrill, SendGrid, Atlassian, and Anthropic (domain verification present) — indicating active CRM, email, and AI tooling behind the scenes.

Findings

1. llms.txt contains only localhost URLs High

   The llms.txt file at /llms.txt returns 200 but every URL uses the local development domain ecapital.local instead of the live domain, making the file useless for AI crawlers.

   What to change: Replace all ecapital.local URLs in llms.txt with the correct live domain ecapital.com.

2. PerplexityBot blocked by Cloudflare High

   PerplexityBot and Perplexity-User receive a 403 response from Cloudflare, preventing AI-powered search engines from indexing the site.

   What to change: Allow PerplexityBot and Perplexity-User in Cloudflare firewall rules or robots.txt.

3. US About page returns 404 High

   The US locale About page at /about-us/ returns a 404 error, while the UK locale version at /en-gb/about-us/ works. This breaks navigation for US visitors and AI crawlers.

   What to change: Restore the US About page at /about-us/ or redirect it to the UK version.

4. Products page has noindex meta tag High

   The /products/ page includes a noindex, follow robots meta tag, excluding it from search engine indexes despite being a primary navigation page.

   What to change: Remove the noindex meta tag from the Products page to allow indexing.

5. Wikipedia page contains negative industry review Medium

   The Wikipedia page includes a section citing a 2014 Truckers Report review with complaints about contract termination and aggressive sales tactics, which AI engines may surface alongside the site's own positive testimonials.

   What to change: Monitor and address negative content on Wikipedia through proper channels; consider publishing a response or updated information on the site.

6. No AI-specific crawler rules in robots.txt Medium

   The robots.txt file does not mention any AI crawlers (GPTBot, ClaudeBot, Google-Extended, etc.), leaving their access unmanaged.

   What to change: Add explicit rules for AI crawlers in robots.txt to control their access.

7. Bytespider blocked by Cloudflare Medium

   Bytespider (ByteDance's crawler) receives a 403 response from Cloudflare, preventing indexing by TikTok/Douyin search.

   What to change: Allow Bytespider in Cloudflare firewall rules if desired.

8. UK history page returns 404 Low

   The UK locale history page at /company/our-history/ returns a 404, while the US version at /history/ works.

   What to change: Restore the UK history page or redirect it to the US version.

What's working

• Permissive robots.txt allows all crawlers — The robots.txt file allows all user agents to access the entire site, ensuring no accidental blocking of legitimate crawlers.
• Homepage provides rich HTML content — The homepage returns 1,870 words of extractable text, not a JavaScript shell, allowing AI crawlers to parse content easily.
• Sitemap index is valid and comprehensive — The sitemap index at /sitemap_index.xml contains 6 sub-sitemaps with over 1,500 URLs across US, UK, and Canadian locales.
• Homepage has correct Corporation schema — The homepage includes a Corporation schema with name, telephone, sameAs links, and a detailed description, aiding AI understanding.
• Blog is active with recent posts — The blog at /blog/ contains posts dated as recently as May 2026, indicating fresh content that AI crawlers can index.
• Reviews page aggregates positive testimonials — The /reviews/ page collects client testimonials and links to Trustpilot, providing social proof for AI engines.
• Wikipedia page is well-maintained and detailed — The Wikipedia page has recent edits (May 2026) and provides a comprehensive history, acquisitions, and company details, serving as a strong external signal.
• Anthropic domain verification present in DNS — DNS TXT records include Anthropic domain verification, indicating active AI tooling integration.