Skip to content
Open
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
50 changes: 30 additions & 20 deletions analytics/traffic.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -2,47 +2,57 @@
title: "Analyze documentation traffic"
sidebarTitle: "Traffic"
description: "Review traffic analytics to track visitors, page views, referrals, popular pages, and traffic from both human readers and AI agents."
keywords: ["analytics", "traffic", "page views", "visitors", "referrals", "agent views"]
keywords:
- "analytics"
- "traffic"
- "page views"
- "visitors"
- "referrals"
- "agent views"
---

<Note>
</Note>

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Empty Note callout on traffic page

Low Severity

An empty Note sits at the top of the traffic analytics page with no content, so it will render as a blank callout. The Spanish, French, and Chinese versions of this page do not include it.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 3eacd49. Configure here.


<Info>
Analytics require a [Pro or Enterprise plan](https://mintlify.com/pricing?ref=analytics).
</Info>

The **Traffic** view of the [analytics](https://app.mintlify.com/analytics) page displays total visitors, page views, assistant conversations, searches, and user feedback messages.

Review traffic analytics to:

- **Monitor traffic trends**: Observe changes in human and agent traffic after updates or new content to understand the impact of your changes.
- **Identify popular pages**: Use highly ranked pages to understand what content is most important to your users. Keep those pages up to date and comprehensive.
- **Track referral sources**: Understand where your users come from so you can optimize content for the right audience.
The **Traffic** view of the [analytics](https://app.mintlify.com/analytics) page shows visitors, page views, assistant conversations, searches, and feedback. Use it to monitor trends, identify popular pages, and track referral sources.

<Frame>
<img
src="/images/analytics/traffic-light.png"
alt="The Traffic view of the analytics page."
className="block dark:hidden"
src="/images/analytics/traffic-light.png"
/>

<img
src="/images/analytics/traffic-dark.png"
alt="The Traffic view of the analytics page."
className="hidden dark:block"
src="/images/analytics/traffic-dark.png"
/>
</Frame>

## Interpret agent views
## How Mintlify counts traffic

Mintlify identifies agent visitors by IP address and user agent. The agent visitor count approximates distinct sources of AI traffic rather than individual agent sessions or conversations. Multiple requests from the same IP address count as one visitor.
Mintlify classifies every request by user agent and counts only human and agent traffic toward visitor and page view totals. Search indexing crawlers, AI training crawlers, and other bots are excluded. See [Interpret traffic exports](/analytics/export#interpret-traffic-exports) for the full breakdown.

Check warning on line 38 in analytics/traffic.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

analytics/traffic.mdx#L38

In general, use active voice instead of passive voice ('are excluded').

<Note>
Agent traffic measurement expanded in June 2026. Before then, the analytics dashboard only captured a subset of agent traffic. Starting June 8, 2026, Mintlify recognizes a broader set of agent user agents, counts agent HTML page views alongside Markdown requests, and serves Markdown to more agents. As a result, agent views increased across most sites around that date. This reflects improved measurement and agent access, not a sudden change in traffic. When comparing agent views over time, account for this shift.

The size of the increase varies by site, since it depends on how much agent traffic each site receives. Sites that AI tools reference frequently show a larger increase than sites with less agent traffic.
In September 2026, visitor counts adopted the same crawler filtering as page views, lowering visitor totals across all date ranges. See [Why your visitor count dropped](/help-center/visitor-count-dropped-after-crawler-filtering).
</Note>

Use agent views to understand:
## Interpret agent views

Mintlify identifies agent visitors by IP address and user agent, approximating distinct sources of AI traffic rather than individual sessions. Use agent views to see which AI platforms access your docs and how usage changes over time.

The agent breakdown groups traffic by provider (ChatGPT, Claude, Cursor, and others), with three catch-all buckets:

- **AI agent distribution**: See which AI platforms access your docs to learn which tools your users prefer.
- **Integration opportunities**: Identify which AI platforms to prioritize for optimization and testing.
- **AI traffic patterns**: Monitor which agents are most active and how their usage changes over time.
- **HTTP clients**: Tools and libraries such as curl, wget, and Python HTTP clients.

Check warning on line 50 in analytics/traffic.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

analytics/traffic.mdx#L50

Use 'cURL' instead of 'curl'.

Check warning on line 50 in analytics/traffic.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

analytics/traffic.mdx#L50

Did you really mean 'wget'?
- **Browser**: Markdown requests made from a web browser.
- **Other**: Agent traffic that does not match a known provider or client.

Mintlify's own internal traffic (link checking, page revalidation) is excluded.

Check warning on line 54 in analytics/traffic.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

analytics/traffic.mdx#L54

In general, use active voice instead of passive voice ('is excluded').

<Note>
Agent traffic measurement expanded on June 8, 2026 to recognize more agent user agents and count agent HTML page views alongside Markdown requests. Agent views increased across most sites around that date, reflecting improved measurement rather than a traffic change. Account for this shift when comparing over time.
</Note>
3 changes: 2 additions & 1 deletion docs.json
Original file line number Diff line number Diff line change
Expand Up @@ -488,7 +488,8 @@
"help-center/preview-deployment-not-created-for-fork-branch",
"help-center/branch-missing-from-editor-branch-list",
"help-center/style-card-icons-with-custom-css",
"help-center/can-i-rename-my-deployment-or-organization"
"help-center/can-i-rename-my-deployment-or-organization",
"help-center/visitor-count-dropped-after-crawler-filtering"
]
}
]
Expand Down
3 changes: 2 additions & 1 deletion es.json
Original file line number Diff line number Diff line change
Expand Up @@ -465,7 +465,8 @@
"es/help-center/static-file-not-served",
"es/help-center/preview-deployment-not-created-for-fork-branch",
"es/help-center/style-card-icons-with-custom-css",
"es/help-center/can-i-rename-my-deployment-or-organization"
"es/help-center/can-i-rename-my-deployment-or-organization",
"es/help-center/visitor-count-dropped-after-crawler-filtering"
]
}
]
Expand Down
18 changes: 18 additions & 0 deletions es/analytics/traffic.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,16 @@ Revisa las analíticas de tráfico para:
/>
</Frame>

<div id="how-mintlify-counts-traffic">
## Cómo cuenta Mintlify el tráfico
</div>

Mintlify clasifica cada solicitud según el user agent y solo cuenta el tráfico humano y de agentes en los totales de visitantes y de vistas de página. El tráfico de rastreadores de indexación de búsqueda, rastreadores de entrenamiento de IA y otros bots se excluye de ambas métricas. Para ver el desglose de cada categoría de tráfico, consulta [Interpretar las exportaciones de tráfico](/es/analytics/export#interpret-traffic-exports).

<Note>
En septiembre de 2026, Mintlify actualizó los conteos de visitantes para usar el mismo filtrado de rastreadores que las vistas de página. Los totales de visitantes bajaron en la mayoría de los sitios, y el cambio se aplica a todos los rangos de fechas. Consulta [Por qué bajó tu conteo de visitantes tras el filtrado de rastreadores](/es/help-center/visitor-count-dropped-after-crawler-filtering).
</Note>

<div id="interpret-agent-views">
## Interpretar las vistas de agentes
</div>
Expand All @@ -48,3 +58,11 @@ Usa las vistas de agentes para comprender:
- **Distribución de agentes de IA**: Observa qué plataformas de IA acceden a tus docs para saber qué herramientas prefieren tus usuarios.
- **Oportunidades de integración**: Identifica qué plataformas de IA priorizar para la optimización y las pruebas.
- **Patrones de tráfico de IA**: Monitorea qué agentes son más activos y cómo cambia su uso a lo largo del tiempo.

El desglose de agentes agrupa el tráfico por proveedor, como ChatGPT, Claude y Cursor. Tres categorías capturan el resto del tráfico de agentes:

- **HTTP clients**: Solicitudes de herramientas y bibliotecas como curl, wget y clientes HTTP de Python.
- **Browser**: Solicitudes de Markdown realizadas desde un navegador web.
- **Other**: Tráfico de agentes que no coincide con un proveedor o cliente conocido.

Mintlify excluye su propio tráfico interno, como la verificación de enlaces y la revalidación de páginas, del desglose de agentes.
26 changes: 26 additions & 0 deletions es/help-center/visitor-count-dropped-after-crawler-filtering.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
---
title: "Por qué bajó tu conteo de visitantes tras el filtrado de rastreadores"
description: "Comprende por qué los totales de visitantes en las analíticas de Mintlify bajaron en septiembre de 2026, cuando el tráfico de rastreadores se excluyó de los conteos de visitantes."
keywords: ["visitor count dropped", "visitors lower than views", "more visitors than views", "crawler traffic", "bot filtering", "analytics visitors"]
---

En septiembre de 2026, Mintlify cambió la forma en que el panel de analíticas cuenta los visitantes únicos. Los totales de visitantes ahora excluyen el tráfico de rastreadores de indexación de búsqueda, rastreadores de entrenamiento de IA y otros bots, igualando el filtrado que ya se aplicaba a las vistas de página. Si tu conteo de visitantes bajó bruscamente, o los números históricos se ven más bajos que antes, este cambio es la causa más probable.

<div id="what-changed">
## Qué cambió
</div>

Antes de esta actualización, el tráfico de rastreadores se excluía de los conteos de vistas de página, pero no de los conteos de visitantes. Los rastreadores inflan los totales de visitantes mucho más que los de vistas porque no conservan cookies, por lo que Mintlify no puede reconocer solicitudes repetidas del mismo rastreador como un solo visitante. En sitios con mucho tráfico de rastreadores, esta inflación podía llevar el conteo de visitantes por encima del conteo de vistas de página, algo imposible con tráfico real de lectores.

Los conteos de visitantes ahora usan la misma clasificación de rastreadores que las vistas de página. Solo los lectores humanos y los agentes de IA cuentan en los totales de visitantes.

<div id="what-to-expect">
## Qué esperar
</div>

- Los totales de visitantes son más bajos en la mayoría de los sitios. Los sitios que reciben mucho tráfico de rastreadores muestran la mayor caída.
- El cambio se aplica a todos los rangos de fechas, incluidos los históricos, porque Mintlify clasifica el tráfico al calcular el informe y no al almacenar los eventos.
- Las vistas por visitante vuelven a una proporción plausible, con más vistas de página que visitantes.
- Los totales de visitantes agentes también pueden cambiar, porque la misma actualización refinó cómo se identifica el tráfico de agentes.

Para saber cómo clasifica Mintlify el tráfico y cómo interpretar las vistas de agentes, consulta [Analizar el tráfico de la documentación](/es/analytics/traffic).
3 changes: 2 additions & 1 deletion fr.json
Original file line number Diff line number Diff line change
Expand Up @@ -465,7 +465,8 @@
"fr/help-center/static-file-not-served",
"fr/help-center/preview-deployment-not-created-for-fork-branch",
"fr/help-center/style-card-icons-with-custom-css",
"fr/help-center/can-i-rename-my-deployment-or-organization"
"fr/help-center/can-i-rename-my-deployment-or-organization",
"fr/help-center/visitor-count-dropped-after-crawler-filtering"
]
}
]
Expand Down
18 changes: 18 additions & 0 deletions fr/analytics/traffic.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,16 @@ Consultez les analytics de trafic pour :
/>
</Frame>

<div id="how-mintlify-counts-traffic">
## Comment Mintlify comptabilise le trafic
</div>

Mintlify classe chaque requête selon son user agent et ne comptabilise que le trafic humain et le trafic des agents dans les totaux de visiteurs et de pages vues. Le trafic des robots d'indexation de recherche, des robots d'entraînement d'IA et des autres bots est exclu des deux métriques. Pour le détail de chaque catégorie de trafic, consultez [Interpréter les exports de trafic](/fr/analytics/export#interpret-traffic-exports).

<Note>
En septembre 2026, Mintlify a mis à jour le comptage des visiteurs pour utiliser le même filtrage des robots que les pages vues. Les totaux de visiteurs ont baissé sur la plupart des sites, et le changement s'applique à toutes les plages de dates. Consultez [Pourquoi votre nombre de visiteurs a baissé après le filtrage des robots](/fr/help-center/visitor-count-dropped-after-crawler-filtering).
</Note>

<div id="interpret-agent-views">
## Interpréter les vues des agents
</div>
Expand All @@ -48,3 +58,11 @@ Utilisez les vues des agents pour comprendre :
- **La distribution des agents IA** : Voyez quelles plateformes IA accèdent à vos docs pour savoir quels outils vos utilisateurs préfèrent.
- **Les opportunités d'intégration** : Identifiez les plateformes IA à prioriser pour l'optimisation et les tests.
- **Les schémas du trafic IA** : Surveillez quels agents sont les plus actifs et comment leur utilisation évolue dans le temps.

La répartition des agents regroupe le trafic par fournisseur, comme ChatGPT, Claude et Cursor. Trois catégories regroupent le reste du trafic des agents :

- **HTTP clients** : Requêtes provenant d'outils et de bibliothèques comme curl, wget et les clients HTTP Python.
- **Browser** : Requêtes Markdown effectuées depuis un navigateur web.
- **Other** : Trafic d'agents qui ne correspond à aucun fournisseur ou client connu.

Mintlify exclut son propre trafic interne, comme la vérification des liens et la revalidation des pages, de la répartition des agents.
26 changes: 26 additions & 0 deletions fr/help-center/visitor-count-dropped-after-crawler-filtering.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
---
title: "Pourquoi votre nombre de visiteurs a baissé après le filtrage des robots"
description: "Comprenez pourquoi les totaux de visiteurs dans les analytics Mintlify ont baissé en septembre 2026, lorsque le trafic des robots a été exclu du comptage des visiteurs."
keywords: ["visitor count dropped", "visitors lower than views", "more visitors than views", "crawler traffic", "bot filtering", "analytics visitors"]
---

En septembre 2026, Mintlify a changé la façon dont le tableau de bord analytics compte les visiteurs uniques. Les totaux de visiteurs excluent désormais le trafic des robots d'indexation de recherche, des robots d'entraînement d'IA et des autres bots, en appliquant le même filtrage que celui déjà utilisé pour les pages vues. Si votre nombre de visiteurs a chuté brusquement, ou si les chiffres historiques semblent plus bas qu'avant, ce changement en est la cause la plus probable.

<div id="what-changed">
## Ce qui a changé
</div>

Avant cette mise à jour, le trafic des robots était exclu du comptage des pages vues, mais pas du comptage des visiteurs. Les robots gonflent les totaux de visiteurs bien plus que ceux des vues, car ils ne conservent pas les cookies. Mintlify ne peut donc pas reconnaître les requêtes répétées d'un même robot comme un seul visiteur. Sur les sites avec un trafic de robots important, cette inflation pouvait faire passer le nombre de visiteurs au-dessus du nombre de pages vues, ce qui est impossible avec du trafic de lecteurs réels.

Le comptage des visiteurs utilise désormais la même classification des robots que les pages vues. Seuls les lecteurs humains et les agents IA comptent dans les totaux de visiteurs.

<div id="what-to-expect">
## À quoi s'attendre
</div>

- Les totaux de visiteurs sont plus bas sur la plupart des sites. Les sites recevant un trafic de robots important affichent la plus forte baisse.
- Le changement s'applique à toutes les plages de dates, y compris historiques, car Mintlify classe le trafic au moment de calculer le rapport et non au moment de stocker les événements.
- Le ratio de vues par visiteur redevient plausible, avec plus de pages vues que de visiteurs.
- Les totaux de visiteurs agents peuvent aussi évoluer, car la même mise à jour a affiné l'identification du trafic des agents.

Pour comprendre comment Mintlify classe le trafic et comment interpréter les vues des agents, consultez [Analyser le trafic de la documentation](/fr/analytics/traffic).
22 changes: 22 additions & 0 deletions help-center/visitor-count-dropped-after-crawler-filtering.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
---
title: "Why your visitor count dropped after crawler filtering"
description: "Understand why visitor totals in Mintlify analytics dropped in September 2026 after crawler traffic was excluded from visitor counts."

Check warning on line 3 in help-center/visitor-count-dropped-after-crawler-filtering.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

help-center/visitor-count-dropped-after-crawler-filtering.mdx#L3

In general, use active voice instead of passive voice ('was excluded').
keywords: ["visitor count dropped", "visitors lower than views", "more visitors than views", "crawler traffic", "bot filtering", "analytics visitors"]
---

In September 2026, Mintlify changed how the analytics dashboard counts unique visitors. Visitor totals now exclude traffic from search indexing crawlers, AI training crawlers, and other bots, matching the filtering that already applied to page views. If your visitor count dropped sharply, or historical numbers look lower than they did before, this change is the most likely cause.

## What changed

Before this update, crawler traffic was excluded from page view counts but not from visitor counts. Crawlers inflate visitor totals far more than view totals because they do not persist cookies, so Mintlify cannot recognize repeat requests from the same crawler as one visitor. On sites with heavy crawler traffic, this inflation could push the visitor count above the page view count, which is impossible for real reader traffic.

Check warning on line 11 in help-center/visitor-count-dropped-after-crawler-filtering.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

help-center/visitor-count-dropped-after-crawler-filtering.mdx#L11

In general, use active voice instead of passive voice ('was excluded').

Visitor counts now use the same crawler classification as page views. Only human readers and AI agents count toward visitor totals.

## What to expect

- Visitor totals are lower on most sites. Sites that receive heavy crawler traffic see the largest drop.
- The change applies to every date range, including historical ones, because Mintlify classifies traffic when it computes the report rather than when it stores events.
- Views per visitor returns to a plausible ratio, with more page views than visitors.
- Agent visitor totals can also shift, because the same update refined how agent traffic is identified.

Check warning on line 20 in help-center/visitor-count-dropped-after-crawler-filtering.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

help-center/visitor-count-dropped-after-crawler-filtering.mdx#L20

In general, use active voice instead of passive voice ('is identified').

For how Mintlify classifies traffic and how to interpret agent views, see [Analyze documentation traffic](/analytics/traffic).
3 changes: 2 additions & 1 deletion zh.json
Original file line number Diff line number Diff line change
Expand Up @@ -465,7 +465,8 @@
"zh/help-center/static-file-not-served",
"zh/help-center/preview-deployment-not-created-for-fork-branch",
"zh/help-center/style-card-icons-with-custom-css",
"zh/help-center/can-i-rename-my-deployment-or-organization"
"zh/help-center/can-i-rename-my-deployment-or-organization",
"zh/help-center/visitor-count-dropped-after-crawler-filtering"
]
}
]
Expand Down
18 changes: 18 additions & 0 deletions zh/analytics/traffic.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,16 @@ keywords: ["analytics", "traffic", "page views", "visitors", "referrals", "agent
/>
</Frame>

<div id="how-mintlify-counts-traffic">
## Mintlify 如何统计流量
</div>

Mintlify 根据 user agent 对每个请求进行分类,只有人类流量和 agent 流量会计入访客数和页面浏览量总数。搜索索引爬虫、AI 训练爬虫和其他 bot 的流量不计入这两项指标。有关各流量类别的详细说明,请参阅[解读流量导出](/zh/analytics/export#interpret-traffic-exports)。

<Note>
2026 年 9 月,Mintlify 更新了访客统计方式,使其采用与页面浏览量相同的爬虫过滤规则。大多数站点的访客总数因此下降,且该变更适用于所有日期范围。请参阅[为什么爬虫过滤后访客数下降了](/zh/help-center/visitor-count-dropped-after-crawler-filtering)。
</Note>

<div id="interpret-agent-views">
## 解读 agent 浏览量
</div>
Expand All @@ -48,3 +58,11 @@ Mintlify 通过 IP 地址和 user agent 识别 agent 访客。agent 访客数近
- **AI agent 分布**:查看哪些 AI 平台访问您的 docs,了解用户偏好哪些工具。
- **集成机会**:识别哪些 AI 平台应优先进行优化和测试。
- **AI 流量模式**:监控哪些 agent 最活跃,以及它们的使用情况如何随时间变化。

agent 明细按提供商对流量进行分组,例如 ChatGPT、Claude 和 Cursor。其余的 agent 流量归入三个类别:

- **HTTP clients**:来自 curl、wget 和 Python HTTP 客户端等工具和库的请求。
- **Browser**:从 Web 浏览器发出的 Markdown 请求。
- **Other**:与已知提供商或客户端不匹配的 agent 流量。

Mintlify 会从 agent 明细中排除自身的内部流量,例如链接检查和页面重新验证。
Loading