A doctor's website has a narrow job and most agencies quote for a wider one. Patients arrive with a specific question, usually whether you treat their problem, whether you take their insurance, and when they can be seen. Everything else on the site exists to support those three answers. Yet development proposals are still priced by page count and design rounds, which measures effort rather than usefulness and produces beautiful sites that patients abandon on a phone in a car park. This page sets out what a medical site must do, which requirements are genuinely non negotiable, and how to compare quotes that look nothing alike.
The three answers a patient came for
Watch a real patient use a practice site and the same pattern appears. They look for the condition or procedure in their own words, not your specialty's words. They look for whether their insurance is accepted, and if the answer is buried they call reception or leave. They look for an appointment, and if booking takes more than a minute on a phone they abandon it. A development quote should describe how each of those three journeys works before it describes a visual direction. Ask to see the proposed structure: is there a page per condition and procedure written in patient language, is insurance and payment information current and findable in one tap, does the booking flow work on a small screen with one hand. Where the practice has multiple physicians, individual profiles matter more than most agencies expect, because patients search by name after a referral and a thin bio page loses a booking that was already won. None of this needs a large budget. It needs the budget aimed at the right thing.
Accessibility and speed are requirements, not upgrades
Patients include people with low vision, motor impairments and screen readers, and the Department of Justice's guidance on web accessibility explains how accessibility obligations apply to the web for the entities covered by the ADA. Treat that as a build requirement written into the contract rather than an audit bolted on afterwards, because retrofitting accessibility into a finished custom theme costs more than building it in. The practical items are ordinary: real text rather than text in images, labelled form fields, keyboard navigation that works, sufficient contrast, captions on any video. Speed sits alongside it for a plainer reason. Patients open your site on mobile networks, often while doing something else, and slow pages lose them. Google's Core Web Vitals describe measurable loading, interactivity and layout stability thresholds, and web.dev documents what those metrics measure and how to improve them. Ask a candidate what scores they will deliver on and how they will be verified after launch. An agency that will commit to a measurable target has built fast sites before.
Privacy is a build decision, not a policy document
Medical sites collect information that is more sensitive than most, and the decisions that matter are made during development rather than in the privacy policy. Where does an appointment request go and is it transmitted and stored securely. Which analytics and advertising tags fire on pages about specific conditions, and what do they transmit about a visitor who was reading about a diagnosis. Who has access to form submissions, and are they retained longer than needed. Practices have been caught out by tracking pixels placed on symptom pages by a marketing vendor with good intentions and no clinical context. Ask any developer to list every third party script the site will load and what each one sends, and ask which vendors will handle information requiring a business associate agreement. A developer who cannot produce that list has not thought about it, which is a different and worse answer than a list you disagree with.
Comparing quotes that look nothing alike
Development quotes diverge because the scope behind them does. Force them onto the same footing with a one page brief listing your physicians, conditions and procedures, locations, the booking system to be integrated, whether content will be written by the agency or supplied, and what must be migrated from the current site. Then ask five questions of each candidate. Who owns the code, the domain and the hosting when we part. What content management system will the front desk actually use, and can a non technical person update insurance information without calling you. What is the post launch arrangement, and is it a support retainer, a fixed hourly rate or nothing. How will URLs from the existing site be redirected, since a rebuild that drops established pages loses visibility that took years to earn. And who writes the clinical copy, because if the answer is your physicians then the timeline belongs to them and not to the agency. Where a build sits alongside an ongoing search engagement, ask whether the same team does both, since a rebuild handed over without redirects is the most common way search results for doctors quietly collapse.
Questions people ask about website development for doctors
Should I use a template or a custom build?
A well chosen template with the budget spent on structure, content and booking beats a custom build for most single specialty practices. Custom is justified when you have unusual integrations, many locations or a genuine brand requirement. Decide by asking what the extra cost buys a patient, and if there is no clear answer, take the template.
Will a redesign hurt our search visibility?
It can, and the usual cause is a rebuild that changes URLs without redirects or drops the pages that earned the visibility. Put a redirect map and a content inventory in the contract as deliverables, and check them before launch rather than after the traffic drops.
Does accessibility really apply to a private practice site?
Accessibility obligations under the ADA extend to the web for covered entities, and the Department of Justice's web guidance explains how. Beyond the legal position, the same fixes improve usability for everyone, including older patients on phones, which is a large part of most practice populations.
Who should write the medical content?
An agency writer can draft and a clinician must review, and the review is where timelines slip. Agree in advance how many hours a week your physicians will give to review, because a build waiting on approvals bills the same as one that is moving.