An AI engine quotes one page at a time. A homepage that tries to answer six patient questions cannot be attributed confidently to any of them, so the engine quotes a competitor with a dedicated page for each. Give every real question its own URL, keep the hierarchy shallow, and make every link describe what is at the other end.

Why One Page Per Question

An engine writing an answer about dentists has to decide which of your pages it is talking about, and it can only do that if one page answers one question. The passage it lifts must be attributable to one thing: one practice, one treatment, one place.

BEFORE
One page for everything
  • /servicesImplants, braces, whitening, emergencies, kids
AFTER
One page per question
  • /emergency-dentistWho is the best emergency dentist near me?
  • /dental-implantsHow much do dental implants cost?
  • /pediatric-dentistBest dentist for a nervous child?
  • /teeth-whiteningIs whitening safe for my teeth?
Illustrative example.

A page that answers six questions is quotable for none of them. Cost, recovery and longevity of an implant may all sit on one URL, and the paragraph the model wants is surrounded by material about something else, so the citation becomes vague and the engine prefers a page where the answer stands alone.

Splitting pages is not about length, it is about attribution: a page that answers one question can be cited on its own, while a page that answers four gets quoted for none of them.

There is a second, quieter benefit. One question per URL means one page to update when the answer changes, one page to attach structured data to, and one page that can collect links. The same answer on six pages has to be corrected in six places.

The Target Structure For a Single-location Practice

Here is a structure that covers the questions patients ask without turning the site into a directory of thin pages. Note the shape: treatments sit one level down, question pages sit beside them, and every question has one address.

Swipe the table sideways to see every column.

URL PathPage TypeThe H1 It CarriesThe Question It Answers
/Homepage[Practice Name], Family Dentistry in [City]What this practice is, who it treats, how to book
/treatments/Treatment hubDental Treatments We OfferWhich treatments exist and where each is covered
/treatments/dental-implants/Treatment pageDental Implants at [Practice Name]What an implant is, who it suits and how long it takes
/questions/how-much-do-implants-cost/Question pageHow Much Do Dental Implants Cost?What patients pay, what moves the number, how payment works
/questions/how-long-do-implants-last/Question pageHow Long Does a Dental Implant Last?Longevity, upkeep and what shortens it
/service-areas/Service area hubDental Care Around [City]Which areas we cover and how to reach each one
/service-areas/northside/Service area pageDentistry in NorthsideLocal parking, hours, insurance and same-day slots
/about/Practice pageAbout [Practice Name]Who the dentists are and what an appointment is like
/reviews/Reviews pageWhat Our Patients SayWhat patients actually wrote

The Depth Limit

Nothing that answers a patient question should sit more than three clicks from the homepage. In the structure above the longest path is three: home, treatments, implants, then one link to the question page. A page four or five clicks down usually belongs one level higher.

Where Question Pages Live

Question pages go beside the treatment pages, not underneath them. If they live as children of the treatment page, that page ends up four clicks from home and every question inherits the depth. At the same level, one treatment can have a dozen questions without the tree growing.

The Target Structure For a Group

Groups add a second axis, geography, and the temptation is to build a tree where every location holds a copy of every treatment. That produces the same question on twenty pages and teaches an engine your site cannot decide which one is right.

Swipe the table sideways to see every column.

URL PathPage TypeWhat It Has To Contain
/locations/Location hubEvery office with its own address, phone and hours, not a list of links
/locations/riverside/Location pageThe identity fields and the page sections, covered in the multi-location and service area posts
/locations/riverside/dental-implants/Location-specific treatment pageOnly where the offer, wait time or clinician genuinely differs
/locations/northside/Location pageIts own facts, written separately, not the same paragraph with the name swapped
/treatments/dental-implants/Group treatment pageThe treatment explained once, for patients who have not chosen an office yet
/about/Group practice pageWho the group is, the clinicians across all offices, how to choose a location
/reviews/Reviews pageReviews grouped by office, so each location page points at its own
/insurance/Payment pageThe plans accepted and any difference between offices

Two rules stop group pages competing. Each location owns a place and nothing else, and the group treatment page owns the treatment for patients who have not chosen an office. If a location page and the group page answer the same question in the same words, the engine has to pick, and may pick neither. Where a location needs a different answer, give it a different URL and link to the group page.

Link Rules That Help Machines

Structure is a set of links, so the links have to carry the meaning. Five rules cover most of what goes wrong.

  • Every anchor says what is on the other end. How to write anchor text that names the destination covers the wording.
  • Breadcrumbs mirror the URL path and are real links, not decoration. Plain-text breadcrumbs tell a machine nothing.
  • No orphan pages. Every page you want quoted has a contextual link pointing at it from a page that already matters.
  • No redirect chains. Link straight to the final address; two or three hops cost you the anchor text and sometimes the crawl.
  • Links are HTML links. A menu that only appears after JavaScript runs is invisible to a crawler that does not run scripts.

What To Do With The Pages You Already Have

Most practices are not starting from zero, so the useful exercise is a decision for every URL. A cluster of pages around one subject is covered in how topical authority is built for dentists.

Pages To Keep

A page stays if it answers a question no other page answers, has inbound links or impressions, and answers it clearly. Keep the URL even if it is untidy: a working address with history beats a neat one to redirect.

Pages To Merge

Two pages aiming at the same question is a split signal. Choose the URL with the better history, fold the unique content into it, and redirect the other URL to it. Do not leave both live.

Pages To Split

If one page is answering four or more questions with different intents, it needs to become several. Each piece gets its own URL, H1 and links, and the original address stays with the strongest.

Thin Service Pages

A page for a treatment you do not really offer, or a service page with a paragraph of copy and a booking button, is worse than no page: it is thin, it competes with your real pages, and it gives an engine something to quote that says almost nothing. Merge it into the hub, or the page that covers the same ground.

A 30-day Restructuring Plan

Sequencing matters more than speed here. Start with the pages that already have questions pointed at them, because they are closest to being citable.

  1. Week 1, inventory. Crawl the site and export every URL with its title, H1, word count, inbound links and its question. Write down the questions patients ask at the front desk. That list is the most valuable output of the week, and it is shorter than expected.
  2. Week 2, decisions. Give every URL one of the four verdicts and settle the target structure. Agree the URL names before you build, because renaming later means redirecting twice.
  3. Week 3, build. Start with the pages that already have links or impressions. Give each one its own question, a matching H1, structured data from our guide to dental schema markup, and three contextual inbound links.
  4. Week 4, clean up and measure. Put the redirects in place, regenerate the sitemap, update the navigation, then run the same patient questions you used in week 1 and compare. Restructuring changes what an engine can attribute, so it has to be measured.
  • Every page you want quoted answers exactly one question, and the H1 says which.
  • No page a patient needs sits more than three clicks from the homepage.
  • Every page has at least one contextual inbound link with a descriptive anchor.
  • No two live pages target the same question.
  • The sitemap lists only URLs that exist, and each redirects in a single hop.

If the site needs more than a reshuffle, our drsmiles.ai team builds the structure with that shape from the start through Smart AI Websites. For practices running several offices, how service area pages are built without becoming doorway pages covers the neighbourhood pages. If you would rather see the starting point first, the full audit lists the questions you lose and where the answers come from.