kiihealth.com — AI Site Grade

Analysis

The cold LLM knows a completely different company — a US digital wellness app acquired by Virgin Pulse — while the actual site is a Canadian B2B workplace health navigation provider operating under CloudMD.

Crawler Access

All major AI crawlers — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, anthropic-ai, Applebot-Extended — receive a full 200 response with identical content to a browser baseline (434 KB). Bytespider is the sole bot blocked (403) by Cloudflare. The robots.txt is a bare Yoast default (User-agent: * Disallow:) with no AI-bot-specific rules, a Crawl-delay: 10, and a reference to sitemap_index.xml. No llms.txt exists (404). The site runs on WordPress on WP Engine behind Cloudflare, serving static HTML with no JS-rendering risk — all bots see the full page content.

Cold-Knowledge Gap

The LLM describes KiiHealth as a US-based digital wellness app (launched 2013 as "Kii", acquired by Virgin Pulse/Personify Health in 2021) offering a mobile app with wearables integration, nudges, and coaching for employers and health plans. The actual site is a Canadian healthcare services company (CloudMD Software & Services Inc.) that provides workplace health navigation, health assurance coaching, disability management, occupational health, and independent medical assessments — no mobile app, no wearables, no consumer product. The site has operated under the kiihealth.com domain since at least 2022, but the Wayback Machine shows the domain was a parked landing page as recently as December 2021. The LLM's prior is entirely about a defunct or rebranded entity that shares the name but not the business.

Schema Posture

Every page carries JSON-LD via Yoast SEO, but the Organization schema consistently names "CloudMD Software & Services Inc." with alternateName "CloudMD" — not "Kii Health". The homepage WebPage schema has datePublished: 2022-09-28 and a futuristic dateModified: 2026-02-06. No LocalBusiness, MedicalBusiness, HealthInsurancePlan, or FAQPage schema types are present despite the site offering medical navigation, occupational health, and disability management services. No meta descriptions exist on any page — every page has an empty description meta tag.

External Signals

Web searches for "Kii Health", "kiihealth.com", and "CloudMD Kii Health" return zero indexed results across multiple queries. The site has no press mentions, no Reddit threads, no review pages, no third-party articles discoverable via search. The only external links on the site point to kiihealth.ca (a JS-shell login portal), cirahealth.ca, refunction.ca, imdhealth.com, and a LinkedIn company page. The brand has essentially no external citation footprint — AI engines have no third-party signals to corroborate or describe the business.

Content & Structure

The site has ~25 indexed pages with a blog of ~60+ posts (mostly employee spotlights and mental health Q&As). Content is well-written, outcome-focused, and uses consistent "Health Assurance" terminology. However, the /connected-care/ URL redirects to /connected-care/health-assurance/ rather than serving as a proper service overview hub. The blog has no category-specific sitemaps for AI crawlers to discover topical depth. No FAQ schema, comparison tables, or structured answer-format signals exist on any page — despite the site offering multiple comparable service lines.

Findings

1. LLM knowledge describes a different company than the actual site High

   The LLM's prior knowledge describes KiiHealth as a US digital wellness app acquired by Virgin Pulse, while the actual site is a Canadian B2B workplace health navigation provider under CloudMD. This mismatch causes AI engines to fabricate or misattribute facts about the company.

   What to change: Publish an llms.txt file with a clear brand description and disambiguation statement. Ensure the homepage and about page explicitly state the company's current identity and relationship to CloudMD.

2. No external web presence or third-party citations High

   Web searches for 'Kii Health', 'kiihealth.com', and related terms return zero indexed results. The brand has no press mentions, reviews, or third-party articles, leaving AI engines without corroborating signals.

   What to change: Build an external citation footprint through PR, guest posts, industry listings, and review platforms. Ensure the site is indexed by Google and other search engines.

3. No schema types for medical or health insurance services High

   Despite offering medical navigation, occupational health, and disability management, the site lacks LocalBusiness, MedicalBusiness, HealthInsurancePlan, or FAQPage schema. Only Organization schema is present, which names 'CloudMD Software & Services Inc.' rather than 'Kii Health'.

   What to change: Add LocalBusiness, MedicalBusiness, and HealthInsurancePlan schema to relevant service pages. Include FAQPage schema for common questions. Ensure the Organization schema uses 'Kii Health' as the primary name.

4. All pages have empty meta description tags Medium

   Every page on the site has an empty description meta tag, which reduces click-through rates from search results and limits the context available to AI crawlers.

   What to change: Add unique, descriptive meta descriptions to every page, incorporating target keywords and a clear value proposition.

5. No llms.txt file for AI crawler guidance Medium

   The site returns a 404 for llms.txt, missing an opportunity to provide AI engines with a curated overview of the company, its services, and disambiguation from the defunct US brand.

   What to change: Create an llms.txt file that describes the company, lists key pages, and includes a disambiguation statement to correct the cold-knowledge gap.

6. Service overview page redirects to a subpage Medium

   The /connected-care/ URL redirects to /connected-care/health-assurance/ instead of serving as a standalone overview of all services, reducing crawl efficiency and diluting topical authority.

   What to change: Make /connected-care/ a proper hub page that summarizes all service lines and links to subpages, rather than redirecting.

7. No FAQ schema on blog or service pages Medium

   Despite a blog with Q&A-style posts and service pages that answer common questions, no FAQPage schema is used, missing a chance to appear in rich results and provide direct answers to AI crawlers.

   What to change: Add FAQPage schema to blog posts and service pages that answer common questions. Consider creating a dedicated FAQ page with structured data.

8. Blog lacks category-specific sitemaps Low

   The blog has no category-specific sitemaps, making it harder for AI crawlers to discover topical depth and understand content organization.

   What to change: Add category-specific sitemaps for the blog to help crawlers discover and prioritize content by topic.

9. Bytespider crawler blocked by Cloudflare Low

   Bytespider receives a 403 response, preventing ByteDance's AI from indexing the site. While not a major crawler, this blocks potential visibility in Chinese AI ecosystems.

   What to change: Allow Bytespider access if the site targets Chinese markets or wants broader AI visibility.

What's working

• All major AI crawlers receive full access — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, and others get a 200 response with identical content to a browser, ensuring AI engines can index the site's content.
• Server-rendered HTML visible to all crawlers — The site serves static HTML with no JavaScript rendering required, so all crawlers see the full page content without execution barriers.
• Robots.txt allows all crawlers with no AI-bot blocks — The robots.txt has a permissive User-agent: * Disallow: rule with no AI-bot-specific restrictions, ensuring all crawlers can access the site.
• Well-written, outcome-focused content — The site's content is well-written, outcome-focused, and uses consistent 'Health Assurance' terminology, providing clear value propositions for both users and AI crawlers.
• JSON-LD Organization schema present on all pages — Every page includes JSON-LD Organization schema via Yoast SEO, providing structured identity data to search engines and AI crawlers.
• Reliable hosting on WP Engine with Cloudflare CDN — The site runs on WordPress on WP Engine behind Cloudflare, ensuring fast load times and DDoS protection, which benefits crawler performance.