Lodgify WordPress plugin vs a custom booking site

You’ve already got a cottage site on WordPress, and someone has told you the Lodgify WordPress plugin will add bookings without a rebuild. Sometimes that’s true. The plugin embeds a booking engine — a calendar and checkout dropped into a page. It does not turn a slow marketing site into a conversion machine. Used as a rescue for a theme that’s already fighting you, it still loses the guest to Airbnb.

I’ve migrated a live holiday cottage off a WordPress diary into a PMS with no dark week. The lesson wasn’t “WordPress is bad”. It was that a form plus a calendar plugin is not a booking path. If you’re shopping the plugin, decide whether you need an embed this month, or a site that can still sell a week in five years.

What the Lodgify WordPress plugin actually embeds

The official plugin is Booking Engine by Lodgify on WordPress.org. You need a Lodgify account with at least one rental. The plugin adds blocks: a search bar and a search widget. Those are Lodgify’s embed, not a native WordPress booking system. Guests click through Lodgify’s rental and checkout flow. You can tint colours in Lodgify. You cannot restyle checkout to match your theme the way a custom front can.

You can skip the plugin and paste Lodgify’s widget code into a Custom HTML block. Same engine, fewer plugin updates. Same iframe-shaped problems. Either way, Airbnb, Booking.com and Vrbo still sync through Lodgify, not through WordPress. That’s the point of using a PMS at all.

Get one property bookable in Lodgify’s booking engine first, then embed. Don’t install the plugin on an empty account and wonder why the block is blank.

Speed, SEO, and theme conflicts

WordPress cottage sites are usually a page builder, a gallery plugin, a cookie banner, and then “we’ll add bookings”. The Lodgify WordPress plugin is another JavaScript payload. On a phone in a supermarket car park the calendar often arrives after the bounce. Core Web Vitals aren’t a vanity score when the widget is the product.

Theme conflicts are mundane and expensive: the widget sits under a sticky header, the date picker clips, the mobile menu covers checkout, Elementor and the embed disagree about width. CSS hacks last until the next theme update. SEO takes a hit when the bookable bit is a black box Google cannot read as well as a native price on the property page.

If the rest of the site is already slow, the plugin will not save it. Fix images and plugins first, or accept guests will finish the stay on Airbnb because the page never finished loading. I wrote the conversion spec in what a direct booking website actually needs.

SuperControl WordPress and Bookalet widgets compared

SuperControl WordPress setups are common in UK self-catering: an older theme, a SuperControl engine or iCal-ish diary, agency channels in the background. The widget is the engine; the theme is whatever a designer left in 2017. If Sykes still matters, SuperControl’s date-blocking connection can be the right OS with a bad website. SuperControl’s Owner prices are published. Cottages.com and Hoseasons APIs currently need three properties. Swapping to the Lodgify WordPress plugin does not connect Sykes, cottages.com or Hoseasons. I covered that split in Lodgify vs SuperControl.

Bookalet is a cheap UK diary: a widget on a site you already have. Airbnb and Booking.com sync is two-way iCal on Pro+ (Lite has no channel management). Not a Lodgify-style API. Don’t install Bookalet’s old WordPress.org plugin — it closed 18 December 2024 for security; the official path is an HTML embed.

All three are embeds. SuperControl: UK operations. Lodgify: Airbnb, Booking.com and Vrbo plus a website product. Bookalet: low cost, iCal distribution. The WordPress bit is the same job: show availability from the PMS, not from a separate calendar plugin.

When to leave WordPress and build custom

Stay on WordPress if the theme is fast, the price is on the property page, the widget completes on mobile, and you aren’t fighting updates every month. Plenty of cottages can live there for a season, especially if content and Google already work. A holiday let website that already ranks doesn’t need a CMS swap for sport — see holiday let website for that fork.

Leave when the stack is the problem: page builders, gallery plugins, a booking iframe, and a property page with no live price. Leave when you need cottage-by-cottage pages that rank in a place, not a generic “rentals” template. Leave when you want the Lodgify website builder out of the way and the Lodgify API on a site you own — that’s website work with a PMS behind it, not another plugin.

You don’t have to migrate the CMS and the calendar on the same weekend. Get Lodgify syncing Airbnb first. Embed. Measure. If guests still cannot book, the front-end is the project. I’ll tell you which side is broken in the audit instead of selling a rebuild you don’t need.