clearcompany.com — AI Site Grade

Analysis

ClearCompany.com: A Rebrand in Progress That AI Models Have Not Yet Registered

The site underwent a full rebrand from ClearCompany to ClearCo on March 23, 2026 — yet the cold LLM knowledge base still describes the company as "ClearCompany," names founder Andre Lavoie as CEO (he left in 2021), and cites "over 1,000 customers" while the site now claims 3,000. The AI-knowledge gap is approximately 2,000 customers, one CEO, and an entire brand identity behind.

Crawler Access

All major AI crawlers — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, anthropic-ai, Bytespider, Applebot-Extended — receive identical 200 responses with full HTML content (205KB each) from the Apache server. No UA-based blocking, no Cloudflare challenge, no JS shell. The robots.txt is minimal: a single User-agent: * rule disallowing only /cpresources/, /vendor/, /.env, and /cache/. No AI-bot-specific directives exist. The llms.txt exists (200) but is a thin stub — 461 bytes listing high-level categories with no URL references, no sitemap links, and no structured guidance for AI consumption.

Cold-Knowledge Gap

The frontier model queried about "ClearCompany" returned a snapshot frozen in time: founded 2004 by Andre Lavoie (CEO until 2021), Boston HQ, "over 1,000 customers," Inc. 5000 recognition, and mixed G2/Glassdoor reviews about support responsiveness. The actual site describes 3,000 clients, 1.8M employees supported, 85M applications processed, a CEO named Jason Beem, a rebrand to ClearCo, and an AI/agent-powered unified platform narrative. The model knows nothing about the rebrand, the new product positioning ("Talent AI," "People Analytics," agent-based framework), or the scale metrics. The gap is structural: any AI answering a question about "ClearCompany" will cite stale data from training cutoffs, while the live site has moved to a different name and value proposition.

Schema Posture

Every page carries the same JSON-LD schema block: WebPage, LocalBusiness (identity), and BreadcrumbList. The LocalBusiness schema uses alternateName: "ClearCompany" — a deliberate bridge between old and new names. However, the schema lacks SoftwareApplication type, which would be the natural type for a SaaS talent platform. No FAQPage, Product, or HowTo schemas appear anywhere. The pricing page has no Product or Offer schema despite listing five named packages (ClearRecruit, TotalTalent, ClearTalent, ClearGrow, ClearLearn) with feature breakdowns. The blog's rebrand announcement redirects off-domain to PRWeb (a 301 to prweb.com), meaning the canonical announcement lives on a third-party press release site, not on the company's own domain.

External Signals

The rebrand press release (March 23, 2026, via PRNewswire-PRWeb) is the only external signal found. No G2, Gartner, Reddit, or analyst coverage surfaced in web searches. The DNS TXT records reveal an anthropic-domain-verification token — confirming ClearCo has proactively registered for Anthropic's crawler verification — alongside HubSpot, Salesforce, Google, Apple, Figma, and Zoom verification tokens. The site runs on AWS (Route53 DNS, EC2 IPs) with Apache/2.4.58 (Ubuntu), no CDN layer, and HubSpot-powered marketing subdomain (offers.clearcompany.com).

Findings

1. AI models unaware of ClearCo rebrand, cite stale CEO and customer count High

   The cold LLM knowledge base describes ClearCompany as having over 1,000 customers and Andre Lavoie as CEO, while the site now claims 3,000 clients and lists Jason Beem as CEO. The rebrand from ClearCompany to ClearCo is not reflected in AI training data.

   What to change: Publish a dedicated rebrand announcement page on the primary domain with structured data (e.g., NewsArticle schema) and ensure it is indexed and linked from the homepage. Submit updated brand information to knowledge panels and data aggregators.

2. No SoftwareApplication schema on a SaaS platform Medium

   All pages carry WebPage, LocalBusiness, and BreadcrumbList schemas, but none use SoftwareApplication schema, which is the natural type for a talent management SaaS platform. This limits AI understanding of the product offering.

   What to change: Add SoftwareApplication schema with applicationCategory, operatingSystem, and offers to all product and platform pages.

3. Pricing page lacks Product and Offer schema Medium

   The pricing page lists five named packages with feature breakdowns but has no Product or Offer structured data, preventing AI from extracting pricing tiers and features.

   What to change: Add Product and Offer schema for each pricing tier, including name, description, and price (if available).

4. Rebrand announcement redirects to third-party PRWeb Medium

   The blog post about the rebrand redirects off-domain to a PRWeb press release, meaning the canonical announcement is not on the company's own domain, reducing its authority for AI indexing.

   What to change: Host the full rebrand announcement on the primary domain and use a canonical tag to point to the original if republishing elsewhere.

5. llms.txt is a stub with no URL references Low

   The llms.txt file exists but is only 461 bytes, listing high-level categories without any specific URLs or structured guidance for AI consumption.

   What to change: Expand llms.txt to include direct URLs to key pages (pricing, product capabilities, documentation) and a brief summary of the platform.

6. No FAQPage schema on any page Low

   Despite having a blog and product pages that could answer common questions, no FAQPage schema is used, missing an opportunity for rich results in AI responses.

   What to change: Add FAQPage schema to pages with Q&A content, such as the rebrand FAQ or product comparison sections.

7. No external review or analyst coverage found Medium

   Web searches for G2, Gartner, Reddit, and other review sites returned zero results for ClearCompany or ClearCo, indicating a lack of third-party validation that AI models often cite.

   What to change: Encourage customers to leave reviews on G2, Gartner, and other platforms, and link to those profiles from the website.

What's working

• All major AI crawlers receive full HTML content — Every tested AI crawler (GPTBot, ClaudeBot, PerplexityBot, etc.) receives a 200 response with complete HTML, no blocking or JS shells.
• Robots.txt is minimal and allows all AI bots — The robots.txt file has a single User-agent: * rule disallowing only non-content directories, with no AI-bot-specific blocks.
• LocalBusiness schema uses alternateName to bridge old and new brand — The JSON-LD includes alternateName: 'ClearCompany' alongside the new name, helping AI connect the rebrand.
• Anthropic domain verification token present — DNS TXT records include an anthropic-domain-verification token, indicating proactive registration for Anthropic's crawler verification.
• Sitemap exists with 80 URLs — A valid sitemap is available and contains 80 URLs, aiding crawler discovery.