The conversation I have most often with hosts doesn't start with pricing or cleaners. It starts with "we were on page one for two years and then we weren't." Nothing had changed at the property. Same photos, same reviews. Something moved upstream, and a business that looked solid turned out to be one distribution channel in the costume of a company. What follows is the ninety-day plan I would hand that host to build a booking channel of their own, run on Lodgify.
Hating OTAs doesn't fix that, and nobody should bother. The answer is a second channel you own, and Lodgify is the tool this plan runs on because the site, the booking engine and the calendar sync that stops you double-booking arrive together instead of as three subscriptions. Airbnb, Vrbo and Booking.com remain the best demand engines a small operator has ever had. The problem was never using them, it's owning nothing else.
Why is leaning on one platform a fragile way to run a rental?
Because a single-channel rental carries three unrelated risks, none of them related to how good the property is. Your commission is set by someone else. Your visibility is set by an algorithm you can't audit. And the guest relationship belongs, practically and often contractually, to the platform.
Commission is the one hosts talk about and the least interesting, because it's knowable. Ranking shifts and new quality thresholds are not. One channel makes those a revenue event; three make them a mix shift.
The third compounds quietly. When every booking arrives through a platform, your repeat business is mediated by it too. The guest who loved the place opens the app a year later, sees eleven near-identical listings, books one. You never got to be the default, because you were never the thing she remembered.
So direct booking is mis-sold as a way to keep the commission. That's the smallest part of it. The real return is optionality: once a fifth of your nights come from a channel you own, an algorithm change is an annoyance, not a crisis. Our comparison of Airbnb versus direct booking works through where each wins. Ninety days builds the machine, not the mix.
What are you not allowed to do to win direct bookings?
Nothing that moves a guest off a platform before they book, and no payment outside it. All three agree there, then diverge sharply on what you may do afterwards, and the divergence is what hosts get wrong.
Airbnb is the strictest. Its Off-Platform and Fee Transparency Policy prohibits encouraging users to move current, future or repeat bookings off Airbnb, links off the platform in listings or messages, asking for contact details before booking, and soliciting an email after one. It also prohibits "selling, sharing, or using guest contact information for marketing communications or signing guests up for contact list", which rules out the tactic most direct-booking advice quietly assumes.
Vrbo bans the same pre-booking behavior, then says something Airbnb doesn't. Expedia Group's Off-Platform Booking Policy forbids communicating outside Vrbo's messaging until a booking is confirmed, plus any link, QR code, button or contact detail meant to redirect guests away. The same document permits "general marketing (for example, opt-in mailing list offers) that is not used to move an active reservation or payment off-platform and that travelers have expressly agreed to receive."
Booking.com keeps guest communication inside its own messaging and governs listing content through partner terms you can only read properly in the extranet, so check your own agreement rather than any blog's summary of it, including this one.
Either way, the list you build in week eight can't come out of platform inboxes. It comes from your own site, from guests who found you directly, and from consent given to you rather than a channel.
The ninety days, week by week
One operator, one to ten units, working evenings, no developer. The hours are what each task takes once you stop researching and start doing.
| Week | Focus | Done when | Time |
|---|---|---|---|
| 1 | Domain and skeleton | Live site, own domain, one property page, real photos | 3-4 h |
| 2 | Property content | A page per unit answering the five questions guests ask | 4-5 h |
| 3 | Rates and stay rules | Rates, fees, taxes, minimum stays mirrored from channels | 2-3 h |
| 4 | Payments and policies | Gateway live, terms published, one test booking refunded | 2-3 h |
| 5 | Calendar integrity | Sync on every unit, availability audited both ways | 2 h |
| 6 | Brand findability | One brand, site indexed, local-listing rule checked | 3 h |
| 7 | Metasearch | Google application in, or ruled out on eligibility | 1-2 h |
| 8 | Email capture | A signup form with a real incentive, a list you own | 2 h |
| 9 | On-property assets | Welcome book with your site address, post-stay email | 3 h |
| 10 | Returning-guest offer | A promo code with a value, expiry, trackable name | 1 h |
| 11 | Past-guest outreach | One email to every guest you may lawfully contact | 2 h |
| 12 | Measurement | Traffic, conversion, direct nights, cost per booking | 2 h |
Three checkpoints matter more than the weekly boxes, and each is a go or no-go. Day 30: can a stranger complete a paid booking on your site, on a phone, without emailing you? Day 60: are impressions for your own property name climbing in Search Console? Day 90: did one booking arrive that you can attribute to something you built?
The lag is what nobody warns you about. Search and metasearch sit early precisely because they pay out late, so week seven is least likely to show anything by week twelve. Email and past guests are the reverse: last to build, capable of a booking the same week.
Weeks 1 to 4: build something a stranger will trust with a deposit
Month one has one deliverable: a site where a guest who already wants your property can pay you without emailing first. Buy the domain first, since it's the decision that's annoying to reverse. Short, reads as a place rather than a company, no hyphens. Then stand the site up. Rental-specific software beats a general page builder here, because the calendar, stay rules, fee logic and tax handling already exist. One trap: on Lodgify the builder and booking engine start at the Starter tier, not the cheapest one. The free trial runs seven days with no card, enough to build the skeleton, and our setup walkthrough covers the screens.
Week two is content, and the failure mode is marketing copy. Write objection-handling copy. Per unit: where exactly is it, how do I get in, what's the parking and wifi situation, what does a typical stay cost in total, what happens if I cancel. A guest used to a platform where all that is standardized notices its absence, and absence reads as risk.
Rates come in week three, and this is where I see hosts lose the most. The instinct is to undercut your own OTA rate by five percent and buy the habit. What it usually buys is a handful of bookings and a set of guests trained to wait for a discount, and it tells the platform you would rather compete with yourself than be worth the money. Match the nightly rate and win on total cost: no service fee at checkout, the late checkout, the good parking space. If your property is in the EEA you do now have the legal room to go further, because Booking Holdings' own DMA compliance report records that it "removed all parity requirements throughout the EEA", effective for accommodation partners on 1 July 2024. Permitted and wise are still different questions.
Week four is payments, the week most hosts skip. Connect a gateway, publish a deposit structure you can administer, write the cancellation terms in your own words, then book your own property with your own card and refund it. Budget two fees, not one: your processor's percentage plus Lodgify's own 1 percent transaction fee on gateway payments. Test bookings catch the tax that appears only on the final screen.
Weeks 5 to 8: get found without breaking the rules
Calendar hygiene comes first, because one double booking in week five costs more than the quarter saves. Run every unit through a single system, then test it: block a date on your own site, confirm it vanishes everywhere, reverse the test. This is the unglamorous reason all-in-one platforms win for small portfolios, and our Lodgify review is the sober version of that case.
Brand findability is the highest-return work here, and it's defensive. Much of your direct volume comes from someone who found you on a platform, remembered a name, then typed it into Google. Be the first result for your own name: one brand everywhere, titles carrying brand and location, a site that's actually indexed. Do not create a Google Business Profile for the rental. Google's eligibility guidelines require in-person contact with customers during stated hours and list rental properties such as vacation homes as ineligible, though a staffed leasing office qualifies.
Week seven is metasearch, and settle eligibility before spending an hour on it. Google's vacation rental surfaces send travelers to your own booking page and take no commission on the referral, but Google's own documentation says individually owned rentals are not eligible: you need to be a registered property management business with a direct booking website, or be listed on an integrated booking site. The route for a small manager is an approved connectivity partner, and Lodgify is on Google's list, with the connection on its Professional and Ultimate tiers. Our guide to connecting the two covers the prerequisites. One owner with one flat should spend the hour on week eight.
Week eight builds the email list, the only asset here that appreciates. Put a form on the site with a reason to use it worth an email address; a short area guide with your actual restaurant opinions beats "subscribe for updates". One honest limitation: Lodgify has no native campaign sender, so the subscribe bar wires to Mailchimp and sending happens there. Collect consent properly and keep the list exportable.
Weeks 9 to 12: turn one stay into the next one
Retention is the cheapest revenue here, which is why it closes the quarter. Weeks nine and ten build the two assets that convert past guests. One is physical: a printed welcome book with your site address on it, fine because the guest has already booked and arrived. The other is a promo code with a defensible value, an expiry, and a name you'll recognize in a report later.
Week eleven is the outreach, and it needs care rather than volume. Email the guests you may lawfully email, meaning those who gave you details and consent away from platform messaging. One email: what's new, two reasons to come back, the code, stop. Then automate it after every checkout.
How do you know at day 90 whether it worked?
Measure six things, and measure the direct share as a percentage of nights rather than bookings, because direct guests book longer stays and counting reservations flatters you. The six: direct share of nights sold, sessions, booking conversion rate, all-in cost per direct booking, net revenue against a comparable channel booking, and brand search impressions.
That last one is the leading indicator almost nobody watches, and I think it's the most useful number here. It tells you whether people are leaving the platform to look for you specifically, and it moves before bookings do.
Now the arithmetic, with figures chosen only to show the shape of the sum. They are not survey data and not any platform's published rate, so substitute your own. Take four units doing 40 bookings a quarter at an average booking value of 1,100, and assume an all-in host-side channel cost of 15 percent, an assumption rather than a quoted rate. Six of the 40 come direct, so commission avoided is 6 x 1,100 x 0.15, or 990. Against that: a quarter of subscription, processing plus the 1 percent platform fee on 6,600 of direct revenue, a domain, thirty-odd hours.
The cash gain lands a few hundred above out-of-pocket costs and well below the value of thirty hours. Quarter one does not pay back. Setup is one-time and the direct share compounds, so the case is the year after. Anyone expecting the quarter to break even quits in week seven, exactly when the slow channels arrive.
What will this playbook not fix?
It won't create demand that isn't there. Direct booking captures demand more cheaply; it doesn't generate it. If a property struggles to fill across three platforms, the diagnosis is the photos, the price or the market.
Some guests will never convert, and refusing is rational of them. Platform payment protection and dispute resolution are real benefits you can't replicate alone. Expect a ceiling, and treat anyone promising a hundred percent direct as a salesman.
Taking payment yourself makes you the merchant, so chargebacks, refund disputes, fraud, guest screening and damage recovery all become your problem, and your insurance may not cover bookings taken outside a platform. Nor does any of this make you compliant with anything: registration numbers, tourist taxes and guest reporting can work differently once you're taking the money, and software that collects a tax is not compliance. Both are questions for a professional.
And you won't win generic search traffic. You are not going to outrank the OTAs for "apartments in Lisbon". Realistic wins are your brand name, your street or building name, long-tail local phrases, metasearch. Adding a channel adds work, permanently.
Which software should you run it on?
Four things have to live in one place: a bookable website, a payment flow, a channel manager keeping the calendars honest, and enough reporting to answer the day-90 questions. Split them across a page builder, a widget and a standalone sync tool and you get the double booking that ends the experiment. For one to four units that makes this the tidiest case for Lodgify, where the builder and booking engine are the product rather than an add-on. As of writing there are four tiers, none charging a booking commission, though a 1 percent transaction fee applies to gateway payments on all of them. The tier that matters is the first one including the website builder, and Google Vacation Rentals sits two tiers up. Confirm current numbers yourself and read our Lodgify pricing analysis.
For five to fifteen units it depends on what you already run. Hospitable is strong if your operation is built around automated messaging and cleaning workflows, and European hosts often land on Smoobu for its commission-free prepaid tier. Either will run most of this playbook, and if you already pay for one, start there rather than migrating in week one. What neither is built around is the direct booking website itself, which is the part this plan depends on, and that is the honest case for Lodgify here. We compare all three in our channel manager and PMS comparison. Above fifteen units it's a different conversation about teams and owner reporting.
Whichever you pick, pick in week one. The expensive mistake isn't the wrong platform, it's spending month one comparing them and month two rebuilding on a second.
So the next thing to do isn't a software decision. Open your last three months of payout statements, work out what a booking actually costs you on each channel, and write the number down. If it doesn't bother you, enjoy the free demand. If it does, week one starts with a domain.
Related Articles
- Airbnb vs direct booking, on where each channel earns its keep.
- Setting up a direct booking website with Lodgify, weeks one to four screen by screen.
- Our full Lodgify review, the unsponsored assessment.