leandata.com — AI Site Grade

Analysis

I have enough data to write a thorough audit. Let me compile the findings.

The llms.txt file references a local development domain (leandata.lndo.site) instead of the production domain for its sitemap link — a Yoast SEO misconfiguration that sends AI crawlers to a dead URL.

Crawler Access

All major AI crawlers — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, anthropic-ai, Applebot-Extended — receive a 200 with full HTML content (135,792 bytes, identical to browser baseline) from Cloudflare. The only blocked bot is Bytespider (TikTok's crawler, 403). The robots.txt has no AI-specific directives — just a generic User-agent: * disallowing /wp-admin/, /wp-login.php, /?p=, and /search/. No bot is blocked from any substantive content. The site runs on WP Engine behind Cloudflare with x-frame-options: SAMEORIGIN but no HSTS, CSP, or permissions policy headers. Pages render server-side HTML — no JS-rendering risk for AI crawlers.

llms.txt and Sitemap Mismatch

The /llms.txt file exists (6,204 bytes, generated by Yoast SEO v26.1.1) and lists pages, posts, resources, newsroom items, and events — a strong signal. However, the sitemap link inside it points to https://leandata.lndo.site/sitemap_index.xml — a local development domain that does not resolve publicly. The production sitemap lives at https://www.leandata.com/sitemap_index.xml (which works and contains 6 sub-sitemaps). An AI crawler consuming the llms.txt would follow the dev URL and hit a dead end. Separately, https://leandata.com/sitemap.xml returns 404 — only the sitemap_index.xml variant works.

Cold-Knowledge Gap

The LLM's prior knowledge describes LeanData as a lead-to-account matching and routing tool focused on deduplication and attribution — a functional, plumbing-layer product. The site itself positions LeanData as an "AI GTM Orchestration" platform — a strategic layer orchestrating AI agents, human sellers, and systems across the full revenue lifecycle. The gap is significant: the cold model knows nothing about the AI-orchestration narrative, the Buying Groups product, the BookIt scheduling suite, or the OpsStars conference. The site's H1 ("AI-Powered GTM That Works") and its emphasis on "AI agents as first-class participants in GTM motion" are entirely absent from the model's prior.

Schema Posture

The homepage and most pages carry WebPage, WebSite, and Organization schema with sameAs links to Facebook, X, and LinkedIn. The pricing page is the only page with a FAQPage schema (4 questions about pricing structure, standalone purchases, enterprise support, and implementation). No Product or SoftwareApplication schema exists anywhere — surprising for a SaaS platform with named editions (Standard, Advanced, Premium, Enterprise). No Review or AggregateRating schema despite prominent display of G2, AppExchange, TrustRadius, and Gartner Peer Insights badges on the pricing page. No HowTo, Article, or VideoObject markup on the blog or resource pages.

External Signals

The site claims 1,000+ customers and displays logos of Uber, Palo Alto Networks, and others. The newsroom shows recent activity: a 2026 G2 Best Sales Product Award, the OpsStars 2026 standalone conference launch, and an HBR research collaboration. DNS records show Google Workspace (MX), HubSpot email, and Intacct — a mid-to-enterprise SaaS stack. No recent funding announcements or valuation data surfaced in search. The blog is actively maintained with posts dated into Q2 2026. The resource center lists 429 resources — a substantial content library that AI crawlers can fully access.

Findings

1. llms.txt sitemap link points to local development domain High

   The llms.txt file references https://leandata.lndo.site/sitemap_index.xml, a local development domain that does not resolve publicly. AI crawlers following this link will encounter a dead URL, reducing the effectiveness of the llms.txt signal.

   What to change: Update the sitemap URL in llms.txt to https://www.leandata.com/sitemap_index.xml.

2. Cold LLM knowledge lacks AI GTM orchestration narrative High

   The LLM's prior knowledge describes LeanData as a lead-to-account matching and routing tool, missing the site's positioning as an AI GTM orchestration platform with AI agents, Buying Groups, BookIt, and OpsStars. This gap means AI assistants cannot accurately represent the current product story.

   What to change: Increase external signals (press releases, industry articles, social media) that reinforce the AI orchestration narrative to help LLMs update their knowledge.

3. No Product or SoftwareApplication schema on SaaS pages Medium

   Despite offering named editions (Standard, Advanced, Premium, Enterprise), the site lacks Product or SoftwareApplication schema. This prevents AI crawlers from understanding the software product structure and pricing tiers.

   What to change: Add Product and SoftwareApplication schema to the pricing page and product pages, including edition names, descriptions, and pricing.

4. No Review or AggregateRating schema despite third-party badges Medium

   The pricing page displays G2, AppExchange, TrustRadius, and Gartner Peer Insights badges but lacks corresponding Review or AggregateRating schema. This misses an opportunity to surface social proof in AI-generated answers.

   What to change: Add AggregateRating schema with rating values and review counts from the displayed badges.

5. No Article or VideoObject schema on blog and resource pages Medium

   The blog and resource center contain substantial content but lack Article, BlogPosting, or VideoObject schema. This reduces the chances of content appearing in rich results or being correctly parsed by AI crawlers.

   What to change: Add Article schema to blog posts and VideoObject schema to any video content on resource pages.

6. Sitemap at /sitemap.xml returns 404 Low

   The standard sitemap URL https://leandata.com/sitemap.xml returns a 404 error. Only the index variant at /sitemap_index.xml works. This may confuse some crawlers that expect the standard path.

   What to change: Redirect /sitemap.xml to /sitemap_index.xml or create a sitemap index at the standard path.

7. Missing HSTS and security headers Low

   The site lacks HSTS, Content-Security-Policy, and Permissions-Policy headers. While not directly impacting AI crawlers, this reduces trust signals and may affect ranking in security-conscious contexts.

   What to change: Add HSTS header with a max-age of at least one year and consider adding CSP and Permissions-Policy headers.

What's working

• All major AI crawlers receive full HTML content — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, and others receive a 200 with full HTML content. No AI-specific blocks in robots.txt, and pages render server-side HTML, ensuring AI crawlers can index all content.
• llms.txt file exists with comprehensive page listing — The /llms.txt file is present (6,204 bytes) and lists pages, posts, resources, newsroom items, and events, providing a strong signal to AI crawlers about important content.
• FAQPage schema present on pricing page — The pricing page includes FAQPage schema with 4 questions about pricing structure, standalone purchases, enterprise support, and implementation, helping AI crawlers understand common queries.
• Organization schema with social media sameAs links — The homepage and most pages carry WebPage, WebSite, and Organization schema with sameAs links to Facebook, X, and LinkedIn, providing structured identity signals.
• Active blog and large resource library fully accessible — The blog is actively maintained with posts into Q2 2026, and the resource center lists 429 resources. All content is server-side rendered and accessible to AI crawlers.
• Newsroom shows recent awards and events — The newsroom features a 2026 G2 Best Sales Product Award, OpsStars 2026 conference launch, and HBR research collaboration, providing fresh external signals.