WordPress — install the widget

On WordPress with a block theme, the tag goes into the Footer template part through the Site Editor. The tag is the same on every platform — Install the widget has the general picture; this page has the exact place on WordPress.

The tag

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>

Where it goes

1. In the dashboard go to Appearance → Editor (the Site Editor; it exists only when a block theme is active).
2. Open Patterns → Template Parts → Footer and click the pencil to edit it.
3. Click the + block inserter, add a Custom HTML block (or type /html), open Edit HTML, paste the tag, press Update.
4. Save — WordPress notes that changes to the Header and Footer template parts apply to every page that uses them.

• A <script> tag inside a Custom HTML block needs the unfiltered_html capability (an Administrator on a single site); for other roles WordPress strips <script> when the block is saved.
• Classic (non-block) themes have no Site Editor — the tag goes in the theme's footer template or through a header-and-footer code plugin; that path is your theme's documentation, not this page.

Verified against the vendor's documentation on 2026-09-09: Site Editor (WordPress documentation, updated 2026-08-19) · Custom HTML block (WordPress documentation, updated 2026-06-15). Vendor interfaces change — if a step no longer matches what you see, the vendor's page above is the source of truth.

Before it shows

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.

Give this to your coding agent

Paste into your coding agent

Install the Guuey chat widget on this WordPress (block themes) site. Before changing anything,
read https://docs.guuey.com/embed/wordpress.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 the Footer template part (Site Editor → Patterns → Template Parts → Footer) in a Custom HTML block — or, if the site uses a classic theme, the theme's footer template as its own documentation describes, 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.