Yablonsky AI Chatbots includes a native WordPress adapter that connects WordPress sites to the canonical Yablonsky AI Chatbots runtime.
It connects a WordPress website to the canonical Yablonsky AI Chatbots runtime while WordPress keeps only local integration settings, page eligibility and safe loading. AI conversations, intelligence, security and conversation continuity remain on Yablonsky AI.
Current version: v0.1.4
Developed and maintained by Yablonsky.io.
Product page: Yablonsky AI Chatbots
Yablonsky AI workspace: ai.yablonsky.io
Use this stable link on your website or documentation when you want visitors to download the latest published WordPress package:
Current version-specific installer:
Latest release page:
https://github.com/Alex-Yablonsky/yablonsky-ai-chatbots/releases/latest
Use the installable release ZIP above for WordPress. GitHub's generic Code → Download ZIP archive is a source-code archive and should not be treated as the canonical WordPress installer.
Before installing the WordPress adapter, make sure you have:
- a Yablonsky AI account;
- an AI Chatbot created in Yablonsky AI;
- the public Chatbot ID for that chatbot;
- your website origin allowed by the chatbot security configuration when origin approval is required;
- administrator access to your WordPress website.
The WordPress plugin does not require a private API key.
The value entered into the plugin is the chatbot's public UUID, called the Chatbot ID in this guide. It is a public integration identifier, not a bearer token, API secret or session credential.
Open:
https://ai.yablonsky.io/signup
Create your account with your first name, last name, email address and password, then complete the registration flow.
If you already have an account, sign in at:
You can also start from the public Yablonsky AI website:
AI Chatbots availability depends on the capabilities included in your active Yablonsky AI plan.
After signing in:
- Open AI Chatbots: https://ai.yablonsky.io/app/secure-chatbots
- Click Add new.
- Enter the AI Chatbot name.
- Click Create.
- Open the chatbot.
- Configure the sections you need, including:
- General
- Agent
- Train
- Content
- Launcher Studio
- Security
- Save your changes.
Your AI Chatbot can then be prepared for the WordPress website where it will be used.
Open the chatbot's Security section and make sure the website where the chatbot will be embedded is allowed by the chatbot's current security/origin policy.
For this WordPress adapter, the browser origin is the actual WordPress website origin, for example:
https://example.com
Do not weaken origin restrictions globally just to make the widget load. Use the intended website origin.
Open the chatbot and select Deploy.
The Install section shows the canonical embed snippet.
Example:
<script>
(function(w,d,i,b,n){if(!w[n]||w[n]("getState")!=="initialized"){var q=function(){(q.q=q.q||[]).push(arguments)};w[n]=new Proxy(q,{get:function(t,p){if(p==="q")return t.q;return function(){t.apply(null,[p].concat(Array.from(arguments)))}}})}const l=function(){const script=d.createElement("script");script.src=new URL("/e/yablonsky/secure-chatbots/sdk.js?v=0.1.66",b).toString();script.type="text/javascript";script.dataset.id=i;script.dataset.base=b;d.body.appendChild(script)};d.readyState==="complete"?l():w.addEventListener("load",l)})
(window,document,"XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX","https://ai.yablonsky.io","chat");
</script>The value in this position:
XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
is your Chatbot ID.
You can also see the same UUID in the chatbot URL, for example:
https://ai.yablonsky.io/app/secure-chatbots/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX/deploy
Copy only the UUID into the WordPress plugin's Chatbot ID field.
Do not paste the complete <script> snippet into the WordPress settings.
If you were looking for a "plugin key", this Chatbot ID is the value the WordPress adapter needs. It is intentionally public and is not a private API key.
- Download the current installable ZIP from the Download section above.
- In WordPress Admin, open Plugins → Add New → Upload Plugin.
- Upload the installable ZIP.
- Install and activate Yablonsky AI Chatbots.
- Open Settings → AI Chatbots.
Version 0.1.4 adopts the canonical WordPress.org packaging identity yablonsky-ai-chatbots. Existing 0.1.3 and earlier installations used the historical folder yablonsky-secure-chatbots.
Leave the historical package installed while activating 0.1.4. The canonical plugin uses a collision-free PHP bootstrap, migrates yablonsky_secure_chatbots_settings to yablonsky_ai_chatbots_settings, and silently deactivates the historical site-level predecessor during activation. The historical package remains installed and its existing option is mirrored for rollback until you complete production acceptance. Only delete the historical package after the canonical plugin has passed live runtime and continuity regression checks.
In Settings → AI Chatbots:
- Enable the adapter when you are ready to publish the chatbot.
- Keep the canonical SDK URL configured as:
https://ai.yablonsky.io/e/yablonsky/secure-chatbots/sdk.js - Paste your public Chatbot ID.
- Configure page exclusions if the chatbot should not appear on specific WordPress pages.
- Keep the consent UI bridge enabled when your site uses compatible consent UI events and you want the chatbot to avoid overlapping the consent interface.
- Save settings.
The adapter allows the canonical SDK to determine the current WordPress parent_origin through the normal runtime contract. It does not create a second authentication or conversation layer.
After saving settings, open the public website in a real browser.
Verify that:
- the AI Chatbot launcher appears on an eligible page;
- the launcher opens correctly;
- only one chatbot iframe is present;
- a message can be sent;
- an AI response is received;
- excluded pages do not load the chatbot;
- the website remains usable if the Yablonsky AI service is temporarily unavailable.
For production acceptance, test at least Chrome, Firefox and Safari. Mobile Safari should also be tested for customer-facing websites.
This WordPress adapter connects to Yablonsky AI at https://ai.yablonsky.io/ to load the canonical chatbot runtime and process conversations. When enabled, the visitor's browser sends the configured public Chatbot ID, current website origin, chatbot messages and technical session metadata required for security and conversation continuity to Yablonsky AI.
The plugin does not store AI provider API keys, private chatbot secrets, bearer tokens or session credentials in WordPress.
- Terms of Service: https://ai.yablonsky.io/policies/terms
- Privacy Policy: https://yablonsky.io/privacy-policy
WordPress
→ native settings and page eligibility
→ same-origin adapter asset transport
→ canonical Yablonsky AI Chatbots SDK on AI.Yablonsky.io
→ Core-owned conversation, intelligence and security runtime
This package is not a chatbot backend and does not copy the canonical SDK.
The adapter places the chatbot. Yablonsky AI owns the chatbot runtime, conversation intelligence, session security and conversation continuity.
- Embed an AI Chatbot on eligible WordPress pages.
- Use a public chatbot reference without storing AI provider secrets in WordPress.
- Whole-site enablement with explicit page exclusions.
- Desktop and mobile-friendly canonical widget delivery.
- Same-origin local adapter asset transport without requiring the raw plugin directory to be publicly reachable.
- Single canonical SDK ownership and iframe adoption.
- Consent UI coexistence bridge for
consent:open,consent:closedandconsent:changed. - Graceful failure if the canonical AI service is unavailable.
- Customer-defined chatbot identity and multilingual conversations provided by the Yablonsky AI Chatbots runtime.
The adapter stores only public integration and presentation settings:
- enabled/disabled state;
- canonical SDK URL;
- public AI Chatbot UUID;
- page exclusions;
- consent UI bridge toggle;
- accessible AI Chatbot frame title.
It does not store:
- AI provider API keys;
- chatbot secrets;
- preview credentials;
- session credentials;
- cross-domain identity credentials;
- conversation databases.
The current adapter uses whole-site placement on eligible public WordPress pages.
Add explicit WordPress page IDs to the exclusion list when the AI Chatbot must not load on a page.
Feeds, robots, trackbacks, 404 responses and WordPress admin surfaces fail closed and do not load the adapter.
The package-local loader and presentation stylesheet are exposed through a same-origin WordPress front-controller endpoint.
The runtime does not require public access to the raw /wp-content/plugins/... directory and does not hardcode security or obfuscation plugin routes.
This design preserves compatibility with WordPress installations that hide or rewrite plugin paths.
The canonical SDK is served from:
https://ai.yablonsky.io/e/yablonsky/secure-chatbots/sdk.js
The WordPress adapter does not fork, copy or bundle the canonical SDK.
The version query shown in a Deploy snippet may change over time as the canonical service evolves. The WordPress plugin should continue to use the approved canonical SDK endpoint configured in its settings.
The WordPress adapter does not store AI provider keys, preview credentials, session credentials or continuity credentials.
Protected conversation/session logic remains server-side on Yablonsky AI.
The canonical service remains responsible for:
- chatbot publication state;
- exact-origin allowlisting;
- bootstrap/session scope;
- object ownership;
- conversation continuity;
- abuse controls;
- revocation.
See docs/SECURITY.md for details.
Conversation continuity is owned by Yablonsky AI Core, not by the WordPress adapter.
A new website origin receives its own origin-scoped authorization/session. The adapter does not transfer session or bearer credentials between origins and does not use browser storage to create cross-domain identity.
The practical rule is simple:
Adapter places the chatbot.
Yablonsky AI owns continuity.
The host page must permit the canonical Yablonsky AI origin where required by its Content Security Policy.
At minimum, deployments using a restrictive CSP should review:
script-src/script-src-elem;connect-src;frame-src;style-srcif the site uses strict nonce/hash-only style rules.
For the current canonical service, https://ai.yablonsky.io must be permitted where the SDK/frame/runtime requires it.
Do not use wildcard CSP exceptions as a shortcut when an exact origin is sufficient.
The optional consent bridge is presentation-only.
It may react to:
consent:open
consent:closed
consent:changed
The consent bridge does not provide authentication, session authorization or legal consent decisions, and it is not a Google Tag Manager dependency.
When a compatible consent UI emits consent:open, the adopted AI Chatbot frame can be hidden to avoid UI overlap; consent:closed restores it.
- WordPress 6.0+
- PHP 7.4+
- Canonical Yablonsky AI Chatbots SDK at the configured approved host
The canonical WordPress.org packaging identity is now:
- plugin slug / installed directory:
yablonsky-ai-chatbots; - main plugin file:
yablonsky-ai-chatbots.php; - text domain:
yablonsky-ai-chatbots.
Runtime compatibility identifiers that are not part of the public package identity remain intentionally unchanged:
- canonical settings option
yablonsky_ai_chatbots_settingswith a compatibility mirror to the historical option; - existing PHP class names;
- stable internal settings page slug and script/style handles;
- canonical SDK path:
/e/yablonsky/secure-chatbots/sdk.js.
This keeps the WordPress.org package clean without changing the Core/session/continuity contract.
Product information:
https://yablonsky.io/ai-chatbots/
Yablonsky.io:
Yablonsky AI workspace:
Developed and maintained by Yablonsky.io.
For Yablonsky AI Chatbots, WordPress integration and related product information, visit Yablonsky AI Chatbots.
AI workspace and account access: ai.yablonsky.io
Yablonsky AI Chatbots is an independent open-source project and is not affiliated with, endorsed by, or sponsored by the WordPress Foundation, Automattic, or related trademark owners.
WordPress and related product names are trademarks of their respective owners. They are used here only to describe compatibility.
Yablonsky AI Chatbots is a hosted Yablonsky.io product. Availability of AI models, tools, quotas and plan capabilities may change over time according to the active service configuration and subscription.
GPL-2.0-or-later. See LICENSE.