Smoobu guide
Embedding the Smoobu booking engine
How the embed works, how far it styles, and where the seams are. Smoobu makes this unusually painless.
Link or HTML, and that is genuinely it
Smoobu's booking system can be added to an existing website by a link or embedded HTML9. There is no plugin dependency, no proprietary hosting requirement and no negotiation about whether custom sites are supported.
That simplicity is why Smoobu is one of the most comfortable platforms to design around. The engine handles dates, guests, rules and payment; everything before and after it is ours to build properly.
Where the seams are, and how we hide them
The embed is a component, and components have edges. Typography, spacing and colour can be brought close to your brand but not identically, and the payment step behaves as Smoobu designed it.
The trick is designing the surrounding page so the transition reads as intentional. Guests forgive a component that looks slightly different if it arrives in a sensible place at a sensible moment. What they do not forgive is a jarring domain change or a page that suddenly looks like a different company.
- Match type scale and spacing rhythm to the embed rather than fighting it
- Place the engine where the decision is being made, not below three sections of copy
- Keep total pricing visible before the guest reaches the engine
- Never let the visual language change mid-journey
When to go further
Above roughly ten properties, or where multilingual pages and portfolio search matter, the Smoobu API becomes the better route. You get full control of search, filtering and rendering, with the same underlying calendar.
Below that, the embed is the right answer nine times out of ten. It is faster to build, cheaper to maintain and difficult to break.
Questions people actually ask
Straight answers.
Can Smoobu's booking engine go on any website?
Effectively yes — it is added by link or embedded HTML9, which works on almost any platform including a fully custom build.
On a site we build we control the markup, so it behaves exactly as documented with no builder quirks.
How far can the Smoobu embed be styled?
Close to your brand, not identical to it. We design the surrounding page to absorb the difference rather than pretending it is not there.
Where pixel-perfect control of the transactional steps is essential, the API is the honest answer.
Does the guest leave my site to book?
With the embed the booking happens in place within your pages. The payment step is Smoobu's component.
That is a much smaller disruption than a full domain redirect, and it is the reason we prefer embedded engines to hosted booking pages.
Back to the main page
Smoobu website design
The full picture on building a direct booking website around Smoobu — integration routes, what changes, and what it costs you not to.
