Does JakBot work on mobile devices?

Yes. All JakBot chat templates are responsive and work on mobile devices, tablets, and desktops. The chat widget adapts to the screen size automatically. Jay’s SEO Checklist also tests mobile performance specifically through its PageSpeed Insights integration, and Jay’s Post Amplifier’s admin interface is fully mobile-responsive.

What are the server requirements for JakBot?

JakBot requires WordPress 5.0 or higher and PHP 7.4 or higher. MySQL 5.6+ or MariaDB 10.3+ is needed for the database. A memory limit of at least 128MB is recommended. The plugin works on both Apache and Nginx web servers. HTTPS is strongly recommended for secure API communication. The JakBot team verifies compatibility during setup.

Is JakBot compatible with page builders like Elementor or Divi?

Yes. JakBot is added via a WordPress shortcode ( Hello! How can I help you today? +/- Default Bot .abg-ai-assistant .avatar { background-image: url('https://getjakbot.ai/wp-content/uploads/2026/06/jakbot-robot-head-white-h.png'); background-repeat: no-repeat; background-position: center center; background-size: contain; text-indent: -999em; } Send ), which is compatible with all major page builders including Elementor, Divi, Beaver Builder, and WPBakery. Simply add a shortcode widget or module and paste in the JakBot shortcode. The chatbot widget will render properly regardless of your theme or page builder.

Does JakBot slow down my website?

No. JakBot is designed for performance. Chat assets (CSS and JavaScript) are only loaded on pages where the chatbot shortcode is present. Embedding search results and API responses are cached using WordPress transients to minimize redundant API calls. The cosine similarity calculations run server-side in PHP and are fast enough that no pre-filtering is needed, even with large content libraries.

Technical Requirements

Is JakBot secure?

Yes. JakBot follows WordPress security best practices throughout:

Nonce verification — Every AJAX request is verified with a WordPress nonce to prevent cross-site request forgery.

Prepared statements — All database queries use $wpdb->prepare() to prevent SQL injection.

Capability checks — Admin-only features require the manage_options capability.

Input sanitization and output escaping — All user input is sanitized and all output is escaped using WordPress functions.

API key encryption — Jay’s Post Amplifier encrypts all API keys with AES-256-CBC using WordPress salts.

SSRF protection — External link checking skips private/reserved IP ranges.

More in Technical Requirements