What a build includes

Found, including by AI assistants

Patients no longer only search. They ask an assistant, and the assistant answers from what it can read.

The facts about your practice, the services, the locations, the people, are held in one place and published as structured data with stable identifiers, so a search engine or an assistant reads one consistent account rather than guessing from page text. Machine readable endpoints and an llms.txt file make the same facts available to assistants that look for them.

Enquiries are measured with first party analytics on your own domain, so you keep the data and no third party is tracking your patients to sell them something. The monthly report under Care shows enquiries by source, which is the number that tells you whether any of this is working.

What you get

• Entity first structured data generated from your own facts, not hand written per page
• Stable identifiers, so the same practice is not read as three different ones
• An llms.txt file and machine readable data endpoints
• First party analytics on your domain, with no third party tracking by default
• A monthly one page report showing enquiries by source

What it does not do

• We do not promise a position in search results or in an assistant's answer, and nobody can.
• What an assistant says is decided by the assistant. What we control is whether it can read you accurately.
• A monthly search program is Growth, not Build. Build makes the site readable; Growth works it.

Where it sits. Structured data is listed under Essential. The AI search readiness layer is Signature. An MCP endpoint is Platform. See the three build tiers.

Related: Growth, the monthly search program, Check your website, free.