invoca.com — AI Site Grade

Analysis

The competitor comparison pages all silently 301-redirect to the homepage

Invoca has four dedicated competitor comparison URLs (/invoca-vs-callrail, /invoca-vs-marchex, /invoca-vs-calltrackingmetrics, /invoca-vs-infinity) listed in the sitemap, but every single one redirects to the homepage with a 200 status — no comparison content exists. An AI crawler following these URLs from the sitemap lands on the generic homepage, not a competitive differentiation page.

Crawler Access

All major AI crawlers — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, anthropic-ai, Applebot-Extended — receive a full 200 response with identical byte size (241,876) to the browser baseline. Bytespider is the sole exception, returning a 403 Cloudflare block. The robots.txt contains no AI-bot directives whatsoever — only a single Sitemap: line. This is permissive by default but misses the opportunity to signal crawl preferences. The site is hosted on Cloudflare with HSTS and X-Frame-Options: SAMEORIGIN set. An llms.txt exists at /llms.txt (15,648 bytes) with explicit allow_training: true, allow_quoting: true, and a curated link list of ~50+ pages — a strong AI-friendly signal that is notably absent from the robots.txt.

Cold-Knowledge Gap

The cold LLM describes Invoca as a "conversation intelligence platform that analyzes phone calls" founded in 2007, headquartered in Santa Barbara, with $100M+ funding. The site itself now positions as an "AI-powered revenue execution platform" — a significant repositioning from conversation intelligence to revenue execution. The cold model knows nothing about the AI Operating System, AI Voice Agent, AI Messaging Agent (SMS), or the agentic AI narrative that dominates the current site. The homepage H1 is "AI you can trust. Revenue you can count on." — the model's prior is still anchored to call analytics, not the broader revenue orchestration story.

Schema Posture

Only the homepage and the /uk page carry Organization JSON-LD schema. Every other page examined — /blog, /company/about, /pricing, /g2, /platform/signal-ai, /platform/ai-voice-agent, /platform/ai-operating-system — has zero structured data. The homepage schema includes an AggregateRating with ratingValue: "5" and reviewCount: "1000", but this same schema block is duplicated verbatim on the /uk page and on the redirect targets. No WebPage, BreadcrumbList, FAQPage, Product, or SoftwareApplication schema appears anywhere. The blog has no Article or BlogPosting schema despite 44 pages of posts.

External Signals

The DNS TXT records reveal integrations with Anthropic (anthropic-domain-verification), Zoom, Adobe, Apple, Atlassian, Drift, Salesforce (SPF include), and Google (multiple verification records). The site claims an NPS of 87 and "1000+ 5-star reviews" on G2, but the /g2 page is a marketing landing page, not the actual G2 review widget — AI crawlers cannot access the live G2 review data from this page. The Wayback Machine shows the site was snapshotted as recently as May 2026, confirming active maintenance.

Content Contradictions

The homepage claims "1000+ 5 star reviews" and "The #1-rated AI platform for revenue teams" but the site has no FAQ schema, no comparison tables, and no structured answer formats that AI answer engines (Google SGE, Perplexity, ChatGPT search) prefer for competitive queries. The competitor comparison URLs exist in the sitemap but serve zero comparison content — they are effectively dead ends for any AI crawler seeking to understand how Invoca differentiates from CallRail, Marchex, or Infinity.

Findings

1. Competitor comparison pages silently redirect to homepage High

   Four competitor comparison URLs listed in the sitemap (e.g., /invoca-vs-callrail, /invoca-vs-marchex) all 301-redirect to the homepage with no comparison content. AI crawlers following these URLs land on the generic homepage instead of competitive differentiation content.

   What to change: Replace the redirects with actual comparison pages containing unique, substantive content that differentiates Invoca from each competitor.

2. Most pages lack structured data High

   Only the homepage and /uk page have Organization JSON-LD schema. All other examined pages — including /blog, /company/about, /pricing, /g2, and platform pages — have zero structured data. No WebPage, BreadcrumbList, FAQPage, Product, or SoftwareApplication schema exists.

   What to change: Add appropriate structured data (WebPage, BreadcrumbList, Article, Product, SoftwareApplication) to every page, especially the blog and platform pages.

3. Cold LLM knowledge is outdated on Invoca's repositioning Medium

   The cold LLM describes Invoca as a conversation intelligence platform, but the site now positions as an AI-powered revenue execution platform with products like AI Operating System, AI Voice Agent, and AI Messaging Agent. The model's prior is anchored to call analytics, not the broader revenue orchestration story.

   What to change: Increase AI-accessible content about the new platform narrative, such as detailed product pages, whitepapers, and structured data that explicitly describes the AI Operating System and agentic AI capabilities.

4. No FAQ schema or structured answer formats on the site Medium

   The site has no FAQPage schema, comparison tables, or structured answer formats that AI answer engines (Google SGE, Perplexity, ChatGPT search) prefer for competitive queries. This limits visibility in AI-generated answers.

   What to change: Add FAQPage schema to relevant pages and create structured comparison content with tables that AI crawlers can parse.

5. G2 page is a marketing landing page, not live review data Medium

   The /g2 page is a marketing landing page, not the actual G2 review widget. AI crawlers cannot access live G2 review data from this page, missing an opportunity to surface social proof in AI answers.

   What to change: Embed the actual G2 review widget or include structured data (e.g., AggregateRating) with accurate review counts and ratings on the page.

6. robots.txt lacks AI bot directives Low

   The robots.txt contains no AI-bot directives whatsoever — only a single Sitemap line. While permissive, this misses the opportunity to signal crawl preferences or guide AI crawlers to important pages.

   What to change: Add explicit directives for AI crawlers (e.g., GPTBot, ClaudeBot) to allow or disallow specific paths, and include a link to llms.txt.

7. Bytespider is blocked by Cloudflare Low

   Bytespider receives a 403 Cloudflare block, preventing it from accessing the site. This limits visibility on Baidu's AI ecosystem.

   What to change: Allow Bytespider access if the site targets Chinese markets or Baidu's AI platforms.

8. Duplicate Organization schema on /uk page Low

   The /uk page carries the same Organization JSON-LD schema as the homepage, including the same AggregateRating with ratingValue '5' and reviewCount '1000'. This duplication may confuse crawlers about which page is canonical.

   What to change: Use a canonical URL or differentiate the schema on the /uk page (e.g., different aggregate rating or no rating).

What's working

• llms.txt file published with curated links — Invoca publishes an llms.txt file (15,648 bytes) with explicit allow_training: true and allow_quoting: true, plus a curated list of ~50+ pages. This is a strong AI-friendly signal that helps AI crawlers discover key content.
• All major AI crawlers receive full 200 responses — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, anthropic-ai, and Applebot-Extended all receive a full 200 response with identical byte size to the browser baseline, ensuring AI crawlers can access the site content.
• Homepage has Organization JSON-LD with AggregateRating — The homepage includes Organization schema with an AggregateRating (ratingValue: '5', reviewCount: '1000'), providing structured social proof to AI crawlers.
• DNS records show integrations with major AI and tech companies — TXT records include verification for Anthropic, Zoom, Adobe, Apple, Atlassian, Drift, Salesforce, and Google, signaling strong partnerships and integrations that may boost credibility with AI systems.
• Site is actively maintained with recent Wayback snapshots — The Wayback Machine shows a snapshot as recent as May 2026, confirming active site maintenance and content updates.
• Site hosted on Cloudflare with security headers — Cloudflare hosting provides CDN, DDoS protection, and security headers (HSTS, X-Frame-Options: SAMEORIGIN), ensuring reliable and secure delivery to AI crawlers.