How to add an AI chatbot to your website

Adding the Allinaa assistant to a website is one line of code: a script tag your setup wizard gives you, pasted once so it loads on every page. It contains no password or secret, so it is safe to e-mail to a developer. The platform guides below follow each builder's own help pages, and say so when a platform's page could not be cited.

The idea: one snippet, every page

Your cabinet shows a short script tag with your assistant's id. Paste it where your platform lets you add code to every page, usually just before the closing body tag or in a footer or head code box, then publish. The chat button appears in the corner of each page that loads it. Keep it off pages that show customer data, such as member areas; the widget skips addresses with private segments like /account/ or /login/, but reads any other page it is loaded on.

Pick your platform

Thirty-one guides in five groups, the same groups as the "Where to paste it" tabs in your cabinet. Where a platform's own help page describes the route, the guide follows it and links to it; where only vendor guides describe it, the guide says so and sends you to the platform's help for the exact menu.

Website builders

• Wix: Settings, Custom Code, all pages, Body - end; and which Wix plans allow it.
• Squarespace: Code Injection, Footer, and the plans that include it.
• GoDaddy Website Builder: an HTML section per page, as GoDaddy's help describes it.
• Webflow: Site settings, Custom code, Footer code, and the publish step people forget.
• Tilda: the head code setting for the whole site, or the T123 block for one page.
• Duda: hand the code to your agency, or the site-wide head HTML area.
• Weebly: the footer code box in the SEO settings; what is confirmed and what is not.
• Hostinger Website Builder: More, Integrations, Custom code, then update the site.
• Framer: Site settings, Custom code, end of body, then publish.
• Carrd: the Embed element, on Pro Standard or higher.
• Jimdo: Creator's head code area on paid plans; the hosted chat page for the no-code builder.
• Strikingly: the custom code box in the site settings, per vendor guides.
• Zoho Sites: the header and footer code setting, or a code snippet element per page.
• WordPress.com: the plans that allow plugins, then the ready-made plugin or WPCode.

E-commerce

• Shopify: the theme's layout file, after duplicating the theme, and what happens on checkout pages.
• BigCommerce: Storefront, Script Manager, a footer script on your storefront pages.
• Square Online: an Embed code section per page, on the Plus or Premium plan.
• PrestaShop: the theme's footer template or a module, then the cache.
• OpenCart: the footer template of your version, or an extension.
• Magento / Adobe Commerce: the design configuration's HTML head field, or a module.

CMS

• WordPress: upload the plugin your cabinet generates, or paste the line into the free WPCode plugin.
• Joomla: the template's index.php or an extension, then the cache.
• Drupal: a theme template, or a small module with hook_page_attachments.
• Ghost: Settings, Code injection, Site footer.
• HubSpot CMS: the settings icon, then Content, then Pages, Site footer HTML.

Developers

• Hand-coded HTML website: just before the closing body tag, then clear caches.
• React / Next.js: one tag in the HTML shell or the root layout; no npm package.
• GitHub Pages and static sites: the base layout, commit, push.

Other

• Google Tag Manager: a Custom HTML tag on DOM Ready, and why the site check can't see it.
• Google Sites: code goes in a per-page embed, so the hosted chat page instead.
• Blogger: a gadget in the layout, or the theme's HTML.

No code box at all? The hosted chat page

A site that cannot take a script, such as Google Sites or a builder plan without a code setting, can still offer the assistant: every bot has a hosted chat page at bot.allinaa.com/chat/ followed by its bot id, a full-page chat you link from a button or a menu item. On a Google Site it cannot be placed inside a page with Insert, Embed: Google's guidance is that an embedded service must permit embedding on googleusercontent.com, which the chat page does not. On your own website a frame works only from the website address saved in your Allinaa account, and only over https. The Google Sites guide explains the route.

Let your developer do it

• Hand the installation to your web developer: the cabinet e-mails the code and the guides to whoever runs your site.

Check the installation, then fix what's wrong

"Check my site" in your cabinet reads your homepage and up to two linked pages, respecting robots.txt, and reports whether the code is there. The cabinet also notices the widget when a visitor loads a page. If the button doesn't appear, the cause is almost always a platform rule rather than the code:

• Chatbot not showing on your website? What to check: unpublished changes, plan restrictions, theme updates, caching and checkout pages, in that order.

Before installing, prepare the knowledge: the launch checklist lists what to check before visitors see the assistant.