The pages that earn the citation in paediatric dentistry are the ones written in a clinician's voice, because parents ask AI about their child's teeth at every hour and most of those questions are not about cavities. They are about whether to wait, whether to worry, and whether your practice is safe for a three-year-old.
Pediatric intent is the fourth of the four patient intents in this series. Cost questions are answered with a range, emergency questions with hours and availability, and cosmetic questions with candidacy.
Child-friendly dental practices nearby:
Child-friendly dental practices nearby:
How Parents Use AI About Children's Teeth
Four kinds of question arrive on a parent's phone at two in the morning: does this need an emergency department tonight, how soon should we come in, does our insurance cover this, and will my child cope with being in the chair. The first is triage, the second timing, the third money, the fourth the one nobody writes a service page for.
None of these are research questions. They are decisions with a deadline, which is why the pages that answer them get read to the end and the page about your technology does not. Parents also use an engine to check the practice itself: is this place real, is the clinician qualified to look after a child, is the address where the map says it is. A model cannot see your child, so it can only lift what you wrote down.
The Question Set, By Age
Write the set by stage rather than by symptom and the same pages can answer it. Each row below becomes one page for one group of parents.
Swipe the table sideways to see every column.
| Age or Stage | What The Parent Asks | What The Answer Settles |
|---|---|---|
| First visit, from the first tooth | When to come, and what happens in the room | That a first visit is an examination and a talk, not a treatment |
| Teething, four months to two years | Does the pain need anything done | Which symptoms are ordinary, which mean a same-day call |
| Fluoride, at every stage | Is varnish, toothpaste or drops right | Who decides the amount for that age |
| Sealants, six to eighteen years | Are they needed, and what happens at the visit | What a sealant does and what happens if it comes off |
| Thumb sucking, two to six years | Intervene now or wait | When a habit affects the bite, and what to try at home |
| Chips and knocks, any age | Can the tooth be saved, and how soon | What to do in the next hour, and who to call tonight |
| Urgent, any age | Emergency department tonight? | Where to go and who to call first |
Questions Arrive Wrapped In Worry
Parents rarely type the clinical question. They type the worry wrapped around it, so the page must contain the sentence they would have typed: is it normal for my child to..., can we wait until..., what happens if we..., will my child.... Two more are worth adding: which symptoms are ordinary, and what the options are when there is no appointment available this week.
Answers That Carry Safety Responsibility
The Clinical Slice Needs Its Own Limits
Most of a paediatric question set is administrative. A small part is genuinely clinical, and that is where a vague answer does damage. A parent who reads keep an eye on it for a swollen face has been given permission to wait, when the right instruction was to go tonight. The same goes for an answer that suggests a dose of pain relief for a four-year-old.
So a page that mentions a symptom must carry its own limits: which signs mean calling your own dentist today, which mean urgent care or an emergency department tonight, and which mean the next routine appointment is fine. It must say it cannot judge this child, and it needs the practice phone number near the top rather than in the footer.
If you are unsure where your child should be seen, call your own dentist or urgent care rather than relying on an engine's answer. Your dentist should advise you about your own child's care, and an emergency department is for what only an emergency department can treat.
We cannot ask a model to hold a boundary it does not have, so the boundary has to live in the page, where the model can lift it with the rest of the answer. Our notes on how AI answers emergency dental questions set out why publishing the urgency rules beats hoping a model invents them.
The Pages That Earn The Citation
The Four Page Types That Cover The Set
The page types follow the one-question-per-page rule set out in how to structure a dental site one page per question. What is paediatric about them is the order: the first-visit page is what a parent reads before choosing you and the emergency page is what they read at midnight.
Each should carry structured data describing the practice rather than the page: the Dentist schema type on schema.org is the closest fit for a general practice, with clinician, address and hours on the same markup. A parent's first check on your hours is often your Business Profile rather than your website, and the two must agree; Google's guidance on managing a Business Profile is worth reading first.
The anxiety page is the one practices skip. It should describe what happens in the room, how long a first appointment takes, and what your team does with a child who will not open their mouth. Our notes on the route from an AI answer to a booked appointment cover the drop-off points between answer and booking. Separate FAQ pages get less love than they deserve, and the reasoning sits in why FAQ pages rarely get cited.
How To Be The Practice Parents Trust Without Over-claiming
Four things make a paediatric page quotable by a parent and by an engine: a named clinician, visible sources, honest boundaries, and no promises about what an engine prints.
Name The Clinician, Then Cite The Source
A named clinician is the strongest signal, and it is cheap. Put the paediatric dentist's name, their qualification and the fact that they see children on the page itself, not on a team page three clicks away, and mirror it on the organisation markup: the Organization type on schema.org exists for that kind of entity detail.
Visible sources matter because paediatric advice is content a reader checks twice: the FAQ page documentation from Google and the FAQPage schema type show how a question block and its answer should be paired.
Boundaries keep the rest credible. Say that the page is general information, that it cannot assess a child, and that your own dentist advises you about your own child's care. Then say what you will not promise: nobody controls what an engine prints, nobody can ask an engine to recommend a practice, and answers change with the wording, the model and the day. For the clinician voice across more pages, writing content a clinician will stand behind sets out the review routine we use: a named author, a date, a source list and a re-check date.
Turning Parent Questions Into Recall
Every Question Is a Recall Record
A paediatric list is unusually useful as a recall tool: every question on it belongs to a family you already have. The lapsed signal is not the first-visit question, which belongs to a new patient. It sits in questions about a child already in your records, such as a fluoride question from a family you have not seen since last year.
- Run your own question set first. The snapshot in drsmiles.ai asks ten questions across three engines in about sixty seconds, enough to see which questions above you are invisible for.
- Sort the answers into three piles: questions where you are named, questions where you are described but not named, and questions where no practice is named.
- Match the third pile against families who have not had a visit in the last twelve months.
- Contact those families with the answer they asked for, not a generic reminder. A parent who gets the specific answer they typed into their phone is far likelier to book.
- Ask at the next visit how they found you and whether they had asked an engine first, and record it in the practice software so the answer becomes a number.
- Publish the answer on the page that owns the question, then check the hours, address and phone number match everywhere else. The Dental AEO work keeps those answers consistent across pages you own.
- A named paediatric clinician on every paediatric page, with a review date beside their name.
- Hours, address and phone number identical on the website and the Business Profile listing.
- An urgency rule on every page that mentions a symptom, naming who to call and when.
- A named owner for the paediatric pages and a diary date to re-read them.
- A monthly re-measurement on the same questions, in the same city, answers kept.
None of this promises that an engine will name your practice tomorrow. What it removes are the usual reasons an engine skips a practice: no answer written down, facts that disagree with each other, nobody accountable for the next version.