Skip to content
Public beta preview — you're seeing the sneak peek

Webflow — install the widget

read as .md

On Webflow the tag goes into the site-wide Footer code setting — no Designer work, one paste, then publish. The tag is the same on every platform — Install the widget has the general picture; this page has the exact place on Webflow.

The tag — put your app id in place of app_abc123
<!-- guuey widget. Add this site to the app's allowed domains or the embed is refused. -->
<script src="https://widget.guuey.com/v1.js" data-app="app_abc123" async></script>
  1. Open Site settings and go to the Custom code tab.
  2. Paste the tag into the Footer code section — Webflow says code entered there "appears before the closing </body> tag in your site's HTML markup and applies to your entire site" — and click Save changes.
  3. Publish the site: Webflow shows custom code in preview, but it "won't go live until your site is published".
  • Webflow's plan sentence, verbatim: "If you have a Core, Growth, Agency, or Freelancer Workspace, or if your site has an active Site plan, Site managers and Designers can add custom code and scripts that apply to your entire site or individual pages."
  • The Footer code section holds up to 50,000 characters. A per-page slot also exists (Page settings → Custom code → Before </body> tag) — the widget belongs in the site-wide Footer code.

Verified against the vendor's documentation on 2026-09-09: Custom code in head and body tags (Webflow Help Center; article updated within the week of the read). Vendor interfaces change — if a step no longer matches what you see, the vendor's page above is the source of truth.

Allow your site’s origin (console → Embed → Allowed origins, or guuey apps update <appId> --domains <origin>; about 15 seconds to apply), add the CSP allowances if your site sets a policy, then verify with guuey apps check <appId> --origin <origin> — the steps are on Install the widget.

Paste into your coding agent
Install the Guuey chat widget on this Webflow site. Before changing anything,
read https://docs.guuey.com/embed/webflow.md and https://docs.guuey.com/install-widget.md
(the raw markdown of the two pages) and follow them exactly; do not invent options
or steps they do not contain.
1. Put this tag in Site settings → Custom code → the Footer code section (Webflow places it before </body> on every page), then publish the site, with my app id <appId> in place of app_abc123:
<script src="https://widget.guuey.com/v1.js" data-app="app_abc123" async></script>
Add nothing else to the tag — except your page's CSP nonce, if the site uses
nonces (step 3).
2. Tell me the exact origin(s) my pages are served from (scheme + host) so I can
add them to the app's allowed domains in the console (Embed → Allowed origins)
or with: guuey apps update <appId> --domains <origin>. Remind me that a bare
hostname covers the apex and every subdomain, while a scheme-prefixed origin is
an exact match, and that changes take about 15 seconds to apply.
3. If this site sets a Content-Security-Policy, add exactly these allowances and
nothing more. If the policy uses nonces (script-src 'nonce-...'): render the
site's per-request nonce on the widget tag the way its other script tags carry
it — that is what lets the loader run, and the loader puts the same nonce on the
one <style> it injects; then allow https://widget.guuey.com in frame-src and
connect-src. If the policy uses host allowlists: add https://widget.guuey.com to
script-src, frame-src and connect-src, and 'unsafe-inline' to style-src.
4. When I've saved the origin, verify with:
guuey apps check <appId> --origin <origin>
Stop and ask me before any step those two pages do not describe.