Proofsource and GitBook: docs pages added the safe way
Connect GitBook with a personal access token and every AI visibility fix you approve can become a page in the space published on your website's domain, added through a GitBook change request. Drafts wait for review in GitBook, approved fixes merge, and Proofsource then measures whether ChatGPT, Perplexity, Gemini and others start naming and citing you.
| Destination | Status | |
|---|---|---|
 GitBook (docs.driffle.ai) | Connected | Publish |
 Zendesk Guide | Suggested | Add |
 GitHub pull request | Suggested | Add |
Proofsource and GitBook, in short
The facts, ready to quote.
- Stage
- Preview: open on Pro plans and above, badge shown in the app
- Connects with
- A GitBook personal access token
- Access it needs
- Edit access to the space published on your website's domain
- Where it shows
- Fixes, under Publish to, and the Integrations directory
- Undo
- Removes the page through another change request
- Review
- Each page arrives as a change request your team can read before it merges
Preview Preview means the publisher is open to Pro plans and above and shows a Preview badge in the app while we widen what it can publish. Approved fixes publish for real; nothing on your site changes until you say yes.
Why we love GitBook
In the makers' own words, from their own pages. Proofsource builds on it, never around it.
Docs that stay accurate for people and AI
GitBook is built so documentation stays right, scanning for stale content and flagging it for review, with an AI Assistant that lets readers ask the docs questions directly.
From gitbook.comChanges that work like pull requests
Change requests and Git Sync give docs the same branch, review and merge flow developers already trust, with two way sync to GitHub or GitLab.
From gitbook.comDocs that bring teams real traffic
More than 30,000 teams publish their documentation on GitBook, and its customer stories include a documented 2.8x rise in organic search traffic.
From gitbook.comHow Proofsource uses GitBook
Adds approved AI visibility fixes as GitBook pages through a change request, checks they are live, and can undo them.
- Know
Find the question your docs never answer
Proofsource sees an AI engine recommend a competitor for a how-to or integration question, because your docs have no page for it.
- Act
Draft the page that wins it
The draft is built from the pages AI already cites for that question, in your voice, with a direct first answer.
- Ship
Add it through a change request
Proofsource opens a change request with the new page. A draft stays open for review in GitBook; a fix you approved to go live is merged, and Proofsource checks the public page.
- Prove
Check whether AI noticed
The same questions are asked again on day 7, 14 and 28 to show whether the engines now name and cite you.
Set up GitBook in 4 steps
Create a personal access token
In GitBook open Settings, Developer settings and create a personal access token.
Pick GitBook in Integrations
Choose the brand and paste the token. Proofsource finds the space published on your website's domain.
Override only if you need to
Optionally paste a space ID (the part after /s/ in the space's address) and the address where the docs are published.
Approve your first fix
Open a drafted fix, choose GitBook under Publish to and preview it. A draft sits as an open change request; approving it to go live merges it. Undo removes the page through another change request.
| Page | Change request | AI now names you |
|---|---|---|
| API quickstart | Merged Oct 28 | ChatGPTClaude |
| Webhooks guide | Merged Oct 21 | Gemini |
 Zapier setup | Open for review | – |
What you unlock with GitBook
Change request first
Every page arrives as a GitBook change request, so your team can review before anything merges.
Grounded drafts
Pages written from the sources AI already trusts for each lost question.
One-click publishing
Approved fixes go live in your docs without copy and paste.
Live check
Proofsource confirms the page is public on your docs address before it counts.
Undo
Remove the page through another change request, from the same screen.
Before and after
See whether AI started naming you after each docs page went live.
Google AI OverviewsGoogle AI Mode
Questions about Proofsource and GitBook
What does Proofsource change in GitBook?
Only your docs space. Proofsource adds one page through a change request, merged only when you approved the fix to go live; a draft stays an open change request for review. It does not edit your existing pages, structure or settings.
How do I disconnect GitBook?
In Proofsource, open Integrations, pick GitBook and remove the connection. You can also delete the personal access token in GitBook's Developer settings, which cuts access at once. Pages already merged stay unless you undo them first.
What does Preview mean for the GitBook integration?
It is open to Pro plans and above and fully publishes, with a Preview badge while we widen what it can publish. Every page still needs your approval first, and each one can be undone.
How do I know a GitBook page helped my AI visibility?
Proofsource asks the same buyer questions again on day 7, 14 and 28 after the page went live and shows, engine by engine, whether AI now names or cites you.
Which AI engines does Proofsource check?
Up to 10 depending on your plan: ChatGPT, Perplexity, Claude, Google AI Overviews, Google AI Mode, Gemini, Microsoft Copilot, Grok, DeepSeek and Meta AI. The free scan and trial run four.
What access does Proofsource need in GitBook?
A personal access token from Settings, Developer settings, for someone who can edit the space. Proofsource uses it to open change requests, merge approved ones, check the published page and undo it.
Pairs well with GitBook
Put GitBook to work for your AI visibility.
Scan your brand, connect GitBook, and see what AI says about you on up to 10 engines.
Google AI OverviewsGoogle AI Mode