livelyme.com — AI Site Grade

Analysis

I have enough data. Let me write the audit.

Lively's AI crawlers get full 200 access with rich content, yet the cold LLM knowledge gap is extreme — a frontier model describes the site as possibly "inactive, low-traffic, or recently launched" despite Lively being a funded HSA/flexible-benefits platform with 664+ indexed pages, a 2026 AI-in-HR report, and a dedicated AI-bundle product page.

Crawler Access

All major AI crawlers — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, anthropic-ai, Applebot-Extended, Bytespider — receive a full 200 response with identical byte size (840,197) to browser traffic. No UA-based blocking exists. The site runs on Netlify with a strict CSP and HSTS preload. The robots.txt is minimal: a single User-agent: * disallowing only /_next/ (Next.js internals), with no AI-bot-specific rules. No llms.txt exists (returns 404). The sitemap index contains 5 sub-sitemaps covering ~664 URLs across pages, blog posts, resources, and FSA content.

Cold-Knowledge Gap

A frontier LLM queried cold about livelyme.com returned: *"I do not have specific, verifiable information... The domain could be inactive, low-traffic, or recently launched."* When queried as "Lively HSA," the model recalled the company was founded in 2016, offers fee-free HSAs with Schwab/TD Ameritrade investment options, and has positive Trustpilot/G2 reviews. The site itself is far more evolved — Lively now positions itself as a full-stack flexible-benefits platform (HSA, FSA, HRA, LSA, MTA, COBRA, Commuter) with a proprietary AI bundle (LivelyIQ chatbot, Smart Claims, File Sync), a 2026 AI in HR Report, and a CEO-authored blog on AI reshaping health benefits. The cold model knows nothing about the AI product line, the expanded benefit categories, or the broker/employer focus.

Schema Posture

Zero JSON-LD structured data was found on any page inspected — homepage, pricing, features, employers, brokers, platform, AI-bundle, or blog. No Organization, Product, FAQPage, BreadcrumbList, WebSite, or HowTo schema exists anywhere. This is a critical gap: the site has FAQ sections on multiple pages (pricing, employers, brokers) with no FAQPage markup, and a pricing page with a fee table that lacks Product or PriceSpecification schema. AI engines crawling the site get rich visible text but zero semantic scaffolding to extract entities, relationships, or answer-format content.

Content & Positioning

The homepage and key pages are text-rich (1,000–1,800 words each) with clear H1/H2/H3 structure, FAQ sections, customer testimonials, and comparison language. The blog publishes forward-dated articles (April 25, 2026) about AI in health benefits — content that is timely and authoritative but invisible to AI knowledge bases because of the schema gap. The site prominently features an "AI Benefits Bundle" page, an "Employer Loss Calculator," and a "White-Label Guide" for brokers. The gap between what the site actually says (AI-forward, multi-product benefits platform) and what AI models know cold (basic HSA provider, possibly inactive) is the single largest AI-visibility problem.

External Signals

DNS TXT records reveal verification tokens for Anthropic (anthropic-domain-verification-sj92kj), Apple, Adobe, Jamf, Miro, Segment, HubSpot, and Zendesk — indicating active integration with the Anthropic ecosystem (likely for the AI chatbot). The site links to Trustpilot and G2 review pages. However, web searches for "Lively HSA reviews 2024 2025" and "Lively HSA NerdWallet" returned zero results, suggesting the site's off-domain citation footprint is thin relative to its content investment.

Findings

1. Zero JSON-LD structured data on any page High

   No page inspected contains JSON-LD markup for Organization, Product, FAQPage, BreadcrumbList, or any other schema type. This prevents AI crawlers from extracting entities, relationships, and answer-format content.

   What to change: Add JSON-LD structured data to every page: Organization schema on the homepage, Product and PriceSpecification on pricing, FAQPage on pages with FAQ sections, and BreadcrumbList site-wide.

2. Frontier LLM describes site as possibly inactive despite rich content High

   A cold query about livelyme.com returned that the domain could be 'inactive, low-traffic, or recently launched,' even though the site is a funded HSA/benefits platform with 664+ indexed pages, an AI bundle, and a 2026 AI-in-HR report.

   What to change: Implement structured data and build off-domain citations (press releases, guest posts, review profiles) to improve LLM knowledge base inclusion.

3. No llms.txt file published Medium

   The site returns a 404 for /llms.txt, missing an opportunity to provide AI crawlers with a curated summary of key pages and content.

   What to change: Create an llms.txt file listing the most important pages (homepage, pricing, features, AI-bundle, blog) with brief descriptions.

4. Thin off-domain citation footprint for AI visibility Medium

   Web searches for 'Lively HSA reviews 2024 2025' and 'Lively HSA NerdWallet' returned zero results, indicating the site is rarely cited by authoritative third-party sources, which limits LLM knowledge inclusion.

   What to change: Proactively earn citations from reputable finance/HR publications (e.g., NerdWallet, Investopedia, SHRM) and encourage customer reviews on G2 and Trustpilot.

5. FAQ sections lack FAQPage structured data Medium

   Multiple pages (pricing, employers, brokers) contain FAQ sections but no FAQPage JSON-LD markup, preventing AI from extracting Q&A pairs for direct answers.

   What to change: Add FAQPage schema to all pages with FAQ sections, marking up each question and answer.

6. Pricing page lacks Product and PriceSpecification schema Medium

   The pricing page displays a fee table but has no Product or PriceSpecification structured data, making it harder for AI to extract pricing information.

   What to change: Add Product and PriceSpecification schema to the pricing page, marking up each plan and its fees.

7. Homepage missing Organization schema Medium

   The homepage does not include Organization structured data, which would help AI engines confirm the company's name, logo, description, and social profiles.

   What to change: Add Organization schema to the homepage with name, URL, logo, description, and sameAs links.

8. No BreadcrumbList schema site-wide Low

   The site does not implement BreadcrumbList structured data, which helps AI crawlers understand site hierarchy and navigation.

   What to change: Add BreadcrumbList schema to all pages to indicate page hierarchy.

9. Zero web search results for brand queries Medium

   Searches for 'Lively HSA reviews 2024 2025' and 'Lively HSA NerdWallet' returned no results, indicating low search engine visibility for key brand terms.

   What to change: Improve SEO and earn backlinks from authoritative sites to increase search visibility.

What's working

• All major AI crawlers receive full 200 access — GPTBot, ClaudeBot, PerplexityBot, and other AI crawlers all get a 200 response with full content, no UA-based blocking, and no AI-specific disallow rules.
• Key pages are text-rich with clear structure — Homepage and landing pages contain 1,000–1,800 words each with clear H1/H2/H3 hierarchy, FAQ sections, and customer testimonials, providing substantial content for AI crawlers.
• Blog publishes forward-looking AI-in-HR content — The blog features articles dated April 2026 about AI in health benefits, positioning Lively as a thought leader in the space.
• Dedicated AI Benefits Bundle page exists — The site has a full page describing the Lively AI Benefits Bundle, including LivelyIQ chatbot, Smart Claims, and File Sync, demonstrating AI-forward positioning.
• Anthropic domain verification token present — DNS TXT records include an Anthropic verification token, indicating active integration with Anthropic's ecosystem, likely for the AI chatbot.
• Sitemap index covers 664+ URLs across multiple content types — The sitemap index contains 5 sub-sitemaps covering pages, blog posts, resources, and FSA content, ensuring good crawl coverage.
• robots.txt allows all AI crawlers with no disallow rules — The robots.txt file has a single User-agent: * rule that only disallows /_next/, leaving all AI crawlers unrestricted.