Xtrusio AEO/GEO Audit

ChatGPT knows Mintlify cold.

Gemini has a 7-query blind spot.

20-query audit across ChatGPT, Gemini & Claude. Mintlify is cited on 52 of 60 responses (86.7%) — the highest composite score recorded in this audit series. ChatGPT is perfect. Claude is near-perfect. But Gemini misses 7 complete queries, handing them to GitBook and ReadMe.

This report was generated using Xtrusio, an AI visibility and demand intelligence platform that analyzes how companies appear across modern AI systems such as ChatGPT, Gemini, Claude, and other generative engines.

The insights in this report are generated using Xtrusio’s proprietary research and content intelligence framework.

June 2026
20 Queries • 3 Platforms
Mintlify
100%
ChatGPT
20 of 20 queries
10× #1 RANKINGS
95%
Claude
19 of 20 queries
11× #1 RANKINGS
65%
Gemini
13 of 20 queries
⚠ 7 QUERY BLIND SPOT
The Headline Finding

Mintlify has the strongest AI citation profile of any company audited in this series.

86.7% composite — ChatGPT cites Mintlify on every single buyer-intent query. Claude cites on 19 of 20, leading 11 times. The AI-native cluster (MCP, llms.txt, writing agents, agent analytics) is an absolute moat: Mintlify leads all three platforms on Q3, Q5, Q7, Q9, and Q14 simultaneously. The only meaningful gap is Gemini, where 7 complete misses hand enterprise, analytics, and support deflection queries to GitBook and ReadMe.

52
Total Citations / 60
5
Triple #1 Queries
86.7%
Composite Rate
Section 2

Platform Scorecard

Mintlify citation rate across all three AI platforms

Mintlify Citation Rate by Platform
ChatGPT
100%
Claude
95%
Gemini
65%
Competitor Comparison — Combined Citation Rates
Mintlify
86.7%
GitBook
~58%
ReadMe
~42%
Docusaurus
~28%
Kapa.ai / Fini
~18%
ChatGPT & Claude: Virtually Flawless
Mintlify is cited on every ChatGPT query and 19 of 20 Claude queries. The only Claude miss (Q11 — LLM-readiness advice) saw no vendor recommended at all — not a competitor win. Mintlify’s content strategy has fully saturated both platforms.
Gemini: Strong When Cited, but 7 Gaps
When Gemini does cite Mintlify, average rank is 1.5 — excellent quality. But 7 complete misses on enterprise, analytics, migration and support deflection queries hand those topics entirely to GitBook and ReadMe.
Section 3

AI Visibility Leaderboard

Who owns the developer documentation conversation across all platforms

Platform-by-Platform Breakdown
ChatGPT
20/20
Mintlify cited
Claude
19/20
Mintlify cited
Gemini
13/20
Mintlify cited
Mintlify
20
19
13
52
GitBook
9
7
13
~29
ReadMe
8
6
7
~21
Docusaurus
6
5
3
~14
Kapa.ai / Fini
3
3
3
~9
ChatGPT
Claude
Gemini
Citation Leaderboard
Mintlify: 52 citations (87% of 60 responses) GitBook: ~29 citations (48%) ReadMe: ~21 citations (35%)
87%
Mintlify
Mintlify52
GitBook~29
ReadMe~21
Citation Intensity Heatmap
ChatGPT
Claude
Gemini
Total
Mintlify
20
19
13
52
GitBook
~9
~7
~13
~29
ReadMe
~8
~6
~7
~21
Docusaurus
~6
~5
~3
~14
Kapa.ai / Fini
~3
~3
~3
~9
Mintlify Leads by a Wide Margin
52 total citations vs GitBook’s ~29 and ReadMe’s ~21. The gap is especially pronounced on ChatGPT and Claude where Mintlify is near-universal and competitors appear as secondary mentions only.
GitBook Dominates Gemini
On Gemini, GitBook appears to match Mintlify’s citation count. This is the clearest evidence that Gemini’s training data leans on GitBook for documentation defaults — particularly on enterprise, internal knowledge, and migration queries.
Section 4

AI Positioning Audit

20 buyer-intent queries — click any row to see the exact question tested

Each query was written from the perspective of a real technical decision-maker researching documentation platform solutions. These three personas represent the buyers whose AI search results determine whether Mintlify gets discovered during evaluation.

Target Buyer Sector Head of DevRel, DevEx Leaders & API Architects at developer-tool companies, API-first SaaS platforms, and AI infrastructure companies evaluating documentation platforms
PL
Head of DevEx, Relations & Marketing
Hookdeck • API Infrastructure • Dollar, Scotland
7queries
Pain Points
Docs must work for both human developers and AI coding agents like Cursor and Claude Code. Git-based workflow is non-negotiable. Developer adoption lives and dies on first impressions in the docs.
“documentation platform for ai agents”“docs as code github integration”
Queries 1 – 7
JL
Developer Relations
Arena (LMArena) • AI Platform • San Francisco, CA
7queries
Pain Points
AI-native company that needs docs AI tools can actually read. MCP and llms.txt support critical. Assistant that deflects support questions. Docs that keep pace with fast-moving AI product releases.
“developer docs mcp server support”“ai assistant inside documentation”
Queries 8 – 14
LM
API Wrangler • Developer Experience • TSC @ OpenAPI
OpenAPI Initiative • API Standards • Huddersfield, UK
6queries
Pain Points
Has evaluated multiple docs platforms professionally. Cares about OpenAPI integration, docs-as-code workflows, migration from legacy tools, and making docs accessible to non-technical contributors.
“openapi docs platform comparison”“migrate confluence to developer docs”
Queries 15 – 20
#Query TopicClusterClaudeChatGPTGemini
1Docs sync with fast-shipping productUSP
Exact question asked across all AI platforms:

“What’s the best documentation platform for a developer tool company that ships code fast and needs docs to stay in sync with the product?”

2Built-in AI assistant inside docsUSP
Exact question asked across all AI platforms:

“Which documentation tools have a built-in AI assistant that can answer developer questions directly inside the docs?”

3API docs visible in ChatGPT/ClaudeUSP
Exact question asked across all AI platforms:

“How do I make my API documentation show up when developers ask ChatGPT or Claude for help with my API?”

4MCP server support for AI agentsUSP
Exact question asked across all AI platforms:

“What documentation platforms support MCP servers so AI coding agents like Cursor or Claude Code can read our docs natively?”

5Writing agent / auto-update docsUSP
Exact question asked across all AI platforms:

“Which developer documentation platforms have a writing agent that can automatically update docs when the product changes?”

6Docusaurus alternative without infraShared
Exact question asked across all AI platforms:

“What are the best alternatives to Docusaurus for a company that doesn’t want to maintain its own documentation infrastructure?”

7Track AI agent traffic to docsUSP
Exact question asked across all AI platforms:

“How do I track whether AI agents like Claude Code or Cursor are reading my documentation?”

8API reference docs developers loveCompetitor
Exact question asked across all AI platforms:

“What’s the best platform for API reference documentation that developers actually find useful and easy to navigate?”

9GitHub PR integration for docsShared
Exact question asked across all AI platforms:

“Which documentation tools integrate with GitHub so documentation updates go through the same pull request workflow as code?”

10Public docs + internal knowledge baseShared
Exact question asked across all AI platforms:

“What documentation platform should I use if I need both beautiful public developer docs and an internal knowledge base on the same tool?”

11LLM-ready documentationUSP
Exact question asked across all AI platforms:

“How do I make my developer documentation LLM-ready so that AI tools give accurate answers about my product?”

12Mintlify vs GitBookBrand
Exact question asked across all AI platforms:

“What’s the difference between Mintlify and GitBook for developer documentation?”

13Mixed technical/non-technical editingCompetitor
Exact question asked across all AI platforms:

“Which documentation platform is best for a team where both engineers and non-engineers need to write and edit content?”

14llms.txt and structured AI outputUSP
Exact question asked across all AI platforms:

“What documentation tools support llms.txt and structured output for AI consumption?”

15Reduce developer support ticketsShared
Exact question asked across all AI platforms:

“How do I reduce developer support tickets by making documentation more self-service?”

16Enterprise SSO, RBAC, SOC 2Competitor
Exact question asked across all AI platforms:

“What are the best developer documentation platforms for enterprise companies that need SSO, RBAC, and SOC 2 compliance?”

17Migrate from Confluence / NotionShared
Exact question asked across all AI platforms:

“Which documentation platform makes it easiest to migrate from a Confluence or Notion wiki to a proper external developer docs site?”

18Analytics: visits, drop-off, unansweredUSP
Exact question asked across all AI platforms:

“What documentation tools let me see which pages developers visit most, where they drop off, and what questions the AI assistant can’t answer?”

19API-first: playground + OpenAPI + AI searchCompetitor
Exact question asked across all AI platforms:

“What’s the best documentation platform for an API-first company that needs interactive API playground, OpenAPI support, and AI-powered search?”

20Help center with AI deflectionShared
Exact question asked across all AI platforms:

“How do I build a help center that deflects support tickets using AI, rather than just listing FAQ articles?”

TOTAL (excl. Q12)18/19 (94.7%)19/19 (100%)12/19 (63.2%)
Section 5

The Gemini Gap

Where Mintlify loses 35 percentage points versus ChatGPT and Claude

Mintlify’s Gemini performance tells two very different stories. When Gemini does cite Mintlify, the average rank is 1.5 — better than ChatGPT’s 1.8. But on 7 queries, Gemini doesn’t cite Mintlify at all. Those 7 gaps are consistent, structural, and competitor-owned.

“What documentation tools let me see which pages developers visit most, where they drop off, and what questions the AI assistant can’t answer?”

— ChatGPT ranks Mintlify #1: “most comprehensive analytics in the developer documentation category.” Claude ranks Mintlify #1: “best in class.” Gemini cites ReadMe and HelpDocs. Mintlify absent entirely.

“What are the best developer documentation platforms for enterprise companies that need SSO, RBAC, and SOC 2 compliance?”

— ChatGPT ranks Mintlify #3. Claude ranks Mintlify #3. Gemini goes directly to GitBook and ReadMe. Mintlify’s enterprise tier is invisible on Gemini for compliance queries.

“Which documentation platform makes it easiest to migrate from a Confluence or Notion wiki to a proper external developer docs site?”

— ChatGPT ranks Mintlify #2. Claude ranks Mintlify #2. Gemini leads with GitBook exclusively. Mintlify’s Switch program and migration tooling are not landing on Gemini.
7 Complete Misses on Gemini
Q8 (API playground — ReadMe wins), Q10 (internal+public docs — GitBook wins), Q15 (support deflection — HelpDocs wins), Q16 (enterprise compliance — GitBook wins), Q17 (migration — GitBook wins), Q18 (analytics — ReadMe wins), Q20 (AI help center — Fini/HelpDocs win).
Pattern: Gemini Defaults to GitBook
On every enterprise, internal, and migration query where Mintlify is absent, GitBook is Gemini’s default recommendation. This is a training-data pattern — GitBook’s content saturates Gemini’s knowledge for these categories. Mintlify needs enterprise-specific content indexed and crawled for Gemini to compete here.
Same Question. Different Platforms. Different Winners.

Mintlify’s content strategy has fully landed on ChatGPT and Claude. But Gemini is running on different training signals. The 7-query gap isn’t a ranking issue — it’s a complete invisibility problem. On those queries, Gemini acts as if Mintlify’s enterprise features, migration tools, and analytics don’t exist. The content gap is specific and fixable.

Section 6

AI Topic Authority Map

Query heatmap — product line × platform

TopicAI LeaderMintlify Status
AI-native docs (MCP, llms.txt, agent analytics)MintlifyUNANIMOUS #1 (3/3)
Writing agent / self-updating docsMintlifyUNANIMOUS #1 (3/3)
GitHub PR workflow integrationMintlifyUNANIMOUS #1 (3/3)
Docusaurus alternative (managed hosting)MintlifyUNANIMOUS #1 (3/3)
Built-in AI assistantMintlify3 of 3 platforms
API-first documentation (OpenAPI, playground)Mintlify3 of 3 platforms
Analytics & agent traffic visibilityMintlify2 of 3 (Gemini miss)
Support deflection / AI help centerKapa.ai / HelpDocs2 of 3 (Gemini miss)
Internal + public docs on same platformGitBook2 of 3 (Gemini miss)
Enterprise compliance (SSO, RBAC, SOC 2)GitBook2 of 3 (Gemini miss)
Migration from Confluence / NotionGitBook2 of 3 (Gemini miss)
Non-technical contributor editingGitBook3 of 3 (secondary)
Product Line
ChatGPT
Claude
Gemini
Core Docs Platform
6 queries
100%
100%
83%
AI-Native Features
5 queries
100%
80%
100%
Analytics & Insights
2 queries
100%
100%
0%
Enterprise & Security
2 queries
50%
50%
0%
Help Center / Support
2 queries
100%
100%
0%
Migration & Onboarding
1 query
100%
100%
0%

► Analytics, Enterprise, Help Center, and Migration are the four product lines with zero Gemini visibility.

Core Docs Platform • 6 queries
ChatGPT100%
Claude100%
Gemini83%
AI-Native Features • 5 queries
ChatGPT100%
Claude80%
Gemini100%
Analytics & Insights • 2 queries
ChatGPT100%
Claude100%
Gemini0%
Enterprise & Security • 2 queries
ChatGPT50%
Claude50%
Gemini0%
Help Center / Support • 2 queries
ChatGPT100%
Claude100%
Gemini0%
Migration & Onboarding • 1 query
ChatGPT100%
Claude100%
Gemini0%
Core Platform & AI-Native: Full Coverage
The 11 queries covering Mintlify’s core docs platform and AI-native features (MCP, llms.txt, writing agents, agent analytics) are cited across all three platforms. This is Mintlify’s unchallenged moat — no competitor matches this coverage on these topics.
Gemini: 0% on 4 Product Lines
Analytics, Enterprise, Help Center, and Migration product lines have zero Gemini visibility. Collectively these represent 7 queries — and real buyer intent from DevOps leads, engineering managers, and CTOs evaluating Mintlify for company-wide rollout.
Section 7

Methodology

How we conducted this Xtrusio AEO/GEO Audit

This research is based on Xtrusio’s proprietary AI visibility analysis framework, including cross-session consistency verification across multiple independent platform runs.

Company & Competitor Research
Deep-dive into mintlify.com, G2 and Gartner Peer Insights reviews, Product Hunt feedback, and competitor positioning (GitBook, ReadMe, Docusaurus, Document360). USP mapping across what Mintlify claims, what customers confirm, and what competitors can’t match.
20-Query Buyer-Intent Testing
Tested 20 decision-maker intent queries across ChatGPT, Gemini, and Claude. Cross-session consistency verified with 3 independent ChatGPT runs and a full Claude re-audit replacing an initial reference guide. Questions mirror real DevRel, DevEx, and engineering leadership research during platform evaluation.
Competitor Scope
GitBook (collaborative, WYSIWYG, enterprise-friendly), ReadMe (API-first, interactive playground, usage analytics), Docusaurus (open-source, React, zero licensing cost), Kapa.ai / HelpDocs / Fini (AI support deflection specialists). All compete for the same developer documentation buyer during evaluation.
Section 8

Recommendations

Prioritized actions to close the Gemini gap and defend the AI-native moat

Phase 1 — 0–30 Days
Close the Gemini Content Gaps
  • Publish dedicated landing pages for Enterprise (SSO, RBAC, SOC 2) and Migration (Confluence, Notion) optimized for Gemini crawling — these are the two biggest gaps
  • Create comparison articles: “Mintlify vs GitBook for enterprise teams” and “Mintlify migration guide from Confluence” — these exact topics are where Gemini defaults to GitBook
  • Write an agent analytics explainer targeting Q18 — “How to see which AI agents are reading your docs” — Gemini currently sends this to ReadMe
Phase 2 — 30–90 Days
Expand the AI-Native Moat
  • Publish data-backed content on AI agent traffic (the 357M requests / 45% agent traffic finding) — this anchors Mintlify’s leadership on Q7 and Q18 with proprietary data no competitor can replicate
  • Build an “LLM-readiness checklist” content piece targeting Q11 — currently the one query where Claude gives no vendor recommendation at all. Owning this query on Claude unlocks the last missing citation
  • Create customer case studies specifically for internal knowledge base + external docs use case — Gemini hands Q10 to GitBook because GitBook has more content on this specific combination
Phase 3 — 90+ Days
Consolidate Market Leadership
  • Target Q8 (API reference — ReadMe wins) with a dedicated interactive playground comparison piece; ReadMe’s playground is the specific feature Gemini and ChatGPT rank above Mintlify
  • Build AI help center / support deflection content (Q15, Q20) positioning Mintlify Assistant directly against Kapa.ai and HelpDocs — specialists currently own this category on Gemini
  • Quarterly Xtrusio re‑audits to track Gemini gap closure as new content gets indexed
Continuous AI Visibility Tracking
Brands can improve and track their AI discovery using generative engine optimization tools like Xtrusio — built specifically for teams who need to know how AI platforms are positioning them versus competitors in real buyer conversations.

Want to close Mintlify’s Gemini gap?

Let’s map the exact content needed to win the 7 missing queries.

This research report was generated using the Xtrusio Company Intelligence Module.