Calendly offers three embed types: an inline embed that shows the full scheduling calendar directly in the page, a popup widget triggered by a button, and a popup text link. All three are pasted onto a site as a short snippet of HTML and JavaScript, and a dedicated WordPress plugin wraps the same thing into a block for sites built there. You can also generate a QR code pointing straight at a scheduling page, handy for print materials or signage where typing a URL isn't realistic.
Inline embed. The full calendar renders directly inside the page, best when scheduling is the main thing that page is for, like a dedicated booking page.
Popup widget. A floating button sits on the page, and clicking it opens the Calendly calendar in a popup overlay, a lighter touch for a page where booking is useful but not the primary action.
Popup text link. The lightest option: a plain text link opens the same popup overlay, useful inside body copy or an email where a full button would feel heavy.
QR code. Generated straight from an event type or scheduling link, this gets printed on a business card, a flyer, or in-person signage, so someone can scan straight to a booking page without typing anything.
The embed itself just displays the calendar. It doesn't decide which event type to show based on which page someone's on, and it doesn't do anything extra with campaign or source data beyond passing along whatever Calendly's own integrations already capture. A business running the same embed across dozens of location pages, or tracking which ad campaign actually drove a booking, needs that logic built around the embed, not inside it.
This gets harder, not easier, at scale. One embed code on one page is simple. Twenty location pages each needing their own calendar, correctly matched, maintained by hand, is where teams start missing updates or copying the wrong code onto the wrong page.
A multi-location or multi-service site gets each page pointed at its correct event type automatically, instead of someone manually tracking which embed code belongs on which of dozens of pages.
UTM or referral data captured at the moment someone lands on the embed gets attached to the resulting booking downstream, instead of getting lost the second the calendar widget takes over.
Tell us how many, and we'll figure out what keeping them all correct should actually look like.
An embed on one page is a five-minute job. The same embed correctly maintained across dozens of location or service pages is a different problem entirely, and it's one we solve constantly, not just for Calendly. Whatever widget or form your business copy-pastes across multiple pages by hand is worth the same question.
Let's talk →An inline embed shows the full calendar directly on the page. A popup widget is a button that opens the same calendar in an overlay instead, better suited to a page where booking is secondary to something else.
Yes, either through the official Calendly plugin, which wraps the embed into a block, or by pasting the raw embed code into a custom HTML block, the same way you would on any other site.
Yes, directly from an event type or scheduling link in your Calendly account, which is a quick way to put a booking page on something printed, like a business card or a flyer.
Generally yes. Since the embed is a standard HTML and JavaScript snippet, it works on any site builder that accepts custom code, Squarespace, Wix, and most others included, not just WordPress.