Chatbot placement rules determine where, when, and for whom a chatbot appears on the frontend. They are the final gate between a configured chatbot and actual visibility. Without placement rules, a chatbot exists but is effectively invisible.
Placement rules are mandatory for frontend display and are evaluated on every page load.
What Placement Rules Do #
Placement rules control:
- page-level visibility
- user-based visibility
- device and environment targeting
- contextual rendering
They do not affect:
- chatbot intelligence
- persona behavior
- model choice
- conversation logic
Placement decides presence, not behavior.
Placement Rules Are Per Chatbot #
Each chatbot has its own independent rule set.
This means:
- different chatbots can appear on different pages
- multiple chatbots can coexist without conflict
- editing rules for one chatbot does not affect others
There is no shared or global placement configuration.
Rule Evaluation Model #
Placement rules are evaluated:
- on the frontend
- during page load
- before the chatbot UI is rendered
If the rules match, the chatbot is rendered.
If they do not, the chatbot is not loaded at all.
There is no background loading or hidden state.
Common Placement Rule Types #
Site-Wide Placement #
The chatbot appears on all frontend pages.
This is typically used for:
- general support bots
- onboarding assistants
- universal helpers
This is the simplest configuration.
Page-Specific Placement #
The chatbot appears only on:
- specific pages
- specific posts
- selected URLs
Used for:
- landing pages
- sales funnels
- documentation pages
- targeted experiences
Post Type–Based Placement #
The chatbot appears only on:
- specific post types
- custom post types
Examples:
- only on product pages
- only on documentation entries
- only on blog posts
This is useful for large sites with structured content.
Taxonomy-Based Placement #
Chatbots can be shown based on:
- categories
- tags
- custom taxonomies
This allows context-aware bots, such as:
- a sales bot on product categories
- a help bot on support articles
User Role–Based Placement #
Visibility can be controlled by:
- logged-in vs guest users
- specific user roles
Examples:
- show chatbot only to customers
- hide chatbot from administrators
- internal chatbot for editors only
Role checks use WordPress’ native role system.
Device-Based Placement #
Chatbots can be shown or hidden based on:
- desktop vs mobile
- device type
This is useful when:
- mobile UX needs to be simplified
- chatbots are designed for touch or voice
- certain layouts do not work well on small screens
Language and Locale Placement #
Chatbots can be targeted by:
- site language
- detected locale
This allows:
- language-specific bots
- region-aware assistants
- multilingual deployments without mixing responses
User Agent / Environment Placement #
Advanced rules can target:
- browser types
- operating systems
- user agents
This is typically used for:
- debugging
- special environments
- controlled deployments
Combining Multiple Rules #
Rules can be combined.
A chatbot can be configured to appear only when all conditions are met, for example:
- only on product pages
- only for logged-out users
- only on desktop
Complex targeting is supported, but should be used sparingly.
Rule Priority and Conflicts #
If multiple chatbots match the same page:
- all matching chatbots may load
- UI stacking and layout rules apply
- no chatbot automatically overrides another
There is no implicit priority unless you design one through rules.
Avoid overlapping rules unless multi-bot behavior is intentional.
Backend Chatbots Ignore Placement Rules #
Placement rules apply only to frontend chatbots.
The backend chatbot (Playground):
- is always accessible in admin
- ignores placement rules entirely
- is unaffected by frontend visibility
Caching Considerations #
Because placement rules are evaluated on page load:
- aggressive caching can interfere with rule logic
- user-based rules may require cache bypass
- role-based rules often need dynamic rendering
Always test placement behavior with caching enabled.
What Placement Rules Do Not Do #
Placement rules do not:
- delay chatbot loading
- dynamically change personas
- switch models
- route conversations
- affect usage limits
They are strictly about visibility.
Common Placement Mistakes #
- enabling frontend display but defining no rules
- overlapping rules between multiple chatbots
- testing while logged in as admin only
- forgetting cache effects
- assuming default visibility exists
Most “chatbot not showing” issues are rule-related.
Best Practices #
- start with simple rules
- test on a single page first
- avoid overlapping chatbots unless intentional
- document rule intent on complex sites
- test with real user roles and devices
Placement rules should be predictable, not clever.
Summary #
Chatbot placement rules determine exactly where and when a chatbot appears on the frontend. They are required for frontend visibility, evaluated per chatbot, and fully decoupled from chatbot behavior. Used correctly, placement rules allow precise, context-aware chatbot deployments without conflicts or surprises.
