NorthCore Labs

Med spa schema markup and llms.txt: what your site should tell Google and the AI assistants.

Schema markup is structured data on each page of a practice's website that states, in a form machines read, what the page is about. For a practice that means a medical business, its services, hours, address and phone. llms.txt is a proposed convention: a plain-text summary of the practice at the root of the site, written so an assistant that looks for it can read the practice in one pass. Together they say what you do, where you are and when you are open, the same way on every page. This guide lists the pieces, where each goes, and how to check it.

Updated 2026-10-26

Structured data states facts; it does not rank anything on its own. It tells a crawler 'this page is a medical business at this address, open these hours, offering these services, with these questions answered.' What any engine does with that statement is the engine's business, and it changes without notice. This page describes what the markup says, not what it earns. One test: a machine that reads only the markup should be able to describe your practice correctly. If the markup says more than the page shows, it fails that test.

The pieces a practice site should carry

  • A medical business type on every page, with the practice name, street address, phone, opening hours, the URL and the geo coordinates, identical everywhere. Which business type fits your practice is a question of what you are licensed as; confirm with counsel before you choose it.
  • The service list: each treatment you offer, named the way a patient types it, with a link to its page.
  • A page per treatment, with the treatment named in the heading, the questions patients ask answered in plain text, and FAQ markup carrying the same questions and answers.
  • Review markup only where the platform's rules allow it, and only for reviews that appear on the page itself; check the platform's current policy before adding any.
  • A breadcrumb trail on every page, so the machine knows how the site is organized.
  • llms.txt at the site root.

What llms.txt is and what to put in it

llms.txt is a plain-text file at the root of the site, like robots.txt, written for AI assistants rather than crawlers. In a few hundred words it says who the practice is, where it is and who the providers are. It says what the practice offers, what it does not, how to book and where the detailed pages live. Write it the way the desk would answer a new caller: the name, the city, the treatments, the hours, the phone, and a line per treatment page. Keep it short and current, and never write anything into it that is not also on the site; an assistant that quotes the file should be quoting the practice. Which assistants read it changes without notice; it costs an hour and says nothing the site does not.

One name, one address, one phone, everywhere

The name, address and phone must match, character for character, on every page of the site, in the markup, in llms.txt, on the Google profile, and on every directory that lists you. 'Suite 200' on one and 'Ste. 200' on another is a mismatch a machine may read as two businesses, and nobody can tell you which machine will. Pick one spelling of the name, one format for the address, one phone with the same punctuation, and write it down. Every new listing copies that line.

Where each piece goes and what it tells the machines

PieceWhat it tells the machinesWhere it goes
Medical business typeWhat kind of business this is, its name, address, phone, hours and locationEvery page, in the head, identical
Service listThe treatments offered, by name, each with its own pageThe home page and the services page
Treatment page with FAQ markupWhat this one treatment is, and the questions patients ask about it, answeredOne page per treatment, markup matching the visible text
Review markupA review that appears on this page, who wrote it and the ratingOnly where the platform's current policy allows it
BreadcrumbsWhere this page sits in the siteEvery page below the home page
llms.txtA plain-language summary of the practice for an assistant to read in one passThe site root, beside robots.txt

How to check it this week

  1. Open the home page and one treatment page in Google's rich results test and read what it found. Every field it shows should match what a patient sees on the page.
  2. Open the raw markup and compare the hours, the phone and the address to the Google profile, line by line.
  3. Load llms.txt in a browser at your own domain. If it is not there, write it; if it is, read it as a new caller would.
  4. Pick three directories that list the practice and compare the name, address and phone to your written line.
  5. Put the check on the calendar for the first Monday of each month. Hours change; the markup forgets.

The mistakes that undo it

  • Marking up what is not on the page: a review the page does not show, a service you stopped offering, a question the page never answers.
  • Stale hours. The holiday hours went into the profile and never into the markup, so two sources now disagree.
  • A different business type on different pages, or the home page claiming one address and the contact page another.
  • Treatment pages that name a prescription treatment with claims the state does not allow in advertising; what a page may say about a prescription treatment is for counsel to confirm.
  • Copying another practice's markup and leaving their phone in it.

What to do next

NorthCore's Get found first solution builds the structured data, the treatment pages and the llms.txt summary on your site, and tracks where you show up on the same dashboard as everything else. Scoped in writing and covered by the promise on this site: results in 90 days, or we keep working until you have them.

Have this built for your practice.

Get found first is the solution this guide belongs to, one of ten jobs in the system we build and run on the software you already use. Scoped in writing. Results in 90 days, or we keep working until you have them.

Questions people ask.

Does schema markup get my med spa ranked higher?

The markup states what the page is about in a form machines read; what any engine does with that statement is up to the engine and changes over time. Build it so a machine reading only the markup would describe your practice correctly, and leave the ranking claims to people selling them.

Can my web designer add this, or do I need a developer?

Any competent site builder can add the business block, the breadcrumbs and the FAQ markup, and anyone can write llms.txt in a text editor. The hard part is keeping the hours, the phone and the service list identical everywhere, every month.

Should I add review markup?

Only where the platform whose reviews you are showing allows it under its current policy, and only for reviews that appear on that page. Check the policy before you add it and again when it changes.

What goes in llms.txt that is not already on the site?

Nothing new. It is the site, summarized in plain text for an assistant to read in one pass: who you are, where, what you offer, how to book, and where each treatment page lives. If the file says something the site does not, fix the site or the file.

Bring the system into your practice.

Walk us through how the practice runs today. We show you what we would build first and how fast. If nothing here fits, we say so on the call.

No card, no contract
A calendar invite and a Zoom link the moment you book.
Prefer email?
admin@northcorelabs.io
NorthCore Labs LLC
7901 4th St N, Ste 300, St. Petersburg, FL 33702