Feature

An AI website builder that only uses facts from your clinic

Paste your current web address. We read the site, hand what we found to a language model, and build you a complete replacement page. The model is told to use only real facts and to leave a section out rather than invent one — which matters more on a medical site than anywhere else.

Two ways in: migrate an existing site, or start from nothing

Most clinics that come to us already have a website. It is usually not that the information on it is wrong — it is that the site is slow, hard to read on a phone, and expensive or awkward to change. Throwing away the accurate information along with the design is a bad trade, so the builder starts by reading what you already have.

You paste your web address at /start. We fetch up to three pages of that site, with a 1.5 MB cap and an eight second timeout, through a fetcher that is guarded against server-side request forgery so a pasted address cannot be used to reach anything private. From those pages we parse the title and meta description, any JSON-LD structured data, your logo image, your theme colour, your phone number, your email address, your postal address, your opening hours, your social links and any external booking link. That parsed set of facts is what the model is given.

If you do not have a site yet, the same builder runs from scratch. You describe the practice and the builder works from your description. There is less confirmed material to build from, so you should expect fewer sections and more editing afterwards. That is the honest trade, and it is the same constraint at work: the builder writes from what it has been told, not from what it can imagine about a clinic like yours.

Generation happens in two phases

First a hero, then the full page. The split exists for a practical reason rather than a stylistic one.

  1. 1

    Phase one: a hero, so you can pick a direction

    The first pass renders only the above-the-fold portion of the page — the sticky header and one hero section, with the typeface, palette and spacing that will define the rest of the site. It is small, so it is fast and cheap to produce. You look at it and decide whether that is the direction you want.
  2. 2

    Phase two: the complete page in the same design system

    Once you have chosen a direction, the approved header and hero are handed back to the model as a style reference and the full page is built around them. The rest of the page inherits the fonts, colours and spacing you already approved instead of drifting into a different look halfway down.
  3. 3

    Then you edit it

    The finished page opens in the visual editor. Nothing about the generated result is fixed — this is a first draft produced in a minute or two, not a final answer you have to argue with.

The alternative design — one long generation that produces the whole site at once — means you wait for a complete page before you learn that the art direction is wrong, and then wait again for a full rebuild. Splitting the work puts the cheapest, fastest decision first. Art direction is the thing people react to immediately and the thing a model is least able to guess correctly on the first try, so it is the right thing to put in front of you early.

Only real facts from your site

This is the part that separates a clinic website builder from a general one. Ask a generic AI site builder for a medical practice page and it will happily produce a polished result containing a Dr. Sarah Chen who does not exist, a list of accepted insurers nobody checked, a starting price for a consultation nobody set, and five-star reviews from patients who were never seen. It reads well. Every sentence of it is a liability.

On a clinic website that is not a cosmetic problem. A fabricated clinician name is a claim about who is licensed to treat people at your address. A fabricated insurance list tells a patient their visit is covered when it is not, and they find out at the desk. A fabricated price is a quote you did not give. A fabricated testimonial is an invented patient — which is both a false advertising problem and, if it had been real, a disclosure problem. Whoever publishes it owns it, and that is you, not the model.

So the constraint is written into the system prompt the generator runs on, in the imperative: use only real facts from the provided content, never invent providers, prices, insurers or contact details, and omit a section rather than fabricate it. That last clause is the load-bearing one. The failure mode of a language model asked for a complete website is that it fills every slot in the template, because an empty slot looks like a mistake. Telling it that a missing section is the correct output when the facts are missing is what makes an absent team section possible.

The practical result: if your current site names three physicians, the generated site names those three. If it names none, the generated site has no team section, and you add one yourself with names you can stand behind. We would rather hand you a shorter page than a longer one you have to audit line by line.

This is an instruction, not a guarantee
The constraint is a hard instruction to the model and it shapes the output strongly, but no language model is perfect. Read the draft before you publish it, the same way you would read anything going out under your practice’s name. The builder is designed so that reading it is quick — the material should all be recognisable to you, because it came from you.

What a generated site contains

The output is one self-contained HTML document — no build step, no page framework — styled with the Tailwind Play CDN and Google Fonts. It is designed to look specific to your practice rather than templated: a paediatric clinic and a surgical group should not come out looking like the same website with different words in it.

Sticky header

Your logo if we found one on your current site, otherwise a clean wordmark of the clinic name, with a contact or booking call to action that stays visible as the visitor scrolls.

Hero

The above-the-fold section you approved in phase one, carrying the headline, subheadline and primary call to action.

Services

What you treat, rewritten to read clearly, from the service information found on your existing pages.

About

The practice’s own description of itself, modernised rather than replaced.

Providers

Real named clinicians only. No section at all if your source material names nobody.

Testimonials

Only patient words that actually appeared on your site. Never generated, never padded, and omitted entirely when there are none.

Insurance

Only plans your current site says you accept. No plausible-looking list.

Contact

The real phone number, email address, postal address and opening hours we parsed. Phone numbers are tel: links and email addresses are mailto: links, so a tap dials or opens a message.

Footer

Navigation and practice details, closing with a small Powered by ClinicSite.net line.

Navigation within the page uses in-page anchors, and the generator is instructed never to invent an external URL. A link that goes nowhere is a small annoyance on a blog and a real problem on a clinic site, where the links people follow are the ones that lead to booking and to directions.

You own the result: visual editing after generation

Generation ends with a draft, and drafts need editing. Every generated site opens in a block-based visual editor. You click a block to change its text, drag blocks to reorder sections, add blocks that the generator left out and delete anything you do not want. There is no code to write and no template you are locked inside.

This is the second half of the honest-facts argument. A builder that refuses to invent your provider list is only useful if adding your real provider list afterwards is easy. The same goes for the insurers you accept, the services you have added since your last site update, and the booking link you want people to reach. The generator gets you to a complete, accurate starting point fast; the editor is where you make it yours. Walk through the whole sequence on how it works.

Publishing, domains and security

When the site is ready you publish it to a subdomain of clinicsite.net, or to your own domain. For a custom domain you can either buy a managed .clinic domain through us, handled via Porkbun, or bring a domain you already own by pointing it at Cloudflare nameservers. Either way HTTPS certificates are issued and renewed automatically through Caddy and Let’s Encrypt, so there is no certificate to remember to renew.

Published sites are served under a deliberately strict content security policy. The default source is nothing at all; no external JavaScript is permitted beyond the Tailwind CDN the page is styled with; outbound connections are blocked unless you have configured the chatbot; form submissions, plugin objects and base URI rewriting are all disabled. The effect is that a published clinic site is a document that renders and does nothing else. It has no route through which visitor information can leave it, which is the property you actually want on a healthcare site. More on that in the HIPAA builder guide.

Model reliability

Generation runs on Anthropic’s Claude by default, with a GLM model from z.ai configured as a fallback. If the primary provider is unavailable, generation is served by the fallback instead of failing. This is not a performance claim — it is the boring reason your Tuesday afternoon is not wasted because someone else’s API is having a bad day.

What the builder does not do

Some of these are deliberate design decisions and some are simply not built yet. We would rather you knew which before you started than found out after you published.

Capabilities of the generated website itself.
CapabilityStatusWhat that means
Contact and booking linksBuiltReal phone numbers as tel: links, real email addresses as mailto: links, and an external booking link you paste in if you use one.
Lead capture formsNot yetPublished sites block form submission entirely, and the generator is told forms must not submit anywhere. Patient contact runs through calling and emailing you directly, which means no patient information is collected through the website at all.
Structured data for search enginesNot yetGenerated sites emit clean semantic HTML and carry over the meta title and description from your existing site, but no JSON-LD schema markup is produced.
Editing after generationBuiltBlock-based visual editing of every section, with no code and no locked template.
Why no forms is a defensible answer
A contact form on a clinic website collects whatever a patient types into it, and patients type symptoms. That turns an ordinary marketing page into something holding health information, with all the storage, access and retention questions that follow. A site that hands the visitor a phone number and an email address instead never takes custody of that information. If you need intake, run it through the system you already use for it.

Trying it, then paying for it

The preview is free. No account, no card: you paste an address, pick a direction, and get a complete generated site to look at. Preview sites are deleted after seven days, so if you want to keep one, move it onto a plan before then.

Publishing requires a subscription. A paid plan opens with a 14-day free trial. A card is required at checkout and nothing is charged that day; the first charge happens when the trial ends, and if there is no payment method on file the subscription cancels rather than charging you. You can cancel at any time from the billing portal. Plan details are on the pricing page.

Frequently asked questions

Do I need an existing website to use the builder?
No. If you paste a web address we read that site and build from what is on it. If you do not have a site yet, you describe the practice at /start and the builder works from your description instead. The from-scratch path produces fewer sections, because there is less confirmed information to work from.
Will it make up the names of my clinicians?
No. The generator is instructed to use only real facts from the material it was given, and to omit a section rather than fabricate one. If your current site does not name your providers, the generated site has no team section. You can add one yourself in the visual editor, with the names you supply.
How much of my current website does it read?
Up to three pages, with a 1.5 MB size cap and an 8 second timeout. It parses the page title and description, JSON-LD, your logo, your theme colour, phone number, email address, postal address, opening hours, social links and any booking link it finds. If your key information lives deeper than three pages, add it in the editor after generation.
Can I change the result, or am I stuck with what the model produced?
You can change all of it. The generated page opens in a block-based visual editor where you edit text, reorder sections, add sections and remove them without writing code. Generation is the starting point, not the final say.
What happens if the AI provider has an outage?
Generation runs on Anthropic's Claude by default with a GLM fallback from z.ai. If the primary provider is unavailable the request is served by the fallback, so a single provider outage does not stop you building a site.
How long does the free preview last, and when do I have to pay?
The preview needs no account and no card, and preview sites are deleted after seven days. Publishing requires a subscription. A paid plan starts with a 14-day free trial; a card is required at checkout, nothing is charged that day, and the first charge happens when the trial ends. If no payment method is on file the subscription cancels rather than charging you. See the pricing page for plan details.

Point it at your current site and see what comes back

A full generated replacement, built only from what is already on your website. Free, no account, no card.

Free preview · no card · previews are deleted after 7 days