How to Build a Salon Website Without Writing Any Code
To build a salon website without code, describe your services with prices, your hours, your address, and how a client books. An AI builder turns that into a live site in a few minutes, you publish it to a real address in one click, and you connect a form or a booking link so appointments actually reach you.
A salon site has one measurable job: turn someone who found you on a phone into an appointment in the book. Most of them fail at it for boring reasons, like a price list that lives only on Instagram or a phone number that is not tappable. This guide is about getting those right.
What does a client actually look for on a salon website?
Watch how people use these sites and the pattern is consistent. They arrive from a map listing or a social profile, on a phone, deciding in under a minute whether to book. Four things decide it.
- Prices. The single most-searched item and the one most often missing. "Prices on request" reads as expensive, and a client who has to ask usually asks somewhere else instead.
- Availability and how to book. One obvious button. Not a phone number in the footer, not an email address, one button that opens booking or a form.
- Proof of the work. Photographs of results, not stock images of a spa. This is the whole reason a beauty business needs a website rather than a text listing.
- Practical details. Address with a map, hours including which days you are closed, parking, and whether you take walk-ins.
Everything else is optional. A page about the founder's philosophy is nice; a price list that a client can read at a bus stop is what fills the chair.
What should the prompt say?
Write the services and prices into the prompt directly. This is the content the builder cannot invent correctly, and a generated placeholder price list is worse than none because it looks finished.
Build a website for [salon name], a [hair / nail / beauty]
salon in [city].
Pages: Home, Services and prices, Gallery, About, Contact.
Home: hero with the salon name, one line about what we do,
a "Book now" button, three highlighted services, and hours.
Services: grouped price list, [group names], each item with
name, duration, and price in [currency].
Gallery: grid of result photos with a lightbox.
Contact: address with an embedded map, tappable phone number,
opening hours table, and a booking request form with
name, phone, service, preferred date.
Sticky "Book now" button on mobile.
Style: [warm and minimal / bold and modern], one accent colour,
large photographs, readable on a phone.
Two lines in that prompt do disproportionate work. The sticky mobile button, because most of your traffic is a thumb on a phone screen. And the duration column in the price list, because it answers "can I fit this in at lunch," which is the second question after price.
How should bookings actually reach you?
This is the decision that matters more than the design, and there are three honest options. The table compares what each one costs you in setup and in daily friction.
| Booking route | Setup effort | What it costs you |
|---|---|---|
| Link to your existing booking system | Minutes. One button, one URL | Nothing, and the calendar you already trust stays the source of truth |
| Request form that emails you | One connector. Resend delivers the submissions | You confirm each one by hand, so it works up to a few a day and then hurts |
| Custom booking built into the site | A sequence of edits plus a database | Real upkeep. You now own a booking system, including double bookings and no-shows |
Most salons should take the first row. If you already pay for booking software with a staff calendar and reminders, the website's job is to send people to it, not to replace it. The form in the second row is right for a single-chair studio or a new salon that has not chosen software yet. The form wiring is covered in the guide to adding an AI website contact form.
How do you keep prices and hours current?
A price list that is six months stale costs you money twice: once when a client argues about the price at the counter, and once when someone books expecting a service you stopped offering.
In Zugo an update is a sentence: "raise the balayage price to $180 and remove the keratin treatment from the services list." Each edit costs 3 credits and goes through the same check as the original build, which is booted in a sandbox before it reaches you. A build that fails to render is reported as a failure rather than shown to you as working, which lowers the risk of a broken price page on a Saturday morning without removing it.
Two seasonal edits are worth planning for: holiday hours, which every salon forgets until the week before, and a promotion banner, which is one edit up and one edit down.
Where does the site live, and what does it cost?
A small multi-page salon site is a platform build: 12 credits for the first three pages and 3 credits for each page after that. A single-page version with everything on one scroll is a quick build at 6 credits. The free tier gives 5 starter credits, Pro is $25 per month with 200 credits, and Business is $99 per month.
Published sites get an address like yoursalon.zugo.run, and connecting your own domain is worth doing before you print anything. A domain on a card, a window sticker, or a receipt has to be short and yours. The setup is described in the guide to using a custom domain for an AI-built site.
Timing is honest: a single page usually lands in about a minute and a multi-page site takes several. Neither is an afternoon of work, which is the actual comparison with hiring out.
What should you do the day after publishing?
The website is one part of how a local business gets found, and on its own it is the weaker part. Three follow-ups matter more than any design change.
Claim and fill the map listing. For "salon near me" searches the map result outranks the website, and it needs the same hours, phone number, and photos. The site is where people land after the listing convinces them.
Put the link everywhere. Social profile bios, the reply text when someone messages, the confirmation SMS. A site nobody links to is a brochure in a drawer.
Add the photos you actually take. Results shot on a phone in your own light beat stock photography for this category, because clients are judging whether the work looks like what they want.
A neighbouring guide worth reading if you also sell products or arrangements is the one on building a florist website: the same local structure with an ordering step added.
When is a website not the right first move?
Honest limits, because a salon can waste a month on the wrong thing.
When you have no photographs. The gallery is the argument. Without your own images, the site is a price list with decoration, and the hour is better spent shooting results for two weeks.
When your booking software already has a public page. If clients can book, see prices, and find you through it, you need a domain pointing at it more than you need a second site to maintain.
When you need deep calendar integration. Live staff availability, per-stylist calendars, and automated reminders synced back to your existing system is integration work, and specific business logic like that gets built through edits with a developer's review rather than one prompt.
For everyone else, an evening is enough: prices published, photos up, one booking button, your own domain. You can write the first prompt at zugo.dev.