Every website builder gives you somewhere to paste code. What matters is what it does with it afterwards. Some drop it into the page as though you'd written it yourself, which is what the booking form needs. Others wrap it in an iframe — a sealed window at a fixed size — and the form ends up scrolling around inside a box.
The general article has the snippet and explains where to find your booking code. This page is only about which builders can take it.
These run it properly
Weebly — drag the Embed Code element to where you want the form, click into it, choose Edit Custom HTML and paste the snippet.
Duda — drag the HTML widget in and paste the snippet into its content box.
In both, paste the container and the script together, in that order, in the one box. The script looks for the container the instant it runs, so splitting them up is the single thing that reliably breaks it.
These seal it in a window
GoDaddy Websites + Marketing — its HTML section puts whatever you paste inside an iframe, isolated from the rest of the page. There is no other way in: GoDaddy's builder doesn't let you put a script into the page itself.
Google Sites — Insert → Embed → Embed code is an iframe too, and again there's no alternative route.
On both, put a Book a Table button on the page linking to your booking page instead. The form the guest lands on is full width, sized properly, and shows Apple Pay and Google Pay — none of which would be true of anything squeezed into that window.
Apple Pay and Google Pay generally
A rule of thumb that holds across all of these. Stripe only offers the wallets on a website it has verified, and verifying means answering one particular file at one particular address on your own domain. If your builder won't let you upload a file to an address of your choosing — and most of the hosted ones won't — the wallets can't appear on your pages, however the form got there.
Cards always work. Nothing breaks. But it's the quickest way for somebody to pay on a phone, and nothing on the page explains its absence, so it's worth knowing which side of that line your website sits before you decide where the form should live.
Something else entirely
If your site is hand-built, or on a framework — Framer, Astro, Next.js, Eleventy, plain HTML — there's nothing special to do. Put the container in the page's own markup where the form should appear, and the script tag straight after it. That's the whole recipe, and the order is the only rule that catches anyone out.
Prefer to hand the whole thing over?
If your builder is one of the ones that can only manage a button, and even that feels like more upkeep than you'd like, we do this ourselves for a number of venues already: a full redesign, hosted by us, with your booking form built directly into the page from the start rather than pasted on afterwards — so none of what's above is anything you ever have to touch again.
There's no charge to build it. Keeping it is £15 a month, and that covers hosting and any change you ever want making — you message us what you'd like changed and we do it, no hourly rate and no quote for every little thing. For most venues that comes out below what the hosting, theme and plugin costs already add up to before a single change is even made.
No pressure either way, and it makes no difference to your booking account whichever you choose. If you'd like to see what we'd put together, just get in touch.