In this guide (10)
- 1Who this guide is useful for (and who it isn't)
- 2Website, OTA and PMS: three pieces, three jobs
- 3What a hotel website needs to have
- 4The room page: a mini-landing page, not a gallery
- 5Direct booking: when the website is enough, when it isn't
- 6How to get a hotel found in its own area
- 7Five mistakes that block bookings
- 8OTA, website, PMS: who does what
- 9How we approach this problem at KeideaCMS
- 10Checklist before you sign
A hotel website does not replace Booking.com and it is not a property management system. It's the channel you control: who you are, where you are, the rooms, why a guest should book with you. OTAs remain useful. A PMS and a channel manager keep availability and rates aligned. This guide is here to help you avoid buying the wrong product: a website instead of a PMS, or a PMS instead of a website.
The website does the rest: trust, searches on the name and area, and direct booking only if it's connected to the system that actually manages the rooms.
This guide is for owners and managers of hotels, B&Bs and small properties who are redoing their website or choosing a provider. The general framework of a website project, costs and phases, is covered in the guide to creating professional websites for businesses.
Who this guide is useful for (and who it isn't)
It's useful if you're the owner or manager of a hotel, a B&B or a small accommodation facility, you have a physical location and you want a website that works alongside OTAs, not instead of them. The typical reader is considering a redesign, a first proper website, or a change of provider, and has to decide what to buy: a showcase, a booking engine, or a property management system.
This isn't the right guide if you're looking for a PMS for check-in, housekeeping and billing, or a channel manager to align Booking.com, Expedia and the website. That's a different product, sold by industry-specific software. It's not the right guide either if all you need is a landing page for a paid campaign: in that case a single page is enough, not a full property website.
Website, OTA and PMS: three pieces, three jobs
Someone looking for a room starts with a search. Often from their phone, often comparing three listings on an OTA. In the first few seconds they decide whether to trust that property or go back to the list. A slow website, with photos from five years ago or no clear way to ask about availability, doesn't "inform" — it hands the booking over to whoever has a ready form.
Booking.com, as it presents itself to partners, is a listing channel: listing, availability, rates, reviews, payments according to their rules. Industry booking engines and channel managers, like those described by Vertical Booking and Simple Booking, exist precisely to keep inventory and prices aligned between OTAs and the website. The property's own website doesn't compete with Booking.com on the volume of "hotel + city" searches. It competes on the property's name, on local queries, and on the trust of people who have already seen the listing and want to understand where they're going.
A property management system, in the sense used in hospitality, covers property operations: guest bookings, details, billing, sometimes POS, housekeeping, interfacing with channel managers and booking engines. It is not a CMS. Buying a website expecting a PMS, or vice versa, is the most costly mistake in this choice.
What a hotel website needs to have
Six pieces. If even one is missing, the website "exists" but doesn't work.
Property pages, not just rooms. Someone booking wants to understand where you are, how to get there, what's nearby, who runs the place. Without these pages the website is a poor clone of the OTA.
Complete room pages. Real photos, room type, what's included, a call to action. Details in the next section.
A single inventory. The availability shown on the website must be the real one. If rooms live in a PMS, the website reads from it. If you manage them manually, the website collects requests and you confirm them. Two calendars means overbooking waiting to happen.
Contacts and request visible from mobile. Number, address, form or booking, without scrolling through three screens. A request should carry with it at least the room type and dates, if you've asked for them.
Aligned Google Business Profile. Name, address and phone number matching on the website and on the profile. A hotel has a location people can visit: that's exactly the use case for Google Business Profile, not a marketing extra.
Speed on the room pages, not just the homepage. Heavy photos slow down exactly the pages that should convert. Speed is measured, not claimed: the reference is Core Web Vitals, explained in the guide to Core Web Vitals.
The room page: a mini-landing page, not a gallery
Each room page has one job: get that room requested, or booked. Quality photos help, but aren't enough. You need the room type (double, superior, family), what's included in the rate, what's paid separately, square footage or at least an honest description, and a button visible without scrolling through the whole page on mobile.
If the page sends people to a generic "contact us", you lose context: at the front desk you won't know which room the person saw. The form must carry with it at least the room and the dates. Booking a stay isn't the same as booking an appointment at a practice: if the property works on service slots (tours, restaurant, treatments) rather than room inventory, the reasoning in the guide on online bookings without duplicates applies. For rooms, the right calendar is the one in the PMS or channel manager, not a second calendar on the CMS.
Direct booking: when the website is enough, when it isn't
Direct booking pays off when the guest already arrives convinced (property name, word of mouth, returning guest) and you want to avoid the OTA commission on that booking. It doesn't pay off if the website shows different availability than Booking.com: the guest notices, and the front desk spends the morning explaining why a room shown as "available" on the website had already been sold.
Three scenarios, explicitly illustrative, not market averages:
B&B or holiday home with few rooms, managed by hand. A clear website plus a "check availability" form may be enough. You confirm yourself, by phone or email. The overbooking risk is low if you're the one keeping the notebook.
Small hotel already on OTAs, without a PMS. The website must sell trust and collect inquiries. A booking engine on the site, not connected to the OTAs, is the piece that creates duplicates. Better to use a form, or an industry booking engine connected to a channel manager.
Property with a PMS or channel manager already in use. The website is the showcase; direct booking is a channel of that software. The CMS shouldn't reinvent the inventory.
Industry booking engine providers promise, reasonably enough for their product, to "win back direct sales". This is a different job from building a website. It should be bought as such, with a declared integration, not as a widget stuck in the footer.
How to get a hotel found in its own area
Hotel searches are local and often captured by OTAs. "Hotel" + city is a crowded field. The website can work on the property's name, on "hotel" + the hamlet or area where you actually are, and on the Google Business Profile (Maps, local listing, reviews).
Three concrete conditions, consistent with Google's guidelines on business profiles: consistent NAP (name, address, phone the same on the website and on the profile), a single profile for that location, accurate category and hours. You don't need dozens of ghost pages with the name of every village thirty kilometres away. You need a few honest pages about where you are and what you offer. The method, valid for any local business, is in the guide to local SEO for SMEs.
Guests' and inquiries' personal data (name, contact details, dates, any requirements) fall under GDPR: the privacy notice and data retention are obligations of the property, not an option offered by the website provider. We cover this in the guide on GDPR and websites.
Five mistakes that block bookings
Two calendars. Availability on the website different from that on the OTA or at the front desk. This is the mistake that causes overbooking and negative reviews.
Website reduced to "book on Booking.com". No room page on the domain, no visible contact details. You paid for a brochure that sends traffic elsewhere.
Photos and rates not matching reality. A renovated room still shown with old photos, or a price on the website you don't recognise at the front desk.
Pages with no action from mobile. Nice galleries, a form in the footer, phone number shown only as an image.
Website left to the developer. Every change of season becomes a ticket. After three months no one opens it anymore and the pages go stale.
None of these mistakes is solved with a new design. They are solved by deciding who holds the inventory, with which tool, and what the website should do relative to the OTAs.
OTA, website, PMS: who does what
Confusing the three pieces is why wrong products get bought. The table is not a ranking: it's a boundary.
| Piece | What it's for | What it doesn't do | When it's essential |
| OTA | Visibility on high-volume searches, reviews, listing | Doesn't tell the property's story under your brand and works on commission | Almost always, at least on one main channel |
| Your own website | Brand, pages, trust, searches on your name and area | It's not a PMS and doesn't align OTAs by itself | Always, if you want a channel you control |
| PMS / channel manager | Room inventory, stays, rate and availability alignment | Doesn't replace a clear website or the Google Business Profile | When you have multiple channels or a volume of rooms that won't fit in a notebook |
How we approach this problem at KeideaCMS
For a property that wants its own website, not a PMS, the work is that of a properly built business website: property pages, pages that can be updated by front-desk staff, contact forms, on-page SEO, hosting and maintenance on us. KeideaCMS is a proprietary subscription platform, on our servers. The domain, content and data remain yours, exportable if you ever decide to switch. We don't hand over the software's code: the subscription pays for continuity, updates and a point of contact, not ownership of the files.
The booking module, where included in the plan, manages slots and services (appointments, treatments, guided tours), not a hotel's room inventory. We don't promise Google rankings and we don't replace OTAs. We connect the website to what you already use, within the limits documented in the plan. What's included and what remains optional can be found in our plans; the comparison with other options is on the comparison page. The project journey, from brief to launch, is described on the building a business website page.
KeideaCMS
Want to understand whether you need a property website or an industry-specific management system?
Request a free analysis → How we build websites
Checklist before you sign
To put in writing in the quote, not to take for granted.
Who updates the room pages, and with what tool, without having to file a ticket to the developer.
There's only one inventory: website, OTAs and front desk all show the same availability.
Every room page carries the room and dates through to the inquiry, and works on mobile.
The domain is registered to the property; content and data are exportable.
It's clear what stays on the OTAs and what lives on the website: no disconnected "book now".
Consistent NAP and a single Google Business Profile for that location.
Privacy notice on the forms; no "compliance" claimed without a defined scope.
Who handles backups, updates and security after launch, and with what response times.
The provider has explicitly stated whether or not they handle PMS, channel manager, OTA sync.
You've compared the cost over three years, not just the starting figure.
A hotel website is worth it if you want a channel of your own alongside the OTAs: room pages, trust, visibility on your name and area, inquiries that stay yours. It's not meant to replace Booking.com and it doesn't replace a PMS. If your daily work is allotments and check-in, start from that software. If your work is getting found and explaining who you are, start from the website, with someone keeping it up to date. The next step, if you want a review of your current website or the quote you have in hand, is an analysis: no commitment, a clear scope.
