Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 17 additions & 1 deletion guides/hidden-pages.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -8,10 +8,18 @@

A page is hidden until you add it to a group, tab, or other navigation element in your `docs.json`.

<Warning>
**Hidden pages are publicly accessible!** While hidden pages don't appear in your site's navigation, they are still publicly accessible to anyone who has the direct URL. These pages are not password-protected or restricted in any way - they're simply not displayed in menus, sidebars, or other navigation elements. If you need true access control, use [Authentication](/settings/authentication-personalization/authentication) instead.
</Warning>

<Note>
Some navigation elements like sidebars, dropdowns, and tabs may shift or appear empty on hidden pages.
</Note>

## SEO and Search Indexing

Hidden pages can still be indexed by search engines and appear in search results unless you explicitly prevent this. By default, hidden pages may be excluded from indexing, but you can control this behavior:

If you want hidden pages to be indexed for SEO purposes and for their contents to appear when people search within your docs, add the following setting to your `docs.json`:

```
Expand All @@ -20,8 +28,16 @@
}
```

If you want to exclude a specific hidden page's content from search engine and internal search results, add `noindex: true` to the frontmatter of the page.

Check warning on line 31 in guides/hidden-pages.mdx

View check run for this annotation

Mintlify / Mintlify Validation - vale-spellcheck

guides/hidden-pages.mdx#L31

Did you really mean 'frontmatter'?

## When to Use Hidden Pages vs. Authentication

Hidden pages are different from authenticated or private pages:

- **Hidden pages**: Publicly accessible via direct URL, just not shown in navigation
- **Authenticated pages**: Require login credentials to access
- **Private pages**: Restricted to specific user groups

If you have pages that you want only specific groups of your own users to have access to, you can use the selective groups access available through [Personalization](/settings/authentication-personalization/personalization#showing-hiding-pages).

If you have pages that you want to maintain strict access control to, you can use [Authentication](/settings/authentication-personalization/authentication).
If you have pages that you want to maintain strict access control to, you can use [Authentication](/settings/authentication-personalization/authentication).
4 changes: 4 additions & 0 deletions navigation.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,10 @@ The [navigation](settings#param-navigation) property in [docs.json](settings) de

With proper navigation configuration, you can organize your content into a logical hierarchy that makes it easy for users to find exactly what they're looking for.

<Info>
**Hidden Pages**: You can create pages that don't appear in your navigation but are still accessible via direct URL. Simply create a page file without adding it to any navigation element in your `docs.json`. These hidden pages remain publicly accessible to anyone with the URL - they're just not displayed in menus or sidebars. Learn more about [hidden pages](/guides/hidden-pages).
</Info>

## Pages

Pages are the most fundamental navigation component.
Expand Down