GitBook

An AI assistant for GitBook content — honestly

Most "GitBook chatbot" pages skip an inconvenient fact: GitBook cloud does not allow custom scripts. Here is what that means, and the setup that works anyway.

  • No script needed
  • About two minutes
  • One field
No snippet on this one

GitBook cloud does not allow third-party scripts on any plan, so no chat widget can run on the docs themselves. Your GitBook content crawls cleanly, so the assistant answers from it on the site you do control.

The route through your admin

  1. Knowledge
  2. Crawl site

The snippet lands in your GitBook site URL.

What works: index GitBook, answer everywhere you control

GitBook publishes server-rendered pages, so the crawler reads your spaces cleanly — headings, structure and all. Index the GitBook site as a source and run the assistant on the sites you do control: your marketing site, your app, your help centre.

GitBook crawls cleanly
Published spaces are complete HTML, so every page becomes answerable, with citations linking back into GitBook.
The widget lives on your site
Product pages, app shell, marketing site — anywhere you can paste two lines.
One bot, both bodies of knowledge
Crawl GitBook and your main site into the same assistant; answers cite whichever page holds the fact.
!

GitBook cloud does not allow third-party scripts on any plan, so no chat widget can run on the docs themselves. Your GitBook content crawls cleanly, so the assistant answers from it on the site you do control.

If the widget must live on the docs

That requires docs on a platform that allows scripts. Docusaurus, MkDocs and Mintlify all take the install in one file — a realistic migration only if you had other reasons to move. For most teams, answering GitBook questions from the main site is the shorter path.

Checking it actually worked

There is no snippet to verify here, so the check is on the knowledge instead: confirm the crawl found your pages, then test the boundary.

  1. 1Hard refresh the page — the launcher appears bottom-right.
  2. 2Ask it something your site answers, and check the reply cites a page.
  3. 3Ask it something your site does not cover, and check it declines.
  4. 4Open Conversations in the dashboard; both should be there.

On a different stack?

The snippet is the same everywhere. Only the place you paste it changes.

What GitBook users ask

Short answers. If yours is not here, the assistant on this page will try it — and tell you honestly if it cannot.

Can any chatbot vendor put a widget on GitBook cloud?

Not within GitBook's rules. Their documentation states custom code cannot be inserted into a site, and that integrations injecting JavaScript are not possible for third parties. Treat claims to the contrary as a red flag.

Does GitBook's own AI answer this need?

GitBook ships its own AI answers inside the docs. What it does not do is run on your other sites, capture leads, hand off to your team, or answer from sources beyond GitBook — that is the half Matter Chat covers.

Will answers still link readers into GitBook?

Yes — citations link to the GitBook page the answer came from, so the docs stay the destination.

From the blog

All posts

Answer honestly. Capture the rest.

Point Matter Chat at your site and see what it can — and can't — answer. It's honest about both.

Start free — chat in your site

No credit card. 2 minute setup.

Every answer cites the source it came from. When there isn't one, it says so — and hands the visitor to you.

Installs on the tools you already run.