meetclearedge.com — AI Site Grade

Analysis

I have enough data to write the audit. Here's the key finding: the LLM conflates this ClearEdge with a completely different company (a B2B tech ABM agency), and the site has virtually zero external web presence despite being in business since 2006.

---

The Cold-Knowledge Gap Is a Brand Identity Crisis

A frontier LLM queried cold about "ClearEdge marketing agency" describes a B2B tech ABM agency serving Dell, VMware, and cybersecurity clients — a company that does not exist at meetclearedge.com. The actual ClearEdge is a staffing and HR-tech industry specialist founded in 2006 by Leslie Vickrey, offering marketing, recruiting, and leadership development under one roof. The model knows nothing about the real business and hallucinates a different one entirely.

Crawler Access

All major AI crawlers — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Bytespider, Applebot-Extended — receive a full 200 response from the homepage with identical byte size (~354KB) to a browser. No UA-based blocking exists. The robots.txt is a bare Yoast-generated file with a wildcard Disallow: (empty, meaning allow all) and no AI-specific directives at all. /llms.txt returns a 404. The site runs on nginx on AWS (EC2, 54.234.75.130) with no CDN or WAF layer — AI crawlers hit the origin server directly.

Schema Posture

Every page carries well-formed WebPage, WebSite, Organization, and BreadcrumbList JSON-LD via Yoast. Blog posts use Article/BlogPosting with author, datePublished, and wordCount. However, the Organization schema is thin: it contains only name, URL, and a logo SVG — no sameAs links, no foundingDate, no description, no knowsAbout to signal the staffing/HR-tech niche. The WebSite description reads "PR, Branding & Digital Marketing Agency" — a generic label that does not distinguish the firm from thousands of other agencies.

Content Quality and Recency

Content is surprisingly fresh and deep. Blog posts from early 2026 (March, February, January) run 2,800+ words with structured headings, case studies, and FAQ sections. The resources hub lists 122 podcast episodes, 60 blog posts, and 21 videos. The blog post on subdomain/iframe job boards is a substantive, data-rich piece with a 90-day case study. The site explicitly mentions "Optimized for AEO, GEO, and AI-driven discovery" on the marketing services page — indicating awareness of AI search trends.

External Signals Vacuum

Web searches for meetclearedge.com, "ClearEdge" "Leslie Vickrey", and "ClearEdge Marketing" staffing returned zero indexed results on DuckDuckGo. No Reddit threads, no press mentions, no reviews, no external backlink references surfaced. The domain has no CDN, no WAF, and no analytics or social proof integrations visible beyond LinkedIn/Twitter/Facebook links in the footer. The site exists in a near-complete external citation vacuum, which directly explains why the LLM has no training data about this brand.

Stale Content and Structural Oddities

The sitemap contains podcast episodes dating back to 2018 (e.g., "Women in Recruitment" episodes, net neutrality repeal coverage) alongside 2026 content — a 7+ year content span with no apparent archival strategy. The homepage dateModified is set to 2026-03-06 (a future date from the perspective of the site's own schema), suggesting a plugin or caching quirk. The ce_job-sitemap.xml and rising-resource-sitemap.xml sub-sitemaps hint at structured content types that are not prominently linked from the main navigation.

Findings

1. LLM cold knowledge describes a different ClearEdge (B2B tech ABM agency) High

   A frontier LLM queried about 'ClearEdge marketing agency' describes a B2B tech ABM agency serving Dell and VMware, not the actual staffing/HR-tech specialist. The model has no training data about the real ClearEdge.

   What to change: Build external citations: publish guest posts, earn backlinks, claim business listings, and ensure the brand name 'ClearEdge' is consistently associated with 'staffing' and 'HR tech' across the web.

2. Zero indexed external mentions or backlinks High

   Web searches for the domain, brand name, and founder returned zero results on DuckDuckGo. No Reddit threads, press mentions, reviews, or backlinks were found. The site exists in a near-complete external citation vacuum.

   What to change: Implement a link-building strategy: contribute to industry publications, get listed in staffing/HR tech directories, and encourage client testimonials on third-party review sites.

3. Organization schema lacks sameAs, foundingDate, and niche description High

   The Organization JSON-LD contains only name, URL, and a logo SVG. Missing sameAs links, foundingDate, description, and knowsAbout properties that would help AI models understand the firm's staffing/HR-tech focus.

   What to change: Add sameAs links (LinkedIn, Twitter, Crunchbase), foundingDate, description, and knowsAbout properties to the Organization schema to disambiguate the brand.

4. WebSite schema description is generic and does not differentiate the firm Medium

   The WebSite schema description reads 'PR, Branding & Digital Marketing Agency' — a label that applies to thousands of agencies and does not signal the staffing/HR-tech specialization.

   What to change: Update the WebSite description to include 'staffing industry', 'HR tech', and 'recruiting' keywords to improve AI understanding.

5. No /llms.txt file to guide AI crawlers Medium

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

   What to change: Create an /llms.txt file listing core pages (services, about, resources) with brief descriptions to help AI crawlers understand site structure.

6. Homepage dateModified set to a future date (2026-03-06) Low

   The homepage schema lists dateModified as 2026-03-06, which is a future date relative to the site's own content, likely a plugin or caching quirk that could confuse crawlers.

   What to change: Investigate and fix the dateModified value in the homepage schema to reflect the actual last modification date.

7. Sitemap includes podcast episodes from 2018 alongside 2026 content Low

   The sitemap contains episodes dating back to 2018 (e.g., net neutrality repeal coverage) with no archival strategy, potentially diluting crawl budget and signaling outdated content.

   What to change: Consider removing or noindexing very old podcast episodes to focus crawl budget on current content.

What's working

• All major AI crawlers receive full 200 responses with no blocking — GPTBot, ClaudeBot, PerplexityBot, and others are allowed via robots.txt and return identical content to browser requests. No UA-based blocking exists.
• Blog posts are fresh (2026) and substantive (2,800+ words) — Recent blog posts from early 2026 run 2,800+ words with structured headings, case studies, and FAQ sections. The content is data-rich and optimized for AI-driven discovery.
• All pages carry valid WebPage, WebSite, Organization, and BreadcrumbList JSON-LD — Yoast-generated schema is present on every page, including Article/BlogPosting on blog posts with author, datePublished, and wordCount.
• Marketing services page explicitly mentions optimization for AEO, GEO, and AI-driven discovery — The site shows awareness of AI search trends by stating 'Optimized for AEO, GEO, and AI-driven discovery' on the marketing agency page.
• Resources hub lists 122 podcast episodes, 60 blog posts, and 21 videos — A substantial content library with multiple formats provides depth for AI crawlers to index.