# Fern search scope by product before cross-doc noise

> Scope docs search to the reader's current product or version before one broad index starts answering the wrong product's questions.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/fern-search-scope-by-product-before-cross-doc-noise/
- Source: [buildwithfern.com](https://buildwithfern.com/learn/docs/customization/search)
- GrowthDex source hub: [Fern Docs: Search configuration](/sources/fern-docs-search-configuration-buildwithfern-com/)
- Last checked: 2026-06-08T10:06:43.000Z
- Rarity: rare
- Budget: low
- Channels: API docs, Conversion, Developer Tools
- Stages: docs search, product fit, versioning, information retrieval, developer trust


## Why this can grow

Multi-product docs often become less trustworthy as they grow because search pulls in adjacent but irrelevant answers. Fern's search configuration is unusually direct about that failure mode. It gives teams a softer ranking boost or a stricter default filter tied to the current product or version. That matters because the reader is usually not searching for everything your company ships. They are searching for the answer that fits the page they are already on.

## 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. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. 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 fern search scope by product before cross-doc noise can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the API docs and Conversion channel.
3. Use the evidence from buildwithfern.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

Fern's `settings.search` options can prioritize the current product in ranking or filter results to the current product by default while still allowing users to broaden the search later.

## Adjacent tactics in the same lane

- [Fern API catalog before agent scrape guesswork](/growth-ideas/fern-api-catalog-before-agent-scrape-guesswork/) - 2 shared channels
- [Fern API key injection before auth copy-paste](/growth-ideas/fern-api-key-injection-before-auth-copy-paste/) - 2 shared channels

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The docs path should stay readable to bots and buyers](/blog/the-docs-path-should-stay-readable-to-bots-and-buyers/) - documentation, API docs, AI visibility

## Advisory

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