Back to GrowthDex
Growth idea action plan

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.

rare tacticmid budget

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.

Company 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 and metric

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.

Source discovered: May 29, 2026

SEODocsProductsite architectureself-serve onboardingai discoverydocs strategy
GrowthDex operator note

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.

Founder checklist

  1. Read GitBook Docs: AI search and identify what is directly supported.
  2. Choose one channel context: SEO, Docs, Product.
  3. Define the test around 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..
  4. Set an owner, evidence window, and stop condition before launch.

Explore the context

Advisory bridge

Apply this with an operator

Turn isolated search tactics into a crawlable visibility system tied to demand and proof.

Work with Ian