Place a chatbot anywhere on your site with one WordPress shortcode
SleekAI adds an AI chatbot for Chatbot With Shortcode Embed to your WordPress site. It answers from the content you choose, such as posts, pages, custom post types, post meta, taxonomies and user data, with your own OpenAI, Anthropic, Google, or OpenRouter key.
Editors should not need a developer to add a chatbot
Many chatbot tools require a snippet of JavaScript in the site header to load anywhere, plus theme edits to position the widget. That works for a single floating bubble in the corner but breaks down the moment you want a bot inside a product page, embedded in a doc, or scoped to a single landing page.
SleekAI solves this with a native WordPress shortcode.
SleekAI was built for the way WordPress editors actually work. Shortcodes plug into the Gutenberg editor, the classic editor, page builders, widgets, and template parts. Anywhere you can put content, you can put a chatbot.
Features
One shortcode, anywhere
The shortcode renders inline wherever WordPress shortcodes work. Posts, pages, sidebars, widget areas, custom fields, and most page builders. Editors take control of placement without needing a developer to touch templates.
Answers from your data
Map post titles, content, post meta, taxonomies or a WP_Query into the instruction, and the bot answers from what your site actually publishes.
Your model, your key
Use OpenAI, Anthropic, Google, OpenRouter or a compatible endpoint with your own API key. The provider bills you directly.
Where it helps
Inline docs assistants
Drop a bot inside a long documentation page so readers can ask follow up questions in context.
Product page concierge
Embed a bot below the product gallery scoped to that product. Shoppers ask about fit, compatibility, or shipping without leaving the page, and the bot reads live product data to answer accurately.
Landing page demos
Launch pages get a live demo bot inline so prospects can try the experience before signing up.
How it works
Build the bot once
One source of truth, many placements.
Map your data
Choose the posts, fields, taxonomies or users the bot should know and reference them in the instruction.
Set display conditions
Decide which pages, post types, roles or logged-in states show the chatbot.
Manage from the editor
Whoever edits content controls where the bot appears. No developer ticket, no theme deploy, no global widget settings to navigate. Moving the bot to a different page is a paste and save, and the bot inherits that page’s context automatically.
Why inline shortcodes scale better than global widgets
Global floating chat widgets had their moment, but they are a poor fit for most modern content sites. A single bubble in the corner cannot tell whether the visitor is on a pricing page or a help doc, cannot adopt different tones for different audiences, and cannot be placed contextually next to the content that triggered the question.
The result is a bot that feels generic everywhere and excellent nowhere. Inline placement changes the dynamics. A bot embedded next to a pricing table can be tuned for sales.
A bot inline with a troubleshooting doc can be tuned for support. A bot in a launch page can be tuned for demos. Editors gain control too. A chatbot becomes a content element, not a site wide overlay.
This shift compounds over time. Campaigns iterate faster. Content teams experiment with placement without code reviews. The result is a chatbot strategy that grows with content velocity instead of being capped at one global widget that does everything badly.
Frequently asked questions
How is the shortcode different from a floating widget?
Floating widgets are global and live in a corner of every page. Shortcodes are inline and live exactly where you paste them. Most sites use both: a global floating bot for general questions plus contextual inline bots for specific articles, products, or landing pages.
Does the shortcode work with page builders like Elementor or Beaver Builder?
Yes. Page builders almost universally support a shortcode widget. Drag the shortcode block, paste [sleek_ai_chatbot id=42], and the bot renders.
Can I have multiple chatbots on the same page?
Yes. A docs page could embed a ‘how do I use this’ bot inline and still load the global support bot in the corner. They run independently with separate conversation history.
Will the shortcode play nicely with caching plugins?
Yes. Variables are resolved at message time, not at page render, so cached HTML never embeds stale chat content.
Does the bot inherit the page context automatically?
It does. The shortcode runs inside the current post, so the bot has access to the post ID, post type, taxonomies, and any mapped variables tied to that post.
What if I want to remove a bot from one page only?
Remove the shortcode from that page. There is no central placement registry, no exclusion list, no theme template edit. Inline placement means inline control.
Which AI providers does it support?
OpenAI, Anthropic, Google and OpenRouter, plus custom OpenAI-compatible endpoints. You bring your own API key and the provider bills you directly.
Where does the chatbot get its answers?
From the WordPress data you map into its instruction: post titles and content, post meta, ACF and Meta Box fields, taxonomies, terms, users and user meta, or a WP_Query. Values resolve on every request.
Related pages
Pricing
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
…or get the Bundle Deal
and save €250
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
SleekAI
SleekByte
SleekMotion
SleekPixel
SleekView
SleekRank
SleekTrack