How to Build a Plumber Website Without Code in 2026
A plumber website without code starts with one description: the jobs you take, the area you cover, and how fast someone can reach you. Zugo builds the page from that text, boots it in a sandbox to check it opens, and publishes it to a live address. A simple site takes about a minute.
A plumbing site has an unusual reader. Half your visitors are standing in a flooded kitchen on a phone, and they will decide in about eight seconds whether to call you or the next result.
What does a plumber's website have to do in eight seconds?
Three things, in this order. Show that you cover their area. Show that you can come today. Give them a phone number that dials with one tap. Everything else on the page is for the calmer half of your visitors who are planning a bathroom.
That ordering has consequences for the layout. The phone number belongs in the hero and in the sticky header, not in a footer. The covered areas belong as readable text near the top, because "do you come to my town" is the question that kills the call before it starts.
The calm visitors need different things: photographs of finished work, your registration numbers, insurance, and a quote form that does not demand a phone conversation. Both audiences fit on one page as long as the emergency path is on top.
What should the prompt say?
Name the trade, the area, the emergency policy, and the trust markers. A vague prompt gives you a generic trades page. A specific one gives you a page that answers the two questions that decide the call.
Build a website for a plumber covering [town and surrounding areas].
Sections:
1. Hero: business name, "Emergency plumber in [town]",
phone number as a tap-to-call button, hours including out-of-hours.
2. Areas covered: list every town and postcode district.
3. Services: emergency leaks, boiler repair and servicing,
bathroom installation, blocked drains, radiator work.
4. Pricing: call-out fee, hourly rate, out-of-hours rate,
and a note that quotes for larger jobs are free.
5. Credentials: registration numbers, insurance, years in trade.
6. Recent work: space for photos with a one-line caption each.
7. Quote form: job type, address, urgency, contact.
Tone: plain, no marketing language. Palette: [your colours].
The areas list is the highest-value block on the page. Plumbers lose calls to competitors who simply wrote the town names down. It is text, it costs the cheapest action to edit, and it answers a search query directly.
If a blank prompt is the obstacle, Zugo ships 25 templates and a local-service template gives you a working shape to edit. The templates guide covers the choice.
Should you publish your rates?
The trade argues about this and the arithmetic usually favours publishing. Being clear about the call-out fee filters out the callers who were never going to accept it, and those calls cost you time you cannot bill.
| What you publish | Effect on calls | When it fits |
|---|---|---|
| Call-out fee and hourly rate | Fewer calls, far better ones | Reactive work, emergencies, small repairs |
| "From" prices per job type | Sets expectations, keeps the phone busy | Boiler services, drain clearing, tap replacement |
| Free quote, no prices | Most calls, most unbillable time | Installations and bathrooms quoted on site |
| Nothing at all | Callers assume the worst | Rarely the right answer |
A useful middle position: publish the call-out fee and the hourly rate honestly, then say that installations are quoted free after a visit. That covers both halves of a plumbing business without pretending a bathroom refit has a list price.
Whatever you choose, write the out-of-hours rate down. A customer who discovers the night surcharge at two in the morning becomes a bad review, and that review outlives the job.
What does the site cost in credits and time?
Zugo bills per action rather than per hour, so the project is priceable before you start. A plumber's site is a single build. It only becomes a multi-page platform if you add customer accounts and a job history, which most one-van businesses never need.
| Action | Credits |
|---|---|
| Edit in chat | 3 |
| Single-page build | 6 |
| Multi-page platform, first three pages | 12 |
| Each page beyond the first three | 3 |
| Hi-Fi edit | 6 |
| Hi-Fi build | 12 |
Free gives 5 credits, enough to look around, and a build costs 6, so a real site starts on Pro at $25 a month with 200 credits. Business is $99 a month. Hosting for the published site is included, which for a sole trader removes one more monthly invoice to chase.
Set against the usual alternatives, that is the whole argument. An agency site for a trades business runs into four figures and a change request takes a week. Adding a new covered town here is a sentence typed at the end of a working day.
How do you know the page works when it matters?
Every build is booted in a sandbox before it is handed over, and a failure is reported as a failure rather than delivered as a blank page. That lowers the risk of publishing something broken. It does not remove it, and no builder should claim otherwise.
What the check confirms is that the page rendered. It cannot confirm that the phone number has the right digits, that the covered areas match where you actually drive, or that the quote form reaches an inbox you open. Tap your own number from the published page and see whether your phone rings.
Then look at the page on a phone in bright daylight, one-handed. That is the real usage condition. If the call button is not reachable with a thumb without scrolling, that single edit is worth more than every other change on the page.
How do you get found in your own town?
Publishing is one action and the site goes live at yourbusiness.zugo.run. Connect your own domain quickly, because trades are judged on looking established, and the domain goes on the van. The custom domain guide covers the DNS records.
Local search rewards plain facts written out. Town names, postcode districts, the words customers actually type such as "emergency plumber" and "blocked drain", opening hours, and whether you charge extra at weekends. None of that is a trick, it is just writing down what you already know.
Google Analytics answers one question worth asking: how many visitors tapped the call button. If traffic is fine and calls are not, the problem is the top of the page, and that is an edit rather than a new site.
Where does an AI builder stop for a trades business?
Four limits, named plainly.
Job scheduling and dispatch are separate software. Live availability, van routing, and job sheets belong in a field-service system. Zugo can build a booking form and a database with Supabase behind it, but replacing a dispatch tool through prompts is not the right project.
Reviews have to be real. Do not let a build fill a testimonial block with invented names. Put your genuine reviews in, or leave the section out until you have three.
Certifications are yours to state correctly. Registration numbers, gas or water credentials, and insurance details go on the page exactly as they appear on your documents. Getting those wrong is a legal problem, not a design one.
Payments are optional here. Most plumbing work is invoiced after the job, so a checkout usually adds nothing. If you do sell fixed-price services or annual boiler plans, payments in an AI-built app covers the Stripe side.
Inside those limits the outcome is a fast, plain page that gets the phone ringing and takes ten minutes to update when your rates change. Describe your business in a paragraph at zugo.dev and look at the first build.