# How to Add an AI Chatbot to Your Wix Site (2026) > A practical 2026 guide to adding a real AI support chatbot to a Wix site: why Wix's own AI Site Chat changed in March 2026, which plan you need for Custom Code, where to paste the embed snippet, the Wix-specific gotchas (Spaces app, December 2025 code-security changes, Stores and Bookings), and how to keep answers grounded and handed off cleanly. *By Mithun · Published July 7, 2026 · 12 min read* Category: SMB AI playbooks Tags: Wix, AI chatbot, Knowledge base, Web widget, Human handoff, Citations {/* Image note: Hero is a generated editorial flat-design illustration of a generic website-builder editor (grid canvas, drag handles, a floating widget panel) with an AI chat widget answering a visitor question, showing a source-citation chip and a human-handoff button. It deliberately avoids the Wix logo, wordmark, or brand colors, and any real site brand, for trademark safety. This is an evergreen how-to, not a comparison post, so no competitor screenshots are needed. */} Wix changed its own AI chat product in March 2026, and most "add a chatbot to Wix" guides haven't caught up. If you want a support agent that actually answers from your pages instead of just building them, here's what changed, which plan you need, and where the install trips people up. This guide covers what Wix's native AI chat now is (and isn't), the plan tier that decides whether Custom Code works at all, exactly where to paste an embed snippet, the Wix-specific gotchas — including a December 2025 security change that broke some existing embeds — and how to ground the agent in your own content with a clean handoff. The first half is tool-agnostic. The "Where Owlish fits" section near the end covers our product, because Owlish is ours. ## Wix's native AI chat changed in March 2026 — know which one you're looking at Wix has shipped AI chat features directly in its editor for a while, but the product changed shape recently. As of March 2026, **Wix AI Site Chat is no longer available to install on new sites** — it's been replaced by **Wix Smart Chat**, installed from the Wix App Market ([Wix Help Center: Wix AI Site Chat overview](https://support.wix.com/en/article/about-the-wix-ai-chat-assistant)). That matters for two reasons. First, if you're reading an older guide or forum post that references "AI Site Chat," it's describing a product Wix has since retired for new installs — verify current behavior in your own dashboard rather than trusting a screenshot from last year. Second, and more importantly: Wix's native chat is built for general visitor conversations inside the Wix ecosystem, not for a support agent that's grounded in your specific policies, ingests your PDFs, shows a citation trail back to the page it used, and hands off to a specific human on your team when it shouldn't guess. If that's what you need, you're adding a third-party tool on top of (or instead of) Wix's own chat — which is what the rest of this guide walks through. ## First, check whether your Wix plan can run Custom Code This is the step that decides whether a third-party chatbot works on Wix at all, and it's easy to get wrong because the *editor* behaves differently than the *published site*. The **iFrame Embed element** — the piece you'd use to drop in a widget — is available in the Wix Editor on every plan, including Domains and free sites, for the purposes of designing your page. But **Custom Code only takes effect on a published site with a paid plan**; on a free plan, code you add either won't run once published, or the page can't be published with a connected domain in the first place ([Wix Help Center: About embeds and codes on your site](https://support.wix.com/en/article/wix-editor-about-embeds-and-codes-on-your-site)). For any **Custom Element** specifically, Wix additionally requires a Premium plan, a connected domain, and no ads on the site ([Wix Help Center: Wix Editor elements and codes](https://support.wix.com/en/article/wix-editor-about-embeds-and-codes-on-your-site)). The practical rule: - **Any paid Wix plan** (Light and above) — Custom Code runs on your published site. The rest of this guide applies directly. - **Free plan** — you can build and preview the widget in the editor, but it won't function the way you need on a live, published site. Upgrade before you promise a chatbot to visitors. - **Studio Editor** — the newer Wix Studio product has its own equivalent embed and custom-code panels; the mechanics are the same idea, different menu labels. If you're not sure which plan you're on, check **Settings → Billing & Payments** in your Wix dashboard before you go further. The gap between "the widget loads in the editor" and "the widget loads for a real visitor" is the single most common reason a Wix chatbot install looks broken. ## Why a website-builder AI doesn't replace a grounded support agent Wix's editor-side AI is genuinely useful for *building* — generating copy, suggesting layout, writing alt text — and Smart Chat adds a conversational layer for visitors browsing your site. Neither is the same job as an agent that reads your shipping policy, your refund PDF, and your FAQ page, and answers "what are your shipping times?" with a link back to the exact page it used. That distinction matters for trust. A generic chat assistant that improvises an answer about your return window is a liability, not a feature — customers act on what it tells them. You want an agent whose answers are traceable to content *you* wrote and can point to, not a model's best guess dressed up as a confident reply. ## Step 1: Decide the bot's job before you touch any code Before installing anything, pull the last few hundred questions you've actually received — through your Wix site's contact form, Wix Chat/inbox, Wix Bookings messages, or your inbox — and group them by intent. You'll usually find a short list doing most of the volume: - shipping times, costs, and order status; - returns, exchanges, and refunds; - booking, rescheduling, and cancellation policy (if you use Wix Bookings); - product or service details (sizing, materials, what's included); - hours, location, and contact options. Rank these by **volume** and **risk**, and start the bot on the high-volume, low-risk ones. A bot that nails your top five repetitive questions and cleanly hands off everything else beats one that tries to answer everything and gets the important parts wrong. ## Step 2: Reconcile your pages so the bot has one clear answer An AI agent grounded in your content is only as good as the content. Wix sites built by hand over time tend to accumulate the same answer in a few slightly different places — a policy line in the footer, a different number on a product page, a stale note in an old blog post. When two pages disagree, the bot will sometimes cite the wrong one. Before launch, do a quick reconciliation pass: give each topic one canonical page, make sure that page is current and dated, and put exceptions ("final-sale items can't be returned") right next to the rule they modify rather than three sections away. This work pays off twice — the bot gets more accurate, and human visitors get clearer pages too. ## Step 3: Ground the agent in your Wix content With a modern AI support tool, this means pointing it at your published site so it can crawl your pages, plus adding anything your pages don't cover: - **Your Wix site** — most support tools discover pages via your sitemap or by following links, then extract the main content and strip navigation and footer boilerplate. Wix sites are heavily JavaScript-rendered; a capable crawler handles that automatically rather than needing a special static export. - **Files** — upload PDFs (size guides, care instructions, policy documents) and any other files that hold answers your pages don't. - **Short direct answers** — for the handful of questions where exact wording matters ("Do you ship internationally? Yes, to 30+ countries, calculated at checkout"), set those explicitly rather than hoping the model phrases it well on its own. The goal is that every answer traces back to a source you control. If a question isn't covered, you want the bot to say so and offer a human, not invent an answer. ## Step 4: Embed the widget through Custom Code Once your agent is configured, you'll have a small embed snippet — typically a single `