AI Website for Doctors: Page Plan, Contact Forms and Privacy Checks

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for AI Website for Doctors: Page Plan, Contact Forms and Privacy Checks.
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for AI Website for Doctors: Page Plan, Contact Forms and Privacy Checks.

A doctor can build a practice website with an AI builder or ChatGPT-written copy using a plain page plan: home, services, doctors, appointments, fees, patient information, contact and privacy pages. The contact form needs the most checking. Collect only name, contact details and preferred time, never symptoms, and audit every tracker the site loads before launch.

The build is the easy part. What goes wrong for medical sites is not the design but what happens behind it: a form that emails patient messages through ordinary channels, an analytics or advertising tag quietly sending page visits to a third party, a chat widget storing conversations on a server nobody read the terms for. Clinical AI tools and scribes are a separate decision, with their own agreements and consent steps, and nothing here depends on them.

Follow me on Instagram@sagnikteaches

Builder or chat assistant: which does what

These are two different jobs, and most doctors use both. An AI website builder (the ones inside Squarespace, Wix and similar services) generates a whole site from a short brief: layout, pages, placeholder copy, a form. A chat assistant (ChatGPT, Claude, Gemini) writes and rewrites the words, and can draft a page plan or a privacy notice for you to adapt.

Connect on LinkedInSagnik Bhattacharya
JobAI builderChat assistantYou
Page structure and layoutFast first draftCan suggest a page planApprove and prune
Writing the wordsGeneric first passBetter at tone and rewritingCheck every claim
Contact formAdds a standard formWrites the wording around itDecide what it collects
Privacy noticeTemplate, if offeredFirst draft to adaptHave an adviser review
Trackers and cookiesSometimes adds them by defaultCannot see your siteAudit them yourself

As anchors, Squarespace's pricing page listed its four plans at $19, $29, $49 and $99 a month on annual billing ($25 to $139 month to month), with AI credits allotted per plan, and Wix's plan page showed roughly $17 to $160 a month across its four paid plans on yearly billing, noting that prices vary by location (both checked November 2026). These change, and prices shown to you may include local tax, so check the plan page. The cost comparison with hiring a designer is in AI website builder or web designer: what each really costs. Be aware that some builders are hard to leave: a Wix site cannot be moved to another host, which matters if your needs later outgrow it.

Subscribe on YouTube@sagnikteaches

The page plan for a small practice

Prompt a builder with the plan, rather than letting it invent one. A six-doctor practice does not need forty pages. Illustrative plan, with what each page must contain and what to keep off it:

  1. Home. What you offer, who you serve, opening hours, how to book, and a prominent emergency notice. Keep claims factual: services, not outcomes.
  2. Services. One short section per service (general consultations, minor procedures, health checks). Describe what happens, not what it achieves.
  3. Our doctors. Name, role, registration details if your rules call for them, and a short professional biography. Use only credentials you can prove.
  4. Appointments. How to book (online booking tool, phone), what to bring, how to cancel, and what to do if it is urgent.
  5. Fees and payment. Consultation fees, insurance or funding arrangements in general terms. Prices change, so give a review date.
  6. Patient information. Practical content: new-patient forms, how to request records, how repeat prescriptions work, how to give feedback.
  7. Contact. Address, phone, map, opening hours, and the form (see below).
  8. Privacy notice and cookie information. What the site collects, why, and who processes it.
  9. Accessibility statement. Contact for people who cannot use the site, and what you have done to make it usable.

Nine pages is enough. If you want health-information articles later, make that a separate decision with its own review process, because informational content has its own accuracy and advertising considerations.

The Complete Excel Course with AI Integration thumbnail

The Complete Excel Course with AI Integration

From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.

By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner

Buy now

A worked example: a three-doctor practice, one weekend

Illustration only. A three-doctor general practice wants a new site to replace an old one. The practice manager sets aside a weekend and uses a builder plus a chat assistant. Rough timings:

StepTime
Write the brief and page plan (use the plan above)45 minutes
Generate the site in the builder and choose a layout1 hour
Rewrite the copy with a chat assistant, page by page2 hours
Doctors read and correct every sentence1.5 hours
Set up the form, booking link and map1 hour
Tracker and cookie audit (see below)1 hour
Privacy notice drafted and sent to an adviser1 hour, plus the adviser's time
Mobile check and launch1 hour

That totals about nine hours of practice time and sits comfortably inside a weekend, though the adviser's review will take longer. At the lower end of the builder prices above, the annual cost for the platform would be a few hundred dollars plus a domain. Compare that with whatever you currently pay your web provider, and with the time your reception team spends answering the same questions by phone.

Here is the brief given to the builder. Note what it does not contain: no patient information, no clinical claims.

Create a website for a three-doctor general practice. Pages: Home,
Services, Our doctors, Appointments, Fees, Patient information, Contact,
Privacy notice, Accessibility. Tone: calm, clear, professional, plain
English. Opening hours Monday to Friday 8am to 6pm, Saturday 9am to 1pm.
Add a banner on every page: "If this is an emergency, call your local
emergency number. Do not use this website." No testimonials, no before and
after images, no claims about results, no prices except where I give them.

Writing the copy: ChatGPT-style help without the claims

Chat assistants write fluent copy that drifts into marketing language. For a doctor, that is a risk, because phrases such as "best", "leading", "guaranteed", "pain-free" or "cure" may break the advertising rules that apply to you. Put your guardrails into the prompt, and read every sentence as if a regulator might.

Rewrite this services paragraph for our practice website. Rules: no
claims about results, outcomes, safety, speed of recovery or being the
best or leading; no testimonials; no comparisons with other practices; no
medical advice; plain English at about age 12; under 90 words.
Original: "We offer the best minor surgery service with fast, painless
results and 100% patient satisfaction."

A typical response keeps the facts and drops the hype: "We carry out minor procedures in the practice, including removal of small skin lesions under local anaesthetic. Your doctor will explain what is involved, the risks and the aftercare before you agree to go ahead." The edit a doctor makes is to confirm the procedure list is true for your practice today and the consent sentence matches what you do. The "100% satisfaction" claim disappeared, which is the right outcome.

Things to scan for in every AI-written page

  • Superlatives and absolute words: best, leading, safest, always, never, guaranteed.
  • Outcome words: cure, heal, reverse, eliminate, results.
  • Invented credentials, awards, memberships or years of experience.
  • Medical advice that belongs in a consultation, such as what to take for a symptom.
  • Statistics or study claims with no source you can open.

The general method for writing a site's pages with AI, covering tone and structure, is in how to write your website copy with AI: home, about and services, and a good analogue for a regulated profession is AI website copy for financial advisers, where the same claim-by-claim review applies.

The contact form: decide what it may collect

The contact form is where a medical website differs from any other. A visitor who is worried will write what is worrying them. If your form has a free-text "message" box and nothing to discourage it, you will receive health information, and it will travel through whatever the builder uses to deliver form messages.

Three design choices that reduce the risk

  1. Collect the minimum. Name, phone or email, and preferred time for a call back. Nothing else.
  2. Warn and redirect. Add a line above the message box, if you keep one: "Please do not include health details. We will call you to discuss. In an emergency, call your local emergency number."
  3. Prefer booking and phone. A booking link into the practice's own system, or a phone number, avoids the problem. If the website only needs to say "ring us on [number]", it is the safest form of all.

If you do need to collect health information, such as a pre-visit questionnaire, use a form service designed for it, with a signed agreement. As an illustration, Jotform's health-forms page says eligible customers with its HIPAA features enabled (it points to its Gold or Enterprise plans) can execute a signed business associate agreement. Other vendors have similar routes. Verify the plan, the agreement and the exact features on the vendor's own page before you build anything, and do not assume that a standard builder form is covered by anything. A builder's help pages also flag practical limits: for example, Squarespace's help centre says trial sites do not send form submission emails at all (it suggests connecting Google Drive or Mailchimp storage during a trial), so a test on a trial site proves nothing about delivery.

Where form messages actually go

Ask three questions of any form, and write the answers down: Where is the submission stored (in the builder's dashboard, a spreadsheet, a connected app)? Who receives the notification (one person's inbox or a shared one), and is that email account protected with a second factor? How long is it kept, and how is it deleted? A form that sends messages to a doctor's personal email account, with no policy on deletion, is the commonest weak point I would expect to find.

A tracker and cookie audit you can do in an hour

Builders and AI assistants love to add "helpful" scripts. Each one can send visit data to another company. Before launch, list every third party the site contacts and decide whether each stays.

  1. List the tools. Analytics, advertising pixels, chat widgets, booking embeds, map embeds, video embeds, web fonts, review widgets, live chat, newsletter pop-ups.
  2. Open the site with a browser's developer tools, or a free page-scanning tool. The network tab shows every domain contacted when a page loads. Note any you do not recognise.
  3. Decide for each: needed or not. A practice site rarely needs advertising pixels, and a pixel on an appointments page is the one most likely to cause trouble.
  4. Check the vendor's terms for what it does with the data. For example, Google's Analytics help says its policies forbid sending Google any data it could recognise as personally identifiable, and warns that page addresses and titles often carry such data by accident. That does not make analytics safe to put on every page of a medical site, because page addresses and form submissions can still reveal that someone looked for a particular service. Whether and how to use analytics on a medical site is a question for your adviser.
  5. Cookie consent. If any non-essential tool stays, use a consent banner that blocks it until a visitor agrees. If you remove them all, state in your privacy notice that the site sets no tracking cookies, and then keep it true.

Chat widgets deserve a special warning. Some builders now bundle an AI chat on the site (Wix, for instance, has Smart Chat, which runs on the plan's AI credits and switches to offline mode when they run out). A chat box on a medical site invites symptom descriptions, and the conversation sits on someone else's server. Unless the tool has a signed agreement and a clear hand-off to a human for anything urgent, leave it off. Guidance on tracking technologies on health websites is also unsettled: one health regulator's guidance was partly vacated by a court in 2024, and the regulator's page says it is still evaluating its next steps. Ask your adviser for the current position rather than relying on a tutorial like this one.

Worked examples: the appointments page and a call-saving sum

Before and after: an appointments page

A first AI draft of the appointments page often reads like a brochure: "Booking with us is quick, easy and stress-free! Our friendly team will have you seen in no time." The doctor's edit turns promises into instructions: "To book, call [number] between 8am and 6pm on weekdays, or use the online booking link. Please arrive five minutes early and bring your appointment reminder. If you need to cancel, tell us at least [24 hours] ahead so someone else can have the slot. If you feel very unwell, do not wait for an appointment: contact urgent care or the emergency number." The second version makes no promise about speed, gives the visitor four useful facts and ends with the safety line. Use that as the test for every page: could a visitor act on it, and could we be held to it?

A quick sum: is the site worth the effort?

Suppose reception takes about 25 calls a week asking the same four things (opening hours, how to register, how to get a repeat prescription, how to request records), at roughly three minutes each. That is 75 minutes a week, about 65 hours a year. If a clear patient-information page deflects even a third of those calls, the practice saves roughly 22 hours a year of front-desk time, plus the callers' frustration. These are made-up numbers, but the method is real: list your repeated questions, count them for two weeks, and build the page that answers the top four. That sum also tells you which page to write first.

A short image and accessibility check

Builders can add alt text automatically, and an AI assistant can draft it from your description of each image, but a human must check it. For a clinic-room photo the alt text might be "Consulting room with a desk, two chairs and an examination couch". Do not describe a patient, a condition or a result. Also check colour contrast on buttons, make sure the phone number is a tap-to-call link on mobile, and make sure forms can be completed with a keyboard alone. Accessibility is not an add-on for a medical site: a good share of your visitors will be older, in pain or using a phone in bright light.

The privacy notice and AI disclosure

A chat assistant can draft a first version of a website privacy notice in minutes, and you should expect to rewrite it. Give it the facts you gathered in the audit: what the form collects, where messages go, which cookies exist, how long data is kept, and who to contact. Ask it to use plain English and not to invent any legal claims. The output is a draft for your adviser, not a finished document. If your own staff use AI in the practice, the privacy notice is also where you might say so; a model for plain wording is in how to write an AI disclosure statement for your website.

Illustrative lines the audit might produce: "Our contact form collects your name, phone number or email address and a preferred time. We use it only to call you back. Please do not send health information through this form. We keep enquiries for [period] and then delete them. This site does not use advertising or tracking cookies." Every sentence there must be true, which is why the audit comes before the notice, not after.

Four ways a practice site goes wrong after launch

A claim that crosses an advertising line

An AI-written page says the practice offers "the safest vaccination service". A complaint, a regulator's letter or a competitor's report follows. Prevention is the claim scan above and one named person who approves every page before publishing.

A form that works on the live site but not on the test site

Messages do not arrive because a builder's trial mode does not send emails, or because notifications land in spam. Test on the live site with a dummy message, and test again from a mobile network.

A tracker added after launch

Someone in marketing adds an analytics script or a chat tool six months later. Put a rule in your practice AI policy that no new script, plug-in or embed goes on the site without the practice manager's approval, and repeat the audit every six months. A staff-facing policy template is in the AI usage policy for a medical practice.

Photos that reveal more than intended

AI image tools produce generic clinic photos, which are safe. Real photos of the waiting room can show patients, screens or notice boards. Use stock or generated images of rooms with no people, and label AI-generated images where your rules require it.

The nine checks before the practice site goes live

  1. Every page read and approved by a named doctor, with the date.
  2. Claims scan completed: no superlatives, outcomes, testimonials or unsourced statistics.
  3. Emergency notice on every page, and the phone number tested.
  4. Form collects only name, contact and preferred time; warning line added; test message received.
  5. Tracker list written down; each item kept or removed; cookie banner working if anything non-essential stays.
  6. Privacy notice and accessibility statement published and linked in the footer.
  7. Site checked on a phone, with large text, and with a screen reader if you have access to one.
  8. Local advertising and data-protection rules confirmed with the right adviser or regulator guidance.
  9. Review date in the diary for six months ahead.

If you would like someone to look at your page plan and tool list with you before you build, that is a good use of my AI implementation consultation.

Questions doctors ask about AI-built practice websites

Is an AI website builder better than ChatGPT-written copy?

They do different jobs. A builder produces the layout, pages and forms quickly; a chat assistant writes the words more flexibly. Many doctors use a builder for structure and a chat assistant for copy, then edit every sentence. Neither knows your local advertising rules, so the final check is yours.

Can a contact form on my website collect symptoms?

Avoid it unless the form and the system behind it are set up for health information. A standard builder form emails messages through ordinary channels and may store them in places you do not control. Keep the form to name, contact details and preferred time, and tell people not to describe symptoms.

Do I need a cookie banner?

If you use analytics, advertising pixels, embedded videos or chat tools that set cookies, data-protection rules in many places require consent before they run. A practice site with no tracking at all may not need one. Check which tools your site loads, then ask your adviser what your local rules require.

Can I put patient testimonials on the site?

Many places restrict testimonials in health advertising, and a testimonial can also reveal a patient's health information. Check your professional regulator's advertising guidance first. The safe default is to leave them out and show your services, hours and credentials instead.

Further reads

Sources: Squarespace and Wix pricing pages, Jotform HIPAA page, Google Analytics help on avoiding PII, Squarespace help on trial sites, Wix help on exporting sites and on Smart Chat AI credits, and HHS guidance on online tracking technologies, checked November 2026. Advertising and privacy rules differ by place: confirm yours.

Want your practice website planned before you build it?

On a 1:1 call we can go through your page plan, the tools your site would load and the form set-up, and decide which parts AI can build for you and which need an adviser's check.

Book a 1:1 call with me