For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Slack communityLog inBook a demo
  • Getting Started
    • Overview
    • Quickstart
    • Customer Showcase
  • Writing Content
    • Markdown
    • Visual Editor
    • Reusable Markdown
    • Custom React Components
      • What is docs.yml
      • Project Structure
      • Frontmatter
      • Search
      • User Feedback
      • Custom CSS & JS
    • Changelog
LogoLogo
Slack communityLog inBook a demo
On this page
  • How search works
  • Using an alternative search
Customization

Search

Was this page helpful?
Previous

Collecting feedback and suggestions from users

Next
Built with

Fern uses Algolia DocSearch to power search for your documentation. DocSearch is designed specifically for documentation sites to help users quickly find what they need.

How search works

DocSearch scans your Fern site’s content and builds an index to generate search results. It includes built-in filters that let users refine their searches by content type:

  • Versions: For sites with separate documentation for different API versions.
  • Endpoints: Filters results by API reference documentation.
  • Guides: Filters results by non-API reference documentation.
  • Changelog: Filters results by changelog updates.

If you are using the AI Search feature, the search box also functions as your site’s chat window.

Note: If an article includes the nofollow or noindex frontmatter, it will not be indexed by Algolia DocSearch and won’t appear in search results.

Using an alternative search

You can override Fern’s search with your own solution. Here is an example of custom JavaScript a customer used to replace the default search with their own implementation and additional features. To learn more, see Custom JavaScript.