FlowSearch
Start free trial
Docs/Search Quality

Search Quality

Make your public content easier for FlowSearch to crawl, rank, summarize, and keep fresh.

What makes a page searchable?

FlowSearch works best when important information is present in server-rendered HTML and written in language visitors actually use. Search can retrieve content that exists on the page; it cannot invent product details, pricing rules, integration steps, or policies that are missing from your website.

High-impact page improvements

  • Use descriptive page titles that include the main topic, such as API Keys, Pricing, or Webflow Installation.
  • Add clear meta descriptions. They help result snippets and give the crawler concise page context.
  • Structure content with one visible h1 and useful h2/h3 sections.
  • Put answers in text, not only images, accordions rendered after login, videos, or canvas elements.
  • Use visitor language in addition to internal product names. If people search "API token", mention how it relates to a FlowSearch Search Key.

Sitemap coverage

A sitemap helps FlowSearch discover public pages consistently. Make sure important docs, pricing pages, feature pages, and help articles are included in /sitemap.xml and linked from public navigation.

Pages can still be crawled through internal links, but sitemap coverage makes the crawl more predictable, especially after a content expansion or site migration.

Exclude low-value pages

Not every page should be searchable. Exclude duplicate landing variants, thin campaign pages, private app routes, checkout pages, dashboards, API endpoints, and pages that should not appear in visitor-facing search results.

Use analytics to improve relevance

Review popular queries and zero-result searches regularly. A zero-result search might mean the page is missing, the topic uses different wording, the sitemap does not include the page, or the page needs a fresh crawl after publishing.

Content review checklist

  • Every important page has a clear title and meta description.
  • Important answers are visible as text in public HTML.
  • Docs and knowledge-base pages are linked from public navigation or the docs index.
  • Sitemap includes public docs, product pages, pricing, and support articles.
  • Excluded pages are intentional and documented.
  • Fresh crawls run after major content changes.

Next steps