What a direct booking website actually needs

A direct booking website is the site that can take the stay: live availability, a real total, a payment, and a confirmation — without an email thread and without sending the guest back to Airbnb to finish. If someone still has to write to you for a price, you haven’t got one yet.

I rebuilt Penmaenucha Farm around that. Guests used to wait on a quote. In one eight-week window more than a third of those submissions were spam, and dates people were waiting on often reappeared as Airbnb. After live pricing and a booking path wired into the PMS, more of those weeks stayed on the farm’s own site. Organic traffic was up 20%. OTA fees were down 15%.

Direct booking engine: calendar, payments, rules

The engine is the software that holds the diary — calendars, rates, minimum stays, closed-to-arrival, deposits, extras, cancellation rules. Lodgify, SuperControl, Bookalet, or a custom integration: the brand matters less than this. The website and Airbnb must not be two diaries. One source of truth. A booking on the site blocks the OTA. A booking on the OTA blocks the site. Same hour, not “we update iCal overnight”.

Payments belong in that engine. A deposit the guest can pay on a phone. A balance reminder that doesn’t depend on someone remembering. Stripe’s UK domestic headline is 1.5% + 20p; on Lodgify, add Lodgify’s 1% application/transaction fee on connected gateways. That is not Airbnb’s most-hosts 15.5% cut. If you only take bank transfers, you’ll still lose people at 10pm on a Thursday who would have booked if checkout existed.

Rules need to sit in the flow, not in a PDF nobody opens. Changeover day, maximum occupancy, pets, a damage deposit if you use one. Surprise terms at the door create refunds and reviews. If the engine can’t express how your cottage actually lets, you’ll override it in email — and you’re back at the old process.

The pages around the engine matter as much as the engine. Homepage: which cottages, where, from what weekly price, one obvious next step. Property page: the unit they will sleep in, not a collage of all three. Availability: dates and a total, on the same screen as the photos. Checkout: guest details, deposit, what happens next. Mobile: the same path with a thumb. If any of those steps dump into a form, you still have an enquiry site, not a booking site.

I often keep Lodgify as the engine because it already talks to Airbnb and Booking.com, and it has an API for a custom front. SuperControl is the usual pick when a Sykes date-block or cottages.com (three-property minimum on SuperControl’s API) is why you are there. Bookalet is fine as a cheap UK diary — £139 / £189 / £239 a year, Airbnb/Booking.com iCal on Pro+. If the engine is already doing that job and the site is the problem, don’t rip the diary out — put a better site in front of it. That’s the custom Lodgify website and API path when you’re on Lodgify’s builder and checkout is the bounce. Lodgify website builder vs custom is that split, and a channel manager for Airbnb is how the three calendars stay in sync.

Airbnb vs direct booking (same property, different margin)

Airbnb vs direct booking is two invoices for the same week. Airbnb’s single host-only service fee is 15.5% for most hosts, based on Airbnb’s global average, not a UK tariff — including cleaning, excluding taxes. Check your payout. Direct, you pay card processing and whatever your engine subscription costs. I walked through a £1,000 week in how much Airbnb takes from hosts. The short version: the most-hosts rate on that week is about £155 before any VAT line on the fee; Stripe plus a 1% PMS application fee is a much smaller number.

Discovery is the other half. Airbnb still sends people who have never typed your farm’s name. Booking.com still matters in Europe. Direct isn’t “delete the OTAs”. Direct is stop paying them on the guests who would have booked with you anyway — name-search, word of mouth, the driver who already knows the lane. If your site can’t complete those stays, every channel dumps into the same inbox.

Run the OTA commission calculator with last year’s book. Then ask whether a stranger can finish a booking tonight without you. If the answer is no, you don’t have an Airbnb vs direct strategy. You have an inbox.

How to get more direct bookings from people who found you on an OTA

First-time guests who found you on Airbnb should book on Airbnb. Don’t play games in the messenger. Airbnb’s off-platform policy covers current, future and repeat bookings, and using guest contact details for marketing. Do not invite Airbnb guests — including after checkout — to book the next stay on your site. Do not use Airbnb-sourced contacts as a mailing list. The legal path is a website people can find on Google, with an engine that can take the week.

The website should already exist before anyone searches your name. The property page they land on must show the cottage they will sleep in, not a homepage carousel of all units and a contact form. Returning guests who can’t find “their” cottage in two taps will open the app they already have.

Email is still useful for guests who booked with you direct and opted in. A confirmation that includes the site URL, and a week-before note with parking and Wi-Fi, belongs on stays you already own. None of that works if the link goes to a form. The engine has to accept the dates they already know they want.

Don’t spend the first year of a new site on blog posts about local walks while checkout is broken. Content helps Google. Checkout keeps the money. I’d rather ship a fast property page with a working calendar than a magazine with an enquiry form. Walks can wait until someone can book the sofa they just looked at.

Price discipline helps. If the site is always £200 more than Airbnb because you never updated rates, you’re training people to stay on the OTA. Match or beat the guest’s all-in OTA total on the weeks you want to win. You don’t need a public “we’ll undercut Airbnb” banner. You need a calendar that isn’t stale.

How to get guests to book direct (trust, photos, price match policy)

Getting guests to book direct is mostly trust on an unknown domain. Airbnb has reviews, payments, and a refund path they already understand. Your site needs enough of that gravity: recent guest quotes you actually have, photos that match arrival (not six-year-old sunsets), a map, a person or farm name, HTTPS, and a payment page that doesn’t look like 2011. Speed is trust. A three-second cottage gallery on mobile is a bounce to the app.

Photos should answer the booking questions: where you sleep, where you cook, what the weather does to the view, where the car goes. House rules belong near the calendar, not only in a footer. People book weeks, not nights, on UK cottages — show weekly totals, changeover days, and winter short-break rules without making them decode a colour key.

A quiet price-match policy is useful: if they have a comparable OTA quote for the same dates and terms, you’ll match it on the site. You won’t always win the first stay. You will win the ones where the only reason they used Airbnb was fear. Put the policy in plain English. Don’t hide the total behind “enquire for price”. That’s still the default on too many UK cottage sites, and it’s why people never leave the app.

Reviews on your own site will never match Airbnb’s pile on day one. Use what you have: named guests, dates of stay, a line about the actual house, not “lovely stay, 10/10”. Hide nothing important — a steep track, a low door, no dishwasher — because surprise is how you earn the review that keeps the next guest on the OTA.

Google is the channel you own more than Airbnb’s search box. A direct booking website that can’t be found for the cottage name and the area is a secret shop. Technical SEO and proper property pages are part of the site, not a later campaign. A Google Business Profile is a separate local-presence product — vacation homes are ineligible as GBP rental locations — so do not treat it as a listing switch for stays. I build the findable, bookable site into website design for holiday cottages.

Speed isn’t a vanity metric. If the property page is heavy with uncompressed galleries, the booking widget never gets a chance. Core Web Vitals are how Google and guests both vote. I treat them as part of the booking path: a slow calendar is a closed calendar. Rural broadband on the owner’s laptop isn’t the test. A phone on 4G in a supermarket car park is.

The Direct Booking Audit is that list in order. Can Google find the cottage by name? Does a property page exist? Is there a price without emailing? Does checkout work on a phone? Is the calendar the same as Airbnb? Those aren’t branding questions. They’re why a “new website” can still convert like the old one. I record a short video so you can see the clicks.

If you already have Lodgify, SuperControl or Bookalet and the engine works, don’t rip it out to “get a website”. Put a site in front that can sell the week. If you have neither, pick an engine that can sync Airbnb and Booking.com, then build the path. I’ll tell you which side is broken in the audit — Google, trust, speed, or checkout — instead of selling you a redesign of the wrong layer.