How to Build a Psychologist Website Without Code

To build a psychologist website without code, describe your specialisms, your credentials and how someone books a first session, then let an AI builder generate the pages. On Zugo a single-page practice site takes about a minute, a multi-page version a few minutes, and publishing to a live address is one click.

A therapy website has an unusual job. The visitor is often anxious, often reading at midnight, and deciding whether to trust a stranger with something difficult. That changes what belongs on the page more than any design trend does.

What does a therapy website need to do before it looks good?

Three things, in this order. Tell the reader whether you work with their problem. Tell them who you are and what qualifies you. Tell them exactly what happens if they contact you.

The third one is the most neglected and the most useful. "Write to me and I will reply within two working days with a time for a free 15 minute call" removes more hesitation than any amount of calm photography. Uncertainty is the barrier, so remove uncertainty.

Plain language beats clinical language on a public page. A visitor searching for help rarely searches by modality name. They search for the thing that is wrong. Name both: the everyday description first, the method second, so you are findable and credible at the same time.

What should the prompt say?

Be specific about who you work with. A generic prompt returns a generic wellness page that could belong to anyone, and "could belong to anyone" is the opposite of what a therapy site is for.

Build a website for [name], a [qualification] practising in [city]
and online.
Work with: [anxiety, burnout, relationships, trauma, grief], adults only.
Approach: [CBT / psychodynamic / EMDR], described in plain language.
Credentials: [degree, registration body, membership number, years].
Sessions: 50 minutes, [in person / video], [price] per session,
[cancellation policy].
Pages: home, about me, how I work, areas I work with, fees and
booking, contact.
Contact form: name, email, what brings you here, preferred times,
consent checkbox for storing the message.
Tone: warm, plain, no promises about outcomes.

That last line matters. Copy that promises results is both a credibility problem and, depending on where you practise and how you are registered, a regulatory one. The builder will write whatever tone you ask for, so ask for the careful one.

Zugo ships 25 ready templates, and a service or landing template is close enough to a practice site that rewriting the sections in your own words is a faster route than a freeform prompt.

Which pages does a private practice need?

Five or six, and each one carries a specific question. A page that answers nothing is a page a hesitant visitor abandons.

Six pages on Zugo is billed as a platform: 12 credits flat for the first three pages, then 3 credits for each additional page, so a six-page practice site costs 12 plus 9. A one-page version with the same content in sections is 6 credits and takes about a minute.

Many practices are better off with one page at first. It is easier to keep current, it reads faster on a phone, and it forces you to say the important things near the top.

How do enquiries and bookings reach you?

An unwired contact form is the worst possible failure here, because the person who wrote to you and heard nothing concludes something about themselves rather than about your form. Wire it on the day you publish and test it yourself.

Resend delivers every submission to your inbox. Supabase stores enquiries in a real database and adds sign-in, which matters if you later want a private area for existing clients. Google Analytics tells you whether people reach the contact page at all.

For scheduling, the honest answer is that most private practices are better served by embedding an existing booking tool than by building a calendar. A scheduler that handles time zones, buffers, reminders and cancellations is a product in its own right, and reproducing it through prompts is a poor use of an evening. Link or embed, then spend your effort on the words.

How do you handle client privacy on a generated site?

Carefully, and with the understanding that the website is the least sensitive part of your practice. Treat the contact form as the front door and nothing more.

Ask for the minimum. Name, email, a short message and preferred times are enough to arrange a call. Do not collect diagnoses, medication, or a case history through a public web form, because that turns a marketing page into a records system and raises every obligation that comes with one.

Publish a privacy notice saying what you collect, where it is stored, how long you keep it and how someone asks for deletion. If your registration body specifies wording, use theirs. This is a page the builder will draft for you, and one you should read line by line before publishing, since it is a statement about your practice rather than about the tool.

Be clear about the boundary: Zugo is a website builder, not a clinical records platform, and connecting a database does not by itself make a system compliant with health data rules in your jurisdiction. Compliance is a decision you make with your professional body or a lawyer, then reflect in the site.

What does a practice website cost to build and run?

Zugo's Free tier gives you 5 credits to try the flow. Pro is $25 per month for 200 credits, which works out to 33 quick builds or 66 edits, and it includes connecting your own domain. Business is $99 per month for teams.

Editing at 3 credits is the cheap action, and a therapy site changes in small ways: fees, availability, a new area of work, a revised cancellation policy. One considered build followed by occasional one-line edits is the pattern that costs least. Hi-Fi mode doubles both figures, 12 to build and 6 to edit.

Until you attach a domain the site lives at yourpractice.zugo.run, which is fine for a first send and thin on a directory listing. A real domain takes a few minutes to point, as described in the guide to connecting a custom domain.

Where does an AI builder stop for a therapy practice?

Four boundaries worth naming before you start.

Clinical records are out of scope. Notes, treatment plans and anything covered by health data regulation belong in software built and certified for that purpose. Zugo builds the public face of the practice.

Regulated wording is your responsibility. Titles you may use, claims you may make and how you must display registration vary by country and body. The builder writes what you ask for. It does not know your rulebook.

Booking depth needs a real scheduler. Recurring appointments, waiting lists, group sessions and automated reminders are all better handled by embedding a specialist tool than by prompting a calendar into existence.

Very specific logic arrives through edits, not one prompt. Sliding scale calculators, insurance eligibility checks, and intake questionnaires with branching are reachable, but through a sequence of refinements. Budget an evening rather than a minute.

Before a build reaches you it is booted in a sandbox: the site has to load and render, and a failure is reported as a failure rather than handed over as a blank page. That lowers the risk of publishing something broken and does not replace your own check. Open the site on a phone, submit your own contact form, and read the privacy page aloud before you send the link anywhere.

Write down the five problems you most want to work with, in the words your clients would use, and describe the site around them. The free credits at zugo.dev are enough to see the first version. If your next step is taking payment for sessions online, the same method applies in the guide to Stripe payments in an AI-built app.