Skip to main content
Cortexvia
Website

Add an AI Chatbot to Your Website

Train a chatbot on your pages, documents, and YouTube links, then add it to your site with one embed snippet. Pick your platform below for the exact place that snippet goes.

Priced in your local currency
No plugin, no app store review

Pick your platform

The snippet is the same everywhere. What changes is where your platform lets you paste it.

01WordPressWPCode, footer.php, or a block-theme footer pattern.
02Shopifytheme.liquid, before the closing body tag.
03WixCustom Code, added to Body end. Needs a published site.
04SquarespaceCode Injection, Footer. Needs a Business plan or higher.
05WebflowSite Settings, Custom Code, Footer Code, then republish.
06ReactMount in an effect, unmount in the cleanup.
07Next.jsnext/script with afterInteractive, App or Pages Router.
08Plain HTMLPaste before the closing body tag. The baseline.

How embedding works

Four steps, and only the third one differs between platforms.

01

Add your sources

Upload documents, add website pages, or paste YouTube links. The chatbot answers from those, and says so when a question falls outside them.

02

Copy one snippet

Once the first source has processed, the Chatbots area gives you an embed snippet that already carries your chatbot key.

03

Paste it before the body tag

One stylesheet and one script from the CDN, then a mount call. Where that goes is the only thing that differs between platforms.

04

Publish and test

Reload a public page and ask a question your source answers. Nothing to deploy, no DNS change, no server configuration.

The snippet

Two CDN files, a container, and a mount call carrying your chatbot key.

html
<link rel="stylesheet" href="https://cdn.cortexvia.in/chatbotsdk-web.css" />
<script src="https://cdn.cortexvia.in/chatbotsdk-web.iife.js"></script>
<div id="cv-chat"></div>
<script>
  window.ChatbotSDK.mount("#cv-chat", {
    chatbotKey: "ctx-cb-xxxxxxxxxxxxxxxx",
    config: {
      mode: "chatbot",
      position: "bottom-right"
    }
  });
</script>

Replace the placeholder key with the one from your Chatbots area. Everything else can stay exactly as it is.

  • Load the two CDN files once per page, not once per widget
  • The container can be any element; the snippet uses a div with id cv-chat
  • mode chatbot is the floating launcher, mode chat is an inline panel

Every platform

The parts of the answer that do not change with your stack.

01

Any platform that allows a script tag

The widget is a CDN script rather than a per-platform plugin, so there is no app store listing to wait on and nothing to keep updated.

02

Loads after your page is interactive

The loader is deferred, so it does not block your theme, your content, or the assets your Core Web Vitals depend on.

03

Mounts into its own container

The widget renders inside the element you point it at, so it does not inherit or fight the rest of your CSS.

04

Local pricing, free tier to test

Plans are priced in your local currency, and the free tier is enough to put one chatbot on a live page.

Questions

What people ask before putting a chatbot on a live site.

Get started

Start on the free tier with a document or two, copy the snippet, and paste it into your platform.

Start with one page and one document. Put it on a live page before paying for anything, then move up a plan once the answers hold.