Barq Meet
Create your free link

How to embed a booking calendar on your website

On this page

What do I need before embedding a booking calendar?

You need a working event link and permission to add custom code to the website. Test the hosted event first so an availability problem doesn't get confused with an embed problem. Keep that link as a fallback.

Prepare a working Google Calendar booking link, then open its Embed & share panel. The builder offers HTML, WordPress, Webflow, Wix and React formats; its output includes the event URL and your chosen presentation options.

We load the widget through a browser script and initialise its booking frame from the public event address. No developer secret belongs in the snippet. If your site editor strips scripts or disallows custom code, use a normal link to the hosted page instead so visitors still have a working way to book.

Which booking-calendar embed mode should I choose?

Choose inline when booking is the page's main task, a pop-up when a button or text link should open the calendar, and a floating badge for a persistent booking entry point. Give each one room. The guest still completes the same booking flow.

ModePlacementGood starting use
InlineCalendar inside the pageA dedicated consultation page
Pop-up buttonButton opens a dialogBeside a description of the appointment
Pop-up textText opens a dialogWithin a paragraph inviting contact
Floating badgePersistent launcherA site-wide booking entry point

Set the theme and accent to remain readable against the surrounding site. You can hide the event details and profile header independently. If you hide meeting details, put the duration and purpose near the widget.

The small Powered by badge stays visible. Use the booking page styling guide to set your logo, layout, cover and event copy.

How do I add the booking calendar to my website?

Copy the builder's generated output into a code-capable website area, then publish and test the result outside the editor. Use the platform selector as the starting point; the examples below use placeholder public event addresses. Replace them with your own.

HTML and code-capable site blocks

This inline example matches the HTML generator with a 30-minute event, automatic theme and visible details. The data attributes are part of the embed API, so keep their names unchanged.

<div data-barq-inline data-url="https://meet.barq.dev/your-name/intro" data-theme="auto" data-color="#0d9488" data-hide-details="false" data-hide-header="false" data-hide-powered="false" data-prefill-name="" data-prefill-email="" data-utm="true" data-duration="30"></div>
<script src="https://meet.barq.dev/embed.js" async></script>

The loader replaces the container with the booking experience. A plain div without the script won't become a calendar, and a script alone doesn't specify where an inline calendar should appear.

WordPress, Webflow and Wix

Choose the matching platform in Embed & share and copy the generated code. Our builder directs WordPress users to a Custom HTML block, Webflow users to an Embed element and Wix users to Embed HTML. Publish the page before judging script execution.

Those are the installation targets provided by our builder, checked 17 Nov 2026. Website plans and editor permissions differ; we haven't established which subscription makes custom code available for every builder. Use a hosted booking link if your editor won't run the snippet.

React

Select React to get a BookingEmbed component that waits until mounting before initialising the loader. This is the generated inline component with a placeholder event URL; retain its cleanup when integrating it into a route. The booking redirect guide keeps a thank-you page neutral when no personal information needs to be carried into its URL.

import { useEffect, useRef, useState } from 'react';

const options = {
  "url": "https://meet.barq.dev/your-name/intro",
  "theme": "auto",
  "color": "#0d9488",
  "hideDetails": false,
  "hideHeader": false,
  "hidePowered": false,
  "prefill": {
    "name": "",
    "email": "",
    "answers": {}
  },
  "utm": true,
  "duration": 30
};

export function BookingEmbed() {
  const container = useRef(null);
  const [ready, setReady] = useState(false);
  useEffect(() => {
    let active = true;
    let badge;
    const initialize = () => {
      if (!active) return;
      window.BarqMeet.inline({ ...options, el: container.current });
      setReady(true);
    };
    let script = document.querySelector('script[data-booking-loader]');
    if (window.BarqMeet) initialize();
    else {
      if (!script) {
        script = document.createElement('script');
        script.src = "https://meet.barq.dev/embed.js";
        script.async = true;
        script.dataset.bookingLoader = 'true';
        document.body.appendChild(script);
      }
      script.addEventListener('load', initialize, { once: true });
    }
    return () => {
      active = false;
      script?.removeEventListener('load', initialize);
      badge?.remove();
    };
  }, []);
  return <div ref={container} />;
}

The generated example uses the loader's browser global. In a TypeScript application, also include your project's declaration for that global and type the element reference according to your existing client code. The developer reference documents the embed API.

Why is a booking iframe blocked on my domain?

A populated allowed-domain list limits which parent origins may frame the booking page. An empty list permits any domain, so adding an entry is an optional restriction, not a prerequisite. Match the published site's exact origin.

Use Settings, then API & webhooks, to review Allowed domains. The validator accepts HTTP and HTTPS origins, without paths or trailing slashes. Prefer HTTPS for production; HTTP is accepted for a local origin such as http://localhost:5173.

For example, https://example.com and https://www.example.com are different origins. If visitors reach both hosts, include both when restricting embedding. An entry such as https://example.com/contact is a page address and won't satisfy the origin format, so enter the scheme and host without the path.

The widget checks the parent website’s origin when delivering events through the embed API. With an empty allowlist, the booking_created event includes only the event slug (eventType), start and end. To receive the booking ID (uid) and guestEmail, add the parent website’s exact origin to the host’s allowlist. These settings govern the embed. The host’s calendar settings still determine which calendars block availability.

How should the published embed behave?

Visitors should see the event's dates and available times, select a slot, and complete the same booking form used on the hosted page. Inline mode stays in the page; pop-up modes open the scheduler after activation. Test the actual published site. The booking-widget definition distinguishes the form inside your site from the direct address that can open the same appointment elsewhere.

We forward supported UTM and ref attribution from the parent page when that option is enabled, and the loader handles frame-size messages. Avoid wrapping the widget in a fixed-height container that crops its content on a phone.

Book once with an inbox you control, inspect the invitation and cancel the test afterwards. A form rendering correctly isn't enough if the page can't complete a booking.

Fixing a blank or cropped booking widget

Check the loader, installed code and origin restrictions before changing the event's schedule. A direct event link that works while its embed is blank usually points to website installation or framing, so inspect those before changing the meeting hours. Compare those two surfaces first.

SymptomLikely causeFix
Empty inline spaceScript removed or blockedInspect published code and script loading
Framing refusedParent origin absent from allowlistAdd the exact origin or revise the restriction
Mobile calendar croppedFixed surrounding heightAllow space for frame resizing
React route has no widgetInitialised before mount or loader readinessUse the generated mount lifecycle
Available dates are empty on both surfacesCalendar or event rulesFix the hosted booking setup first

Review embed availability and account terms, then create a booking calendar for your website. Keep a visible hosted-link fallback where visitors can find it.

Steps

  1. Test the public booking link

    Make sure the event offers the intended times before embedding it. Use the public event URL, not an app dashboard address.

  2. Open Embed & share

    Choose inline, pop-up button, pop-up text or floating badge. Set theme and visibility options for the surrounding page.

  3. Review API & webhooks in Settings

    Allowed domains are optional: an empty list allows all domains. To restrict embedding, enter exact HTTP or HTTPS origins without paths or trailing slashes.

  4. Choose the website code format

    Select HTML, WordPress, Webflow, Wix or React in the builder. Copy the generated snippet for the event and display options you selected.

  5. Install and publish the code

    Place the snippet in a code-capable part of the site. React components must initialise the loader after mounting.

  6. Check the published booking flow

    Test outside the site editor at desktop and phone widths. Complete and cancel a test booking to verify the calendar and confirmation.

Frequently asked questions

Do I need an API key in the embed code?

No. The public booking embed uses the event URL and loader, not a secret API key. Don't paste developer credentials into website HTML or a client-side React component; visitors can inspect everything shipped to their browser. Keep secret credentials out of the page and use the documented embed snippet, treating API authentication as a separate concern for a custom-built booking integration.

Will an embedded booking still check my calendars?

Yes. The widget uses the same booking availability and submission checks as the hosted event page. A website embed changes where the guest sees the calendar; it doesn't bypass selected Google calendars, notice rules or booking protection. Test a busy interval through the embedded form too, so you verify the same event rules are applied inside the actual website layout you intend to publish.

Can I prefill the form for a known visitor?

Yes. The builder supports prefilled details, but values placed in public code or URL parameters can be inspected by visitors. Only include information intended for that page, and don't publish a real client's email as a reusable default. Check that the values belong to the current visitor and avoid exposing personal details in a publicly shared address or example embed on the site.

Create your free booking link

Sign in with Google, create an event and share your link.

Create your free link