medbridge.com — AI Site Grade

Analysis

Medbridge.com AI-Visibility Audit

The site's core course catalog — its most valuable content for AI engines — is a JavaScript shell that returns only 36 words of visible text to crawlers, while the homepage and all marketing pages serve full HTML to every AI bot without restriction.

Crawler Access

All 11 AI bot user-agents tested (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, Bytespider, Applebot-Extended, anthropic-ai, Perplexity-User, and a browser baseline) receive a 200 status with identical 266KB payloads from the homepage. Cloudflare terminates the requests but does not discriminate by UA. The robots.txt contains a single User-agent: * rule with no AI-bot-specific directives — no mention of GPTBot, ClaudeBot, or any other crawler. The llms.txt returns a 404, meaning no AI-friendly content map exists. However, the /educate/courses page — the gateway to 2,500+ courses — is a thin JS shell (36 words extracted) that renders no course listings to crawlers. The courses sitemap lists 1,400+ individual course URLs, but those pages likely suffer the same JS-rendering problem.

Schema Posture

Every major page carries a single WebPage JSON-LD block with Organization publisher metadata. No Product, Course, FAQPage, MedicalWebPage, or HowTo schema is present anywhere on the homepage, educate, care, or pricing pages. The pricing page has a comparison table rendered in HTML but no Product or Offer schema. The /resource-center and /educate/courses pages have zero JSON-LD at all. Given the site's 2,500+ accredited courses, the absence of Course schema is a significant gap for AI engines trying to understand the catalog.

Cold-Knowledge Gap

The LLM knows Medbridge as a continuing education platform for PTs, OTs, and SLPs — founded in 2011, APTA/ASHA-accredited, video-based CE courses. This matches the site's "Educate" pillar well. But the model has no awareness of Medbridge's "Care" pillar: Remote Therapeutic Monitoring (RTM), digital MSK Pathways, motion capture AI, patient-reported outcomes, or the "One Care" platform. The site has invested heavily in positioning itself as a hybrid-care platform (the /care page is 3,244 words with detailed patient scenarios), but cold LLM knowledge still describes a pure CE company. The AI-assisted motion capture (Rehab Boost acquisition, October 2024) and the "Care Intelligence Loop" (May 2026) are entirely absent from the model's prior.

External Signals

The site links to Capterra, Software Advice, GetApp, Trustpilot, and app store review pages — all returning 4.7+ ratings. The newsroom lists press releases about the Rehab Boost acquisition, Epic/MyChart integration, CHAP verification, and the "One Care" platform launch. However, no third-party media coverage was found in search results — all press releases are self-published. The /solutions page returns zero words of visible content, suggesting it is also a JS-rendered shell.

Surprising Findings

The /blogqa path is explicitly disallowed in robots.txt — a QA system or internal tool that crawlers are blocked from. The dateModified fields on several pages show dates in 2026 (e.g., homepage 2026-05-13, about page 2026-05-14), indicating the site is publishing content with future timestamps or the CMS is misconfigured. The /educate/courses page is essentially invisible to crawlers despite being the most important content page on the site. The gap between the site's ambitious AI and hybrid-care narrative and what AI models know cold is the single largest visibility risk.

Findings

1. Course catalog renders as thin JavaScript shell to crawlers High

   The /educate/courses page, gateway to 2,500+ accredited courses, returns only 36 words of visible text to crawlers. The courses sitemap lists 1,400+ individual course URLs, but those pages likely suffer the same JS-rendering problem, making the core catalog invisible to AI engines.

   What to change: Implement server-side rendering or static generation for the course catalog pages so that course listings and metadata are present in the initial HTML payload.

2. No Course schema on any page despite 2,500+ accredited courses High

   Every major page carries only a WebPage JSON-LD block. No Course, Product, FAQPage, MedicalWebPage, or HowTo schema is present. The /resource-center and /educate/courses pages have zero JSON-LD at all. This prevents AI engines from understanding the catalog structure and surfacing course details in rich results.

   What to change: Add Course, Product, and FAQPage structured data to relevant pages, especially the course catalog and individual course pages.

3. LLMs have no awareness of Medbridge's Care pillar High

   Cold LLM knowledge describes Medbridge as a pure continuing education platform for PTs, OTs, and SLPs. The model has no awareness of the Care pillar: Remote Therapeutic Monitoring, digital MSK Pathways, motion capture AI, patient-reported outcomes, or the One Care platform. The /care page is 3,244 words with detailed patient scenarios, but this content is not being indexed or understood by AI engines.

   What to change: Ensure the Care pillar content is fully crawlable and indexed, and consider adding structured data (e.g., MedicalWebPage, Product) to help AI engines understand the offerings.

4. llms.txt returns 404, no AI-friendly content map exists Medium

   The standard llms.txt file, which provides a curated list of important URLs for AI engines, is missing (404). This means AI crawlers have no guidance on which pages are most valuable, reducing the likelihood of the site being used as a knowledge source.

   What to change: Create an llms.txt file listing key pages such as the course catalog, care overview, and resource center.

5. Solutions page returns zero visible words to crawlers Medium

   The /solutions page, which should describe Medbridge's product offerings, returns 0 words of visible content, indicating it is also a JS-rendered shell. This page is likely important for AI understanding of the product suite.

   What to change: Implement server-side rendering for the solutions page to ensure its content is visible to crawlers.

6. Pages contain future dateModified timestamps (2026) Medium

   The homepage and about page show dateModified values in 2026 (e.g., 2026-05-13), indicating either future-dated content or CMS misconfiguration. This can confuse crawlers and reduce trust in freshness signals.

   What to change: Correct the dateModified fields to reflect actual last-modified dates and ensure the CMS does not output future timestamps.

7. No third-party media coverage found in search results Medium

   Despite press releases about acquisitions and integrations, no independent news articles or reviews were found in web searches. All press coverage is self-published, limiting external validation signals for AI engines.

   What to change: Pursue earned media coverage and encourage third-party reviews to build external authority signals.

8. Blog QA path disallowed in robots.txt Low

   The /blogqa path is explicitly disallowed in robots.txt, blocking crawlers from accessing what appears to be a QA system or internal tool. If this contains valuable content, it is hidden from AI engines.

   What to change: Review the /blogqa path and either remove the disallow rule if the content is public, or ensure it is not needed for AI visibility.

What's working

• Homepage serves full HTML to all AI bots without restriction — All 11 tested AI bot user-agents receive a 200 status with identical 266KB payloads from the homepage. No bot-specific blocking or cloaking is applied, ensuring the homepage content is fully accessible to crawlers.
• Robots.txt does not block any AI bots — The robots.txt file contains a single User-agent: * rule with no AI-bot-specific directives, meaning no AI crawlers are explicitly blocked. This is a positive baseline for crawlability.
• WebPage JSON-LD with Organization metadata on key pages — Every major page carries a single WebPage JSON-LD block with Organization publisher metadata, providing basic structured data for search engines.
• Care page provides 3,244 words of detailed patient scenarios — The /care page contains extensive content describing Remote Therapeutic Monitoring, digital MSK Pathways, and patient outcomes, which is valuable for AI understanding if properly indexed.
• Blog includes AI-focused Q&A with Head of AI — The blog contains a detailed Q&A about the future of AI at Medbridge, demonstrating thought leadership and providing content that can help AI engines understand the company's AI initiatives.
• Newsroom lists press releases about acquisitions and integrations — The newsroom page contains press releases about the Rehab Boost acquisition, Epic/MyChart integration, CHAP verification, and One Care platform launch, providing authoritative self-published content.
• External review sites show 4.7+ ratings — The site links to Capterra, Software Advice, GetApp, Trustpilot, and app store review pages, all returning 4.7+ ratings, providing positive social proof.