title	Docsbook documentation: publish, get cited, measure
description	Find the Docsbook guide for the job you are doing — publishing from GitHub, getting cited by AI assistants, measuring readers, translating, or automating.

Docsbook documentation: publish, get cited, measure

Docsbook publishes Markdown from a GitHub repository, a website scan, or a written brief as a documentation site people and AI assistants can read. This index is organised by the job you are doing, not by the menu the admin panel uses — pick the job, then the guide.

Every capability page here follows one rule: it states what you get, how it is built in enough mechanical detail to predict the output, the evidence with a link to a primary source, and what is not proven. If we cannot source a claim, the page says so rather than dropping it — see how we prove it.

New to Docsbook? Read the overview first, then publish a site.

Start here

• Overview — What Docsbook does with your repository, and what it costs {compass}
• Quick start — Publish a documentation site, from source to public URL {rocket}
• Concepts — Workspace, project balance, indexing and the other terms {box}
• Use cases — The jobs teams hire documentation for {target}
• How we prove it — The evidence rule every capability page here follows {scale}

Publish your documentation

• Create your first site — Step-by-step, no prior GitHub experience assumed {file-plus}
• Manage an existing site — Settings, reindexing, and who can read the site {folder-cog}
• Connect a GitHub repository — An "Edit on GitHub" link on every page, and where repository sync is set up {git-branch}
• Choose what gets indexed — Which folders and files become pages {settings-2}
• Point your own domain at it — One CNAME, SSL provisioned automatically {globe}
• Restrict who can read it — Shared password, or your own SSO identity provider {lock}
• Brand it — Name, icon, accent colour, fonts {palette}
• Set the theme and layout — Light, dark and system defaults {sun-moon}

Get found by search engines

• SEO overview — What Docsbook emits for search engines without you configuring anything {search}
• How the head is built — Title, description, canonical, hreflang, cards, robots and sitemap, in resolution order {file-code}
• Indexing — How a change reaches the index, and what actually gates that {refresh-cw}

Get quoted by AI assistants

• GEO overview — What Docsbook adds so Perplexity, ChatGPT Search and AI Overviews can quote you {sparkles}
• Citation signals — The rules that make a passage quotable, and what has been measured not to work {quote}
• llms.txt — A plain-text index of your docs for AI clients, and who really reads it {file-text}

Win the answer box

• AEO overview — What an answer engine needs from a page, and what Docsbook emits {message-square-quote}
• Structured answers — The JSON-LD Docsbook emits, what triggers it, and what Google still shows {braces}
• Content rules — The rules Docsbook writes by, each with what it does to an answering agent {list-checks}

Make your docs agent-ready

• Agent-ready overview — Documentation an agent can navigate and act on, not just read {bot}
• Docs skills — SKILL.md files that teach any agent documentation work {graduation-cap}
• MCP server — The tools that let an agent read and edit your docs {plug}
• Source of truth — The document graph an agent navigates {network}
• MCP security — Auth model, what a read-only token cannot do, and what is not offered yet {shield}

Answer readers with AI chat

• AI chat — An assistant that answers from your indexed pages {message-circle}
• Answer quality — The retrieval and grounding pipeline, and what happens when nothing matches {target}
• Full-text search — A search box in the header, the sidebar, or both {search}
• Connected sources — Repositories and sites your agent may read as fact {link}
• Chat hooks — Run your own code before and after the model {webhook}
• Page feedback — Thumbs up and down, per page {thumbs-up}

Measure what your docs earn

• Tracking overview — What Docsbook measures and where it comes from {bar-chart-3}
• How measurement works — Visitor identity, bot filtering, read time, and what is never collected {microscope}
• Goals and funnels — Whether readers reach the page that sells {git-fork}
• Events — AI opens, code copies, link clicks, goals {mouse-pointer-click}
• Read time — How long readers spend on each page {timer}
• Countries and languages — Where readers are and what they read in {map}
• AI usage and cost — What AI work drew on the project balance {wallet}

Reach readers in other languages

• Translation settings — Enable languages and place the switcher {sliders-horizontal}
• AI translations — How automatic translation works, and how to correct it {languages}
• Translation quality — What is protected from translation, how drift is caught, and the hreflang side {badge-check}

Reference

• Pricing — What is metered, and what a project balance pays for {credit-card}
• FAQ — Cost, cancellation, sync, privacy and data ownership {help-circle}
• Reference index — Every reference page in one list {book-open}
• MCP tools reference — Every tool, its parameters and its price class {list}
• REST API — Call your docs chat from your own backend {code}
• Webhooks — Event catalogue, payload schemas, signature format {bell}
• Content widgets — Cards, accordions, steps and CTA blocks in Markdown {layout-grid}
• Changelog — What shipped, and what each change was meant to buy {history}
• Blog — Longer pieces on AI search, docs SEO, analytics and platform comparisons {newspaper}

Support

Email support@docsbook.io, or ask in the Docsbook Discord.

Publish your first site

Paste a repository, a website URL, or a sentence about your product. The draft is generated before you sign in.

Start free — no credit card