Direct booking has become one of the clearer signs that a host is treating the property as a business rather than a side activity. You keep more of the revenue, you build a guest relationship that doesn't reset every stay, and you stop being fully dependent on a platform's pricing and policy changes. For a serious operator, moving some share of bookings off Airbnb or Vrbo is usually a sound decision.
It also changes something underneath the operation that most hosts never revisit: the protection that was quietly attached to every platform booking is no longer there, and whether your own policy fills that space depends entirely on how it was written.
This is one of the more common gaps we see in audits, and it tends to appear precisely in the operations that are doing well enough to start going direct. It doesn't show up in the numbers. It shows up at the worst possible moment, when a claim arrives.
What a Platform Booking Quietly Bundles
When a guest books through Airbnb or Vrbo, you receive two things at once. The first is obvious: a reservation, with payment processing and a guest of record. The second is easy to forget, because it requires no action on your part. Riding along with that reservation is a layer of platform protection, branded as AirCover or a host guarantee, that sits behind the stay.
There is a legitimate debate about how strong that protection actually is. We've written before about why it is thinner than the marketing suggests, particularly around ordinary negligence and the claims process itself. But thin is not the same as absent. For platform bookings, something is there. Many hosts have been quietly relying on it without ever naming it as part of their coverage.
What Disappears the Moment a Booking Goes Direct
A direct booking is a transaction the platform was never part of. That single fact removes the entire platform layer from the stay. Not a reduced version of it. The whole thing.
The damage protection does not apply. The liability backstop does not apply. The identity verification, the payment dispute mechanism, the after-the-fact support structure, none of it attaches to a booking the platform never processed. The guest who books directly from your site or by referral is, from a coverage standpoint, in a different category than the guest who books the same property through an app.
Most experienced hosts understand this at a surface level. The exposure comes from the assumption that follows it: that their own insurance policy quietly steps into the space the platform used to occupy. Sometimes it does. Sometimes it does not. And the difference is rarely visible until it is tested.
The Deeper Issue: Your Policy May Have Been Built Around the Platform
Here is the part that surprises people, because it has nothing to do with the booking channel itself and everything to do with how the policy was underwritten.
Many STR policies were quoted with platform activity as the assumed model. The agent asked how the property is rented. The host said Airbnb. The policy was built around that description, sometimes with assumptions baked into the underwriting that were never explained in plain language. The operation was understood as platform-based, and the platform's own protections were silently doing part of the work.
Then the operation changed. The host added direct bookings, or shifted a meaningful share off-platform, and the policy stayed exactly as it was. The underwriting picture and the actual operation drifted apart, which is one of the most common ways coverage gaps form. They rarely come from a single bad decision. They come from an operation that evolved while the policy underneath it stood still.
To be clear, this is not an argument that every STR policy mishandles direct bookings. A properly written commercial STR liability policy generally does not care how the guest found you. It covers the business activity of renting the property to paying guests, regardless of channel. That is exactly the policy you want. The problem is that a large share of hosts are not on that kind of policy. They are operating on a homeowner's policy with a short-term rental endorsement, a landlord policy they were told would handle the rental, or a personal policy that was never designed for paying guests at all. Those policies often carry exclusions that have nothing to do with the booking channel and everything to do with running a business out of the property. The platform protection had been masking that exclusion. Direct booking removes the mask.
A Representative Claim
Consider a host in a four-season mountain market with a strong direct-booking operation: a clean website, repeat guests, a property that performs across seasons. The kind of operation other hosts study.
One direct booking is a family with two children. During the stay, a child falls on an exterior staircase with a loose railing. It begins as a minor injury, then becomes a series of medical visits and a specialist referral. Several weeks later, a demand letter arrives. The family alleges the railing was a known maintenance issue and seeks damages for the injury and ongoing treatment. The demand is roughly $185,000.
The host's first instinct is the common one: there is insurance, and in the back of his mind the platform's liability coverage had always felt like the real safety net. But this stay never touched the platform. There is no platform liability to call on. The figure available from that source is zero.
That leaves the host's own policy, which is a landlord policy that excludes the commercial guest operation actually taking place at the property. The carrier does not deny the claim out of bad faith. It denies because the activity that produced the loss falls outside what the policy was built to cover. The deductible is irrelevant. The policy limit is irrelevant. The coverage for that specific loss simply is not present.
The matter settles for well below the original demand, but the host pays for his own defense and a meaningful share of the settlement directly. The out-of-pocket figure lands in the mid five figures, plus a year of stress and distraction. The hardest part to absorb is not the money. It is that the host was one direct conversation away from knowing this in advance, and nothing in the normal course of business had ever forced that conversation. The booking channel is what finally forced it.
Channel and Coverage Are Two Different Decisions
It helps to separate two things that hosts tend to blur together.
The first is your booking channel. That is a business decision about fees, control, and guest relationships. Going direct is frequently the right call, and nothing here argues against it.
The second is your liability and property coverage. That should respond to a loss based on what happened at the property, not on which website sent the guest. If your coverage only holds when the platform is involved, you do not really have coverage. You have an arrangement that has been working out so far because the platform layer kept absorbing what your policy would not.
When those two decisions are aligned, direct booking is exactly the upgrade its advocates describe: better margins, better guest relationships, and a real policy underneath that responds regardless of channel. When they are not aligned, going direct leaves you running a more exposed operation than you had before you started keeping the platform's share of the revenue.
What to Verify Before the Next Direct Guest
None of this calls for alarm. It calls for one conversation and a few minutes with your own paperwork.
Ask your agent a precise question. Not "am I covered," but "does my policy respond to a guest injury or property loss the same way whether the booking came through a platform or directly from me?" Ask them to point to the language that supports the answer. If they cannot, treat that as the answer.
Identify what policy you are actually on. Pull your declarations page and confirm the category: homeowner's with an endorsement, landlord, or a true commercial STR policy. If you are running direct bookings on anything other than a purpose-built STR policy, treat that as a flag to resolve rather than a maybe to revisit later.
Stop counting platform protection as part of your coverage stack. Look only at what your own policy would pay if a guest were injured tomorrow on a stay the platform never saw. If that number is uncomfortable, you have found the specific thing to fix before the next direct guest checks in.
A Measured Way to Frame It
Direct booking is not the risk. The risk is changing how you operate while leaving the coverage underneath it untouched. The hosts who get caught are not the ones running direct bookings. They are the ones who evolved the business and never updated the policy to match it.
The shift to direct booking is a good moment to confirm which category you are in, the same way the start of any season is a reasonable moment to review coverage. Not alarmist. Just operational. The protection you have should depend on what happens at your property, not on where the guest happened to click.
If you take direct bookings, it is worth confirming your own policy responds no matter how a guest arrives. Take five minutes to get your free risk score and see where you stand.
Threshold STR helps hosts confirm that their coverage responds regardless of how a booking originates, including the channel gaps that open up when an operation moves off-platform. A free risk score takes five minutes. A professional audit reviews your full policy against how you actually operate.