Docs from GitHub. For humans and AI agents.

Frequently asked questions

• I don't even have documentation — can I still use Docsbook?Absolutely. Connect your GitHub repo — even just a README — and Docsbook turns it into a full site in under a minute. No writing required to get started. And if you want professional, branded docs written from scratch, Docsbook skills let an AI agent generate, structure, and publish production-ready documentation in one prompt.
• GitHub works fine — why do I need a separate site?GitHub README is not indexed by Google the same way a custom domain is. You lose organic traffic every day. Plus: no analytics, worse mobile UX, no AI search, and no branding. Docsbook gives you all of that in 5 seconds — plus SEO, GEO, and AEO markup so your docs appear in Google AI Overviews, Perplexity, and ChatGPT Search results.
• What is SEO / GEO / AEO and why does it matter for docs?Classic SEO puts your docs in Google. GEO (Generative Engine Optimization) puts them in AI answers — Perplexity citations, ChatGPT Search, Google AI Overviews. AEO (Answer Engine Optimization) adds structured markup so voice assistants and featured snippets pull directly from your content. Docsbook generates all three automatically: TL;DR blocks, FAQPage / HowTo JSON-LD, dateModified, author markup, and speakable selectors. One toggle in the dashboard — no manual work.
• Can my users interact with docs through AI?Yes. Every Docsbook site has an optional AI chat trained on your documentation content — users ask questions and get precise answers instantly, without reading through pages. It supports 15 languages, streams responses in real time, and you can use your own OpenAI / Anthropic / Gemini API key. Result: fewer support tickets, faster onboarding, higher conversion.
• What can I manage through the MCP server as an admin?Everything except writing the Markdown itself. The Docsbook MCP server exposes ~40 tools: full workspace setup, branding, custom domain, SEO/GEO/AEO settings, AI chat configuration, translation management, webhook subscriptions, and analytics queries. You can configure an AI agent once and it will autonomously monitor user journeys, track failed searches, collect negative feedback, and alert you via webhooks — all without opening a dashboard.
• Can an AI agent set up and maintain docs completely autonomously?Yes — that's the point. One prompt to Claude Code (or any MCP-compatible agent): create workspace, write docs using Docsbook skills, set branding, enable SEO + GEO, configure AI chat, turn on translation for target markets, set up webhooks for quality monitoring. The agent does all of it. You review the result. Ongoing maintenance — stale content alerts, unanswered questions, traffic spikes — can be delegated to the same agent.
• What are Docsbook skills?Skills are AI agent instructions (SKILL.md files) for documentation tasks: audit structure, write missing sections, check SEO, enable translations, track analytics gaps. Install them locally with 'npx docs-skills install' or let any MCP-connected agent discover and use them at runtime via find_skill(). 25 skills across 5 categories: analysis, creation, publishing, automation, observability.
• What if Docsbook shuts down — will I lose my docs?No. Your Markdown files always stay on GitHub. You can export everything at any time. No lock-in, no proprietary format.
• Isn't Docusaurus / GitBook free? Why pay for Docsbook?Docusaurus is free but takes 2–3 days to set up, configure, and maintain — and has no AI, no analytics, no MCP. GitBook charges $8+/month per editor with no AI translations or MCP. Docsbook is free to start, $150 one-time for PRO, or $59/month for PRO+ — and zero maintenance time.
• Do I need to configure CI/CD or GitHub Actions?Not at all. Connect your GitHub account once and docs sync automatically on every push to main — no pipelines, no config files.
• Is it a subscription?PRO is a one-time payment for life — pay once, own it forever. PRO+ is $59/month with higher AI/translation limits, white-label, and full MCP analytics access.