Dental Practice Website Template

Most practices have never seen their own site through Google’s eyes. The free grader fixes that in about thirty seconds: it runs PageSpeed on a simulated phone, reports all four Lighthouse scores, and checks the details patients never see but Google weighs, such as structured data, SSL expiry, the sitemap, and robots.txt. No account, no email. Run it now, then read the rest of this page with your real numbers in front of you.

The Math That Makes Speed Matter for a Practice

Acquiring a new patient through the usual channels costs a practice somewhere between $150 and $350. That patient is worth $500-800 a year and $5,000-10,000 over their time with the practice. Those two numbers are why the website matters more for a dentist than for almost any other local business: the site is the last step between paid or organic traffic and a booked exam, and every visitor who leaves because the page hung is an acquisition cost paid for nothing.

Consider the same ad budget on two sites. One converts two visitors in a hundred into an appointment request; the other converts five. The second practice gets two and a half times the new patients for identical spend. Nothing about the ads changed. The page did.

Slow pages do not just lose the click. They shape the judgment. A patient deciding whether to trust someone with a drill reads a five-second load and a 2018 layout as a practice that has not kept up, whatever the clinical reality. Fast, clear, and current is the baseline before anything about your care can register.

What a Practice Can Build on Pro Right Now

Pro launches with ten trade templates: roofing, HVAC, plumbing, electrical, landscaping, cleaning, pressure washing, pest control, garage door, and painting. Dental is not one of them. Everyone who owns Pro receives the dental layout later as a free update, with no date promised here. What is available on day one is the base those templates sit on, which is the part that carries the practice’s weight anyway.

Procedure pages. Out of the box the site has a home page, a services index where each service gets its own detail page, plus about, blog, contact, thank-you, privacy and a 404. For a practice, “services” means procedures. Each is a plain text file: what a crown visit involves, how long clear aligner treatment usually runs, what to expect after an extraction. Each becomes its own URL with Service schema and a breadcrumb, so implants and whitening are indexed as separate pages.

New-patient intake. The lead form and the multi-step quote wizard both post to the Pro lead engine, a serverless API rather than a plugin. A request is emailed to the front desk, pushed to a phone by Telegram or SMS, stored in DynamoDB, and can be forwarded by webhook to practice software that accepts one. Spam defenses are built in; Turnstile is optional. A practical note: keep the public form to name, contact details, insurance carrier, and preferred time. Symptoms and history are clinical information, and where you store them is a question for your compliance advisor, not a web form.

Smile gallery. The before/after gallery widget takes paired images and a caption per case. Images are optimized at build time, so a gallery with thirty cases loads as quickly as one with three. Use only cases with written consent.

Reviews. The reviews carousel displays the reviews you already have. Amrify ships no sample testimonials and no star ratings; the product’s own marketing follows the same rule.

Sticky call bar. On mobile, the phone number and a “Request Appointment” button stay pinned while the patient scrolls. A toothache at 9 pm does not go hunting for the contact page.

Insurance and payment page. This is content, not a component. Write a page listing every plan you accept plus CareCredit, in-house financing, and your uninsured fee schedule. It reduces front-desk calls and gives the city pages something specific to link.

Suburb pages. The local SEO engine generates a service-area page per city and a procedure-in-city page per procedure per city, scaffolded from Census place names. A build gate fails any page too thin to justify its URL. A practice in San Diego can have real pages for La Jolla, Encinitas, and Chula Vista without producing the doorway pattern Google filters.

Provider bios. The about page and the blog’s author pages hold each dentist’s education, credentials, and photo. A hygienist-written post about deep cleanings carries her byline.

Under the procedure pages sits the plumbing a practice never has to think about. Organization, WebSite, Service, Article, FAQPage and BreadcrumbList JSON-LD are generated from the content. Open Graph images are produced per page. The build writes the sitemap, robots.txt, RSS feed, llms.txt and web manifest. GA4, GTM and Clarity are optional switches, and six design switches cover the look. The stack is Astro 7, Tailwind CSS 4 and TypeScript, with CI failing the build the moment a Lighthouse category drops below 100.

Compared With a WordPress Practice Site

A WordPress dental site is usually a theme, a booking plugin, a form plugin, an SEO plugin, and shared hosting. It loads in four to eight seconds on a phone and scores somewhere between 30 and 55 on Lighthouse. Hosting runs $25-60 a month, plugins $150-400 a year, and someone has to apply updates or the intake form eventually stops working. Over three years the practice spends $2,000-5,000 and still has a site that patients wait on.

The Amrify base build is static HTML with no JavaScript framework on the page. The widgets are small SolidJS islands that load only where placed. Hosting on Netlify, Vercel, or Cloudflare Pages costs nothing. There is no admin panel to attack and nothing to patch, because there is no server. Structured data and image optimization are part of the build rather than plugins. Pro costs $249 once for founding members.

The WordPress to Astro migration guide covers moving pages and setting redirects so existing rankings carry over.

From Repo Access to a Live Practice Site

Reserve the founding price. Checkout has not opened. A free Amrify account holds a founding spot at $249; the price rises to $399 after the first 5,000 members, and the discount is enforced at checkout rather than by a countdown timer. On release day the account dashboard gains a link to the private GitHub repo. A seat means one person holding repo access.

Enter the practice. Fill site.json with the practice name, phone, address, hours, and emergency line. Write a text file per procedure. Add the insurance page. Add provider bios and headshots. Load consented cases into the gallery. Add your city list; the scaffolder pulls Census names. The repo includes a CLAUDE.md and four Claude Code skills, which turns “add a page for pediatric cleanings with a first-visit FAQ” into a request to an assistant rather than an afternoon of editing. Cursor and Copilot read the same files.

Deploy. Commit to GitHub, then hook the repo up to Netlify, Vercel or Cloudflare Pages; the practice site is live with SSL. The lead API runs in an AWS account you own. Route the Telegram or SMS notification to the front-desk phone. If your practice software accepts inbound webhooks, connect it; the database keeps a record regardless.

With the practice site live, the next habit is checking it: add it to the free Website Monitor from your account. The watch list holds up to thirty sites, Google’s test re-runs whenever you click, and the last ten results per site are kept. Nothing runs on a schedule and no alerts go out, but it is enough to catch a score drop after a content change before a patient does.

Practices This Fits

A new graduate opening a first office. The lease is signed and the schedule is empty. The base build gives you procedure pages, intake, a gallery ready for your first consented cases, and suburb pages for one payment, so the marketing budget goes to ads and outreach instead of a $10,000 site that ships in three months.

An established practice adding cosmetic or orthodontic work. Veneers, aligners, and full-mouth reconstruction draw a different patient with a different search. Each gets its own procedure page and its own procedure-in-city pages, gated for substance, and the gallery does the persuading that copy cannot. If you brand the cosmetic side separately, that second site is included.

A group with several offices. Each location is its own site in the monorepo with its own providers, hours, phone, and cities, sharing the codebase and the widgets. Change the intake form or add a group-wide post once and every office picks it up on the next build. There is no per-location fee.

Alex Crabinsky wrote the codebase. He is a full-stack developer in Alpharetta, Georgia, with more than a decade of production web work behind him. He runs Amrify’s own live sites on it, across roofing, TV mounting, glass, and exterior cleaning, and every one of them can be run through the grader above. Who builds Amrify.

Frequently Asked Questions

What does a dental practice website cost on Amrify?

One payment. Founding members (the first 5,000) pay $249 for Pro; the list price afterward is $399. That covers unlimited practice sites, the lead engine, the local SEO engine, the conversion widgets, and every update for life, including the dental template when it ships. Static hosting is free on Netlify, Vercel, or Cloudflare Pages. Custom dental sites typically run $5,000-15,000, and a WordPress practice site costs $2,000-5,000 over three years once hosting, plugins, and someone to patch them are counted.

Does the dental template exist today?

No, and this page will not pretend otherwise. Pro launches with ten trade templates aimed at home services; the dental template is a later free update to every owner, with no date attached. What a practice can use immediately is the base build underneath those templates: a complete site with a detail page per procedure, the serverless intake form, the before/after gallery, the reviews carousel, the sticky call bar, and city pages for every suburb the practice draws from.

Can new patients request an appointment through the site?

Yes. The lead form and the multi-step quote wizard both post to the Pro lead engine, which emails the front desk, notifies a phone through Telegram or SMS, stores the request in a database, and can forward it by webhook to practice software that accepts inbound webhooks. One caution from the practice side: keep a public form to name, contact details, and preferred time. Health details on a public form become a compliance question your advisor should answer before you store them anywhere.

Can I show before-and-after cases?

Yes. The before/after gallery is one of the five widgets in Pro. Each pair takes a caption, so ‘six veneers, upper arch’ sits under the photos, and images are optimized at build time so a gallery of thirty cases does not slow the page. Publish only cases you have written consent to use.

Where does the insurance and payment information go?

On a page you write. The base site has an about page, a contact page, and a services section, and you can add any number of standalone pages in plain text. A page listing every plan you accept, plus CareCredit or in-house financing, answers the question that generates the most front-desk calls and can rank for ‘dentist that takes [plan] in [city]’ once the local SEO engine’s city pages point to it.

Will the site rank for my suburbs?

The local SEO engine generates a service-area page per city and a service-in-city page per procedure per city, scaffolded from Census place names. A build gate fails any page that is too thin, so ‘dental implants in Encinitas’ has to say something about implants in Encinitas or it does not ship. JSON-LD for Organization, Service, FAQPage, and BreadcrumbList is generated for every page; a Dentist-specific type is not emitted by the base build today.

How long until a practice site is live?

Writing procedure descriptions and gathering provider headshots and consented case photos is the long part; most practices already have that material in patient handouts. With it in hand, a working day is a fair estimate: clone the private repo, fill in config, write the procedure pages, add the insurance page, upload the gallery, add cities, deploy. Hosting connection takes about thirty minutes.

We are a group with several offices. Do we pay per location?

No. Pro is one seat with unlimited production sites. The repo is a monorepo, so each office is its own site with its own providers, hours, phone number, and city list, sharing the codebase and the widgets. Update the intake form once and every office gets it on the next build.

Can we track where new-patient requests come from?

GA4, Google Tag Manager, and Microsoft Clarity are optional and load deferred so they do not affect the Lighthouse score. Track form submissions and page views there; the lead database keeps every request as its own record, so nothing is lost if analytics misses one.

---

Related solutions: Veterinary | Legal | Real Estate | Auto Repair

Every site in the Showcase runs on this codebase in production. Pricing details are listed in full on their own page.

Weighing WordPress or Wix for a dental site? Start with Amrify against WordPress, then against Wix and against Next.js; the practice-site trade-offs are spelled out on each.

Reserve a founding spot above, or send a question if your practice setup raises something this page did not. The full solutions list shows which trades are in the launch set and which follow as updates.