Skip to content
AEOprobe
Healthcare content and crawler access

AEO for Healthcare

Review public health information for accurate authorship, medical review, access and technical clarity.

Updated

AI Overview landscape

In its September 2025 study, Conductor reported AI Overviews on 26% of Healthcare Providers & Services keywords. It reported them on 37% of Healthcare Equipment & Supplies keywords. These are historical figures from a keyword sample. They are not a current rate for every healthcare search. They are not evidence that your site will be cited.

Source: Conductor AI Overview study, September 2025 (opens in a new tab).

Recommended schemas

MedicalWebPage
A public medical pageIts reviewedBy property can name the real reviewer.
MedicalEntity subtypes
The medical subject the page is about
Person or Organization
Real authors and providers

A schema type does not certify medical quality, credentials or legal compliance.

Use only markup that applies and matches content visitors can see.

Google FAQ rich results stopped appearing from 7 May 2026.

Write helpful Q&A on the page and do not promise a rich result.

Common AEO issues

Common AEO issues, their impact and fixes
IssueImpactFix
Authorship or medical review is unclearImpactReaders cannot assess who prepared or reviewed the information and when.FixShow real author and reviewer details, relevant credentials, sources and actual review dates. Never invent professional qualifications.
Markup describes the wrong entityImpactA reviewer, a provider and a medical subject can get mixed up.FixAttach reviewedBy to WebPage or MedicalWebPage. Describe authors, organizations and medical subjects each as its own entity of the right type.
Public and private content boundaries are unclearImpactA crawler policy alone does not protect patient or account information.FixReview public material before you publish it. Protect private data with authentication and authorization. Get the appropriate privacy or compliance review.
Patient information is hard to navigateImpactReaders may struggle to locate the scope, evidence and limitations of an explanation.FixUse clear headings, accessible text and accurate visible questions and answers. Have qualified reviewers assess medical accuracy.

Key tools

Step-by-step guide

  1. 1

    Define the public review scope

    Select public education and provider pages. Exclude private patient, appointment and account information from the public audit.

  2. 2

    Review publication and access boundaries

    Decide which uses of your public content you intend to allow.

    • Check each relevant crawler’s current documentation.
    • Search and training bots have different roles. For example, OAI-SearchBot is for search and GPTBot is for training.
    • Check robots.txt and hosting or firewall access separately.
    • Protect private content with authentication and authorization. Robots.txt is not access control.
  3. 3

    Verify authors, reviewers and sources

    Use real credentials and actual review dates. Ask a qualified reviewer to assess the health information and its limitations.

  4. 4

    Check applicable medical-page markup

    Describe the actual page and entities. Use reviewedBy on MedicalWebPage only for a real reviewer. Validate the markup against supported vocabulary.

  5. 5

    Prepare the technical repair, then publish it

    Work from the to-do for the finding and publish the edits. Medical accuracy and privacy need separate human review.

  6. 6

    Recheck without overstating acceptance

    A technical recheck can confirm an observable change. It does not certify medical accuracy, privacy compliance or AI citation selection.

From a finding to a checked repair

The free audit covers up to 3 pages and needs no sign-up. A saved-site audit costs 20 credits. It covers up to 10 pages on Free, 50 on Watch and 100 on Pro. A free account shows 5 findings for each site, and a paid plan shows them all.

A saved-site finding becomes a to-do with the evidence, what to change and how to check it. You or your developer publish the edits, then run a scoped technical recheck. Claude Code and Codex can work in the same flow. After a coding agent reports a fix, its recheck runs by itself within your weekly credit limit. Every other action that spends credits asks for your confirmation first.

AEOprobe plans are Free at €0/month, Watch at €7/month and Pro at €21/month. Credit packs add extra credits to a Watch or Pro plan. Only customers with an active Watch or Pro plan can buy them. Credits that expire soonest are used first, usually the monthly ones. Bought credits stay valid for 12 months after purchase, even if your plan ends. They can still pay for audits and checks after your plan ends. They do not open the full lists without an active Watch or Pro plan. A page capture or recheck costs 1 credit. Your account shows what you can buy. See plans and credits and the coding-agent workflow.

Sources and technical guidance

Checked Oct 2026

Questions

Can robots.txt protect patient information?

No. Robots.txt is crawler guidance, not access control. Protect private data with authentication and authorization. Review public content with the appropriate privacy and clinical owners.

Does structured data guarantee AI search inclusion?

Google does not require special schema for generative search. Markup does not guarantee a citation.

What does AEOprobe check?

The audit checks robots.txt policies for AI crawlers and other technical page findings. For structured data it reads JSON-LD only. See the audit methodology.

How do I turn a finding into a published fix?

A saved-site finding becomes a to-do with what to change and how to check it. You publish the edits, then run a recheck. See the steps and costs on this page.

Check what AI crawlers can actually reach

Run a free audit to find public crawler, indexing, markup, and page-structure issues.

Run free audit