The short answer
Collect the questions your front desk actually hears, group them by topic, and answer each one in the first sentence in plain words before adding detail. Keep every answer visible on the page, specific to your office, and linked to the page that covers the topic in depth. Treat FAQ schema as optional labeling: Google stopped showing FAQ rich results in May 2026, so the page has to earn its place as a normal, genuinely useful result. Review it whenever your hours, insurance, or services change.
What an FAQ Page Does for You Now
A good FAQ page saves your front desk time and gives patients the answer before they call. For search, it works like any other page: it can rank when it answers a question better than other pages do. Google builds the short description under a result mainly from the text on the page, so a clear one-sentence answer often becomes the snippet a patient reads.
Older advice promised that FAQ schema would put your questions in an expandable list right under your Google listing. That display is gone. Google stopped showing FAQ rich results in Search on May 7, 2026, and removed the documentation for the feature in June 2026. AI answer tools still read and quote clear question and answer passages, so the format remains useful. The difference is that the page has to stand on the quality of its answers, not on a special box.
Find the Questions Patients Ask
Start inside the practice, because your own patients are the best source. Then use search tools to check wording and spot gaps.
- •A two-week front desk log: ask the team to jot down every question from calls, check-ins, and booking messages. Tally the repeats. The top ten usually cover hours, insurance, cost ranges, first visits, emergencies, and payment plans.
- •Your reviews and messages: patients often mention what confused or surprised them. A review that says "I didn't know they took my plan until I called" points to a missing answer.
- •Google autocomplete: type the start of a question, such as "does a dental crown", and note the suggestions. Google says predictions reflect real searches, shaped by language, location, trending interest, and your own past searches, so use them for wording ideas, not as a volume count.
- •People also ask: the related questions box in Google results shows how people phrase follow-up questions on a topic. Write your own answers; never copy another site's text.
- •Search Console queries: in Google Search Console, filter the Performance report for queries containing words like how, what, does, or can. These are questions people already used to find your site.
Write Answers That Hold Up
The best format is answer-first: the direct answer in the first sentence, then the detail, exceptions, and next step. "Yes, we see emergency patients the same day when we can; call before 10 a.m. for the best chance of a morning slot" is far more useful than a paragraph that only gets to the point at the end.
- •Be specific to your office: your actual hours, the plans you are in network with, where to park, what to bring. Generic answers that could sit on any dental site give patients, Google, and AI tools no reason to pick yours.
- •Let the length follow the question: some answers need one sentence, others need a short list. Google says it has no preferred word count. If an answer keeps growing, it probably deserves its own page.
- •Use the patient's words: write "cleaning inside the tooth" and then name the clinical term once, rather than the other way around.
- •Have clinical answers reviewed: anything about treatment, pain, or recovery should be checked by a dentist on your team before it goes live, and kept general enough that it never replaces a visit.
- •Give a next step where it helps: a link to book, the phone number, or the service page. Not every answer needs one.
Structure the Page
- •A descriptive H1: "Questions About Your First Visit" or "Dental Insurance Questions" tells patients and search engines more than a bare "FAQ".
- •Questions as headings: mark each question as a real heading (H2 or H3), with the answer in normal text underneath, and group related questions under topic headings.
- •Answers visible on load: accordions are popular, but Google notes that its "read more" links to a section of a page appear more often when that content is visible without a click. Short pages read well fully open; if you use an accordion, make sure the text is in the page code, not loaded later.
- •A unique meta description: summarize what the page covers in plain words. Google may use it when it describes the page better than the page text does.
- •Topic pages plus service-page questions: keep logistics on a general FAQ and put service questions on the matching service page, where they help the patient who is already reading about that treatment.
FAQ Markup: Optional Labeling
FAQPage is a schema.org type for a web page that presents frequently asked questions. In schema markup it labels each question and its accepted answer. It no longer earns a special Google display, but it does no harm when every question and answer in the code also appears as visible text on the page. A minimal example:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [{
"@type": "Question",
"name": "Do you see emergency patients?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes, we see emergency patients the same day when we can..."
}}
]
}
</script>
Many site builders and SEO plugins generate this for you. Because FAQ is no longer a Google rich result, the Rich Results Test is not the right check; validate the code with the Schema Markup Validator instead. For the markup that does matter most for a practice, such as Dentist with your exact name, address, and phone, see our schema markup guide.
Keep It Accurate
A wrong answer costs more than a missing one. When a patient arrives expecting a plan you dropped or hours you changed, the FAQ has created a problem at the front desk. Put a review on the calendar every quarter, and also whenever hours, insurance networks, providers, or services change.
Be careful with dates. Show a visible "Last updated" date, and change it only when you actually change the answers. Google lists changing page dates to make content look fresh, when it has not substantially changed, as a warning sign, and it says adding or removing content just to seem fresh will not help rankings. If your site also sets a dateModified value in its structured data, keep it matched to the visible date.
Retire questions nobody asks anymore and add the new ones your front desk keeps hearing. That habit keeps the page short, current, and trusted.
Link It and Measure It
Link to the FAQ from places patients already are: the contact page, the new patient page, booking confirmation emails, and the matching service pages. From each answer, link out to the page that covers the topic in depth. Internal links like these help patients find the next step and help search engines understand how your pages relate. Our guide to writing content that ranks covers this in more detail, and our content marketing team can build the page with you.
To see whether it works, open the Performance report in Search Console, filter by the FAQ page, and check which queries bring impressions and clicks over a few months. Search Console now also has a Generative AI performance report that shows when your pages are linked in AI Overviews and AI Mode; our AI search guide explains the wider setup, and earning AI Overview citations covers the Generative AI report in more depth. Inside the practice, the simplest measure is whether the same questions keep coming in by phone.
Sources
Google updates these pages often, so check them for current wording.
- •Google Search Central: Latest documentation updates (FAQ rich result changes, May and June 2026)
- •Google Search Central: Creating helpful, reliable, people-first content
- •Google Search Central: Control your snippets in search results
- •Google Search Central: Influence your byline dates in Google Search
- •Google Search Help: How Google autocomplete predictions work
- •Schema.org: FAQPage
Frequently Asked Questions
Does an FAQ page still help SEO now that FAQ rich results are gone?
Yes, as a normal page. Google stopped showing the expandable FAQ rich result in May 2026, but an FAQ page can still rank as a regular result, and its clear answers can be used in snippets and quoted by AI answer tools. What changed is the special display, not the value of answering real patient questions well.
Should I keep FAQPage schema on my practice website?
It is optional. FAQPage markup no longer earns a special Google display, but it does no harm when every question and answer in the code also appears as visible text on the page. If your site already has it and it matches, leave it. If adding it would take real developer time, spend that time on better answers instead.
How many questions should a dental FAQ page have?
There is no magic number, and Google says it has no preferred word count. Include every question patients genuinely ask about that topic and nothing else. A focused page on new patient visits might need eight questions; one on dental insurance might need fifteen. Remove filler questions that nobody asks.
Should I have one FAQ page or several?
Most practices do best with a short general FAQ for logistics, such as hours, parking, insurance, and first visits, plus a few questions on each service page about that service. Very large topics, such as implants or sedation options, can earn their own question page that links back to the main service page.