Will my site look exactly the same?

The goal is preservation, not re-design: we fetch the real HTML and CSS of the page you point us at, clean it, and open it in the editor as-is. What you edit is what you had. Pages built heavily in JavaScript can be imperfect, because scripts are stripped for safety — what remains is your content and styling.

What happens to my images?

They are copied to our own storage and the page is rewritten to serve them from there. Your old site can go away without your new one breaking, and you are never hotlinking another server.

How does the AI editing work?

You describe the change in plain language — 'make the heading say we accept walk-ins' — and the assistant replies with a list of exact find-and-replace changes, which are applied to the page deterministically. Every anchor must match the page exactly once: if the model points at text that appears twice or not at all, the whole edit is refused rather than applied in the wrong place. Your page is never regenerated wholesale.

Is there a size limit?

Yes. Extremely large pages are refused with a clear error instead of silently failing. It is a deliberate bound so an AI edit stays fast and reviewable; normal clinic pages are comfortably inside it.

Every explicit save snapshots the site, and you can restore any previous snapshot from the revisions list. Restoring snapshots your current draft first, so an undo is itself undoable.

Capturing and editing a clone is free while you are previewing. Publishing it — putting it on your domain as your live site — requires a paid plan (Pro or above). See the pricing page for current plans.

Pro plan and above to publish

Change platforms without throwing away your design

Point us at your current website. We capture the real pages, you keep editing them in a visual editor — with AI assistance that can only make the exact changes you ask for — and publish when you are ready. Nothing is re-designed unless you ask for it.

What it is

The usual migration story is 'rebuild everything and hope the result looks like you'. This is the other path.

Most clinics coming to a new website platform are not unhappy with how their site looks. They are unhappy with what is under it: no editing control, no booking, a designer who left. The rebuild path asks you to give up a design that works and gamble on a generated one. The clone path does not: we fetch the actual HTML and CSS of your existing page, strip out anything unsafe, and hand it to you in a visual editor as your starting point.

From there it behaves like any ClinicSite site. You edit visually, or describe changes and let the AI apply them; every save is versioned; and publishing runs under the same strict security policy as the rest of the platform — captured pages get scripts and inline event handlers removed, not preserved.

How an AI edit stays under control

The failure mode to design against is an assistant that rewrites your homepage when you asked it to change one word. This one cannot.

It returns changes, not pages

The assistant never regenerates your site. It replies with a short list of exact find-and-replace changes, and a deterministic function — not a model — applies them to the page you already have.

Anchors must match exactly once

Every change names the exact text it replaces. If that text appears twice, or has drifted, or does not exist, the whole edit is refused with an explanation. A hallucinated anchor cannot splice content anywhere.

The result is sanitized again

Whatever the assistant touched, the edited page passes back through the same sanitizer as the original capture: scripts, inline handlers, and scripting URLs are removed before anything is stored.

You review before it is live

Edits land on your draft. Nothing reaches your published site until you press publish, and every explicit save is a restore point you can go back to.

What carries over — and what deliberately does not

Your layout, text, styling, and images carry over. Scripts do not: a captured page is stripped of its JavaScript before it ever becomes a draft, because running a foreign clinic’s — or your own abandoned vendor’s — unreviewed scripts on a healthcare site is exactly the kind of inheritance you are trying to escape. Widgets that depended on those scripts (third-party chat bubbles, trackers, embedded tools) will not function; the ClinicSite equivalents, where they exist, are added by the platform instead.

Forms on the captured page are inert, like every form on a published ClinicSite site: form-action ’none’is part of the published site’s security policy, so captured contact forms do not silently start collecting patient data on a platform that was never designed to receive it. Contact runs through phone, email, and chat on qualifying plans.

Revisions come with it

Every explicit save in the editor snapshots the site automatically, so “the AI changed too much” has a one-click answer. This is the same revision history generated sites have.

Honest limits

What cloning does and does not do.
Capability	Status	What that means
Preserve your existing design	Built	Your real HTML and CSS are captured and opened in the editor as the draft.
Visual editing after capture	Built	A full design editor on the captured page: edit text and styles directly, save, and restore any previous save.
AI-assisted edits in plain language	Built	Applied as exact, anchored find-and-replace changes — never a regenerated page. Very large pages are refused with a clear error.
Rehosting your images	Built	Images are copied to ClinicSite storage so nothing is hotlinked from your old host.
Carrying over your scripts and embedded widgets	Not yet	Scripts are stripped on purpose. Third-party widgets that need them will not function.
Publishing on a free plan	Not yet	Previewing and editing a clone is free; publishing it to your domain requires a paid plan (Pro or above).

Cloning is one of the two ways to start. If you would rather have a new design built from your real details, that is the AI website builder. Current plans are on the pricing page.

Frequently asked questions

Will my site look exactly the same?: The goal is preservation, not re-design: we fetch the real HTML and CSS of the page you point us at, clean it, and open it in the editor as-is. What you edit is what you had. Pages built heavily in JavaScript can be imperfect, because scripts are stripped for safety — what remains is your content and styling.
What happens to my images?: They are copied to our own storage and the page is rewritten to serve them from there. Your old site can go away without your new one breaking, and you are never hotlinking another server.
How does the AI editing work?: You describe the change in plain language — 'make the heading say we accept walk-ins' — and the assistant replies with a list of exact find-and-replace changes, which are applied to the page deterministically. Every anchor must match the page exactly once: if the model points at text that appears twice or not at all, the whole edit is refused rather than applied in the wrong place. Your page is never regenerated wholesale.
Is there a size limit?: Yes. Extremely large pages are refused with a clear error instead of silently failing. It is a deliberate bound so an AI edit stays fast and reviewable; normal clinic pages are comfortably inside it.
Can I undo a change?: Every explicit save snapshots the site, and you can restore any previous snapshot from the revisions list. Restoring snapshots your current draft first, so an undo is itself undoable.
What does it cost?: Capturing and editing a clone is free while you are previewing. Publishing it — putting it on your domain as your live site — requires a paid plan (Pro or above). See the pricing page for current plans.

Keep reading

See what your clinic site could look like

Paste your current website address. You get a full generated replacement to look at — free, no account, no card.

Rebuild my site free See how it works

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