Show Your AI Chatbot on Only Certain Pages (Like /support)

A chat bubble sitting in the corner of every single page — homepage, product pages, blog, checkout — is the default almost every chatbot tool ships with. For a lot of businesses that's exactly right. For others, it's the reason they've never turned a chatbot on at all.

Maybe your homepage is a carefully designed first impression and a bubble in the corner clutters it. Maybe your checkout flow can't afford one more distraction. Maybe you just want an AI assistant that handles support questions and nothing else — present when someone needs help, invisible everywhere else.

That's page targeting, and it's something you configure once in your dashboard, not something you solve by rewriting your site.

Why "everywhere" isn't always right

A chatbot that appears on every page is optimizing for maximum exposure. That's the right call if the goal is capturing leads or answering pre-sales questions before someone bounces. It's the wrong call when:

• Your homepage is a landing page, tuned for one conversion action, and a chat bubble competes with your CTA.
• You only want the bot handling support, not sales chatter, and putting it everywhere blurs that line for visitors.
• Some pages already have their own support tooling — an embedded help centre, a contact form — and a second chat option is just noise.
• You're testing the waters. Turning on a chatbot for your whole site feels like a bigger commitment than trying it on one page first.

How page targeting works

Instead of choosing which pages to add a script tag to (fragile — you have to remember to add or remove it as your site changes), you keep the same one-line embed everywhere and control visibility from the dashboard instead. Three modes:

• All pages (the default) — the widget shows up everywhere it's embedded, same as before.
• Only on these pages — you list the paths where it should appear, and it stays hidden everywhere else. Best for a support-only assistant.
• Everywhere except these — the widget shows up everywhere except the pages you list. Best when there are just one or two pages — checkout, an admin area — where you don't want it.

Patterns support exact matches and whole-section wildcards:

• /support matches only that page.
• /help/* matches /help itself and everything underneath it — /help/billing, /help/faq, /help/returns, all of it — so you don't have to list every sub-page individually.

Because this is evaluated against the page the visitor is actually on (not baked into the embed code), it also works correctly on single-page apps — a React, Vue, or Next.js site that navigates between "/" and "/support" without a full page reload still gets the widget mounted and unmounted at the right moments.

One chatbot, multiple websites

If the same chatbot is embedded on more than one domain, a plain path applies everywhere it's embedded — /support matches on any site. To target just one of those domains, qualify the pattern with a host:

• docs.example.com/* — only on that subdomain, matching every page under it.
• example.com/support — only that exact page on that exact domain.
• *.example.com — every subdomain of example.com, any page.

Mix and match freely — /support alongside docs.example.com/* in the same list works exactly as you'd expect.

Setting it up

1. Open your chatbot in the dashboard and go to the Integration tab.
2. Under Page Visibility, pick "Only on these pages" or "Everywhere except these."
3. Add the patterns — e.g. /support, /help/* for a whole section, or docs.example.com/* if it's a multi-site chatbot.
4. That's it. No changes to your embed snippet, no redeploying your site.

If you later decide you want it everywhere again, switch back to "All pages" — nothing about your embed code changes either way.

A practical example

Say you run a SaaS product with a marketing site at the root and a documentation/help centre at /docs. You don't want a chat bubble hovering over your pricing page or your blog — but you absolutely want an AI assistant answering questions the moment someone's stuck reading documentation. Set it to "Only on these pages" with /docs/*, and it appears exactly where people are already looking for help, and nowhere else.

Or flip it around: you're happy with the widget everywhere except your checkout flow, where one more popup competing for attention could cost you a sale. Set it to "Everywhere except these" with /checkout/*, and leave the rest of the site alone.

The point isn't to use a chatbot less — it's to put it exactly where it earns its place.