Salon website design that books the chair you have

We start from the booking tool, not from a brainstorm. The service names on the site should match the names a guest sees when they book, so a "gloss" on the site is not a different service from the "gloss treatment" in the book. Someone at the salon confirms the list: what you offer, what you stopped offering, and which services are only with certain stylists. A service you no longer want on the book comes off the site in the same pass.

Prices go on the site when you already publish them, on the card at the desk or in the booking tool. If a cut has a set price, we use your number. If color is quoted after a consult, the page says it is quoted at the visit. We do not invent a price list to make the menu look complete. A wrong price is a conversation at the chair that you should not have to have.

Stylist pages are for stylists who want clients from the site. Each page has a photo they approve, the services they perform, and a booking link into their column. A stylist who does not want new online clients can stay off the site or be listed without a book button, whichever you prefer. When someone leaves, their page comes down. Bios stay short and factual: years at the salon if they want that, the work they focus on, and the languages they work in if that is useful. We do not replace those facts with a slogan.

• Service names aligned with the booking tool
• Prices only when you already publish those prices
• A page for each stylist who wants clients from the site
• Booking that opens that stylist's calendar
• A removal step for people who no longer work there

Mobile booking is the test that matters. The guest is often holding a phone with one hand. The book button should be obvious, and it should open the system you already use, on the right service or the right stylist when the link allows it. We do not build a second calendar inside the website. Two calendars means a double-booked chair. If your tool cannot deep-link to a stylist, we say that, and the button still lands in the real book rather than in a form that pretends the time is held.

The confirmation path should be the one your tool already sends. The website thank-you text should not say you are booked if the tool has only received a request. Wording follows the truth of the integration: requested, or confirmed. We check this on a phone, as a guest would, including a stylist page and a service page.

Hours on the site match the hours the book accepts. If the front desk answers until seven but online booking stops at five, both facts can be on the page. A map and a parking or transit note help a first visit. The phone remains available for people who need a question answered before they book, unless you would rather force the book. We follow that preference instead of adding a widget you will not watch.

• One booking system, the one that holds the real appointments
• Links from stylist and service pages when the tool supports them
• Request versus confirmed, stated the way the tool behaves
• A one-thumb test on a phone before launch
• Hours on the site matched to hours the book will accept

The gallery is work from your chairs. Color, cuts, and styling you did, photographed with enough care that a guest can tell what they are looking at. If a face or another identifying feature is in the frame, we want the guest's permission before it is public. We do not drop in stock hair and call it the salon portfolio. Guests can tell, and the stylist whose page it sits on has to live with it.

A smaller true gallery is better than a large borrowed one. We can sort by stylist or by service when you have the pictures to support the sort. If one stylist has no photos yet, their page does not borrow another person's work. It can launch without a gallery and gain photos later.

Gift cards appear only when they are real. If you sell them online through a product you fulfill, we link to that product. If you sell them at the desk and do not want online sales, the site says gift cards are available in the salon. We will not add a buy button that charges a card you cannot redeem, and we will not imply a balance checker you do not have.

Fake reviews stay off the site. We will not write guest quotes about a color correction, attach them to first names, or build a testimonial carousel from nothing. If your booking tool or a public profile has real reviews, linking there is enough. Invented praise is a fast way to look like every other template.

Doorway city pages stay off the site. "Balayage in" plus every town you are willing to drive toward, with the same paragraph, is not a salon page. You have a shop. The site can name the neighborhood and, in one section, how far guests usually come. It does not need a cloned URL per town. A second location is a second page, with its own stylists and its own book.

Guaranteed rankings stay off the site. We will not promise the map pack, a standing for a service term, or a full book. We also will not add fake scarcity, such as a banner that says booked solid when the book has openings. The useful promise is narrower: the services, the people, and a booking link that tells the truth.

Example, not a case study, and not a client result. Picture a five-chair salon. Cuts have published prices, so those prices go on the service page. Color corrections are quoted in person, so the page says that and does not invent a number. Three stylists want their own pages and their own booking links. Two do not, and they are not given pages. The book button on a stylist page opens that stylist column in the tool they already use.

They sell gift cards online through the same company that runs the book, and the link is the real catalog. The gallery is twelve photos they took, with guest permission on the three that show a face. We do not add stock to make twelve look like forty. A stylist bio that arrived with the phrase transformation artist gets rewritten to the services that stylist performs. They approve the rewrite.

The launch check is a phone: open a stylist, tap book, and land in the live tool, then confirm the site does not say confirmed when the tool says requested. That is the workflow. It is an example. It says nothing about how full the book became.