Three routes
- Theme footer — add the script before the closing body tag in a child theme
- A header/footer plugin — no code, survives theme changes
- Tag manager — if you already run one
Use a child theme, not the parent. A theme update will overwrite the parent and your widget will disappear without warning.
Keep it out of the critical path
- Load it in the footer, not the head
- Do not let it block rendering
- Exclude it from pages where it is not wanted — checkout, for example
- Check your page speed before and after, so you know
Caching and WordPress
Most caching plugins handle a footer script correctly. If you use aggressive optimisation — deferring or combining scripts — test that the widget still appears after a cache clear.
The classic failure is a widget that works for logged-in administrators and is invisible to everyone else, because they are served the cached page.
Where to show it
| Page type | Show it? |
|---|---|
| Service and product pages | Yes — highest intent |
| Contact page | Yes |
| Blog posts | Yes |
| Checkout or booking flow | Usually not — do not distract |
| Admin or member areas | No |
Feed it your own content
Crawl the site so it learns from your pages, then check the answers to your top twenty questions. Where it gets one wrong, the page behind it is usually the problem.
Fixing those pages helps your human visitors and your search visibility as well as the bot.