Very few hotels have sat down and made a call on AI. The decision got made somewhere else: a security plugin, a hosting firewall, a bot setting on the CDN. Those tools were set up to stop scrapers copying your rates. They don’t know the difference between a scraper and an assistant answering a guest who asked for a pet-friendly place near the beach with parking.
Even the big players are still working it out. Skift found Airbnb allowed OpenAI’s and Anthropic’s crawlers in August and blocked both by October. If companies with whole legal teams are changing their minds month to month, a 40-room hotel shouldn’t be deciding this by accident.
This is the part most of the conversation misses. The AI companies run different bots for different jobs:
You can reasonably say no to training and yes to the other two. Some chains go further: Skift found Best Western and ITC Hotels explicitly welcome OpenAI’s training crawler. Either way, it should be a choice. Blocking the search and live bots means the guest’s assistant can talk about you, but can’t send them to you.
Adobe’s Vivek Pandya put it plainly: when AI can’t read a site, “potential revenue is being left on the table.” The fix is rarely a big project. It’s a decision, a short edit to one file and a conversation with whoever runs your firewall.
The OTAs have already made their call. A direct booking only happens if the guest, or the assistant working for them, can actually get to you. Make sure yours can.
Source: Skift, “Dear Robot: How Travel Is (and Isn’t) Talking to AI”, 9 November 2026, including Adobe and Cloudflare data cited there.