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.
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.
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
- Define one narrow startup segment where single gitbook site sections for cross-docs search can create a measurable lift.
- Turn the tactic into one offer, page, campaign, or workflow for the SEO and Docs channel.
- Use the evidence from gitbook.com to set the first version of the message, format, and audience.
- Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
- 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.
Source: GitBook Docs: AI search (gitbook.com)
GrowthDex source hub: GitBook Docs: AI search
Last checked: 2026-05-29
Adjacent tactics in the same lane
If this page is close to your problem, these tactic pages usually belong in the same working set.
- Enriched company-page programmatic SEO 2 shared channels
- Interactive competitor demo pages 2 shared channels
- Checkout-first Core Web Vitals rehab 2 shared channels
- Exact-intent free tool one-pager 2 shared channels
Related GrowthDex essays
- The docs site should answer like one product technical seo, docs strategy, brand trust
Read GrowthDex essays
The Blog turns real growth tactics into plain-English case studies by niche, channel, and buying situation.
Why this is worth your time
GrowthDex starts with tactics that founders, marketers, and product teams have actually tried. Each essay turns the evidence into a practical move you can test without pretending one case study is a guarantee.
Ian Goh has helped grow consumer platforms across Southeast Asia, India, and MENA. His work includes scaling Tiki to 100M+ users, doubling BIGO's MENA revenue in 7 months, and increasing OYO's direct booking share across 6 Southeast Asian markets.
- Helped scale Tiki to 100M+ users.
- Doubled BIGO's MENA revenue in 7 months.
- Raised OYO's direct booking share by 50% across 6 Southeast Asian markets.
Want help turning this into a growth system?
If you want someone to pressure-test this against your real market, Ian works with founders on growth, market entry, and operator-led distribution.
Work with Ian on growth advisory