Widget Display and Visibility

The visual integration of an AI chatbot is as critical as its conversational intelligence. The Widget Display and Visibility settings within the Antimanual plugin provide administrators with comprehensive control over how the chatbot interface appears and where it triggers across the WordPress ecosystem. Proper configuration ensures that the chatbot complements the site design rather than obstructing the user experience, maintaining brand consistency while optimizing engagement rates.

Table of Contents

• Appearance Customization
• Configuring Visibility Rules
• Mobile Responsiveness and Accessibility
• Technical Best Practices
• Frequently Asked Questions

Appearance Customization

The aesthetics of the chatbot widget should align seamlessly with your corporate identity. Antimanual allows for deep customization of the primary interface elements to ensure the bot feels like an organic part of your digital presence. To begin customizing the identity of your bot beyond just the visuals, you should also review the documentation.

• Widget Position: You can choose to dock the widget on either the left or right side of the viewport. Most modern interfaces prefer the bottom-right corner, but left-side docking is available for sites with conflicting floating elements like “Back to Top” buttons or social share bars.
• Widget Icon: The launcher icon is the first point of contact. You can select from a library of pre-set professional icons or upload a custom SVG/PNG to act as your brand’s unique chat trigger.
• Theme Color: The plugin supports hex-code precision for primary and secondary colors. The primary color typically dictates the header and launcher background, while the secondary color is used for accent elements and user message bubbles.

Configuring Visibility Rules

Strategic placement of the chatbot is essential for maximizing lead generation without annoying the user. High-intent pages may require a more prominent bot, while checkout or landing pages might benefit from its absence to reduce friction. This logic is closely tied to how you handle .

Antimanual provides three primary layers of visibility control:

• Global Display: Enabling this ensures the widget loads on every public-facing page of your WordPress site. This is ideal for general support bots.
• Conditional Loading: For advanced users, specific conditions can be set. This allows the widget to appear only on specific Post Types (e.g., only on ‘Docs’ or ‘Products’) or on specific URL patterns. This prevents the bot from appearing on administrative or irrelevant pages.
• Manual Exclusion: You can explicitly hide the widget on high-conversion pages where you want the user to focus strictly on a specific call to action.

Mobile Responsiveness and Accessibility

Mobile traffic often accounts for over half of web engagement. However, floating widgets can sometimes obscure content on smaller screens. Antimanual includes a dedicated Hide on Mobile Devices toggle. When enabled, the widget will only initialize for users on tablet or desktop resolutions, ensuring your mobile site remains clean and compliant with mobile-friendly SEO standards.

Technical Best Practices

To ensure optimal performance while using the widget, consider the following technical recommendations:

• Contrast Ratios: When selecting theme colors, ensure there is sufficient contrast between the background and text colors to meet WCAG accessibility standards.
• Asynchronous Loading: The Antimanual widget is designed to load asynchronously, meaning it will not block the rendering of your primary page content, preserving your Core Web Vitals scores.
• Icon Optimization: If uploading a custom icon, use a compressed SVG format to minimize the initial payload size of the widget launcher.

Frequently Asked Questions

Can I show the widget only to logged-in users?
Currently, visibility is controlled primarily via page-level conditions. However, you can use WordPress conditional tags or third-party snippet plugins to wrap the Antimanual initialization script if user-role-based visibility is required.

Will the widget slow down my site’s mobile performance?
No. Because the widget loads after the main page content, its impact on user-perceived performance is negligible. Using the “Hide on Mobile” feature further ensures no resources are spent on mobile devices if the bot is not needed.

Can I use a different color for the chat bubbles than the header?
Yes, the Secondary Color setting allows you to differentiate the accent elements and message bubbles from the main brand header color.