Dental Website SEO — Core Web Vitals, ADA, Schema, HIPAA (2026)

Dental website SEO in 2026 is a website engineering project, not a marketing project. The dental SERP rewards seven specific subsystems: Core Web Vitals on mobile (LCP under 2.5s, INP under 200ms, CLS under 0.1), mobile-first architecture (78% of dental search is mobile, 91% of emergency dental is), six-type schema markup (Dentist, MedicalProcedure, FAQPage, BreadcrumbList, Review, Organization), WCAG 2.2 AA accessibility (Title III lawsuit risk is real), treatment-page on-page SEO, internal linking architecture, and HIPAA-safe analytics.

Most dental practices ship two of the seven. The rest are missing or baked into a vendor template (ProSites, PBHS, Smile Marketing, Officite, PatientPop/Tebra, WEO Media) the practice cannot edit. The result is a hard ranking ceiling.

Rule27 ships all seven. We do not use accessibility overlays. We do not paste vendor-template schema. We do not recommend Hotjar without a BAA. We do publish your CWV scores, your axe-core report, your schema validation, and your sub-processor list quarterly.

We have inherited recovery work from Phoenix dental practices who spent two-plus years on ProSites, PBHS, or Smile Marketing templates and could not break past page two for their money keywords. The pattern is identical every time: the template ships with vendor JS bloat that tanks INP, schema that declares generic LocalBusiness instead of Dentist, accessibility violations baked into the template, and analytics that capture PHI without a BAA. The practice pays the platform $400-$800/month, the practice pays an SEO agency $2,000-$3,500/month, and the ranking ceiling does not move because the template is the ceiling.

AZ-specific demand layers compound the cost. Maryvale and west Phoenix Spanish-language search demand is real and ignored by templated sites. AZ State Board of Dental Examiners rules on testimonials and cost disclosure are well-defined and rarely respected by template content mills. Heat-seasonal demand (back-to-school pediatric cleanings in August, end-of-year insurance benefit reminders in November, snowbird arrival in October) requires content calendar variation no national template ships.

The migration off the template is the highest-leverage move most multi-location AZ dental practices have available.

Dental website SEO is not a marketing project. It is a website engineering project that happens to drive rankings.

Most dental practices we audit ship two of the seven website subsystems that actually move the SERP in 2026. They have a Google Business Profile and they have blog posts about teeth whitening. The other five subsystems — Core Web Vitals on mobile, six-type schema markup, WCAG 2.2 AA accessibility, HIPAA-safe analytics, treatment-page on-page architecture — are missing, broken, or worse, baked into a vendor template (ProSites, PBHS, Smile Marketing, Officite, PatientPop/Tebra, WEO Media) that the practice cannot edit. The result is a website that ranks to a hard ceiling and stops, no matter how many backlinks or blog posts get layered on top.

This page is the technical playbook. Editorial, opinionated, and named-competitor. If you are a Phoenix dental practice paying a national platform $400-$800/month for a templated site plus "SEO services," read the entire thing before your renewal date.

Dental website SEO is seven subsystems, not one

The SERP for dental website seo is dominated by website-platform vendors who sell the bundle: we build your site, so we own your SEO. ProSites, PBHS, Smile Marketing, Officite, PatientPop (now Tebra), and WEO Media all rank for this query. They rank because they have domain authority, not because their underlying platform is technically excellent. We have audited their template output line by line. The technical debt is consistent across all six.

The seven website subsystems that determine whether a dental site ranks in 2026:

1. Core Web Vitals on mobile — LCP under 2.5 seconds, INP under 200 milliseconds (INP replaced FID in March 2024 and is now the responsiveness metric), CLS under 0.1. Measured with CrUX field data, not Lighthouse lab data.
2. Mobile-first architecture — 78% of dental search is mobile, 91% of emergency dental search is mobile. Tap-to-call above the fold, intake forms that work on a 360px screen, map embeds that do not tank LCP.
3. Schema markup, six types, all JSON-LD, all validated — Dentist + MedicalBusiness, MedicalProcedure on every treatment page, FAQPage on every question block, BreadcrumbList below the homepage, Review + AggregateRating, Organization + sameAs.
4. WCAG 2.2 AA accessibility conformance — ADA Title III lawsuit risk is real and rising. Color contrast 4.5:1, keyboard navigation through booking flows, ARIA labels on icon-only buttons, alt text on the before/after gallery. Not an overlay widget.
5. Treatment-page on-page SEO — one page per signature procedure (Invisalign, implants, emergency, cosmetic, pediatric, root canal, periodontal), MedicalProcedure schema, FAQPage block, HIPAA-compliant before/after gallery, realistic cost-range disclosure where AZ State Board allows.
6. Internal linking architecture — hub-and-spoke from treatment hub to individual treatment pages to city-plus-treatment long-tail. Doctor-bio to treatment cross-links for E-E-A-T credit. No homepage-versus-hub cannibalization.
7. HIPAA-safe analytics — session-recording tools (Hotjar, FullStory, Crazy Egg, Mouseflow) capture PHI by default. CallRail without a signed BAA stores PHI. Heatmaps record keystrokes in form fields. A website SEO vendor who does not audit this is exposing the practice to OCR penalty.

Most dental sites ship subsystem 1 partially, subsystem 2 partially, and ignore 3 through 7. That is the structural reason a practice can pay an agency $2,000/month for two years and not move past page two for [city] dentist.

Core Web Vitals on a dental website — the real numbers

Google uses CrUX field data, not Lighthouse lab scores, to rank pages. A dental site that scores 92 on Lighthouse desktop and fails CrUX mobile is not ranking. Most ProSites and PBHS templates fall into exactly this gap because the lab test runs on a fast simulated connection and the field test runs on a Pixel 7 in a parking lot on Verizon LTE.

LCP (Largest Contentful Paint) — target under 2.5 seconds on mobile

The Largest Contentful Paint element on most dental sites is the hero image. The hero image on most dental sites is a 2.4 MB JPEG of a smiling family that loads in 4.8 seconds on 4G. Three fixes, in priority order:

• Serve WebP or AVIF at the actual rendered size. A 1920x1080 hero on a 360px viewport is rendered at 720x405 — serving the 1920 version wastes 7x the bytes.
• Preload the hero image in the document head with <link rel="preload" as="image"> so the browser fetches it before parsing the rest of the DOM.
• Eliminate render-blocking JavaScript. Most dental templates load 600 KB of vendor JS in the head, blocking the LCP element from painting until the JS finishes parsing.

INP (Interaction to Next Paint) — target under 200 milliseconds

INP replaced FID (First Input Delay) as the responsiveness metric in March 2024. It measures the worst interaction latency over a page visit, not just the first one. Dental sites tank INP in three predictable places: the appointment-request form submission, the live-chat widget initialization, and the photo-gallery lightbox. All three are usually long-running JavaScript tasks blocking the main thread for 400-800 milliseconds at a time.

The fix is unsexy. Break long tasks into chunks with requestIdleCallback, defer non-critical JS until after the page is interactive, and remove any third-party chat widget that is not actually generating leads. We have removed Drift and Intercom from three dental sites in the last year purely because the INP cost was not justified by the conversion volume.

CLS (Cumulative Layout Shift) — target under 0.1

CLS on dental sites comes from three places: hero images without explicit width and height attributes, web fonts that swap mid-load (FOUT), and ads or embeds (insurance carrier badges, sometimes a Google Maps embed) that insert themselves above already-rendered content. All three are fixable in a few hours of engineering. Most templates do not bother.

Why dental-specific assets wreck CWV by default

The assets that dental marketing demands — doctor headshots, smiling-family heroes, before/after galleries, intake forms with 30+ fields — are exactly the assets that destroy Core Web Vitals if shipped naively. The before/after gallery alone is usually 8-15 unoptimized JPEGs in a lightbox that pre-renders all of them on page load. Lazy-loading offscreen gallery images is a one-line fix. We have never seen a ProSites or PBHS template do it.

Why CrUX field data beats Lighthouse lab data on dental sites

Lighthouse runs on simulated throttling. CrUX runs on real Chrome users. Phoenix dental patients run Chrome on Pixel 6 and iPhone 13 on Verizon LTE in 110° heat with five other apps open in the background. That is the device profile your site has to perform on. Lighthouse will tell you the site loads in 1.8 seconds. CrUX will tell you 67% of your real users see LCP over 4 seconds. The CrUX number is the one Google uses for ranking.

Pull your real numbers from PageSpeed Insights' "Origin Summary" panel (which sources CrUX), not from the Lighthouse score on the same page. If you do not see an Origin Summary, your site has too little traffic for CrUX to report on, which is a separate problem.

Mobile-first dental website architecture — 78% of patients, 91% of emergencies

Google has been mobile-first indexing since 2019. For dental specifically, the traffic mix is more extreme than the average industry. ADA-published data and Tebra's 2025 dental search reports converge on:

• 78% of dental search across all intents is mobile
• 91% of emergency dental search (emergency dentist near me, tooth pain dentist open today, weekend emergency dental) is mobile
• 64% of new-patient appointment bookings happen on mobile

The practical implications for a dental site:

Tap-to-call CTAs above the fold on every treatment page

<a href="tel:+16025551234"> with prominent placement, visible without scrolling on a 360px viewport. Not a fly-in widget that appears at 4 seconds. Not a chat bot. A phone number, big, tappable, above the fold. Emergency dental patients do not fill out intake forms.

Mobile-friendly intake forms (no 47-field forms on a 360px screen)

The dental intake form is the place where most templated sites lose conversion. A 47-field form designed for desktop becomes a 12-screen scroll on mobile. The fix is progressive disclosure: collect name + phone + reason for visit on screen one, then move the patient to a thank-you page that says "we will call you within 10 minutes." Detailed health history goes on a tablet in the lobby, not the website.

Map embeds that do not tank LCP

A Google Maps iframe is roughly 600 KB of JS plus tiles. On a mobile dental site it can move LCP from 2.1 to 4.4 seconds. The fix: load a static map image (Google Static Maps API or a Mapbox static image) by default, and lazy-load the interactive iframe only if the user clicks "directions." Most users only need the address and phone number.

Click-to-text and click-to-WhatsApp for after-hours emergency

For practices that take after-hours emergencies, a <a href="sms:+16025551234?body=Emergency dental"> link converts emergency mobile users who do not want to call at 11 PM but will text. We have measured this. The conversion lift is real.

Schema markup for dental websites — six types, all JSON-LD, all validated

Schema markup is now load-bearing for two reasons: rich-result eligibility in the traditional SERP (review stars, FAQ accordions, breadcrumb trails) and citation eligibility in AI Overview, ChatGPT, Perplexity, and Gemini. AI engines parse JSON-LD to decide which entity an answer belongs to. A dental site without schema is a string of text; a dental site with clean schema is a named entity the AI can cite.

Dentist + MedicalBusiness — the entity layer

Every dental site should declare itself as both Dentist and MedicalBusiness (Dentist is a sub-type of MedicalBusiness). The schema lives in the homepage <head> and includes name, address, phone, hours, area served, accepted insurance, and sameAs links to the practice's GBP, Yelp, and Healthgrades profiles. The sameAs array is the credential trail AI engines use to verify the entity exists across multiple authoritative sources.

MedicalProcedure — every treatment page

A dental implant page should declare @type: MedicalProcedure with procedureType, bodyLocation, preparation, followup, and howPerformed. Same for root canal, crown, Invisalign (which is MedicalTherapy), pediatric cleaning, periodontal scaling, and so on. ProSites templates ship a generic Service schema with no medical specificity. The Medical schema is what makes the page eligible for the rich-result treatments Google added for healthcare in 2023.

FAQPage — every page with a question block

FAQ accordions are a near-universal dental page pattern. The FAQPage schema makes them eligible to expand inline in the SERP and inline in AI Overview. Two questions minimum, well-structured Question and Answer nodes, no marketing copy in the answer. The answer should be the answer.

BreadcrumbList — every page below the homepage

Breadcrumbs in the SERP replace the URL with a readable trail (Home > Services > Implants). The signal is small but free. There is no reason to not ship it.

Review + AggregateRating — for star display in SERP

Review schema must reflect reviews that exist on the page or on a third-party source you can name. Schema gaming (declaring 4.9 stars when you have 11 Google reviews averaging 4.2) is a manual action waiting to happen. Pull from your verified Google Business Profile data, declare the source via sameAs, and ship accurate numbers.

Organization + sameAs — credential trail for AI engines

Organization schema with a deep sameAs array (GBP, Yelp, Healthgrades, ZocDoc, the doctor's state board license page, the AGD or AACD membership page, social profiles) is the citation web that AI engines use to verify you are a real, credentialed practice. The more authoritative the sameAs source, the higher the citation confidence.

ADA Title III + WCAG 2.2 AA — dental websites are getting sued

This is the section most dental SEO agencies leave out. They leave it out because they do not know it. The convergence of accessibility law and SEO is one of the most important shifts in dental website strategy in 2026.

The Title III lawsuit landscape for dental practices

The ADA Title III applies to "places of public accommodation," and federal court decisions have repeatedly extended this to commercial websites that serve as gateways to physical services. Dental practices have been named defendants in increasing numbers of Title III demand letters and lawsuits over the last five years. Most settle for $10,000-$35,000 plus remediation. The DOJ's April 2024 final rule on Title II (state and local government) clarified WCAG 2.1 AA as the conformance standard, and the same standard is the de facto reference for Title III private-business litigation.

State-level reinforcement compounds the risk: California's Unruh Civil Rights Act (statutory damages of $4,000 per visit, multiplied per plaintiff — California dental practices have been the highest-frequency target nationally); New York's NYSHRL and NYCHRL (statutory damages plus fee-shifting that incentivizes plaintiff firms); Florida federal courts (the Southern District of Florida processes more ADA website cases than any other state); and Texas and Arizona, where dental practices increasingly receive demand letters from out-of-state plaintiff firms targeting templated sites en masse.

The vector for a dental practice is the templated platform. Plaintiff firms scan templated dental sites at scale, identify the same violations across thousands of practices (because the violations are baked into the template), and serve demand letters in waves. If you are on a ProSites or Smile Marketing template, you are sharing a violation profile with several thousand other dental practices, and the demand letter is identical.

Color contrast 4.5:1 — the most common single violation

WCAG 2.2 AA requires 4.5:1 contrast between text and background for normal text, 3:1 for large text. Most dental templates ship a light-blue brand color on a white background at roughly 2.8:1. Every body paragraph on the site fails the standard. Plaintiff firms automate this check with axe-core. It is the single most common violation cited in dental Title III demand letters.

Screen-reader compatibility on appointment-booking flows

The appointment-booking widget is the highest-stakes accessibility surface on a dental site. A patient using NVDA or VoiceOver must be able to navigate the form, hear the field labels, submit, and receive a confirmation. Most templated booking widgets fail at least three points in this flow — unlabeled inputs, missing ARIA live regions for validation errors, focus traps in the date-picker. A patient who cannot book is a patient who can sue.

Keyboard navigation through intake forms

A patient who cannot use a mouse must be able to tab through every field in logical order, see a visible focus indicator on the current field, and submit. Most dental templates ship with outline: none in CSS to "clean up" the focus ring. That single line of CSS is a Title III violation.

ARIA labels on icon-only buttons (tap-to-call, hamburger menu)

The tap-to-call button on a dental site is usually a phone icon with no visible text. To a screen reader, it is just "button." Adding aria-label="Call our Phoenix dental office at 602-555-1234" fixes the violation and is free.

Alt text on before/after gallery images

Every image needs alt text. Decorative images take alt="". Content images (before/after smile galleries) take descriptive alt text that does not contain PHI (no patient names, no specific medical conditions). "Before and after of cosmetic veneers, anterior teeth" is fine. "Before and after of Maria Lopez, age 34, with severe enamel erosion" is a HIPAA violation.

Why an overlay widget is not a substitute for real conformance

AccessiBe and UserWay are the dental industry's most-purchased shortcut. The pitch is appealing: drop in one JavaScript tag, the widget overlays "accessibility features," and your liability is gone. The reality is uglier. The Federation of the Blind has issued formal positions against overlay widgets. Plaintiff firms now include overlay-widget identification as part of their demand-letter intake — sites with overlays are sometimes targeted specifically because the overlay signals an attempt to avoid real remediation. Several federal courts have held overlays do not meet WCAG conformance. The widget is a $50/month liability shield that does not shield.

The only way to conform is the way nobody wants to do it: remediate the underlying code. We do this for every dental site we ship.

Treatment-page on-page SEO — where the patient actually converts

The dental homepage is for branding. The treatment pages are for conversion. Most templated dental sites have a /services/ folder with 8-12 thin pages — 500 words each, identical structure, identical CTAs, written by a content mill, no schema, no FAQ, no real photos. Rebuilding the treatment-page architecture is the single highest-leverage move on most dental sites we audit.

One page per signature procedure

Invisalign, dental implants, cosmetic veneers, emergency dental, pediatric dentistry, root canal therapy, periodontal therapy, sedation dentistry, sleep apnea oral appliances, full-mouth reconstruction. Each gets its own page, 1,500-3,000 words, written by someone who has been in the chair or shadowed a dentist.

Realistic cost-range disclosure where AZ State Board allows

A Phoenix dental practice we work with publishes "Invisalign at our Phoenix office typically ranges from $4,200 to $6,800 depending on case complexity" on the Invisalign page. AZ State Board of Dental Examiners allows this with caveats (no false or misleading claims, no specific case price without examination). The result: the page ranks for invisalign cost phoenix and the patients who book a consult have already self-qualified by budget. Most agencies are too risk-averse to publish anything. Rule27 publishes.

MedicalProcedure schema on every treatment page

See the schema section. The Invisalign page declares @type: MedicalTherapy, the implant page declares @type: MedicalProcedure with procedureType: SurgicalProcedure, the cleaning page declares @type: MedicalProcedure with procedureType: TherapeuticProcedure. Specificity makes the page eligible for healthcare-specific rich results.

FAQPage block answering the top 5-8 patient questions per procedure

"How long does Invisalign take?" "Does insurance cover dental implants?" "What is the recovery time for a root canal?" The questions come from the GBP Q&A, the practice's email inbox, and the "People Also Ask" box on the SERP. The answers are honest, structured, and shipped as FAQPage schema.

HIPAA-compliant before/after galleries

Consent docs on file. No PHI in alt text. No PHI in filenames ("smile-makeover-1.jpg" not "john-doe-veneers-march-2025.jpg"). EXIF data stripped before upload. The gallery itself loads lazily and links to a full-resolution lightbox only on click.

Insurance-acceptance disclosure per major carrier

Delta Dental, Cigna, Aetna, MetLife, Guardian, United Concordia, Humana — list every carrier you accept on every treatment page. Patients filter heavily by insurance, and a page that does not name the carrier is a page they bounce from in three seconds.

Tap-to-call CTA above the fold + booking widget below the fold

The two CTAs serve different patients. The tap-to-call serves the urgent patient ("I have pain, I want a human now"). The booking widget serves the deliberate patient ("I am comparing three practices for a routine cleaning, I will book online when I find the right fit"). Both belong on the page. The tap-to-call goes above the fold because urgent patients do not scroll.

Internal linking architecture for dental websites

Internal links are the cheapest SEO signal you can ship and the one most dental sites get backward. The architecture that works:

Hub-and-spoke from treatment hub to individual treatment to city + treatment long-tail

/services/ (treatment hub) links to /services/dental-implants/ (treatment page) links to /dental-implants-scottsdale/ (city + treatment long-tail). Each layer narrows the intent and inherits authority from the layer above. The long-tail page captures the in-market patient; the treatment page captures the comparison shopper; the hub captures the general intent.

Doctor-bio to treatment cross-links for E-E-A-T credit

The doctor's bio page should link to the treatments the doctor performs ("Dr. Smith specializes in implant dentistry and prosthodontics"). The treatment page should link back to the doctor ("Dr. Smith has placed over 2,400 implants since 2014"). The cross-link makes the page eligible for Experience and Expertise signals under Google's E-E-A-T framework.

Insurance pages to treatment pages cross-links

If you publish an insurance-acceptance page (/insurance/delta-dental/), it should link to every treatment page that takes that insurance. Patients filtering by carrier are pre-qualified by intent, and the link helps the treatment page rank for [procedure] delta dental long-tail queries.

Why most dental websites accidentally cannibalize themselves

Homepage, services hub, and about page often all target [city] dentist. Google picks one — usually the wrong one. Assign each page a distinct primary keyword and reinforce with internal anchor text: homepage targets brand, hub targets dental services [city], treatment pages target each procedure.

HIPAA-safe website analytics — the leak surfaces most dental sites ignore

This section is where a website SEO vendor proves they understand healthcare law. Dental practices are HIPAA-covered entities. PHI captured by a website tool without a Business Associate Agreement (BAA) is an OCR-reportable breach. The penalties run $100-$50,000 per violation, with annual caps in the millions for willful neglect.

Session-recording tools capture PHI by default

Hotjar, FullStory, Crazy Egg, Mouseflow, LogRocket — all of these record everything the user does on the page. If a patient types their name into the appointment form and the session recorder captures the keystrokes, you have just sent PHI to a third party without a BAA. Hotjar does offer a "suppress sensitive content" setting that has to be configured per element — most dental sites do not configure it. FullStory offers HIPAA-eligible plans with BAA — most dental sites are not on that plan.

The audit question: does your session-recording vendor have a signed BAA with your practice? If no, turn it off or upgrade the plan.

Heatmaps record keystroke data in form fields

Same mechanism as session recordings. Form-field tracking is the highest-risk surface because it captures explicit PHI (name, DOB, condition, insurance ID). Same fix.

Call recordings via CallRail or WhatConverts store PHI without a BAA

CallRail offers a HIPAA-compliant plan with a BAA. WhatConverts does too. The default plan does not include the BAA. A practice that records calls for "quality assurance" on the default plan is storing PHI without authorization. The fix is to upgrade to the BAA-enabled plan or stop recording calls.

Form submissions through non-BAA SaaS = HIPAA violation

Gravity Forms, Wufoo, JotForm, Typeform — none ship with a BAA by default. Patient intake form submitted to a non-BAA form processor is a breach. JotForm offers a HIPAA-compliant tier; Typeform does not. The website SEO vendor has to verify the form vendor and the form's data flow.

Server-side GA4 + IP anonymization

Google Analytics 4 is not HIPAA-compliant out of the box. The fix is server-side GA4 (Google Tag Manager server container) with IP anonymization and PHI scrubbing in the data layer. Most dental sites ship client-side GA4 with default settings. The fix is one weekend of engineering and a switch in GTM.

Why a website SEO vendor that does not audit this is exposing the practice

HHS OCR issued specific guidance on tracking technologies and PHI (December 2022, revised March 2024) stating that IP address combined with any health-related URL constitutes PHI when the user is identifiable. Default Hotjar, default CallRail, and client-side GA4 on a dental site is documented OCR enforcement risk. A vendor who does not audit this is, charitably, incompetent.

Platform problem — why ProSites, PBHS, Smile Marketing, and PatientPop dental templates cap your ranking ceiling

The website-platform vendors who rank for dental website seo make a tidy living. The bundle is genuinely convenient: one vendor for hosting, design, content, and SEO. The trade-offs are real.

Template homogeneity — Google notices when 4,000 dental sites share the same DOM

A ProSites template is rendered with the same DOM structure across every practice that uses it. The class names, the section order, the navigation pattern, the schema block — identical. Google's site clustering algorithms detect this and treat the cohort as a single template signal, not as 4,000 independent endorsements. The result is a hard ranking ceiling: every ProSites dental site competes against every other ProSites dental site for the same SERP positions, and the differentiator is local proximity, not content quality.

Vendor JS bloat that wrecks INP and LCP

A typical ProSites template ships 800-1,200 KB of JavaScript on initial load — vendor analytics, vendor chat widget, vendor appointment booker, vendor accessibility overlay, vendor schema injector, jQuery, and a handful of legacy polyfills for Internet Explorer. None of it is removable by the practice. The INP cost is structural.

Schema baked into vendor template that cannot be customized

The schema block in a ProSites template declares @type: LocalBusiness (not Dentist), LocalBusiness (not MedicalBusiness), no medicalSpecialty, no MedicalProcedure on the treatment pages. The practice cannot edit the schema because the template generates it. The result is a generic local-business signal where a healthcare-specific signal should be.

Switching cost engineered in

The content lives in the vendor's CMS. The URL structure is the vendor's. The image library is the vendor's. The schema is the vendor's. Migrating off the platform means rebuilding the site from scratch and risking 6-12 months of ranking volatility. The platforms know this and price renewals accordingly.

When platform-bundle works and when it does not

A solo dental practice in a low-competition market (small town, 5-15-mile primary draw, three or fewer dental competitors) can rank reasonably well on a ProSites template because the local competition is also on templates. The cost-benefit favors convenience.

A multi-location dental group in a competitive metro (Phoenix, Houston, Atlanta, Chicago) cannot rank to its potential on a template. The technical ceiling is a real ceiling. The fix is migration to a custom build with full control of CWV, schema, accessibility, and analytics.

AZ-specific dental website SEO context

The nationally-applicable playbook above is the foundation. AZ-specific layering moves the needle further.

AZ State Board of Dental Examiners — what website content triggers review

The AZ State Board reviews dental marketing content for false or misleading claims under R4-11-1206 and parallel statutes. Specialty claims ("specialist in implants") require board certification in a recognized specialty (per ADA Section 5). Cost claims must be honest and not bait-and-switch. Testimonials must be honest. The AZ State Board has issued advisory letters and disciplinary actions over website content. A website SEO vendor should know the rules.

ADA Section 5 (Veracity) on testimonials, before/after, specialty claims

ADA's Code of Ethics Section 5 (Veracity) is the national reference for dental advertising. Testimonials that are not from actual patients, before/after photos that are not the actual patient, specialty claims without recognized specialty board certification — all violate Section 5 and are commonly cited in board complaints. The website SEO vendor should not be the reason the practice gets a complaint filed.

Spanish-language priority pages for Maryvale and west Phoenix demand

Maryvale's population is roughly 76% Hispanic. West Phoenix dental search demand in Spanish is real, measurable, and ignored by most templated sites. A Spanish-language treatment page for the top three procedures (cleanings, implants, emergency) is a 30-hour project that opens a market most competitors leave on the table. The page lives at /es/servicios/implantes/ with proper hreflang tagging, not at a Google-translated /services/implants/?lang=es.

Heat-seasonal demand

Phoenix dental demand is seasonal in non-obvious ways. August: back-to-school pediatric cleanings spike weeks two and three. November: use-it-or-lose-it insurance benefit reminders drive elective procedure search (implants, crowns) to mid-month peaks. October: snowbird arrival drives new patient dentist search from out-of-state Chrome geolocations identifying as Phoenix-area. June-August: emergency dental dips slightly while elective cosmetic rises (wedding and graduation season). Content calendars that ignore the curve waste demand.

How Rule27 builds dental websites for SEO (and what we will not do)

This is the section that closes the loop. We have opinions, and our opinions are constraints.

We do not lock you into a proprietary CMS

Your site lives in a CMS you can take with you. WordPress with a clean theme, or a headless setup on Next.js. Your content is yours. Your domain is yours. Your URLs are yours.

We do not paste schema as a vendor template — we customize per practice

The Dentist schema for a single-doctor pediatric practice is not the same as the schema for a six-location multi-specialty group. We write it per practice, validate it in the Rich Results Test, and ship the source so you can read it.

We do not ship accessibility-overlay widgets

No AccessiBe. No UserWay. We remediate the underlying code to WCAG 2.2 AA. We give you the axe-core report before and after.

We do not recommend session-recording tools without a signed BAA

We will recommend FullStory's HIPAA-eligible plan or no session recording at all. We will not recommend the default Hotjar plan on a dental site.

We do publish your CWV scores, accessibility report, schema validation, and sub-processor list

Quarterly. PDF. With the underlying data. You forward it to your compliance officer; they have what they need.

Anonymized AZ dental wins

The wins below are anonymized per HIPAA-adjacent caution and per the practice's preference. Specific numbers are accurate; identifying details are scrubbed.

East Valley pediatric practice — CWV remediation lifted mobile rankings. A two-location pediatric practice in the East Valley came to us with mobile LCP at 4.8 seconds and INP at 380ms, both deep in the "poor" CrUX bucket. The site was on a templated platform we will not name. We could not migrate the platform on the engagement budget, but we did remove three render-blocking third-party scripts, lazy-load the hero gallery, and preload the LCP image. Eight weeks later mobile LCP was 2.3 seconds and INP was 165ms, both in "good." Rankings for [city] pediatric dentist moved from average position 9.2 to 4.6 in twelve weeks. Booked new-patient consults from organic moved from 14/month to 31/month over the same window.

Scottsdale cosmetic practice — schema + treatment-page rebuild drove first AI Overview citation. A single-location Scottsdale cosmetic practice with strong Google reviews but weak treatment-page content. We rebuilt seven treatment pages (Invisalign, veneers, whitening, implants, smile makeover, full-mouth reconstruction, gum contouring) at 2,200-3,000 words each, deployed MedicalProcedure and FAQPage schema, and tightened the Dentist + Organization schema. Sixteen weeks after launch, the practice received its first AI Overview citation on Google for cosmetic dentist scottsdale arizona. Perplexity cited the Invisalign page eight weeks after that for invisalign cost scottsdale. The schema and content quality together — not either alone — moved the AI signal.

Phoenix multi-location group — accessibility remediation closed a Title III demand letter. A four-location Phoenix dental group received a Title III demand letter from an out-of-state plaintiff firm citing 17 specific WCAG 2.2 AA violations. We were engaged on a six-week remediation. We did not use an overlay. We remediated color contrast across the brand palette (the brand color shifted from a 2.9:1 ratio to a 4.7:1 ratio), added ARIA labels to 41 icon-only buttons, restored visible focus indicators across the entire template, repaired the booking-widget keyboard flow, and rewrote alt text on 312 gallery images. The plaintiff's counsel accepted the remediation report and the matter closed without trial. Total cost was lower than the projected settlement. The site now ships with an accessibility statement linked in the footer and an annual re-audit on the calendar.

Ready to fix your dental website's SEO foundation?

The free dental website audit covers Core Web Vitals (CrUX field data, not Lighthouse), WCAG 2.2 AA conformance check (axe-core report), six-type schema validation (Rich Results Test), HIPAA exposure review (session recording, call recording, GA4, form vendor), and treatment-page architecture review. 72-hour turnaround. Real PDF. Real numbers. No upsell. The structured FAQ section below answers the seven questions practices ask most often before they engage.