> ## Documentation Index
> Fetch the complete documentation index at: https://help-center-starter-replace-template-content.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Search and navigation

> How search works on your Mintlify docs site and how to configure navigation.

Mintlify includes built-in search on every docs site. No external search provider or index configuration required.

## Reader search

Readers can search your docs by clicking the search bar or pressing `⌘K`. Search covers page titles, headings, and body content.

### AI search

On Growth and Enterprise plans, enable AI search in **Project Settings → Search**. AI search understands natural language questions — readers can ask "how do I do X?" and get a direct answer drawn from your docs, rather than a list of links.

### Search analytics

The **Analytics → Search** tab in your dashboard shows what readers are searching for, including queries that returned no results. Use the "no results" list to identify gaps in your documentation.

## Site navigation

Your docs site's navigation is defined in `docs.json`. The sidebar structure supports:

* **Groups** — Collapsible sections containing pages.
* **Tabs** — A top-level nav bar for switching between major sections.
* **Anchors** — Persistent links to external URLs or specific pages, always visible in the sidebar.

### Tips for good navigation

* Keep group names short and action-oriented ("Get started", "Configure", "Reference").
* Limit nesting to 2-3 levels — deeper hierarchies are hard to scan.
* Use anchors for frequently accessed external links like your API reference or changelog.

## Editor navigation

In the web editor, the sidebar on the left shows all pages in your docs site. You can drag pages to reorder them, create new pages with the `+` button, and rename pages by clicking on their name.

<Note>
  Navigation order in the web editor reflects the order in `docs.json`. If you reorder pages in `docs.json` directly via Git, the change will appear in the editor after the next sync.
</Note>