Free tool
Get a free AI chat widget for your website
Discovery moved to chat: your audience asks an assistant about you before they ever browse your site. Give them somewhere to ask you instead — an AI chat widget that answers from your own pages, links every source, and shows the plans you actually sell. It's a free AI chatbot you can set up in minutes, with one script tag and no account.
- Your site
- Configure
- Try it
- Go live
How it works
People used to find a publication by searching, landing on a page and clicking around. Increasingly they just ask — and an assistant answers for you, from whatever it scraped, with no link back. Your site, meanwhile, is still a set of static pages waiting to be browsed. This closes that gap on your own domain, in four steps.
- 1
Tell it your website
Enter your domain. The assistant reads your sitemap to learn which pages exist — no crawl, no upload, nothing to install yet.
- 2
Brand it and connect your products
Pick your colour, name the assistant, write the greeting, and connect your catalog — your Pelcro site ID, or your own product endpoint. This is also where you decide whether interactions go to your Google Analytics, and where you leave your work email so we can send you the snippet.
- 3
Try it on your own site
The real widget opens on this page, branded and pointed at your domain. Ask it what a reader would ask, and ask it what you offer, then watch it answer from your pages with a source link.
- 4
Paste one script tag
Copy the snippet and paste it before the closing body tag on your site. The launcher appears in the bottom-right corner. There is nothing else to install and nothing to maintain.
What you get
Answers from your pages, with the source attached
It reads your own site to answer — not a general chatbot with your logo on it. Every reply links the page it came from, so a reader can check it and you can see what it used. If the answer isn't on your site, it says so instead of inventing one.
Your real products, with images and prices
Connect your catalog and “what do you offer?” is answered with your actual products — name, image and price on every card, and a tap through to the plans inside each one. Prices come from your billing system, so a rate rise can't leave a stale number in the chat.
A way in, not just an answer
When someone asks to sign in or join, the assistant shows a Log in or Create an account button that opens the flow you already run. On a Pelcro site those are your own URL triggers, so there is nothing to configure.
Every interaction in your own Google Analytics
If GA is already on your page, the widget fires ai_chat_opened, ai_chat_message_sent and ai_chat_action_clicked as counts — no question text leaves the browser. You measure it where you already report.
What it can't do
- It only knows what is on your public pages. Anything behind your paywall or login is invisible to it, and so are your CMS, your CRM and your subscriber records.
- It reads at most two pages per question, so a question whose answer is spread across a dozen articles will get a partial answer and a link.
- It can't take an action on a reader's account — it can't subscribe them, change a plan, or cancel. It can only point them at the page that does.
- It answers from what your sitemap lists. If a page isn't in your sitemap, the assistant can't reach it. Sites without a sitemap get answers from the homepage only.
- Answers are generated, so they can be wrong. The source link under every answer is there so a reader can check.
The last three are what a billing system fixes. See what it looks like connected to Pelcro.
AI for publishers
Readers hit a paywall with questions your FAQ page never gets asked: what do I get for $9.95, is the archive included, why am I being asked to pay when I already subscribe, how do I cancel. Those questions decide whether someone subscribes or leaves, and a search box can't answer any of them.
The assistant answers from your own pages, so the wording is yours and every reply links the article or policy it came from. Connect your catalog and it shows your actual products — print plus digital, the annual saving, the free trial — with prices read from your billing system rather than a page that went stale two rate rises ago. When a reader says they already pay, it offers a Log inbutton; when they're ready to start, a Create an account button, both opening the subscription flow you already run.
Every interaction lands in your own Google Analytics, so you can finally see how many readers had a question your pages weren't answering. It is usually more than anyone expects. See how this fits alongside newspaper subscription management software.
AI for associations
Members ask different questions. When does my membership expire, is the member rate on the annual conference included, how do I add a colleague to our group membership, can I renew without calling the office. Most of it is answered somewhere on your site — usually three clicks deep, in a PDF nobody finds.
The assistant reads those pages and answers in plain language, with a link back so a member can check. Connect your catalog and it lays out membership tiers side by side, shows what each one includes, and surfaces the renewal price without anyone digging. When the answer is “you need to be signed in”, it offers a Log inbutton; when it's “you're not a member yet”, a Join button — both opening the flow you already run.
For a small team that is the difference between answering the same renewal question forty times a month and answering the ones that actually need a person. It pairs naturally with association management software.
Free Chatbase alternative
Most people shopping for a chatbot builder land on Chatbase or something like it. Those tools are general by design: you feed them documents, you get a bot. This one is deliberately narrower.
It is built for sites that sell subscriptions or memberships. It reads your pages through your sitemap instead of asking you to upload anything. It reads your products and prices from your billing system, so a price it quotes is the price you charge. And it can hand a visitor a Log in or Join button that opens the flow you already run, rather than telling them to go and find it. There is no account to create, nothing to train, and no cost.
The trade is honest: if you want a general assistant over arbitrary documents, a general builder is the better fit. If your questions are about paywalls, plans, renewals and access, this is shaped for exactly that.
Frequently asked questions
How do I add an AI chatbot to my website?
Enter your domain above, pick a colour and a name, connect your products if you sell subscriptions, then copy the one-line script tag and paste it before the closing body tag. The launcher appears in the bottom-right corner of every page that includes the tag. No account, no plugin, and nothing to deploy.
How do I embed AI chat on my website?
Embedding is a single script tag. Paste it once into your global template or footer include so it loads everywhere, rather than adding it page by page. The widget renders inside a shadow DOM at a fixed position, so it inherits none of your CSS, leaks none of its own, and causes no layout shift.
Can I add an AI chatbot to my website for free?
Yes. This one is free to use, with no account to create and no card required. You leave a work email to see it running on your own site, and that is the only thing we ask for. What costs money is what sits behind it: taking a payment, changing a plan or cancelling a subscription needs a billing system.
How do I put an AI chatbot on a website?
The same script tag works anywhere you can edit HTML — a custom site, a CMS template, or a tag manager as a custom HTML tag firing on all pages. Because the configuration is encoded in the tag itself, there is no dashboard to log into afterwards; to change a setting you run the setup again and replace the snippet.
Where do the answers come from?
From your own pages, fetched live at the moment someone asks. The assistant is given an index of your site built from your sitemap.xml, and is restricted to fetching pages on your domain — it cannot read any other site. Nothing about your site is stored on our servers between questions.
How does it know my products and prices?
You connect them during setup. If you run Pelcro, you enter your site ID and we read your products, plans, prices and product images from your site settings — along with your company name and your login and join links. If you don't, point us at any public endpoint that returns your products as JSON.
What data do you collect from my visitors?
Counts, not content. We record the domain the question came from, an anonymous per-tab session id, timings and token counts — never the text of a question or an answer. The widget sets no cookies; its session id lives in sessionStorage and disappears when the tab closes.
What is an MCP server, and why does it matter for a publisher?
MCP is the emerging standard for connecting an AI assistant to a real system rather than to a web page. Instead of scraping whatever it can find about you, an assistant asks your endpoint and gets structured answers — what you publish, what a subscription costs, what a signed-in reader already has.
What comes next
Your voice shouldn't stop at your website
A widget on your own pages only helps the people already there. The readers you're losing are the ones who never arrive — the ones asking an assistant, in another app, on another channel. Reaching them means your content and your subscriptions have to be something an assistant can actually talk to.
That connection has a name now: an MCP server. It's the standard way an AI assistant plugs into a real system — not by scraping your pages, but by asking it questions and getting structured answers back. One endpoint, and the assistants your audience already uses can describe what you publish, what a subscription costs, and what a particular reader has.
Pelcro publishes one by default for the sites it runs, and we can help you design and connect your own — so the same voice you just put on your homepage can show up wherever your audience is asking.