captivatechat.ai — AI Site Grade

Analysis

Captivate Chat: A well-built site with zero external footprint and no AI crawler awareness

The most significant finding is that a frontier LLM queried cold has zero knowledge of Captivate Chat — it cannot name a single product, customer, or market position — despite the site presenting a polished, multi-product AI sales platform deployed at TD SYNNEX with a London office and a founder who started at IBM in 1985.

Crawler Access

All 11 tested AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, Bytespider, Applebot-Extended, anthropic-ai, Perplexity-User) receive a 200 status with full HTML content identical to the browser baseline (~299KB). Cloudflare sits in front but does not UA-block any AI bot. The robots.txt is a bare Yoast-generated file with a wildcard Disallow: (empty — nothing blocked) and no AI-specific directives whatsoever. No llms.txt exists (404). The sitemap is present and well-formed with 40 URLs across two sub-sitemaps.

Cold-Knowledge Gap

The LLM prior is a complete void: "I do not have specific, verifiable information about captivatechat.ai." The site itself claims deployment at TD SYNNEX (one of the world's largest IT distributors), names a VP-level quote from Craig Smith, lists three products (Engage, Pilot, Signal), and pitches channel-sales AI to vendors, distributors, and resellers. The gap between the site's ambition and the model's blank slate is total — no external reviews, no press coverage, no Reddit threads, no G2 or Capterra pages surfaced in web searches. The DNS TXT record includes a Trustpilot verification token, but no Trustpilot page was found in search results.

Schema Posture

Every page carries Yoast-generated JSON-LD with WebPage, BreadcrumbList, WebSite, and Organization types. The Organization schema includes logo, name, and URL but is missing description, sameAs (social profiles), foundingDate, address, contactPoint, and aggregateRating. Blog articles use Article schema with author (Chris Patterson) and datePublished. No FAQPage schema is used on the FAQs page despite 30+ Q&A pairs in visible HTML — a significant missed signal for AI answer extraction. No Product or SoftwareApplication schema exists for Engage, Pilot, or Signal.

Content & Positioning

The site is a WordPress installation (Astra theme, Yoast SEO) with substantial, well-written copy. The homepage makes a clear value proposition: "Selling shouldn't stop at the lead form" — channel-sales AI that replaces static landing-page forms with conversational qualification. The three products form a logical progression (Engage → Pilot → Signal). Pricing is mentioned only on the for-vendors page: Engage Pro from £6,000 per campaign. The about-us page reveals the company was founded by Chris Patterson (ex-IBM, 1985) and has a "farshore" engineering hub in the Philippines (captivatelabs.ai). The site publishes blog content regularly (last post March 2026) on AI sales topics.

External Signals

Web searches returned zero results for the domain, the brand name, the founder, or the TD SYNNEX partnership claim. No press releases, no analyst mentions, no review sites, no social proof beyond the single testimonial on the homepage. The LinkedIn company page exists (linked in footer) but was not crawled by search engines for this query set. The parent domain captivatelabs.ai has G2 and Capterra review links, but captivatechat.ai itself has no independent third-party validation visible to search engines or AI crawlers.

Findings

1. Frontier LLMs have zero knowledge of Captivate Chat High

   A cold query to a frontier LLM returned no information about Captivate Chat, its products, customers, or market position, despite the site claiming deployment at TD SYNNEX and naming specific products.

   What to change: Build external signals through press releases, guest posts, review profiles (G2, Capterra), and social media activity to create a verifiable digital footprint.

2. No external reviews, press coverage, or social proof found High

   Web searches for the domain, brand name, founder, and TD SYNNEX partnership returned zero results. No G2, Capterra, Trustpilot, or press mentions were found, despite a Trustpilot verification token in DNS.

   What to change: Claim and populate profiles on G2, Capterra, and Trustpilot; issue press releases for partnerships; encourage customer reviews.

3. FAQ page lacks FAQPage schema despite 30+ Q&A pairs High

   The /faqs/ page contains over 30 visible question-answer pairs but uses only generic WebPage schema. FAQPage structured data would enable direct answer extraction by AI crawlers and search engines.

   What to change: Add FAQPage JSON-LD schema to the /faqs/ page marking each Q&A pair.

4. No Product or SoftwareApplication schema for Engage, Pilot, Signal High

   The three product pages (Engage, Pilot, Signal) lack structured data describing them as products or software applications. This limits AI crawlers' ability to understand and cite these offerings.

   What to change: Add SoftwareApplication or Product schema to each product page with name, description, offers, and application category.

5. Organization schema missing description, sameAs, and other key fields Medium

   The Organization JSON-LD includes logo, name, and URL but omits description, sameAs (social profiles), foundingDate, address, contactPoint, and aggregateRating, reducing its value for knowledge graph construction.

   What to change: Extend Organization schema with description, sameAs links to LinkedIn/Twitter, foundingDate, address, and contactPoint.

6. No llms.txt file for AI crawler guidance Medium

   The site returns a 404 for /llms.txt, missing an opportunity to provide AI crawlers with a curated summary of key pages and content for LLM consumption.

   What to change: Create an llms.txt file listing key pages (products, about, blog) with brief descriptions to guide AI crawlers.

7. Robots.txt has no AI-specific directives Low

   The robots.txt is a bare Yoast file with a wildcard empty Disallow and no rules for GPTBot, ClaudeBot, or other AI crawlers. While not blocking, it misses the chance to signal crawl preferences.

   What to change: Add explicit Allow/Disallow directives for AI crawlers and consider a separate AI-specific section.

8. No third-party review or testimonial pages found externally Medium

   Despite a Trustpilot DNS token, no Trustpilot page was found in search results. The only testimonial is on the homepage, with no external validation on G2, Capterra, or similar sites.

   What to change: Actively collect and publish reviews on G2, Capterra, and Trustpilot; link to them from the site.

9. Blog articles use basic Article schema without enhanced properties Low

   Blog posts have Article schema with author and datePublished but lack properties like image, description, or mainEntityOfPage, which could improve AI extraction.

   What to change: Enrich Article schema with image, description, and mainEntityOfPage properties.

What's working

• All 11 tested AI crawlers receive full HTML content — Every major AI crawler (GPTBot, ClaudeBot, PerplexityBot, etc.) gets a 200 response with complete HTML, ensuring no technical blocking.
• Sitemap is present and well-formed with 40 URLs — The sitemap index contains two sub-sitemaps covering 40 URLs, aiding crawler discovery.
• Every page includes Yoast-generated JSON-LD structured data — All pages have WebPage, BreadcrumbList, WebSite, and Organization schema, providing a baseline for AI understanding.
• Site has substantial, well-written copy across multiple pages — Product pages, blog, and about page contain detailed, relevant content that AI crawlers can index and cite.
• Blog publishes regularly on AI sales topics — The blog has recent posts (March 2026) with relevant content, demonstrating active content marketing.
• Clear three-product architecture (Engage, Pilot, Signal) — Products are logically structured and described, making it easy for crawlers to understand the offering.
• Cloudflare protects the site without blocking AI bots — Cloudflare is configured to allow all AI crawlers through, balancing security with accessibility.
• LinkedIn company page is linked in footer — The site links to a LinkedIn company page, providing a potential social signal, though not crawled in this audit.