Tutorials

Where to Place AI Chat on a Publisher or Store Website

A practical placement brief and page-coexistence checklist for Publishers and Brands evaluating AI chat.

8 min read
CROecommerce UXsite chatbuying guidesWordPress

Place AI chat where a reader or shopper has a useful question, then check that it leaves the rest of the page usable. An inline unit, a floating launcher and a contextual button solve different problems. None is the best placement for every site.

For a publisher, the test includes the article, existing advertising and the route to a recommended product or another story. For a store, it includes product details, filters, cart controls and the next buying step. Choose one clear job before adding another invitation.

Start with the page and the visitor's task

Use a representative page rather than an empty demonstration. Include the consent banner, sticky navigation, existing ads and other controls that visitors actually encounter. A placement that looks clear in isolation may cover something important when those elements appear together.

Write a short placement brief: the page type, the question being answered, the approved sources, the intended destination and the owner who can remove or change the placement. For example, a buying-guide reader may want to compare two products the editor already recommends. A category-page shopper may need help narrowing a documented set of options. These are illustrative tasks, not reported customer results.

Preserve the existing route. Readers should still be able to read the article and follow its links. Shoppers should still be able to use filters, inspect product information and reach checkout. Chat earns a place by helping with a task, not by making the alternative harder to use.

Choose a placement for a specific reason

Inline within an article: useful to evaluate when a reader has reached a relevant explanation or comparison. Check that the unit fits the article column and does not displace editorial recommendations, an ad slot or essential navigation. Keep the distinction between editorial content and any commercial recommendation clear.

A floating launcher: useful to evaluate when help needs to remain available across a journey. Inspect its collapsed and expanded states. The launcher and panel must be checked against consent controls, sticky ads and mobile page actions; a clear desktop corner can be crowded on a phone.

A contextual button: useful to evaluate beside a comparison or other decision point. Its wording should explain what opens and what help is available. Confirm that the implementation actually receives the relevant page or product context. A button beside a filter does not establish that selected filters are passed into chat.

A link from a table of contents or the footer: useful when it answers a navigational need. Make its destination clear and test the return to reading. Do not assume a footer placement reaches the same audience as an invitation beside the main decision.

Start with the placement your implementation supports and your page can accommodate. Multiple entry points can be evaluated later, with clear rules about what appears together. Avoid presenting several competing invitations simply because the components exist.

Run a page-coexistence check

Check each proposed placement in the states below. Record the page, device, browser, configuration and observed result so another person can reproduce a failure.

Collapsed and open: can the visitor read the main content, reach navigation, use consent controls and follow the original product or article links? Inspect both the launcher and the open panel.

Mobile and zoomed: do chat, ads and sticky controls overlap? Can a visitor reach the close control, input and relevant page action without moving through an unusable layout? Include a narrow viewport and enlarged text in the review.

Keyboard: can a visitor reach and activate the entry point, understand the visible focus, use the interface and leave it? When the interface is a modal dialog, follow the W3C dialog pattern for focus inside the dialog, Escape to close and returning focus to the invoking control. An inline region is a different interaction pattern; do not apply a focus trap simply because it contains chat.

Slow or failed loading: what remains on the page when the assistant takes longer than expected or cannot answer? The original content and destination should remain useful. Provide a clear explanation and an appropriate next step rather than an indefinite loading state.

Content changes: does a relevant source update change what the assistant can answer? Check the actual source and selected product or article destination. A plausible answer is not enough when it points to the wrong variant or misstates the editor's recommendation.

Check accessibility and page movement separately

A placement review should include keyboard and assistive-technology testing, not just a screenshot. Ask whether the entry point has a clear name, controls have understandable labels, new information is available to screen-reader users, and a visitor can find appropriate help when chat cannot resolve the task.

W3C's guidance on focus not being obscured explains why author-created content should not entirely hide the control a keyboard user has focused. Check the surrounding page while chat is present, including sticky elements that appear after scrolling. This is one focused test, not an accessibility certification.

Unexpected page movement is another problem. Google's CLS guidance identifies dynamically inserted content and resizing third-party elements as possible causes of layout shifts. Ask the implementation team to reserve suitable space for inline content and test the actual loading sequence. Compare laboratory diagnosis with available real-user data; a tidy mockup does not prove a Core Web Vitals result.

Agree on the opening behavior

Decide whether the visitor opens chat, selects a suggested question or sees a supported product presentation before interacting. Test the exact configuration rather than assuming every placement has the same trigger or initial content.

A proposed delay, scroll threshold or filter-based trigger is a hypothesis until the implementation supports it and the page test confirms it. Choose behavior for the task and audience, then observe whether it helps. There is no universal number of seconds, filters or page views that makes a prompt appropriate.

Keep typed questions separate from selected suggestions and automatically generated content in your reporting. Those inputs can all be useful, but they do not establish the same kind of reader demand.

Measure the placement through to its destination

Before changing the page, agree on the eligible audience and record the configuration. Separate the events your instrumentation can actually observe: eligible page visits, rendered or visible placement, opening or question selection, useful answer, article or product click, and any verified downstream order or other outcome.

Name the denominator for every rate. Opens per eligible page visit and product clicks per conversation answer different questions. A rendered component is not necessarily a viewed one, an interaction is not necessarily a typed question, and a merchant click is not a completed purchase.

Keep existing commerce and editorial outcomes in the review. More chat activity alone does not show that the placement helped the site. Where practical, use a suitable controlled comparison. Otherwise describe the result as observational and retain differences in audience, device and traffic source. Use the chat revenue measurement guide to distinguish assisted revenue from an incremental result.

Where Brambles.ai fits

Brambles.ai powers AI chat for Publishers and Brands. Its inline and floating experiences provide placement options to evaluate on representative content and products. Confirm the supported configuration, source scope, opening behavior, controls and measurement with the implementation team before a pilot.

Start with the inline placement overview and the practical proactive-chat guide. Use the checks above to decide whether the selected experience fits your page. Placement availability does not establish a particular trigger, accessibility result, ad compatibility or revenue improvement on your site.

FAQ

Is inline chat always better than floating chat? No. Inline can suit a specific place in an article or product journey; floating chat can keep help available across pages. Compare them against the same visitor task and the actual surrounding page.

Should chat open automatically? Treat that as a configuration and experience decision to test. Verify the supported behavior and check whether it interrupts reading or important page actions. More openings alone are not proof of a better result.

Can chat coexist with existing ads? It needs to be checked on the particular page and configuration. Review collapsed and open states, ad refreshes, consent controls, mobile overlap and the site's applicable commercial requirements. One successful example cannot establish compatibility everywhere.

What should make us stop or revise a placement? An obstructed page action, inaccessible interaction, incorrect source or destination, or unresolved measurement gap is a concrete reason to revise the test. Expand only when the page experience and the outcome evidence support the next step.

Explore Brambles.ai

Learn more about our AI-powered agentic commerce platform, agentic shopping, and shopping assistance solutions.

Explore More Insights

Discover more articles on AI, automation, and business innovation

View All Articles