Where a chat widget should and should not appear

A chat widget is one script tag, so the usual decision is "every page" by default. That is nearly right, and the exceptions matter more than they look - particularly on a phone, where a badly placed bubble covers the button you want people to press.

Start with every page, because you cannot predict the entrance

Visitors from search do not land on your home page. They land on the one page that matched their question - a service page, a blog post, a product - and that is where they have the question. Putting the widget only on the home page and the contact page means most of your visitors never see it. Install it site-wide; an assistant that can read the page it is on answers better from a deep page than from the home page anyway. See page-aware answers.

The pages to leave alone

• Checkout and payment pages. Nothing should distract or overlay a payment flow, and nothing on that page should be read by a third-party script. Allinaa's widget already skips private path segments such as checkout and account pages when it reads the page for context; keeping it off those pages entirely is the simplest rule.
• Signed-in account areas, for the same reason, and because a visitor there is a customer with a different question, usually one the assistant cannot answer.
• Legal pages, if a floating bubble over your terms bothers you. Harmless either way.
• Landing pages built for one action. Sometimes correct, sometimes not - see below.

Landing pages: one decision, made deliberately

A paid landing page exists to produce one action. A chat bubble is a second action, and on a page with a single form it can either rescue the visitor who has a question or distract the one who was about to fill the form in. The honest answer is that it depends on the page, and the only way to know is to try it with the campaign running. What is not in doubt: if the page sells something with conditions - sizes, areas, eligibility - the questions get asked somewhere, and a bubble is cheaper than a lost visitor. See chat on landing pages.

On a phone, the bottom-right corner is contested

This is where placement actually goes wrong. On a phone the chat bubble sits in the same corner as a cookie banner, a "back to top" arrow, a sticky "add to basket" bar, a floating call button and some scroll-to-section widgets. Two of those overlapping makes both unusable, and visitors do not report it - they leave. Open your own site on a real phone, scroll to the bottom of your longest page, and look at that corner. Then check it with the cookie banner showing, because that is what a first-time visitor sees. See a chatbot on a phone.

Do not make it leap out

An automatic pop-open on page load, especially with a sound, is the single most reliable way to make somebody close a chat and not come back. If a widget can open itself, the only defensible trigger is a deliberate one - a visitor who has been on a pricing page for a while, say - and even then a quiet bubble with a short label does the same job with none of the resentment. A visitor who opens the chat themselves is already asking a question.

The label matters more than the icon

A bare speech bubble says "chat widget". A short label says what it is for, and the specific version works better than the friendly one: "Ask about prices", "Ask a question", "Check if we cover your area". Say what the visitor can get, in the visitor's words.

Where it loads in the page

A chat widget should never delay your page. Allinaa's tag is deferred, so it loads after the page is usable, and the widget's own styles live in a shadow DOM so they cannot be broken by your theme or break it. If your installation uses a tag manager, remember that the container has to be published, not just saved - the most common "the widget isn't showing" cause. See installing with Google Tag Manager and install troubleshooting.

A five-minute check before you call it done

1. Open your three most-visited pages on a real phone. Is the bubble reachable, and is it covering anything?
2. Load a page with the cookie banner showing. Still fine?
3. Visit a checkout page. Is the widget absent, as you intended?
4. Open a deep service page and ask the assistant something about that page. Does it answer about the right thing?
5. Ask for a person. Does the handover sentence say what will happen?

See the launch checklist for the rest.