Say where you are in Middle Tennessee terms, not with a map pin
Somebody who moved here last year cannot place your address, so name the roads, the neighborhood and the areas you actually draw from in plain text.
The word Nashville covers a great deal of ground and several counties worth of driving. A visitor reading it learns almost nothing about whether they can get to you before work.
Write the location the way a patient would describe it to a friend: the neighborhood, the nearest main road, which side of the interstate, where to park and whether it is free. If you sit in Germantown or The Gulch, parking is a genuine objection and answering it in a sentence removes it.
Name the areas you serve rather than listing every place name in the region. Patients coming from Brentwood, Bellevue or Donelson want to see their own drive acknowledged, and a short honest list is more convincing than a directory.
Put the address in real text, not only inside an embedded map. Maps are useful, but the words are what search engines and screen readers can read, and they are what somebody copies into a phone.
Provider bios are the referral network your newcomers do not have
When nobody in a patient's life can vouch for you, the bio page is the recommendation.
The bios on most practice sites are interchangeable: a stock portrait, a school, a sentence about a passion for patient care. Nothing there helps a stranger choose.
Write what a patient would want to know. Where you trained, what you treat most often, how long you have practiced here, what you refer out. Specific detail reads as confidence, and generic warmth reads as a template.
Use real photographs of the actual people, taken in the actual office. A newcomer is trying to picture walking in, and a stock image of somebody else's dental team quietly undermines everything around it.
Be careful with claims. Terms like specialist, expert and painless carry professional advertising rules, and what you may say about credentials and results is worth confirming with your own counsel or the state dental board before it goes live. Publish nothing you cannot substantiate on request.
The skyline video above your phone number costs you the booking
A heavy hero pushes the only thing the visitor came for below the fold and slows the page down while it does it.
Full width video of Broadway at night is a local design cliché and it works against you twice. It buries the phone number, the hours and the booking button, and it consumes the seconds a visitor was willing to give you.
The top of the page should carry four things: what you are, where you are, whether you are accepting new patients, and how to book. Everything else can wait for the scroll.
Speed is a business number, not a technical one. Every second the page spends loading is paid out of whatever you spent to bring that person there, and paid clicks are the most expensive traffic to lose this way.
Test on a mid-range Android phone on cellular data, not on office wifi with a new laptop. Size the images properly, load anything below the fold late, and be ruthless about third-party scripts. Chat widgets, review carousels, booking embeds and tracking tags stack up fast and each one arrives with a cost.
Ask for the carrier and the reason, then stop asking
The form exists to start a conversation, not to complete a chart, and every extra field is a reason to close the tab.
For a dental inquiry, the useful fields are short: name, mobile number, whether they are a new patient, their insurance carrier or self-pay, the reason for the visit, and a preferred time block. That is enough to call back prepared and to quote something honest.
Reason for visit is the field most sites skip and the one that changes the most. An emergency, a cleaning and an implant consult need different callbacks, different urgency and different people picking up the phone.
Do not ask for dates of birth, insurance member numbers or anything clinical on a public form. Collecting health information brings handling and transmission obligations, and how you store and route it is worth confirming with your own counsel and whoever manages your systems.
Add a clear line about text messages and permission to reply by text. A large share of patients would rather receive a text than a voicemail, and asking for that consent at the form is the cleanest place to get it.
The eleven o'clock booking comes from someone whose shift just ended
A service and hospitality workforce browses long after your phone has stopped being answered, and at that hour the site is the entire practice.
The downtown economy around Broadway runs on evening and overnight shifts, and short term rental turnover keeps a lot of people working hours that do not overlap with a dental office at all. Those people are on your site when nobody is there.
Real-time scheduling that writes into your actual open slots is the best answer, if your system supports it and your team trusts it. A booking button that opens a contact form and promises nothing is worse than a plainly labeled request form, because it breaks the expectation it just set.
If you cannot offer live booking, say exactly what happens next. We will call you back before nine in the morning is a promise a visitor can act on. Someone will be in touch is not.
Set up an automatic text reply to missed calls and after-hours form submissions. The person who filled in your form at eleven is filling in someone else's at ten past.
Set the type for the patient who is reading at arm's length
A lot of the treatment that pays for the practice sits with older patients, and thin gray text on white is where they give up.
Small light type is the most common accessibility failure on practice websites and it lands directly on the group most likely to book significant work. Use a comfortable body size, real contrast and generous line spacing.
Make the phone number a tappable link everywhere it appears, and make tap targets big enough for an imprecise thumb. A number that has to be copied out by hand loses calls that were already decided.
Forms need visible labels that stay visible, not placeholder text that disappears the moment somebody starts typing. Error messages should say what to fix in words.
A proper accessibility review is worth doing rather than guessing at, both because it widens who can use the site and because it is a reasonable thing for any public-facing business to have looked at.
Questions we actually get
- How fast does a dental website need to be?
- Fast enough that a phone on cellular data shows the phone number and booking button almost immediately. Rather than chasing a score, test the real experience on a mid-range Android on a normal connection. Heavy hero video, unoptimized photos and stacked third-party scripts cause most of the damage.
- Should we publish our prices?
- Publishing what a new patient exam includes and how payment works generally helps, particularly with self-pay patients, who are a real segment here. Ranges are fine if you say clearly that the final number depends on what the exam finds, and if the front desk quotes the same thing you published.
- Do we need a smile gallery?
- Only if you can maintain it properly. Before and after images are the heaviest content on most practice sites, and what you may claim alongside them is governed by professional advertising rules worth confirming with your own counsel or the state board. A small, well documented set beats a large unsourced one.
- Is online booking worth it if our schedule is complicated?
- Sometimes the honest answer is a well designed request form with a clear callback promise. Live booking only helps when it writes into the real schedule and the team trusts it. A booking button that quietly becomes a contact form damages trust at the exact moment you were earning it.
- How many pages does a practice site actually need?
- Fewer than most agencies propose, and each one substantial. A strong homepage, real provider bios, a location page written for the drive, separate pages for the two or three procedures you want more of, and clear pages on payment and new patient process will outperform a site with thirty thin pages.
