lyrahealth.com — AI Site Grade

Analysis

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

The most striking finding is the /about/ page returning 0 bytes — a completely empty page that's linked from the FAQ and sitemap. Combined with the missing llms.txt, no AI bot rules in robots.txt, and the cold-knowledge gap around clinician reimbursement criticism, this is a rich audit.

---

Lyra Health AI-Visibility Audit

The /about/ page — a top-level page linked from the FAQ and included in the sitemap — returns zero bytes of content to both browser and bot crawlers, making it an invisible dead end for any AI engine trying to learn about the company's history, leadership, or founding story.

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 on the homepage — identical byte size to browser baseline (185KB). Only Bytespider is blocked (403 by Cloudflare). The robots.txt is minimal: a single User-agent: * rule disallowing /wp-admin/ and no AI-bot-specific directives whatsoever. No llms.txt exists (404). The site runs on WP Engine behind Cloudflare with HSTS and a frame-ancestors 'self' CSP. The sitemap.xml contains 828 URLs and is well-formed.

The Empty About Page

The /about/ page returns HTTP 200 with 0 bytes of body content from a browser fetch. GPTBot receives a 429 (rate-limited) on the same URL. This page is listed in the sitemap and linked from the FAQ page ("Learn more about us"). An AI engine that follows that link encounters a blank page or a rate-limit error — no leadership team, no founding story, no company history. This is a critical gap for any model trying to build a complete entity profile.

Cold-Knowledge Gap

The LLM prior knows Lyra Health as a $4.6B-valued company founded in 2015 by David Ebersman (ex-Facebook CFO), serving employers like Starbucks, Uber, and Salesforce. It also recalls clinician reimbursement criticism from 2023. The site itself makes no mention of the founding story, the CEO, the $900M+ funding, or any valuation. The clinician reimbursement controversy is entirely absent from the public-facing site. The cold model knows more about Lyra's corporate history and controversies than the site discloses.

Schema and Content Posture

The site uses JSON-LD WebSite, WebPage, Organization, and BreadcrumbList schema consistently across all pages, with a SearchAction potential action. The /faqs/ page correctly implements FAQPage schema with Question/Answer entities. However, the Organization schema lacks foundingDate, founder, sameAs links, description, or foundingLocation — all fields that would help AI engines build a richer knowledge graph entry. The homepage has a strong FAQ section with 6 questions, but no FAQPage schema on the homepage itself.

External Signals

The DNS TXT records reveal OpenAI domain verification (openai-domain-verification=dv-sX7KOtZ9xyvVDwdcfm44Ydrn) and Anthropic domain verification (anthropic-domain-verification-1nz9be=...), confirming Lyra has proactively registered with both major AI platforms for crawler authentication. The site also has Google Workspace mail (Google MX servers) and multiple Google Search Console verification tokens. No external review or press results surfaced in search for recent employer or clinician sentiment.

Surprising Contradictions

The /methodology/ URL redirects to /why-choose-lyra/ — a 301 that any AI crawler will follow, but the sitemap still lists /methodology/ as a canonical URL. The blog post "Introducing Lyra AI" linked from the Empower platform page returns a 404. The logo in the Organization schema references a 2026/02 dated path, suggesting the site is actively maintained with 2026 content, yet the /about/ page remains empty. The site heavily promotes "Lyra AI" and "Empower" platform as differentiators, but the cold LLM knowledge does not mention either product by name — a positioning gap the site's own content could close if AI crawlers could reliably ingest the /about/ page and blog content.

Findings

1. Empty /about/ page returns zero bytes to all crawlers High

   The /about/ page returns HTTP 200 with 0 bytes of body content to both browser and bot crawlers. GPTBot receives a 429 rate-limit error. This page is listed in the sitemap and linked from the FAQ, making it a dead end for AI engines seeking company history or leadership information.

   What to change: Populate the /about/ page with substantive content about the company's history, leadership, and mission. Ensure the page renders full HTML for all crawlers.

2. Missing llms.txt file Medium

   The site does not provide an llms.txt file, which is a standard way to guide AI crawlers to the most important pages and provide structured context.

   What to change: Create an llms.txt file at the root that lists key pages (e.g., /about/, /care/, /faqs/) and provides a brief summary of the site's content.

3. No AI bot directives in robots.txt Medium

   The robots.txt only contains a single User-agent: * rule disallowing /wp-admin/. No specific directives for AI crawlers like GPTBot, ClaudeBot, or Google-Extended are present, leaving crawler behavior to defaults.

   What to change: Add explicit allow/disallow rules for major AI crawlers to ensure they can access key pages and avoid rate-limiting issues.

4. Organization schema lacks founding date, founder, and sameAs links Medium

   The JSON-LD Organization schema is present but missing fields like foundingDate, founder, sameAs, and description. These fields help AI engines build a richer knowledge graph entry.

   What to change: Add foundingDate, founder, sameAs (e.g., Crunchbase, LinkedIn), and description to the Organization schema markup.

5. Homepage FAQ section lacks FAQPage schema Medium

   The homepage includes a FAQ section with 6 questions, but no FAQPage schema is applied. This reduces the chance of AI engines surfacing these Q&As in rich results.

   What to change: Add FAQPage schema markup to the FAQ section on the homepage.

6. Blog post about Lyra AI returns 404 Medium

   The blog post 'Introducing Lyra AI' linked from the Empower platform page returns a 404 error, breaking a key content path about the company's AI product.

   What to change: Restore the blog post or set up a 301 redirect to a relevant page.

7. Sitemap lists /methodology/ which redirects to /why-choose-lyra/ Low

   The sitemap includes /methodology/ as a canonical URL, but it redirects (301) to /why-choose-lyra/. This inconsistency can confuse crawlers and dilute link equity.

   What to change: Update the sitemap to use the final redirect target URL /why-choose-lyra/ instead of /methodology/.

8. Cold LLM knowledge lacks mention of Lyra AI and Empower products Medium

   The site heavily promotes Lyra AI and Empower platform, but the cold LLM knowledge does not mention these products by name. This indicates a positioning gap that the site's own content could close if AI crawlers could reliably ingest key pages.

   What to change: Ensure key product pages are crawlable and contain clear, structured descriptions of Lyra AI and Empower. Consider adding product schema markup.

What's working

• OpenAI and Anthropic domain verification records present — DNS TXT records include verification tokens for both OpenAI and Anthropic, indicating proactive registration with major AI platforms for crawler authentication.
• Consistent JSON-LD schema across pages — The site uses WebSite, WebPage, Organization, and BreadcrumbList schema consistently, with a SearchAction potential action on the homepage.
• FAQ page correctly implements FAQPage schema — The /faqs/ page uses FAQPage schema with Question/Answer entities, enabling rich results for AI engines.
• Homepage accessible to all major AI crawlers — All major AI crawlers receive a 200 with full HTML content on the homepage, with identical byte size to browser baseline.
• Well-formed sitemap with 828 URLs — The sitemap.xml is well-formed and contains 828 URLs, providing good coverage for crawlers.
• Customer stories page with substantive content — The Starbucks customer story page contains 905 words of detailed content, providing rich material for AI engines to understand the company's value proposition.