Single GitBook site sections for cross-docs search
Keep related product, developer, and support docs as sections on one GitBook site when you want one search surface instead of several isolated docs islands.
Why this can grow a startup
Many teams split product docs, API docs, and help content across separate sites because the org chart is split the same way. The reader does not care. GitBook is explicit that AI search does not work across different docs sites, while multi-space search works when the content lives as sections within the same site. If the user has one question that spans onboarding, API setup, and billing, a unified search surface usually does more for adoption than a cleaner internal ownership map.
Source-backed example
GitBook says AI search does not work across individual published spaces on different docs sites, and that multi-space search is available when published spaces live as site sections within the same site.
Source-reported evidence
Source: GitBook Docs: AI search
GitBook AI search works within one docs site, while multi-space search only spans published spaces that are grouped as site sections on that same site.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
Source discovered: May 29, 2026
When to use it
Use this when SEO, Docs, Product is relevant to site architecture, self-serve onboarding, ai discovery and you can run a bounded test with a mid budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to SEO and Docs, using evidence from GitBook Docs: AI search as context—not as a promised result.
- Record a baseline for: Share of target users completing the product's first-value action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Turn isolated search tactics into a crawlable visibility system tied to demand and proof.