llms.txt for dental websites: what it is and whether you need one
By the FirstInChat team
Dental owners keep hearing about a new file called llms.txt. Some agencies treat it like a magic ticket into AI answers. Others ignore it. The useful middle path is boring and honest: understand what the file is, fix the site basics that actually matter, and do not confuse a proposed convention with a ranking guarantee.
This guide is for independent dental practices (and whoever updates your site). It covers what llms.txt is, how it relates to robots.txt, a labeled example for a fictional practice, sitemap and HTTPS basics, and how to add the file by platform. It is not medical advice. Check your state dental board's advertising rules before you publish claims. We are not giving legal advice.
Honest product note up front: FirstInChat's free audit today is a website readiness check plus a Google Gemini snapshot from built-in knowledge only (ungrounded: no live search; may be out of date; not AI Overviews or AI Mode). Grounded Gemini + Google Search comes later, with no date. We do not claim ChatGPT or Perplexity product results. We do not claim we score llms.txt as its own graded line item — we talk about site basics you control (HTTPS, crawl access, clear pages). Nobody can promise that adding llms.txt will make any AI assistant name your practice.
What llms.txt is (and what is still unproven)
llms.txt is a proposed plain-text file, usually placed at the root of a website (like https://www.yourpractice.com/llms.txt). The idea is to give large language models a short, curated map of the pages and facts you want them to notice — similar in spirit to how robots.txt speaks to crawlers, but aimed at AI systems that summarize the open web.
What is still unproven:
- There is no guarantee that major AI assistants read, prefer, or rank pages because of an llms.txt file.
- Support and behavior differ by tool and change over time.
- Treating llms.txt as a paid "AI ranking" lever is marketing theater.
Think of it as an optional, low-cost clarity file — useful if you want one place that points to your services, contact, and FAQ pages in plain text. It is not a substitute for a clear website, a tidy Google Business Profile, real reviews, or schema markup.
If someone sells you "AI domination" that hinges only on uploading llms.txt, walk away.
robots.txt and AI crawlers: don't block them by accident
Before you obsess over a new file, check the old one.
robots.txt tells crawlers which paths they may fetch. Practices (or security plugins) sometimes add aggressive "block everything" rules that also stop useful bots — including ones that help search engines and some AI systems discover public pages.
Practical checks:
- Open
https://www.yourpractice.com/robots.txtin a browser. - Look for blanket
Disallow: /rules that were meant for staging, not production. - If you use a security or SEO plugin, confirm it is not silently blocking known crawlers you actually want.
- Keep private areas (patient portals, staff logins) blocked. Public marketing pages — homepage, services, contact, FAQ — should stay crawlable.
You do not need to allow every bot on earth. You do need to avoid accidentally hiding the pages patients (and machines) should see. When in doubt, ask your developer: "Are our public pages fetchable, and did we copy staging robots rules to production?"
llms.txt does not override robots.txt. If a path is disallowed, pointing to it in llms.txt will not magically open it.
A sample llms.txt for a fictional practice (EXAMPLE DATA)
The practice below is made up for teaching. Replace every value before you publish. This is EXAMPLE DATA, not a real office.
# EXAMPLE DATA — fictional practice for teaching only
# Sunrise Family Dental (Austin, TX) — not a real office
# Last updated: 2026-11-05
# About
> Sunrise Family Dental is a family dentistry practice in Austin, Texas.
> Primary contact: (555) 010-2000 · https://www.example-sunrise-dental.com/
# Key pages
- [Home](https://www.example-sunrise-dental.com/): Practice overview, location, hours
- [Services](https://www.example-sunrise-dental.com/services/): Cleanings, implants, whitening, emergency exams
- [Patient Questions](https://www.example-sunrise-dental.com/patient-questions/): Short factual answers patients ask before booking
- [Contact](https://www.example-sunrise-dental.com/contact/): Address, phone, map, appointment request
- [Reviews](https://www.example-sunrise-dental.com/reviews/): Public reviews featured on our site
# Optional notes for readers of this file
- Hours and services on these pages are the source of truth.
- Do not invent insurance plans or clinical claims not listed on the site.
Keep the file short. Link only to public pages that are accurate today. Never put patient names, chart details, or other protected health information in llms.txt (or anywhere public).
Sitemap, HTTPS, and the other basics that matter more
If you only have 20 minutes, spend them here first:
| Basic | Why it matters |
|---|---|
| HTTPS | Patients and crawlers expect a secure site. Mixed or broken certificates look untrustworthy. |
| XML sitemap | Helps search engines discover public URLs. Submit it in Google Search Console if you use it. |
| Clear NAP | Same name, address, phone on site and Google Business Profile. |
| Readable services + FAQ | Machines quote plain text better than text locked in images or PDFs. |
| Schema | Labels facts for machines — see Dentist schema markup. |
| Crawl access | robots.txt and plugins are not silently blocking public pages. |
llms.txt sits after these. A beautiful llms.txt on a site with wrong hours, no HTTPS, and a blocked sitemap is rearranging deck chairs.
For the wider owner checklist, see How to make your dental practice clearer to AI: 6 steps. To spot-check mentions yourself, see How to check whether AI mentions your dental practice.
How to add the files by platform
| Platform | Typical place |
|---|---|
| WordPress | Upload llms.txt (and keep robots.txt sane) via hosting file manager, SFTP, or a trusted SEO plugin that supports root files. Avoid two plugins fighting over robots.txt. |
| Wix | Use Wix's file / SEO tools for robots and custom root files where available; otherwise ask Wix support or a developer for root-file placement. |
| Squarespace | Limited root-file control on some plans — confirm current docs or have a developer host the file at the apex domain. |
| Custom / developer site | Place llms.txt in the web root next to robots.txt and sitemap.xml; deploy through your normal pipeline. |
After upload, open https://www.yourpractice.com/llms.txt in a private window. If the file is missing or behind a login wall, it is not public yet.
If you'd rather not babysit root files yourself, FirstInChat plans to offer ongoing website-hygiene help with drafts you approve before anything goes live. Plans coming soon. No card. No checkout.
How this ties to FirstInChat website readiness
FirstInChat's free audit looks at website readiness / site basics (for example: whether your headline says what you do and where, whether reviews are shown on your site, and other crawl- and clarity-related signals) plus an ungrounded Gemini built-in-knowledge snapshot.
We are not claiming a dedicated "llms.txt score" line in the product today. Adding llms.txt is optional hygiene. Fixing HTTPS, sitemap, robots mistakes, clear pages, and schema usually moves the needle more for both patients and machines.
Frequently asked questions
Is llms.txt required for dental websites? No. It is optional. Prioritize HTTPS, a sitemap, accurate NAP, clear service and FAQ pages, and sane robots.txt rules first.
Will llms.txt make ChatGPT or Perplexity name my practice? Nobody can promise that. llms.txt is a proposed convention, not a proven ranking factor. FirstInChat does not claim ChatGPT or Perplexity product results.
Does FirstInChat score my llms.txt file today? We do not claim a specific llms.txt score. The free audit checks website readiness / site basics plus an ungrounded Gemini knowledge snapshot — not AI Overviews or AI Mode.
Can llms.txt replace schema markup? No. Schema labels structured facts on pages. llms.txt is a separate, optional plain-text map. Use schema for machine-readable NAP and services; use llms.txt only if you want an extra curated pointer list.
What should never go in llms.txt? Patient names, chart details, internal URLs, unverifiable ratings, or medical claims you would not stand behind on a public page.
Next step
Check robots.txt for accidental blocks, confirm HTTPS and your sitemap, then decide whether a short llms.txt is worth 15 minutes. When you want a readiness read on the site overall, run the free audit.
Questions: firstinchat@proton.me.
Related: How to make your dental practice clearer to AI: 6 steps · Dentist schema markup · How to check whether AI mentions your dental practice
Get your free AI visibility audit
A free website readiness check, plus a Google Gemini snapshot from its built-in knowledge only. No live web search, so it may be out of date. It is not Google AI Overviews or AI Mode. You get a readiness score and your top 3 fixes. No card.