AI chatbot for Smush: read image optimization state and rules in plain English
SleekAI reads Smush's stored configuration and per-image optimization records directly from WordPress, so admins know what is compressed, what is queued, and what is excluded. Bring your own OpenAI, Anthropic, Google, or OpenRouter key.
♾️ Lifetime License available
A chatbot that knows your Smush optimization state
Smush stores per-image optimization data as postmeta on each attachment, records the bulk queue in WordPress options, and keeps settings for WebP, lazyload, CDN, and resize behaviour in a top-level options bag. SleekAI can be wired to read all of that as data sources, so the bot's system message exposes how many images are optimized, how many are pending, which directories are scanned, and whether WebP delivery is on. Variables resolve at request time, so a fresh bulk run shows up in the next answer.
That makes the Smush dashboard a conversation. An admin asks how many images are still unoptimized, the bot reads the queue state and answers with a number and a percentage. A developer asks whether WebP is being served from the CDN or generated locally, the bot reads the option and answers without anyone opening the Bulk Smush tab. Lazyload exclusions, max image dimensions, ShortPixel-style resize rules, all of it is available for a one-line conversational read.
Display conditions keep the Smush bot scoped to administrators on wp-admin URLs, so the public chatbot you run for visitors has no path to optimization data. Conversation logging records every question and answer in WordPress with model name, token usage, and page URL, so the team can audit what was asked and refine the system prompt over time.
Workflow
How SleekAI plugs into Smush
Map Smush data
Lock to admins
wp-admin URL patterns. The image bot only appears for administrators; the public bot has no overlap.
Bring your own key
Review the logs
Try it now
A typical Smush conversation
Comparison
Generic chatbot vs SleekAI for Smush
Generic chatbot
- Doesn't know how many images are optimized
- Can't see queue depth or recent runs
- No view of WebP, AVIF, or CDN delivery state
- Treats every image question as generic advice
- Can't be scoped to admins on wp-admin URLs
SleekAI chatbot
- Reads Smush attachment meta and queue state
- Reports optimized count, pending count, and savings
- Surfaces WebP and lazyload exclusions
- Display conditions lock the bot to admins
- Logs every conversation inside WordPress
Features
What SleekAI gives you for Smush
Queue-aware answers
The system message includes counts of optimized and pending images, total savings, and the most recent bulk run, so the bot answers with the real state instead of a guess at progress.
WebP and AVIF status
Ask whether WebP or AVIF delivery is on, how the rewrites are configured, and whether the CDN is in front. The bot reads the options and reports without anyone opening the Smush UI.
Folder and class rules
See which folders are excluded from optimization and which CSS classes are excluded from lazyload, in one short answer rather than two tabs of settings.
Use cases
Where admins use SleekAI for Smush
Bulk run check-ins
During a long bulk optimization, ask the bot for progress, pending count, and ETA. The bot reads the queue state and answers without forcing a page reload of the Smush dashboard.
Pre-launch image audits
Before a campaign, ask the bot to confirm WebP delivery is active, lazyload covers the new hero, and excluded folders still match the import workflow.
Onboarding new editors
Let new editors check whether their freshly uploaded images are already optimized. The bot answers from the live attachment meta without giving them full plugin access.
The bigger picture
Why a plain-English layer over Smush pays off
Smush has one job, make images smaller without making them ugly, but in practice it raises a steady drumbeat of operational questions. How many of the new uploads are still unoptimized, is the bulk run done, is WebP delivery actually firing, are the originals folder and the import folder excluded the way the workflow expects, how much have we saved this month. The data is all there, scattered across attachment postmeta, a few options, and the Smush dashboard.
A generic chatbot trained on the open web cannot answer any of it, because the answer is in this site's records. SleekAI exposes the real data to the model under display conditions that keep the bot scoped to administrators. The result is shorter check-ins, faster confirmation that a fresh upload is already compressed, and a clean log of the questions the team keeps asking.
Smush keeps doing the compression and the WebP work; SleekAI is the conversational read layer that turns its state into answers the team can act on in seconds.
Questions
Common questions about SleekAI for Smush
Yes. Smush stores per-attachment optimization status in postmeta and tracks bulk queues in WordPress options. SleekAI can be configured to read those as data sources, so the bot's system message exposes optimized and pending counts, savings, and the most recent run as named variables the model uses at request time.
By default, SleekAI is read-only against Smush. It reports state. If you want write actions, you can wire Smush's bulk start helper into a SleekAI tool with a tight permission check, but most teams kick off bulk runs from the Smush UI and treat the chatbot as a read layer over the resulting state.
Not unless you configure it that way. Display conditions on user role, capability, and URL pattern keep the Smush bot scoped to administrators inside wp-admin. Any public chatbot you run on the same site is a separate bot under multibot, with its own data sources and no access to Smush data.
Yes. The bot reads whatever Smush has stored, whether you are on the free plan or Smush Pro with the CDN add-on. It can describe whether the Smush CDN is active, which formats are served, and whether per-image optimization happens locally or via the API, as long as those values are exposed as data sources.
It can describe whether WebP is enabled, which delivery method is configured (rewrite, picture tag, or CDN), and whether the test image probe is green. It cannot inspect a specific HTTP response from a visitor's browser, but the config-level summary usually points to whether the rewrite is missing or the CDN config has drifted.
No. The Smush dashboard remains the right place for kicking off bulk runs, reviewing per-attachment savings, and managing the Pro account. SleekAI answers a different question, what is happening right now, in plain English. Many teams keep both and link from the bot's answers to the relevant Smush page.
Only to whoever the chatbot's display conditions allow. If the bot is scoped to administrators, only logged-in admins see optimization counts and folder exclusions. The public bot you run on the same site is a separate chatbot with its own data sources and never reads Smush postmeta.
Yes. Each site in the network has its own SleekAI chatbots and its own data sources. Smush configuration is per-site, so the bot for each site reads its own attachment data. Network admins can run a higher-scope bot on the network admin if they wire it to the right values.
Pricing
More than 1000+
happy customers
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.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...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
-
SleekRank
-
SleekView
€749
Continue to checkout