The Best Website Structure for a Dental Practice
- Structure is a measurable asset, not a design preference. Pages with 0–4 internal inbound links average roughly 2 Google clicks; pages with 40–44 get about four times that — from a study of 23 million internal links across 1,800 websites.
- Click depth matters; folder depth does not. Google states it does not count slashes in URLs. What matters is how many internal links it takes to reach a page — and the famous "3-click rule" is contested research, not a Google threshold.
- Orphan pages are the most common structural failure. 66.2% of websites contain a page with a single inbound internal link — and an orphan page burns crawl budget while producing nothing.
- Almost nobody marks up their dental site correctly. Among local businesses that use structured data, only 31.6% use LocalBusiness, and only about 1.4% of dental sites use the specific Dentist type — a cheap, largely unclaimed advantage.
- AI crawlers do not run JavaScript. In published CDN crawl data, ChatGPT hit a 404 on 34.8% of its fetches versus Google's 8.2%. Clean structure is now AI-visibility infrastructure.
Most advice about dental website structure is a screenshot of somebody's menu with a caption saying "clean and professional". That is not a structure — it is a preference. A structure is something you can measure: how many clicks it takes to reach a booking page, how many pages have no inbound links, whether the markup tells a machine what your clinic is, and whether a crawler that does not execute JavaScript can read your content at all.
This guide builds the structure from the evidence up: the internal-linking dataset, what Google has and has not said about depth, what structured data coverage actually looks like across local businesses, and what happens when AI crawlers arrive at a site with dead ends. If you have not decided how many pages to build yet, read how many pages a dental practice website should have first; if you are still deciding whether to build one at all, start with whether your dental practice needs a website.
1. The Structure: Levels, URLs and Jobs
Three levels below the homepage is the practical ceiling for a practice site. Anything deeper is a symptom of a content decision that was not made.
| Level | URL pattern | Its job |
|---|---|---|
| Level 0 | / |
Say what you treat, where you are, and that you take new patients — above the fold — and route everything else |
| Level 1 — hubs | /services/ · /our-dentists/ · /about/ · /patient-info/ · /blog/ · /contact/ |
Group everything and pass it on. Hubs are never the destination for a specific question |
| Level 2 — revenue | /services/dental-implants/ · /services/invisalign/ · /services/emergency-dentistry/ · /our-dentists/dr-smith/ |
The pages patients actually want. One per treatment, one per clinician |
| Level 3 — support | /patient-info/insurance/ · /patient-info/financing/ · /patient-info/faq/ · /blog/{post}/ |
Remove objections and answer questions. Every one links back up to its parent and sideways to siblings |
| Trust & legal | /privacy-policy/ · /accessibility/ · /imprint/ |
Linked from every page footer. Not conversion drivers, but non-negotiable |
2. What the Data Says About Internal Linking and Depth
Four findings you can defend, and two myths worth discarding.
- Internal link count matters, up to a point. The clearest dataset published cross-referenced 23 million internal links across 1,800 websites to Search Console data. Pages with few inbound links averaged about two Google clicks; pages with 40–44 got roughly four times that. The relationship then inverts — heavy link counts usually come from sitewide navigation with identical anchor text, which correlates with weaker performance.
- Anchor-text variety correlated monotonically with clicks. Descriptive, entity-named anchors ("dental implant recovery timeline") beat "click here" and raw URLs. Uniqueness, not volume, is the signal.
- Local searches care more about internal links than most people expect. Across one million US keywords, internal inlinks correlated weakly overall but markedly stronger for local queries — which is exactly what a dental practice competes in.
- Google has never published a click-depth threshold. Google's own position is that it infers relative importance from links. The "keep everything within three clicks" rule comes from elsewhere, and usability researchers have directly challenged it — published studies show no abandonment past three clicks when the path is clear, and one study found product findability improved at four clicks.
/services/implants/info/cost/ that is linked from the homepage is one click away. A page at /cost/ with no inbound links is invisible. Google has said it does not count slashes in URLs — judge structure by links, not by folders.
3. Navigation: How Many Items, and What to Hide
The main menu is the one piece of structure patients touch directly, and there is unusually good research on it.
- Keep the main menu short. The widely repeated guidance is 5–7 top-level items. Usability researchers are more careful: they do not endorse a fixed number, because the right count depends on task, labelling and how predictable the site is. Six well-labelled hubs beat ten vague ones.
- Do not hide navigation on desktop. In a controlled study of 179 users across six sites, tasks on desktop using a hidden menu were 39% slower, and content discoverability with hidden navigation reached only 54% on desktop and 64% on mobile versus 80–85% when a visible-plus-menu combination was used.
- If you have four or fewer key destinations, show them on mobile. Hiding everything behind a hamburger makes your menu the single point of failure — and patients arriving from Google search have no patience for hunting.
- Use a sticky header and a persistent booking action. The most common reason a patient leaves a dental site is not finding the phone number or the booking button. Both should be reachable on every page without scrolling.
- Avoid multi-level dropdowns. Nested menus hide the structure you just built. A single level of sub-pages under each hub keeps the hierarchy visible.
On-site search is not a substitute for any of this: across large usability studies, the large majority of visitors navigate first and only reach for search after browsing fails. Build the navigation that works when search is not an option.
4. URL Structure: The Rules That Actually Matter
- Readable words, not IDs.
/services/teeth-whitening/, never/page?id=12. This is Google's explicit guidance and it makes every URL self-describing when it appears in search results. - Hyphens, not underscores. Google recommends hyphens to separate words.
- Lowercase, https, one host, one trailing-slash convention — each enforced with a 301 so you never split authority across duplicates.
- Keep keywords in URLs honest and minimal. The measured correlation between a keyword in the URL and ranking is 0.034 — barely above noise. Use the words a patient would say, not a keyword list.
- Use your patients' language. If your site is multilingual, URLs follow the language, and each version must link to all the others with correct
hreflangannotations. - No dates, no parameters for content, no filter URLs that get indexed. Calendar filters and sort options are the classic source of thousands of duplicate URLs.
- If you migrate, map every old URL to exactly one new URL with a server-side 301, avoid redirect chains, and keep the redirects for at least a year.
More on the technical layer, including sitemaps and what to do about duplicate pages, is in our dental website SEO guide.
5. Breadcrumbs: Small Element, Measurable Effect
Breadcrumbs do three useful things: they give patients who arrived from Google a sense of place, they pass internal authority up to parent pages, and they replace a raw URL with readable text in the search result.
- Render them in server-side HTML and show them on mobile. In a controlled test, adding visible mobile breadcrumbs plus matching server-side breadcrumb markup produced a statistically significant +5% organic traffic. Removing the visible breadcrumb while leaving the markup in place cost −5.5% — mismatched breadcrumbs actively hurt.
- Keep the visible breadcrumb and the structured data identical. Google treats breadcrumb markup as normal internal links; sending a different structure is a manual-action risk and generates errors in Search Console.
- Placement is a convention, not a lever. Top of the page is normal; the data shows no significant difference between top and bottom.
Planning a rebuild? Work through the content side before the code.
Build a Site That Generates Leads 10 Things Every Dental Site Needs6. Structured Data: The Stack a Dental Site Should Have
Structured data is machine-readable description of your clinic. Coverage is poor enough that doing it properly is a genuine advantage: in an audit of 16,673 local-business sites, only 31.6% of the sites using schema used LocalBusiness at all, and among dental sites roughly 65% have no LocalBusiness markup.
| Schema type | Where to use it | Why it matters |
|---|---|---|
| Dentist (subtype of LocalBusiness) | Homepage and location pages | The most specific valid type for a dental practice — and used by only about 1.4% of sites |
| LocalBusiness | Every page with address or hours | name and address are required; geo, telephone, openingHoursSpecification, priceRange and sameAs are what make it useful |
| Person / Physician | One per clinician | Connects the team to the clinic and to licensing profiles — the entity link AI systems read |
| MedicalProcedure | Treatment pages | Describes what the treatment actually is, in a format search engines can extract |
| BreadcrumbList | Every subpage, matching the visible breadcrumb | Replaces the URL in the search result and passes authority upward |
| FAQPage | Treatment and FAQ pages | Helps machines extract answers — with the honest caveat below |
Two honest caveats before you pay for "stars"
- Your own patient reviews will not produce star ratings in search results. Since 2019 Google stopped showing review rich results for self-serving reviews on local business and organisation pages — including reviews pulled through third-party widgets. The markup is still valid; the promise is not. Your Google Business Profile is unaffected and remains the place reviews pay off.
- FAQ rich results are now restricted to a small set of well-known, authoritative government and health websites. A single practice is unlikely to qualify for the visual FAQ block. It is still worth marking up — it helps machines extract your answers — but judge it on comprehension and AI citation, not on stars.
7. Structure for AI Search: What Crawlers Can and Cannot See
This is the newest layer, and it changes the priorities for a practice site.
- Most AI crawlers do not execute JavaScript. Confirmed for GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot and PerplexityBot in published CDN crawl data. Anything rendered client-side is invisible to them. Gemini and Apple see rendered pages; most of the rest see raw HTML.
- They are far less tolerant of broken links. In the same data, ChatGPT received a 404 on 34.8% of its fetches and Claude on 34.2%, versus Googlebot at 8.2%. Redirects burned 14.4% of ChatGPT's fetches against Google's 1.5%. A tidy sitemap with no dead internal links is now an AI-visibility tactic, not just tidiness.
- Know which bot blocks what. Training crawlers and search/indexing crawlers are different agents. For a local practice, the sensible policy is to allow the search and indexing crawlers and keep the site crawlable.
- Server-rendered HTML is the baseline. Your service descriptions, team, hours and prices should exist in the HTML, not just in a booking widget.
- Entity consistency beats page optimisation. AI systems cross-reference your website, Google Business Profile, Apple Business Connect, directories and professional profiles. Make the facts identical everywhere and connect them with
sameAs.
For the wider picture of how patients find clinics now, see how local SEO brings dental practices new patients and what makes a dental website convert patients.
8. Multi-Location Practices: One Site, Directory, Location Pages
- One domain, always. Separate sites or subdomains per location split your authority; a single site with a location directory concentrates it.
- One location page per staffed practice, each with its own address, phone, hours, team, services offered there, and its own Google Business Profile. One profile per physical location, never shared.
- Make each page genuinely different. A workable rule: at least a third of each location page cannot exist on any other — the team who work there, parking, transport, local services.
- Do not build treatment × location combinations. That pattern generates thin, near-identical pages at scale.
- Cross-link properly: each location page links to its team's profiles and the services it offers; each treatment page links to the locations that provide it.
9. The Technical Checklist
| Item | Rule | Common mistake |
|---|---|---|
| XML sitemap | Canonical, indexable URLs only; absolute; accurate last-modified; ≤50,000 URLs per file | Filling it with filter and parameter URLs |
| robots.txt | Use it to block crawling of waste; use noindex to keep a page out of the index |
Blocking a page you wanted de-indexed and finding it still listed |
| Canonicals | One version per URL, self-referencing, including on every language version | Cross-canonicalising language versions to one language |
| hreflang | Every version lists itself and all others, bidirectionally, with exactly one x-default | One-way annotations, which Google ignores |
| Redirects | 301 for permanent moves, no chains, a real 404 for permanently removed pages | Redirecting deleted pages to the homepage |
| Navigation markup | Real links with real hrefs, not JavaScript routing | A menu a crawler cannot follow |
| Tracking | One page, one job, one metric you actually review | Analytics installed, never opened |
10. A Structure Patients Can Finish: Turn Visits Into Bookings With DentalManager Cloud
A perfect structure still loses the patient at the last click. The gap is always the same: the booking button leads to a form that emails an inbox nobody checks, or a calendar that shows slots the practice already gave away by phone.
DentalManager Cloud closes that gap with one system behind every page: appointments, patient records, odontogram, billing and documents in a secure browser workspace with nothing to install.
- Google Calendar two-way sync: a booking from any page updates the real calendar instantly, and changes flow back, so no page ever advertises a slot you no longer have.
- Automatic confirmations and day-before reminders: the direct answer to the no-shows that waste the traffic your structure worked to attract.
- Multi-provider calendars: up to 4 dentists with individual calendars, plus role-based access for assistants and secretaries.
- Patient records with interactive odontogram: history, treatment status and balances beside the schedule, so the call after the click is fast and informed.
- Billing and printable documents: pending and overdue payment tracking, certificates, prescriptions and payment statements.
- Cloud, no installation: secure Google sign-in from phone, tablet or desktop.
- English, Spanish, German and Portuguese for practices treating international patients.
- $20 per month for the whole clinic with a free 7-day trial and no setup fee.
Build the Structure Once, Then Let the Calendar Do the Rest
Two-way Calendar sync, automatic reminders, multi-provider calendars and complete patient records — $20/month for the whole clinic.
Start Your Free 7-Day TrialSummary: The Dental Site Structure Checklist
| Layer | Do this | Result |
|---|---|---|
| Hierarchy | Home → 5–7 hubs → treatment and clinician pages → supporting detail | Nothing important deeper than three levels |
| Hubs | One page per treatment category, never one giant services list | A page for every question patients actually ask |
| URLs | Readable words, hyphens, lowercase, one host, 301 everything else | No duplicates competing with themselves |
| Menu | Short, visible on desktop, four or fewer key items on mobile, sticky booking action | Navigation that works when search does not |
| Breadcrumbs | Visible on mobile, server-rendered, identical to the markup | Context for patients, authority for pages |
| Internal links | At least three contextual inbound links per page, descriptive anchors, hub ↔ spoke both ways | No orphan pages, distributed authority |
| Schema | Dentist + LocalBusiness + Person per clinician + MedicalProcedure + BreadcrumbList + FAQPage | A connected entity graph machines can read |
| Technical | Clean sitemap, honest robots.txt, canonicals, bidirectional hreflang, real link markup | Crawlable by Google and by AI crawlers that skip JavaScript |
| Locations | One page per staffed practice on the same domain, each genuinely different | Local relevance without thin duplicates |
| Booking | One calendar behind every page, with confirmations and reminders | The structure finally produces appointments |
Frequently Asked Questions: Website Structure for a Dental Practice
A three-level hub-and-spoke model: a homepage, five to seven hubs (services, team, about, patient info, blog, contact), and one page per treatment and per clinician underneath, plus supporting pages for insurance, financing and FAQs. Every spoke links up to its hub, every hub links down to all its spokes, and related treatments link sideways. This keeps anything important within three clicks without forcing everything flat.
Three levels below the homepage is the practical limit. Note that folder depth is not click depth — Google states it does not count slashes in URLs, so what matters is how many internal links it takes to reach a page. The familiar "three-click rule" is contested research rather than a Google threshold, but keeping important pages within three clicks is still good practice for patients.
The common guidance is five to seven top-level items. Usability researchers are deliberately less prescriptive, because the right number depends on how clearly the labels describe the choice. Keep it short, avoid multi-level dropdowns that hide the structure, show your key destinations rather than hiding them all on desktop, and keep a persistent booking or call action visible on every page.
They give patients arriving from search a sense of place, pass internal authority to parent pages, and replace an unreadable URL with a readable path in the search result. A controlled test found a statistically significant 5% organic traffic gain from adding visible mobile breadcrumbs with matching server-side markup — and a 5.5% loss when the visible breadcrumb was removed while the markup stayed. Keep the visible breadcrumb and the structured data identical.
Start with Dentist, the most specific LocalBusiness subtype, then LocalBusiness itself with name and address plus geolocation, telephone, opening hours and price range. Add a Person or Physician entity per clinician, MedicalProcedure on treatment pages, BreadcrumbList on every subpage and FAQPage where questions are answered. Coverage is low: among local businesses using schema only 31.6% use LocalBusiness, and around 1.4% of dental sites use the Dentist type specifically.
Not since 2019. Google stopped showing review rich results for self-serving reviews on local business and organisation pages, including reviews displayed through third-party widgets. The markup remains valid — you simply should not expect the star treatment. Your Google Business Profile is unaffected, and reviews still influence patients directly; what changed is only the visual result, not the reputation effect.
Directly, because most AI crawlers do not execute JavaScript — confirmed for GPTBot, OAI-SearchBot, ClaudeBot and PerplexityBot. Client-rendered content is invisible to them. They are also far less tolerant of broken links: published CDN data shows ChatGPT hitting 404s on 34.8% of fetches versus Google's 8.2%. Clean internal linking, live sitemaps, no redirect chains and consistent facts across your site and profiles are what make a practice readable by AI assistants.
One domain with a location directory, one page per staffed practice and one Google Business Profile per location — never separate sites or subdomains, which split authority. Each location page needs its own address, phone, hours, team and services offered there, with at least a third of its content impossible to reuse elsewhere. Avoid treatment-by-location combinations, which generate thin near-duplicate pages at scale.
A Dental Website Structured Around Patient Decisions
Clean hierarchy, readable URLs, breadcrumbs, schema, and a booking path that reaches your real calendar — planned, not patched.
View Web Development Services