Guide for hosts
What a retreat website needs
A retreat website needs three things to do its job: a page that makes the case for the trip, a booking flow that takes a deposit without friction, and enough structure that people, and search engines, can find it. Everything past those three is extra.
I've built websites since 1999, back when that meant typing HTML by hand, When a retreat page doesn't convert, the first thing I look for is which of the three is missing.
What does a retreat website need on it?
A retreat website needs the retreat page itself (what it is, who it's for, the dates, the price, what's included), real photos of the actual rooms and the actual food, the host in their own words, an FAQ, and a booking button that's never more than a scroll away. That's the floor. Nothing on that list is optional, and nothing past it is required.
Order matters more than most hosts expect. Open with who this is for and what changes for them, not a biography. Follow with what's included and what it costs, because a reader deciding whether to keep reading needs the price before the third paragraph, not the eighth. Then the host, then proof if you have it (a past guest's own words, not a star rating pulled from nowhere), then the FAQ, then the booking button again. What's actually included (the venue, the room, the days) comes straight out of the planning work in How to plan and run a retreat.
If you're capturing a name and an email from people who read the whole page and still aren't ready to put down a deposit, that's a second page doing a second job: the list you warm before the next launch. That's a different piece of work, covered in Email marketing for retreat hosts.
Do you need a whole website, or just one page?
Most hosts running their first retreat need one really good page, not a whole site. One page that does everything above, on its own domain or as a page on a site you already have, can be enough to fill a retreat. A full website, with a blog, a homepage and a navigation menu, is a job for your second or third year, once you're running more than one retreat and need somewhere for all of them to live.
The trap is spending your limited time and money on a homepage, an about page and a contact form before the one page that actually takes money exists. Build the retreat page first. Build the rest of the site, if you ever need it, once that page has already proven it works. Our free planning checklist, The Other Half, puts this step in order alongside the rest of your launch, so you're not guessing what comes before what.
What should the booking page say?
A booking page should remove every open question before it asks for money, not repeat the pitch you already made. By the time someone clicks "book," they've read the retreat page. The booking page's job is different: state the deposit amount, when the balance is due, the cancellation policy in plain language, exactly what's included for that price, and who to contact if something goes wrong before the retreat.
Don't make someone hunt for the cancellation terms after they've already paid a deposit. Put it on the booking page, in the same place every time, even if it's a sentence instead of a paragraph. A booking page that hides its cancellation terms makes the person paying nervous instead of confident, right when you need the opposite.
What do the best retreat websites have in common?
The best retreat websites share a few habits. They name who the trip is for in one sentence a reader could repeat back. They show the actual rooms and actual food instead of stock photos of a beach nobody's going to. And the price and dates sit near the top instead of buried after three screens of scrolling. You can tell within ten seconds what the retreat is, who it's for, and what it costs.
They also tend to say less than you'd expect. A site trying to be everything to everyone (every kind of guest, every kind of benefit) usually ends up persuading nobody, because a reader who isn't sure the trip is for them will assume it isn't. The sites that fill retreats pick one thing to say clearly, and let the booking page carry the close rather than a popup or a chat widget.
What do you need for people to find it?
People find a retreat website two ways: searching for it, or you pointing them at it. For search, the page needs to use the actual words a real person would type (the kind of retreat, who it's for, roughly where), in plain sentences, not just a mood and a photo. A gorgeous page that never uses the words someone would search for won't show up for them, no matter how good it looks once they land on it.
Search alone is rarely enough for a first retreat, though, especially with a new site that hasn't been around long enough to rank. Most of your early traffic will come from you sending people to the page directly: your own list, your own social accounts, your own DMs. That's its own piece of work, covered in Social media for retreat hosts. For the order that turns that traffic into bookings, see how to fill a retreat and what actually fills seats.
What should you track once it's live?
Track three numbers, not twenty: how many people land on the retreat page, how many of those click through to the booking page, and how many finish the booking. Those three tell you where people are dropping off. A lot of visitors and few clicks to book usually means the page isn't making its case. Plenty of clicks to the booking page and few completions usually means the booking flow itself is asking too much, or something on it (the price, the cancellation terms, the deposit amount) is giving someone a reason to close the tab.
Set those three up before launch, not after you're wondering why the numbers look thin.
If building the page, wiring up the booking flow and setting up that tracking isn't how you want to spend your week, that's Done For You: we build the retreat page, the booking flow and the tracking to this same standard, and a principal signs off before it reaches your readers. See what Done For You covers →
Questions hosts ask
Do I need a web designer to build my retreat website?
No, not for one good page. The page needs the right information in the right order more than it needs custom design work. You can build your first retreat page yourself on a simple page builder and bring in design help once you're running retreats often enough to justify it.
How much does a retreat website cost?
It depends on whether you're building one page yourself on a tool you already pay for, or hiring someone to build and host a full site. A single retreat page can cost close to nothing beyond your time. A built, designed site with ongoing hosting runs into real money, and it's worth that cost only once you're running retreats regularly enough to need it.
Can I sell retreat spots without a website at all?
You can start with a single page on a tool you already use, or even a well-built social post with a link to a booking form, and still take deposits. What you can't skip is the information itself: who it's for, what's included, the price, the dates and the cancellation terms, somewhere a person can read it before they pay. The website is the container. The information inside it is what sells the seat.