# 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.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/single-gitbook-site-sections-for-cross-docs-search/
- Source: [gitbook.com](https://gitbook.com/docs/publishing-documentation/ai-search)
- GrowthDex source hub: [GitBook Docs: AI search](/sources/gitbook-docs-ai-search-gitbook-com/)
- Last checked: 2026-05-29
- Rarity: rare
- Budget: mid
- Channels: SEO, Docs, Product
- Stages: site architecture, self-serve onboarding, ai discovery, docs strategy


## Why this can grow

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.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. For SEO and AI search, I care less about clever keyword tricks and more about clarity. A buyer, crawler, or answer engine should quickly understand who this is for, why it works, what proof backs it, and what page deserves to be cited. For activation, the useful question is not whether users liked the page. It is whether they got to the first meaningful win faster. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where single gitbook site sections for cross-docs search can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the SEO and Docs channel.
3. Use the evidence from gitbook.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## 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.

## Adjacent tactics in the same lane

- [Enriched company-page programmatic SEO](/growth-ideas/enriched-company-page-programmatic-seo/) - 2 shared channels
- [Interactive competitor demo pages](/growth-ideas/interactive-competitor-demo-pages/) - 2 shared channels
- [Checkout-first Core Web Vitals rehab](/growth-ideas/checkout-first-core-web-vitals-rehab/) - 2 shared channels
- [Exact-intent free tool one-pager](/growth-ideas/exact-intent-free-tool-one-pager/) - 2 shared channels

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The docs site should answer like one product](/blog/the-docs-site-should-answer-like-one-product/) - technical seo, docs strategy, brand trust

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.