If you have a website, three patterns work for adding online booking. Pick whichever matches your control and effort budget.
Pattern 1: Link out to a hosted booking page
The booking happens on the booking platform’s domain
(book.zedule.app/your-slug). You add a “Book now” button on your
website that links to that URL.
Effort: 30 seconds — paste a URL into a button.
Trade-off: customers leave your domain during booking. They
return automatically after confirmation, but the URL bar shows
book.zedule.app for the booking flow.
Who this fits: new businesses without yet-strong brand presence; businesses where the booking flow speed matters more than domain consistency; businesses on platforms that don’t allow embed (some lower-tier vendor plans).
Pattern 2: Embed via iframe
The booking page renders inside an iframe on your website. URL bar shows your domain throughout. The booking flow feels native to your site.
Effort: 5 minutes — paste an iframe snippet on your site.
<iframe
src="https://book.zedule.app/your-slug?embed=1"
width="100%" height="820"
style="border:none;border-radius:12px;max-width:720px;"
loading="lazy"
title="Book an appointment"
></iframe>
The ?embed=1 query param strips the platform’s chrome (header,
footer) so the booking widget feels native.
Trade-off: iframes don’t allow full customisation; you can’t modify the booking flow, only the surrounding container.
Who this fits: most businesses with an existing website. Best balance of control and effort.
Pattern 3: Custom API integration
The booking platform exposes an API; you build a fully custom booking flow on your own site that talks to the platform via backend calls.
Effort: weeks of development work.
Trade-off: total control; total cost; ongoing maintenance.
Who this fits: large businesses with development teams and specific UX requirements; almost no small businesses.
Which to pick
For 90% of businesses, Pattern 2 (iframe embed) is correct. It keeps customers on your domain while requiring zero development work.
Pattern 1 is fine for businesses without their own website, or where the booking platform’s hosted page is the website (which is how many solo operators run).
Pattern 3 is for enterprise; ignore unless you specifically need the customisation.
Embedding on common website builders
- Squarespace: add a Code Block, paste the iframe.
- Wix: Embed → HTML Embed → paste the iframe.
- WordPress: Custom HTML block, paste the iframe.
- Webflow: Embed element, paste the iframe.
- Custom HTML site: paste the iframe wherever you want it.
All accept standard iframe tags. The 720px max-width on the container works well for most layouts; scale it to your design.
Where to embed
Don’t bury the booking flow on a contact page that no one reads. Pattern that converts:
- Sticky bottom CTA on the homepage — “Book an appointment” button visible on every scroll.
- Top of every service page — when a customer reads about a service, the booking option should be one click away.
- End of every blog post — content brings them in; booking flow converts them.
- About page — customers reading about your team often want to book; embed there too.