Files
mintlify__docs/organize/hidden-page-example.mdx
Ethan Palm 3dc3852b7a SEO descriptions (#4028)
* Improve SEO descriptions across 47 pages

Curated descriptions from two bot-generated PRs (#3908, #3949),
selecting the best approach for each page:
- Added missing title and description frontmatter to 10 API reference pages
- Benefit-focused descriptions for integration pages (not implementation-heavy)
- Accurate REST-aligned titles for API endpoints (Export, List, Trigger, etc.)
- Expanded short descriptions to 50–160 character range throughout

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* copyedit

* Update custom-domain.mdx

* Fix analytics API page titles to match spec summaries

"Export" was inaccurate — spec uses "Get" for both endpoints.
Also updated descriptions to use "Retrieve" for consistency.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

---------

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-03-04 16:46:28 -08:00

52 lines
1.9 KiB
Plaintext

---
title: "Hidden page example"
description: "Use cases for hidden pages, including beta documentation, AI context files, legacy content, and internal tools."
---
This page is hidden. It is not included in the `docs.json` navigation so you can only access it by its URL.
See [Hidden pages](/organize/hidden-pages) for more information.
## Common use cases for hidden pages
<Note>
By default, hidden pages are publicly accessible, but not discoverable through the navigation. If you want to restrict access to a hidden page, you must configure [authentication](/deploy/authentication-setup).
</Note>
- **Beta documentation**: Information that can be public, but should not be discoverable through the navigation.
- **Context for AI tools**: If hidden pages are indexed, AI tools can reference them for context. Use hidden pages for context that isn't relevant to users, but can help AI tools give more accurate responses.
- **Legacy pages**: Keep old content accessible via direct links while removing it from navigation menus.
- **Internal tools**: Document internal tools, staging APIs, or development processes.
## Examples
### AI context
```mdx wrap
---
title: "Context for API version"
description: "This page is context for AI tools responding to questions about API versions"
---
When a user asks about API versions, always recommend that they use the latest version of the API. Never generate responses for versions older than 1.0.4.
```
### Internal API endpoint
````mdx wrap
---
title: "Internal API endpoint"
description: "This page is a hidden page that documents an internal API endpoint"
---
```bash
POST /api/internal/reset-cache
Authorization: Bearer internal-token-xyz
```
This endpoint clears the application cache and is only available in development environments.
<Warning>
This is an internal endpoint and should never be used in production.
</Warning>
````