Lead with comparison content
Cloud Development Environments (CDEs) has 27.9% blog share, 16.0% docs share, and 17.8% comparison/listicle share. Start with the content type AI already cites here, then fill in the missing page types around it.
We asked five AI search platforms thousands of tool-evaluation questions across 43 developer tool verticals and recorded every source they cited. This report shows which pages get cited, which brands appear in answers, and what to build if you want to improve your visibility.
Blog posts earn more citations than docs, product pages, and landing pages combined. The homepage establishes the positioning; detailed explainers give answer engines the context and evidence they can cite. If you want to shape how AI describes your market, write the explainer.
Documentation is the second most-cited content type, and it matters most in hands-on categories such as API Development & Management (39.6% docs share), Documentation & Developer Portals (37.5% docs share), API Mocking & Service Virtualization (30.5% docs share). Before AI recommends a tool for a technical job, it looks for docs that prove the tool can do it.
Northflank shows up in AI Code Sandboxes & Agent Runtimes answers 40.8 percentage points more often than the typical brand in that category, and 22.7 points more than second-placed Modal. Gaps like this are built from citable pages: docs, comparisons, and third-party coverage.
On Google AI Mode, 64.4% of citations were the answer's #1, #2, or #3 source, the highest share of any platform we measured. To show up there, your best page has to be good enough to be a primary source, not one of thirty.
Reddit is the single most-cited third-party domain in the dataset. AI answers lean on the places developers already go to sanity-check tools: Reddit, forums, GitHub discussions. What communities say about you is part of your AI search visibility.
Together, comparison pages and listicles account for this share of all citation records in the report. Being cited is not the same as being recommended: useful pages state clear criteria, honest tradeoffs, and who each tool fits. Unsupported "we're #1" claims are not evidence.
AI search is forcing an infrastructure update, one built for depth, not volume.
Gandharva KumarCo-Founder & CEO at MeasureThe report uses DevTune tracking data for public developer-tool categories. We ask each AI search platform a fixed set of tool-evaluation questions, then record every source it cites: the brand, domain, URL, content type, and where it sat in the source list.
The analysis uses a fixed 90-day window from 2 Apr 2026 to 30 Jun 2026. It covers 43 public developer-tool categories across five platforms, with every question re-run weekly during that period. Current data for the underlying categories is available on the DevTune verticals index.
For every public category we track the brands, the URLs AI answers cite, the domains behind them, the content types, and where each source sat in the answer. That is what shows where visibility is actually earned.
This edition covers five AI search platforms: Google AI Mode, ChatGPT Search, Perplexity, Gemini Search, and xAI Search. Future editions will add more, including Microsoft Bing Copilot Search. We analyze each platform separately because they pick sources very differently.
Each category gets its own set of 25 questions across five topics: Capability, Developer Experience, Integrations & Ecosystem, Performance & Reliability, and Setup & First Run. Using the same structure everywhere shows which proof AI search needs before it recommends, explains, or compares tools.
Every term and metric used in the report is defined in the glossary at the end.
This edition covers five AI search platforms: Google AI Mode, ChatGPT Search, Perplexity, Gemini Search, and xAI Search. Future editions will add more, including Microsoft Bing Copilot Search.
| Platform | Measured projects | Runs | Citation records | Citations / test |
|---|---|---|---|---|
| Google AI Mode | 43 | 327 | 13,018 | 1.60 |
| ChatGPT Search | 43 | 523 | 44,586 | 3.42 |
| Perplexity | 43 | 519 | 20,076 | 1.56 |
| Gemini Search | 43 | 522 | 33,774 | 2.64 |
| xAI Search | 43 | 297 | 15,360 | 2.33 |
The data splits the work into three jobs. On selective platforms like Gemini Search, get picked as one of the first few sources. On platforms like ChatGPT Search, make your own site answer buyers' questions. On broad platforms like Google AI Mode and xAI Search, get the rest of the web talking about you.
Gemini Search, Perplexity
Gemini Search currently shows 46.8% of citations in sources #1-#3 and 2.64 citations per test. Perplexity shows 29.6% of citations in sources #1-#3 and 1.56 citations per test.
These platforms cite few sources, and the first few carry most of the weight. A thin page doesn't get a second chance.
Pick a small number of pages — category explainers, comparisons, key docs — and make each one good enough to be the answer on its own.
ChatGPT Search, Google AI Mode
ChatGPT Search cites the most balanced mix of docs, product pages, discussions, and comparisons. Google AI Mode casts wider but still leans on company and editorial pages.
Your site needs to read like proof, not a brochure. Product pages, docs, and blog posts should make the same claims in words an AI answer can quote directly.
For each thing buyers care about, build the full set: what it is, how it works, what it integrates with, what it costs, and what the limits are. A well-structured FAQ section is a straightforward, clean way to answer these questions on the page.
Google AI Mode, Perplexity, xAI Search
These platforms cite community posts, video, editorial pages, and reference sites. Reddit, YouTube, Medium, GitHub, Dev.to, LinkedIn, and Stack Overflow all show up in the data.
AI search doesn't just read your site. If Reddit or an old tutorial explains your category badly, that version becomes part of your answers.
Treat community answers, GitHub, tutorials, listicles, and partner pages as channels. Show up there and keep the story consistent.
It's too easy as a founder to believe your category is defined on your homepage, and get really precious about the messaging there. The reality is it's defined in a Reddit thread you've maybe never even read, and now that thread is training the answer engine your buyers talk to. You can either be in that conversation or be described by the people who are.
Barrie SegalFounder at Kind StrangerCategories differ in citation activity, brand presence, docs reliance, and third-party influence. Locate the pattern that best matches your category, then use the corresponding action as a benchmark to test against current data for your own brand.
Optimizing for AI search is the new marketing frontier, which is especially true in devtools. To win, generic content won't cut it. One needs a rigorous, focused strategy that establishes absolute domain authority.
Chris BrightVP of Revenue at DepotThis edition covers Google AI Mode, ChatGPT Search, Perplexity, Gemini Search, and xAI Search. Compare them one at a time: how many sources they cite, how concentrated those sources are, and how often they cite brand-owned sites all vary a lot.
Bubble size shows how many distinct domains a platform cites. The vertical axis shows how much weight its first three sources carry. Platforms high on this chart reward one great page; platforms to the right reward breadth.
| Platform | Volume | Citations / test | Domains | Sources #1-#3 | Tracked-brand share |
|---|---|---|---|---|---|
| Google AI Mode | 13,018 | 1.60 | 2,802 | 64.4% | 23.0% |
| ChatGPT Search | 44,586 | 3.42 | 5,274 | 38.0% | 24.6% |
| Perplexity | 20,076 | 1.56 | 4,785 | 29.6% | 12.9% |
| Gemini Search | 33,774 | 2.64 | 4,000 | 46.8% | 26.9% |
| xAI Search | 15,360 | 2.33 | 3,340 | 12.7% | 31.5% |
Casts a wider net than Gemini Search. Strong pages on your own site help, but video, editorial coverage, and community discussion count too.
Balanced mix of sources. Make your docs, product pages, and comparisons each answer buying questions on their own, without needing the homepage for context.
Puts heavy weight on its first few sources and likes third-party pages: listicles, short explainers, community threads, GitHub, and video.
The most selective platform. It cites few sources, so every cited page matters. One definitive, current page beats ten average ones.
Pulls from the widest slice of the web. Community posts, video, social, and long-tail pages all feed its answers.
Gemini Search cites a few strong sources. ChatGPT Search leans on docs, product pages, discussions, and comparisons. xAI Search pulls from the long tail of the web. Decide which platforms matter for you before you assign content budget.
| Platform | Company / commercial | Community | Editorial |
|---|---|---|---|
| xAI Search | 74.5% | 3.8% | 8.1% |
| Google AI Mode | 66.3% | 6.8% | 7.2% |
| ChatGPT Search | 59.4% | 21.0% | 4.5% |
| Perplexity | 68.8% | 7.0% | 8.9% |
| Gemini Search | 77.7% | 3.1% | 10.5% |
For the past few years savvy buyers have been appending 'reddit' to their Google searches because they trust a stranger with first-hand experience over a vendor landing page. AI is now outsourcing trust to the same place buyers already did, but at scale. The winning tools aren't gaming it; they just actually showed up in those conversations.
Barrie SegalFounder at Kind StrangerBlog posts dominate, but docs, discussions, articles, listicles, product pages, and comparisons all earn real share. The useful unit is a connected set of pages that explains the category, proves the technical claims, and makes comparison easy.
The report-wide mix is a benchmark, not a substitute for monitoring your own brand. A company's cited sources can look very different from the aggregate pattern.
It’s much more distracting than it is helpful to think about AEO in terms of purely keywords. When looking at actually cited sources at Railway, it’s mostly sources that are user-generated, not company-generated.
Sarah Krasnik BedellFounding Growth Marketer at RailwayThe data is compelling: blog posts are the largest citation surface, docs second, and landing pages barely register. Useful explainers win. Specific docs win. Concrete comparisons win. Vague landing pages lose.
Blogs often come from having actually solved a real problem, which is probably why they win. It is also why Stack Overflow worked so well, and why Reddit threads are cited so often today: real questions, specific context, answers shaped by people who have actually encountered the problem.
Gandharva KumarCo-Founder & CEO at MeasureDocs used to be for developers who had already chosen you. Now AI search reads them to decide whether to recommend you at all: what you integrate with, how security works, and whether your claims hold up.
GitBook recorded 23.8 million AI-agent requests and 22.2 million human requests across qualifying GitBook-hosted documentation sites from 27 April to 3 May 2026. After excluding crawler and other detected-bot traffic, agents accounted for 51.8% of human-plus-agent requests.
This is GitBook traffic data, not part of DevTune's 90-day citation benchmark, but it points to the same operating reality: documentation now serves machines as well as people.
GitBook included sites with more than 100 human page views in April 2026. Figures are aggregate requests or page views, not unique readers or sessions; about 22% of agent traffic had no identifiable bot name. Read the GitBook research.
Documentation is the second most-cited content type overall, and its share is much higher in hands-on categories such as API Development & Management (39.6% docs share), Documentation & Developer Portals (37.5% docs share), API Mocking & Service Virtualization (30.5% docs share).
Make each docs page complete on its own: what it is for, prerequisites, limits, working examples, error cases, and next steps.
Categories where docs win the most citations are the ones where buyers need to see the workflow before they trust a recommendation.
Write task-level guides for the questions buyers actually ask: setup, integration, migration, security, pricing limits, and what happens when things fail.
Blog posts often define a market, but AI needs docs and product detail before it can recommend a tool for a concrete job.
For every claim a blog post introduces, make sure a docs page proves it.
The brand scorecards show different brands winning with different pages: FAQs, category blog posts, product pages, docs, and comparisons all carry visibility somewhere.
Find your strongest cited page type, then build the companion pages around it so AI doesn't have to guess the missing context.
AI agents now account for the majority of intentional documentation reads on GitBook — they crossed 50% this spring, up from under 10% at the start of 2025. Docs used to convert developers who had already chosen you. Now they're the evidence AI weighs before it recommends you at all. The teams that win won't be the ones with the most content — they'll be the ones whose docs are structured, specific, and current enough for a machine to trust.
Addison SchultzDeveloper Relations Lead at GitBookIn these categories, docs already win a big share of citations. If you compete here, your docs need to answer buying questions, not just setup steps.
These categories get lots of citations, but few of them go to docs. That is an open gap: publish the technical detail before comparison sites and Reddit threads define the category for you.
Our argument at dbt is that outputs are only as trustworthy as the context behind them. That holds for analytics, and it turns out it holds for AI search too.
Dan PoppySenior Manager, Content at dbt LabsInterestingly enough, we see that Docs tend to be the most commonly cited surface for Clerk
Alex RappHead of Growth Marketing at ClerkA page can shape an AI answer without getting a click, so page views alone miss part of its influence. Measure citations and recommendations alongside traffic, then follow AI-referred visitors through signup, activation, monetisation, and retention.
Utilizing AI search tracking tools are imperative for attribution strategy and progress tracking, as AI search relevancy is no longer 1:1 leading to direct clicks. By relying upon basic attribution through a platform like GA4, you're missing out on detailed information about how AI search overviews and AI answers are leading (or not) back to your brand.
Samantha TroiloMarketing Lead at BeefreeCitation visibility shows whether answer engines use your content; it does not establish commercial impact on its own. The dashboard should answer two connected questions: when buyers and AI search look at our category, do they find current, provable pages that make our case; and when those answers send us traffic, does that traffic produce valuable, retained customers?
Do this next: add an AI-search view to the content review you already run. Join citation visibility to the referral funnel: visits, signups, activation, paid conversion, revenue, and retention by platform and landing page.
| Metric | Business question | What to do |
|---|---|---|
| Answer presence | Do we show up when people ask about our category? | Track this per platform and per question topic. One blended number hides where you are losing. |
| Recommendation language | Does the answer recommend us, or just cite us as a source? | Track when answers recommend you, when they recommend competitors, and which pages back each recommendation. |
| Citation count | Which of our pages are AI answers actually using? | Double down on pages that are getting cited. Check they support your story rather than a competitor narrative. |
| Citations per test | How many sources does an answer in our category cite? | Categories with many citations per answer have room for lots of content. Categories with few need one definitive page. |
| Source #1-#3 citation share | How often are we one of the first three sources cited? | On platforms where the first few sources dominate, one strong page beats ten average ones. Consolidate. |
| Own-site citation share | Is AI learning about us from our site, or from someone else? | If third-party pages carry your story, publish the definitive version on your own site, then keep the external coverage accurate. |
| Third-party dependency | Which outside sites shape answers about us? | Treat Reddit, GitHub, YouTube, and review sites as channels. Show up there deliberately. |
| AI-referral conversion | Do visits from AI answers become signups, trials, or leads? | Preserve AI referrers and landing pages through the signup journey. Compare conversion rates by platform, category page, and cited URL. |
| Activation and retention | Do AI-referred users reach value and keep using the product? | Cohort AI-referred signups by activation milestone, time to value, retained usage, and churn. Use those outcomes to test whether AI referrals bring better-fit users, not only more visits. |
| Monetisation | Does AI-referred demand create pipeline and revenue? | Connect acquisition data to CRM and billing outcomes: qualified pipeline, paid conversion, revenue, expansion, and payback by AI source. |
| Platform coverage | Which platforms need their own plan? | Report each platform separately. Averaging five platforms into one number hides what each one needs. |
| Freshness / movement | Is our visibility improving or decaying? | Review movement weekly. Refresh pages before a stale claim becomes the cited answer. |
The goal: get an LLM to mention your product, and then enable the user to implement it in their project effectively. Even better, to cite something you wrote, but frankly citation of first-party content is a byproduct, not a goal.
Sarah Krasnik BedellFounding Growth Marketer at RailwayIn these categories, each AI answer cites more sources, which means more chances for your pages to be one of them. Publish the page type the category is missing, then watch whether it starts getting cited.
Find your category by name or by a tracked brand. The category profile then shows its leaders, citation sources, platform patterns, and benchmark-backed priorities in one place.
Find your category by its name or any tracked brand, then select a row. Every panel in the category profile below will update.
A 0-100 score combining citations per test (35%), cited-domain breadth (20%), lower average brand presence (25%), and lower tracked-brand citation share (20%). Higher scores indicate less-settled category visibility.
| Category | Openness | Cites / test | Domains | Docs | Blog | Brand share | Top-3 share |
|---|---|---|---|---|---|---|---|
IDEs & Code Editors | 54.2 | 2.44 | 791 | 8.9% | 31.1% | 5.5% | 39.3% |
Open Source Commercial / OSS Infrastructure | 52.6 | 2.12 | 633 | 14.0% | 38.3% | 6.2% | 40.4% |
Mobile Development Platforms & Cross-Platform | 51.5 | 2.15 | 657 | 15.0% | 45.5% | 9.5% | 40.8% |
AI/ML Infrastructure & LLM Tools | 51.4 | 2.45 | 643 | 12.6% | 37.3% | 12.7% | 38.1% |
API Development & Management | 50.8 | 2.30 | 495 | 39.6% | 30.6% | 7.9% | 41.1% |
Search & Vector Databases | 50.4 | 2.48 | 685 | 13.5% | 32.6% | 18.1% | 35.1% |
Containers & Orchestration | 50.3 | 1.92 | 544 | 13.0% | 41.1% | 9.2% | 38.2% |
Communications APIs | 50.1 | 2.43 | 671 | 15.6% | 30.9% | 17.9% | 36.8% |
Databases & Data Infrastructure | 49.5 | 1.98 | 546 | 19.0% | 38.6% | 14.4% | 41.8% |
Agent Authentication & Identity for AI | 49.1 | 2.63 | 603 | 20.3% | 36.1% | 20.0% | 35.6% |
Testing & QA | 48.8 | 2.12 | 500 | 11.2% | 46.1% | 14.2% | 37.4% |
Cloud Development Environments (CDEs) | 48.6 | 2.47 | 500 | 16.0% | 27.9% | 16.0% | 41.7% |
Developer Tunnels & Localhost Ingress | 48.5 | 3.95 | 550 | 16.3% | 35.6% | 24.3% | 36.1% |
CI/CD & Build Systems | 48.4 | 1.92 | 545 | 14.2% | 35.8% | 17.0% | 43.2% |
DevSecOps & Application Security | 48.3 | 2.64 | 518 | 6.2% | 36.2% | 19.1% | 33.1% |
Messaging & Event Streaming | 48.2 | 2.53 | 534 | 22.0% | 34.4% | 19.0% | 38.1% |
Cloud Infrastructure & PaaS | 47.9 | 2.50 | 673 | 15.8% | 35.1% | 28.0% | 36.5% |
Deployment & Hosting Platforms | 47.6 | 2.23 | 615 | 16.9% | 30.7% | 25.3% | 40.7% |
Documentation & Developer Portals | 47.5 | 2.40 | 620 | 37.5% | 28.9% | 27.2% | 37.8% |
AI Code Review & Code Quality | 47.1 | 2.32 | 447 | 11.7% | 32.3% | 18.6% | 39.7% |
Web Data Infrastructure for AI | 47.1 | 2.93 | 566 | 11.1% | 32.3% | 27.1% | 33.0% |
Design Systems & Component Libraries | 47.0 | 2.29 | 513 | 30.1% | 29.6% | 21.8% | 39.7% |
Payments & Fintech APIs | 46.7 | 2.20 | 559 | 23.3% | 31.2% | 27.3% | 39.3% |
Transactional Email & Developer Email APIs | 46.7 | 2.52 | 432 | 14.5% | 29.9% | 17.5% | 39.5% |
Workflow Orchestration & Durable Execution | 46.5 | 2.65 | 517 | 23.8% | 28.7% | 26.2% | 37.5% |
Version Control & Code Collaboration | 46.4 | 2.07 | 559 | 27.1% | 31.9% | 22.5% | 40.5% |
Error Tracking & Crash Reporting | 45.8 | 2.38 | 388 | 23.4% | 27.0% | 22.7% | 37.1% |
Data Engineering & ETL/ELT Pipelines | 45.3 | 2.70 | 464 | 8.9% | 44.0% | 27.4% | 36.3% |
Issue Tracking & Project Management | 45.3 | 2.13 | 521 | 16.4% | 30.5% | 27.5% | 42.3% |
Observability & Monitoring | 45.3 | 2.11 | 381 | 10.3% | 34.9% | 23.6% | 39.7% |
Developer Analytics & Product Analytics | 44.6 | 1.79 | 432 | 12.3% | 33.8% | 25.6% | 44.1% |
AI Code Sandboxes & Agent Runtimes | 44.4 | 2.75 | 467 | 12.3% | 28.9% | 32.3% | 38.5% |
Backend-as-a-Service & Realtime | 43.9 | 2.22 | 476 | 23.8% | 35.5% | 32.4% | 40.1% |
AI Browser Infrastructure | 43.7 | 2.78 | 395 | 15.1% | 40.7% | 30.2% | 33.7% |
API Mocking & Service Virtualization | 43.5 | 2.57 | 318 | 30.5% | 27.3% | 25.5% | 43.8% |
Headless CMS & Content Platforms | 43.4 | 2.63 | 426 | 15.8% | 38.4% | 35.7% | 36.1% |
Infrastructure as Code | 43.3 | 1.90 | 401 | 13.9% | 46.0% | 31.0% | 40.7% |
Internal Developer Platforms | 43.0 | 2.34 | 381 | 15.2% | 41.4% | 31.8% | 38.9% |
Secrets Management & Vault | 42.7 | 2.34 | 358 | 24.6% | 27.5% | 30.7% | 40.4% |
Authentication & Identity | 42.5 | 2.12 | 468 | 19.7% | 36.3% | 33.7% | 40.1% |
Salesforce DevOps | 38.5 | 2.72 | 190 | 9.8% | 29.6% | 43.5% | 36.5% |
Incident Management & On-Call | 37.8 | 2.38 | 325 | 11.5% | 28.9% | 47.7% | 41.2% |
Feature Flags & Experimentation | 36.3 | 2.31 | 264 | 16.1% | 34.1% | 52.4% | 41.1% |
The plan, brand ranking, platform metrics, and source matrix below are all filtered to this category. Choose another heatmap row to update the complete profile.
These recommendations use only the citation patterns measured for this category. Treat them as a market benchmark, then validate the priorities against current monitoring for your own brand.
Cloud Development Environments (CDEs) has 27.9% blog share, 16.0% docs share, and 17.8% comparison/listicle share. Start with the content type AI already cites here, then fill in the missing page types around it.
16.0% of citations point to tracked brand domains and average brand presence is 7.1%. Define the category language now, before AI answers settle around incumbents.
The top question theme here is what cloud development environments support air-gapped or private network configurations for teams working with regulated data?. Treat it as a page brief: answer the question directly, explain the tradeoffs, add proof, and link to the relevant docs and comparisons.
What cloud development environments support air-gapped or private network configurations for teams working with regulated data?
Use “What cloud development environments support air-gapped or private network configurations for teams working with regulated data?” as a page brief: answer it directly, explain tradeoffs, add verifiable proof, and connect the page to the relevant docs and comparisons.
What cloud development environment tools allow enterprises to bring their own cloud account so workspace infrastructure runs in their own VPC?
Use “What cloud development environment tools allow enterprises to bring their own cloud account so workspace infrastructure runs in their own VPC?” as a page brief: answer it directly, explain tradeoffs, add verifiable proof, and connect the page to the relevant docs and comparisons.
Which cloud IDE platforms let a contributor open and run a project in a browser without installing anything locally?
Create a dedicated page for “Which cloud IDE platforms let a contributor open and run a project in a browser without installing anything locally?” that names the decision criteria, gives a direct answer, and links every claim to product or technical proof.
Each platform rewards different things. Use these cards to adapt the category plan to how each platform actually picks its sources.
Broad Google research surface. It cites more pages and includes video and wider web coverage.
Pair strong blog and docs pages with video, third-party validation, and consistent entity language across the open web.
Balanced source selection. Docs, product pages, discussion, and comparisons appear more often than on most platforms.
Make core docs and product pages answer buying and implementation questions without needing homepage context.
Puts heavy weight on its first few sources. Listicles and compact third-party pages can carry unusual weight.
Earn credible ranked-list coverage and keep owned comparison pages concise, specific, and current.
Selective source selection. Fewer sources make top citation positions unusually important.
Prioritize definitive, fresh, tightly structured pages that can earn a top citation slot for the questions buyers ask in your category.
Largest long-tail source set. Community, video, and deep web sources matter more than elsewhere.
Broaden surface area across Reddit, GitHub, YouTube, docs, blogs, and category comparisons so the long tail reinforces your positioning.
Brand presence is the share of measured answer observations in this category with at least one citation mapped to each tracked company. This is an AI-search visibility ranking, not a judgment of product quality.
Category leader
Second-highest presence
The middle tracked brand when category presence is ranked.
Documentation authority drives most of the leader's citations. ChatGPT Search cites the leader most.
Brand presence is the share of measured answer observations with at least one citation mapped to the company. Owned citations count every such citation record, so one answer can contribute more than one; top-three share and average position show how prominently those sources appear. Select any column heading to reorder the comparison.
GitHub Codespaces github.com | 22.3% | 158 | 52.5% | 9.2 | Documentation | ChatGPT Search |
Coder coder.com | 18.4% | 109 | 46.8% | 11.6 | Comparison page | ChatGPT Search |
Gitpod www.gitpod.io | 14.3% | 108 | 62.0% | 5.1 | Documentation | ChatGPT Search |
DevPod devpod.sh | 13.3% | 66 | 25.8% | 8.6 | Documentation | ChatGPT Search |
Codeanywhere codeanywhere.com | 5.7% | 19 | 15.8% | 19.3 | Landing page | xAI Search |
Replit replit.com | 2.2% | 10 | 40.0% | 25.9 | Product page | xAI Search |
StackBlitz stackblitz.com | 1.0% | 6 | 16.7% | 21.7 | Product page | ChatGPT Search |
CodeSandbox codesandbox.io | 0.7% | 4 | 0.0% | 6.3 | Landing page | ChatGPT Search |
Firebase Studio studio.firebase.google.com | 0.7% | 3 | 0.0% | 6.0 | Blog post | Gemini Search |
Jetify www.jetify.com | 0.1% | 0 | — | — | No owned citation | No owned citation |
Daytona www.daytona.io | 0.0% | 0 | — | — | No owned citation | No owned citation |
This matrix contains only citation records from the selected category and platform. It shows whether answers rely on company pages, editorial coverage, community sources, reference material, or video, and which page types carry that evidence.
AEO is still the wild west. Spam reddit profiles, mass produced 'we're the best, obviously' listicles and comparison pages, llms.txt could be a thing now. Finding out what fight you're in, so you can test the right things obsessively feels like the way to uncover wins right now.
Matt HendersonDirector of Growth Marketing at SentryThese views aggregate the complete report dataset. Use them to compare platforms, content types, sources, categories, and brands; they do not change the category profile above.
Return to your category profileCasts a wider net than Gemini Search. Strong pages on your own site help, but video, editorial coverage, and community discussion count too.
Balanced mix of sources. Make your docs, product pages, and comparisons each answer buying questions on their own, without needing the homepage for context.
Puts heavy weight on its first few sources and likes third-party pages: listicles, short explainers, community threads, GitHub, and video.
The most selective platform. It cites few sources, so every cited page matters. One definitive, current page beats ten average ones.
Pulls from the widest slice of the web. Community posts, video, social, and long-tail pages all feed its answers.
The category openness score weights citations per test (35%), cited-domain breadth (20%), lower average brand presence (25%), and lower tracked-brand citation share (20%). A higher score means AI answers draw on an active, broad source set that tracked brands control less. Pair it with your own demand, pipeline, and brand-monitoring data before setting priorities.
All 43 categories are plotted so every team can locate its market. Use category search, brand search, or the quadrant filter to isolate a market, then hover a bubble for the category name and score. The full category table is in the Strategy Lab. Bubble size encodes cited domains.
Use the category metrics to see what AI already cites here, then build the missing docs, comparison pages, and third-party coverage around the same decision criteria.
Use the category metrics to see what AI already cites here, then build the missing docs, comparison pages, and third-party coverage around the same decision criteria.
Use the category metrics to see what AI already cites here, then build the missing docs, comparison pages, and third-party coverage around the same decision criteria.
Use the category metrics to see what AI already cites here, then build the missing docs, comparison pages, and third-party coverage around the same decision criteria.
Use the category metrics to see what AI already cites here, then build the missing docs, comparison pages, and third-party coverage around the same decision criteria.
Use the category metrics to see what AI already cites here, then build the missing docs, comparison pages, and third-party coverage around the same decision criteria.
In these categories, AI answers rarely name the tracked brands. They lean on third-party pages instead, or scatter mentions across a fragmented field. If you compete here, the opening is to become the obvious source before the story settles around someone else.
AI search has raised the cost of not being useful. It filters out slop at a level classic SEO never did.
But this is not fundamentally new. DigitalOcean built its growth engine around this more than a decade ago. AI search has changed how content gets distributed and consumed, not the fundamentals of what makes it useful.
Gandharva KumarCo-Founder & CEO at MeasureThis ranking excludes domains owned by the tracked brands and other commercial vendors. What's left is where AI search goes for an independent second opinion: community threads, video, editorial posts, GitHub, reference and review pages. Reddit tops the list. Treat these sites as channels you need a presence on.
When AI usage explodes, so does the surface area in which a company can get mentioned. Railway's mentions and citations actually originate from content that we didn’t write. This is the power of UGC and word of mouth.
Sarah Krasnik BedellFounding Growth Marketer at RailwayThe mistake I'd warn against is reading this and dumping a bunch of promotional posts into subreddits. Reddit is the most-cited domain because it's not marketing. Show up as a participant, be genuinely useful, let the citations follow. It's slower and it's the only thing that works.
Barrie SegalFounder at Kind StrangerEach category is tested with 25 questions across five topics: Capability, Developer Experience, Integrations & Ecosystem, Performance & Reliability, and Setup & First Run. Use those five topics as a checklist. If your site can't answer one of them, AI search will borrow the answer from someone else. The table combines these topics across all 43 measured categories.
AI search has resulted in an evolution of 'long-tailed search term optimization,' as AI tools are not only being asked in an even more conversational tone for input, but it's especially tailored for a specific use case. It's no longer give me the best X for Y category, but for input upon their very specific, personalized use case. As such, documentation and blog strategies have to evolve for this thinking.
Samantha TroiloMarketing Lead at Beefree| Topic category | Prompts / category | Answer runs | Avg brand presence |
|---|---|---|---|
| Capability | 5 215 total | 10,948 | 8.7% |
| Developer Experience | 5 215 total | 10,949 | 8.7% |
| Integrations & Ecosystem | 5 215 total | 10,951 | 8.3% |
| Performance & Reliability | 5 215 total | 10,949 | 8.5% |
| Setup & First Run | 5 215 total | 10,950 | 8.3% |
These are the 8test questions that produced the most citations. That doesn't mean users ask them most often. It means AI search needed the most source material to answer them.
The pattern matters more than the exact questions: hands-on topics like performance, reliability, SDK behavior, and integrations pull in the most sources. If your category has questions like these, they deserve clear docs, examples, and third-party coverage.
We collect first-party data on what prompts people use to find PostHog. Although some are as long and elaborate as you might expect, a majority are as simple as SEO keywords. We see a lot of "best feature flags" or "free feature flags" for example.
Ian VanagasTechnical Content Marketer at PostHogThe pages AI search cites most are recently updated market overviews, ranked lists, vendor-written comparisons, and thorough docs explainers. What they have in common: they help AI sort the market, compare options, and explain which tool fits which job. The value is in the criteria and proof, not in calling yourself the best.
It's not enough to just get your page referenced, you also want to see your product mentioned. This is especially important for developers as tools like Claude Code aren't going to give references, just recommendations. This is significantly different from non-developer roles.
Ian VanagasTechnical Content Marketer at PostHog| Page pattern | Domain | Title | Citations | Platforms |
|---|---|---|---|---|
| Category education | cycode.com | Best Secrets Management Tools for 2026 | Cycode | 121 | 5 |
| Category education | firecrawl.dev | 11 Best AI Browser Agents in 2026 | 120 | 5 |
| Product proof page | blaxel.ai | Best Code Execution Sandboxes for AI Agents 2026 | Blaxel Blog | 116 | 4 |
| Category education | pinggy.io | Top 10 Ngrok alternatives in 2026 | 106 | 5 |
| Best-tools list | modal.com | Best Code Execution Sandboxes for AI Agents in 2026 | Modal Blog | 101 | 4 |
| Best-tools list | thesoftwarescout.com | Best Cloud IDE 2026: Top Browser-Based Dev Environments Ranked & Tested | 99 | 5 |
| FAQ page | northflank.com | What's the best code execution sandbox for AI agents in 2026? | Blog - Northflank | 98 | 5 |
| Best-tools list | hookdeck.com | Best ngrok Alternatives: Local Tunneling Tools for Webhook Development - Hookdeck | 98 | 3 |
| Category education | posthog.com | The best error tracking tools for developers, compared - PostHog | 96 | 4 |
| Category education | northflank.com | Top internal developer portals in 2026 | Blog — Northflank | 96 | 4 |
| Documentation explainer | sanity.io | Top 5 Headless CMS Platforms for 2026 on G2 - Sanity | 93 | 3 |
| Comparison page | flosum.com | Best Salesforce DevOps Tools Compared: 2026 Rankings | 91 | 5 |
The most-cited pages have 2026 in them. LLMs love freshness. You need a strategy not only to publish, but to keep published pages up to date.
Justin DunhamFounder at érculeAcross 668 vendor-authored ranked pages, the report records 2,607 citations across 2,295 page-and-answer pairings. These pages often help the publisher, but they also give answer engines criteria and competitor names to reuse.
The cited page's brand also appeared in the answer.
Another tracked brand appeared, but the publisher did not.
Versus 15.2% for comparison pages.
What this proves: vendor-authored ranked pages earn citations, but a citation does not guarantee that the publisher is even named in the answer.
How to read this: the analysis shows whether vendor-authored ranked pages earn citations and whether the publisher or another tracked brand appears in the answer. An explicit recommendation is a separate outcome to track alongside citations and mentions.
Method note: one page-and-answer pairing means one ranked page was cited in one recorded answer. This subset includes comparison and best-tools pages on tracked brands' own domains where the page title or URL signals a ranking, alternatives, versus, or comparison format.
While flooding the internet with AI-generated ranking pages worked for the beginning of AI search, the tools have become much more intelligent and these low-quality pages now work against your brand.
Samantha TroiloMarketing Lead at BeefreeThe cited pages aren't random. They help AI sort the market, compare options, check technical claims, and test vendor claims against outside evidence. Being cited is influence, not victory: a citation alone does not tell you which brand the answer presents most strongly.
AI can't compare tools without criteria. Pages that name real tradeoffs become source material. Pages that just declare a winner don't.
Write category pages that define the use cases, the selection criteria, the tradeoffs, and the credible alternatives, without a self-serving #1 claim.
A docs page with code, limits, setup steps, and integration detail is easier to cite than a marketing claim.
Add quotable sections to docs: what is supported, what the limits are, example output, how security works, and where the product doesn't fit.
AI search needs contrast. Honest tradeoffs and clear "use X if, use Y if" boundaries make a page more reusable than a feature grid.
Write alternatives and versus pages with buyer profiles, reasons to switch, technical constraints, and cases where the other tool is better.
Claims from outside your site carry more weight than your own, and they reach the platforms that cite broadly.
Give partners, community authors, and tutorial creators the same criteria your own pages use, so every telling of the story matches.
AI favors pages that organize a category and explain why each option fits a specific job.
Refresh market guides quarterly. Show your inclusion criteria, add new entrants, say who each tool fits, and link to the technical detail.
Developers and AI both check public activity (issues, examples, discussions) to see whether a tool is alive and useful.
Keep your README, examples, release notes, and community answers telling the same story as your website.
The best thing we do for our content is refuse to undermine the reader.
We assume they're coming in with a real understanding of the space, and our job is to build on it, not talk around it – which sometimes means conceding that a competitor genuinely does something better than us. Comparison content isn't about winning every use case; you can't be everything for everyone. It's about winning the right use case, and knowing you can be everything for someone.
This is where long-tail queries earn their keep: spelling out exactly which use cases you're most suitable for (stack, team size, budget, business stage, etc) is how the right someone finds you.
Natalia AmorimContent Marketing Manager at PostHogOne risk of citing your competitors: If your competitors are small enough, they'll benefit from your mentioning them. Their LLM visibility may even increase, with citations from your pages. Think through who you really want to position against, and how.
Justin DunhamFounder at érculeIn some categories one brand dominates the answers; in others, citations scatter across a weak field. The useful questions: how far ahead is the leader, and which pages built that lead?
No standard page type dominates the leader citations. Audit the answer mentions, then build clearer docs, product proof, or third-party evidence pages.
Category education drives most of the leader's citations. ChatGPT Search cites the leader most.
Product proof drives most of the leader's citations. ChatGPT Search cites the leader most.
Documentation authority drives most of the leader's citations. ChatGPT Search cites the leader most.
Documentation authority drives most of the leader's citations. ChatGPT Search cites the leader most.
Category education drives most of the leader's citations. Gemini Search cites the leader most.
Documentation authority drives most of the leader's citations. Gemini Search cites the leader most.
Big gaps usually trace back to something concrete: a docs hub, a set of comparison pages, or a category explainer library that AI answers cite again and again.
In these categories even the leader isn't the obvious answer yet. A focused content push can still change who AI recommends.
A tight gap is a warning for the leader: the category has demand, but nobody has built enough citable proof to own it yet.
Changing how AI describes you is a slog and there's no shortcut. What we've learned is that it's doable, but only if you're ruthless about scope. Pick the one perception you most need to change, then throw everything at it: your site, your docs, your case studies, third-party mentions, all pointing in the same direction. Spread that effort across ten perceptions and you move nothing. Concentrate it on one and the answers start to shift.
Holly WhiteTechnical Content Manager at GearsetThe short version: decide which criteria you want to be judged on, publish pages that answer them, show up in the places AI search already looks, and measure each platform separately.
We're writing more content we might not have written if we were just focused on SEO. It's less focused on keywords and more focused on target audiences and use cases.
Ian VanagasTechnical Content Marketer at PostHogThe report covers 1,075 test questions across 43 developer-tool categories.
Write category pages, alternatives pages, migration pages, and market guides around the exact criteria buyers use to shortlist tools. Thin "top 10" posts that rank you first don't count.
17.1% of vendor-authored ranked-page citation events mentioned another tracked brand without mentioning the publisher.
Track cited pages, brand mentions, and recommendations as three different numbers, so a page that merely explains the category isn't mistaken for a win.
The homepage establishes what the company is and what it does. Deeper evidence earns more direct citations: blog posts earned 34.3% of citations; product pages 7.5%; landing pages 2.6%.
Keep homepage positioning clear and consistent, then substantiate its claims in docs, blog posts, comparisons, integration pages, changelogs, and credible third-party coverage.
Docs reached 37.5% of citations in Documentation & Developer Portals and 39.6% in API Development & Management.
State what is supported, what it integrates with, the limits, the security model, and the pricing constraints. Write it in sentences that make sense out of context, because that's how AI will quote them.
Reddit, YouTube, Medium, GitHub, Dev.to, LinkedIn, and Stack Overflow are among the most-cited domains.
Keep GitHub tidy, answer community questions, support good tutorials, and check whether third-party pages describe your product accurately.
The five platforms differ in how many sources they cite, how concentrated those sources are, and what content they prefer.
Track each platform separately. Getting mentioned everywhere and becoming a top-three source are different jobs. Don't blend them.
The ecosystem's response to AI search has been to flood the space with subpar AI articles. We're watching competitors publish tens of articles a day, betting that sheer volume gets them cited. It might work in the very short-term, but they've ended up with a huge pile of thin content that says very little. At Gearset we'd rather publish less and prove more. In a world where models reward corroboration and accuracy, volume without substance is only ever going to leave you worse off.
Holly WhiteTechnical Content Manager at GearsetThe shift for my team is less about producing more and more about deciding what's worth standing behind.
Dan PoppySenior Manager, Content at dbt LabsStale docs and outdated comparison claims get cited too. Important pages need maintenance, not a publish date and a year of silence.
'Keep comparison claims current' is easier said than done. We ship fast, and so do our competitors. We've built internal skills for monitoring competitor changes, and our site is a public repo, so anyone can open a PR against it, but it's still a constant uphill battle. When a competitor calls out a stale claim about them, we stay open and responsive and fix it. I'd recommend every team do the same. It's common courtesy, it keeps the landscape fair, and I'd love for it to become an industry norm.
Natalia AmorimContent Marketing Manager at PostHogTeams lose AI search visibility in different ways: nobody agrees what the category is called, the buying criteria are missing, sources contradict each other, or the leading pages have gone stale. Each problem has a different fix.
| Visibility problem | Risk | Next sprint | Outcome |
|---|---|---|---|
| Nobody agrees what the category is called | AI borrows language from adjacent categories, generic lists, or community shorthand, and describes you wrong. | Publish a category definition page, a problem explainer, a first comparison page, and how-to guides that show the use case in code. | AI can name the category and explain why your product exists. |
| The buying criteria are missing | Your site explains the product but not how to choose between options, so AI compares you on terms someone else wrote. | Build a comparison hub, alternatives pages for your closest rivals, integration pages for common stacks, and docs that state limits plainly. | You show up in comparison answers on the right criteria, not only when someone asks about you by name. |
| The sources contradict each other | Your docs, community threads, partners, and review sites each describe the product differently. | Find the third-party pages AI cites, refresh your own top pages, brief the credible authors, and set up a recurring review. | Your pages and the outside coverage tell the same story on every platform. |
| You lead, and the lead needs defending | Stale pages and outdated comparisons give challengers an opening in the answers. | Refresh market overviews, publish data, update migration content, and correct third-party pages that describe your old positioning. | You keep the top citation slots while shaping where the category goes next. |
| You are the challenger and need a wedge | On generic category questions, better-known competitors win before AI ever reaches your proof. | Target the questions incumbents ignore: neglected use cases, awkward tradeoffs, migration paths, and stack-specific how-tos. | You earn citations where being specific beats being famous. |
Similar to SEO, you want to optimize your discoverability at each stage of the user journey. This is especially true for lower authority brands. This helps build trust among users and authority among agents.
Alex RappHead of Growth Marketing at ClerkThese aren't generic content ideas. Each one is a page pattern that shows up repeatedly in the citation data. Start here, then check what your own category actually cites before setting priorities.
Teach AI what the category is, when it matters, and how to tell credible tools apart.
14.5% of citations come from comparison and list-style pages, and freshly updated market overviews keep appearing among the most-cited URLs.
A definition, use cases, common architectures, selection criteria, common mistakes, and a maintained overview of the market that doesn't rank yourself first.
Links to docs, examples, changelog entries, benchmarks, and credible third-party references.
Help AI compare options without leaning on third-party lists or unsupported vendor claims.
7.3% of citations are comparison pages, and vendor-written comparisons appear among the most-cited URLs.
Who each option fits, technical constraints, reasons to switch, tradeoffs, and honest cases where the alternative wins.
Screenshots, code-level differences, pricing notes, integration coverage, and customer or community evidence.
Prove the product works inside the stack developers actually use.
The questions that pull the most citations are hands-on: SDK performance, local testing, retries, background jobs, integrations, and build notifications.
Prerequisites, complete code, expected output, common errors, auth and setup notes, and next steps.
Runnable examples, GitHub repo links, package versions, and troubleshooting detail.
Turn technical facts into evidence AI can quote when it recommends tools.
Documentation is 17.3% of citations overall, and much higher in docs-led categories such as API Development & Management.
Supported workflows, limits, security model, compliance posture, API behavior, and example responses.
Reference links, changelog history, testable code, and precise language about limitations.
Create original data that other pages and AI answers can cite: proof that isn't just your own claim.
Recently updated best-tools posts, ranked editorials, and vendor market guides recur among the most-cited URLs.
Method, dataset scope, findings, limitations, ranked tables, charts, and what to do about it.
Downloadable data, transparent definitions, repeatable calculations, and dated updates.
Help partners and authors get your story right, so the coverage AI cites is accurate.
Domains outside the tracked brands account for 76.0% of citations.
Positioning, criteria, technical proof, comparisons, screenshots, example use cases, and what not to claim.
Public docs, GitHub links, customer examples, release notes, and benchmark references.
Developers are doing more and more of their work in tools like Claude Code. They're also making more and more of their decisions there too.
If you want to get picked by developers, you need to show up there too and AI Search is how that happens.
Ian VanagasTechnical Content Marketer at PostHogThis report is a fixed snapshot. DevTune tracks the questions, platforms, competitors, and pages that shape your own AI search visibility, week after week.
Short answers for founders, marketers, SEO, docs, and developer relations teams turning this data into a plan.
A DevTune report on which sources AI search platforms cite and which developer-tool brands appear in their answers. It covers 43 developer-tool categories, 478 tracked brands, 1,075 test questions, 54,747 recorded answers, 55,446 cited URLs, and 12,148 cited domains. It is written for founders, marketers, SEO, docs, and developer relations teams.
Five platforms: Google AI Mode, ChatGPT Search, Perplexity, Gemini Search, and xAI Search. Future editions will add more, including Microsoft Bing Copilot Search.
Yes. Future editions will add more platforms, including Microsoft Bing Copilot Search. Each platform still needs to be read separately, because they differ in which sources they pick, how many they cite, and how often they cite brand-owned sites versus community pages.
The most-cited content types in the dataset are blog post 34.3%, documentation 17.3%, discussion 8.8%, product page 7.5%, article 7.4%, comparison 7.3%, listicle 7.2%. No single format wins on its own: docs, product pages, comparisons, category explainers, and third-party coverage need to back up the same claims.
Decide which criteria you want to be judged on. Publish docs and comparison pages that AI answers can quote. Show up on the community and third-party sites AI already cites. Keep everything current. And measure each platform separately, because each one picks sources differently.
As the place your category gets defined, not as another SEO channel. If you don't spell out the buying criteria, AI will borrow them from competitors, listicles, and community threads, and describe your market in someone else's words.
Start with the six page patterns already earning citations: a category definition page, alternatives and versus pages, integration guides, docs proof pages, an original benchmark or report, and briefs that help third parties get your story right. Each page should answer one buyer question and include proof AI can cite. If you publish listicles, make them honest about fit rather than ranking yourself first.
No. A citation means the answer used your page as a source. A brand mention means your product appeared in the answer, while a recommendation goes further by endorsing it for the use case. In the vendor-authored ranked-page subset, 17.1% of citation events mentioned another tracked brand without mentioning the publisher. Teams should monitor citations, mentions, and recommendations separately to see whether cited pages ultimately support the publisher or another brand.
No. Some platforms cite a short, concentrated list of sources; others pull from a broad mix of community, editorial, docs, and video pages. One blended "AI visibility" number hides the specific work each platform needs.
The categories with the highest category openness scores in this analysis include IDEs & Code Editors, Open Source Commercial / OSS Infrastructure, Mobile Development Platforms & Cross-Platform, AI/ML Infrastructure & LLM Tools, and API Development & Management. The score weights citations per test (35%), cited-domain breadth (20%), lower average brand presence (25%), and lower tracked-brand citation share (20%). It compares openness in cited answers; teams should combine it with their own demand, pipeline, and brand data when setting priorities.
An interactive table of every measured category. You can sort by category openness score, citations per test, number of cited domains, docs share, blog share, comparison share, community share, brand presence, and more.
Pick your category and explore its numbers: category metrics, platform citation patterns, brand scorecards, and question topics. Use it to form a hypothesis about what to build, then check it against live monitoring for your own brand.
Yes. The Strategy Lab has CSV exports for the category heatmap, the citation-network matrix, and the question drilldowns.
Recently updated market overviews, ranked lists, vendor-written comparisons, and thorough docs explainers. The common thread: pages that help AI sort the market and compare options with real criteria and proof, not homepage positioning or unsupported "we are the best" claims.
The appendix lists every tracked brand in this edition, grouped by category. Where a public DevTune page exists, the brand or category links to it under /verticals so you can inspect the underlying data.
DevTune gives you the same view this report is built on, live for your own category: where you show up, which pages get cited, how competitors are moving, and which gaps to fix next.
Plain definitions for every term and metric in the report, in alphabetical order.
This appendix lists the 478 tracked public brands included in this version of the report, grouped across 43 developer-tool categories. Category headings link to the relevant vertical overview; brand names link to the matching public brand page when available.
This report shows the market pattern. Your next move is specific to your category: find the questions, platforms, competitors, and pages that shape the answers about you.