Embedding puts the booking page inside your own site. Inline for context, popup for compact pages, and a plain link as the fallback that always works. The widget builder generates the code; the embed guide explains where an embed helps and where it hurts.
Before you start
- The page where visitors have already decided to book.
- Your consent banner and content security policy.
- A phone, to test completion.
How to complete this task
- Choose inline for context, popup for compact pages, or a normal link for maximum resilience.
- Load the scheduler only where the visitor expects to book.
- Preserve keyboard focus, responsive sizing, and a visible fallback link.
- Test performance, consent, source attribution, and mobile completion.
Finish by opening the public link in a signed-out browser: a saved setting is not proof that the guest path works.
Troubleshooting
The problems people report most often with this task, and the cause behind each one.
The embed does not appear on the page.
Check the content security policy and any consent banner blocking third-party frames. Always keep a plain text link as a fallback.
The embed breaks the mobile layout.
Inline embeds need a responsive container. On narrow screens a direct link often converts better than a squeezed frame.
Keyboard users get trapped in the embed.
Verify focus can enter and leave the frame with the keyboard alone. This is an accessibility requirement, not a preference.
Related Meetin.gs help
Return to the Meetin.gs Help Center for the adjacent configuration guide, or send the exact event code and expected result when the documented checks do not explain the behavior.
