Model analysis · September 2026

AI SRE + Observability Brands — AI Overview Position Reality & Market Analysis

A data-driven audit of 20 observability and AI SRE brands. For every commercial term each brand claims on its own pages, we measured whether Google's AI Overview actually cites the brand for that term — or hands the answer to someone else. This report is a proof of concept: AI-visibility research can produce defensible content priorities, not guesses.

September 2026 91 curated commercial terms · 284 AIO citations analysed Muninder Adavelli Source & reproducibility

What the data says

Eight numbers from the study, ordered by what a Head of Marketing or Head of Content should worry about first.

87.7%
of AI Overview citations across the industry go to non-vendors — YouTube, IBM, Wikipedia, generic explainer blogs. Only 12.3% land on any vendor in the corpus.
9.6%
Industry-average brand fidelity on its own claimed vocabulary. Brands land in the AI Overview for a term they claim only 1 in 10 times.
92%
of invented-category terms (claimed by exactly one brand) answer the buyer with someone else. 84 of 91 terms are invented by a single vendor; the answer engine cites its inventor 8% of the time.
12 / 18
brands land in AI Overviews on zero of their claimed terms. Includes Edge Delta, Rootly, Snowflake, New Relic, dbt Labs, Great Expectations, Soda.
77%
of the time an AI Overview triggers on a term you claim, a competitor is cited instead. Vocabulary ownership does not defend the answer slot.
84 / 91
curated commercial terms are open whitespace — only 1-2 brands claim them and buyers are actively researching. Uncontested demand.
94.5%
of curated commercial terms do trigger an AI Overview. Buyers are researching in the answer, not the link list. The demand is real.
17 vs 7
IBM & YouTube each get cited 17× across the 91 terms. Datadog — the largest observability vendor — is cited 7×. The generic explainer sources beat every single vendor.

The market is not AEO-optimized

The observability & AI SRE category has fully migrated to AI-answer search — 94.5% of its commercial vocabulary triggers an AI Overview. The vendors have not migrated with it. Their websites still read like 2018 SEO product pages. The measurement below is the direct consequence.

Where every brand claim lands, across the industry

Industry aggregate: 9.6% brand ranked, 85.1% competitor ranked, 5.0% no AI Overview trigger
Every claim by every brand on any of the 91 curated terms, one big bar. Brand ranked = the brand claiming the term is cited. Competitor ranked = someone else is. No AI Overview = the search didn't trigger an answer.

The 85% competitor-ranked share is not a per-brand failure — it is a category-level failure. When an observability brand claims a commercial term on its website, roughly nine times out of ten the AI Overview hands the answer to a different source. The vocabulary is real, the buyer demand is real, and the answer engine is real. What is missing is content that AI Overviews will cite.

The per-brand distribution

Per-brand leaderboard showing 12 of 18 brands never rank in AI Overviews for their own claimed terms
Twelve of eighteen scored brands never rank in AI Overviews for their own claimed terms. Six brands account for every "brand ranked" point in the industry.
Note: 2 of the 20 corpus brands (Atlan, Metaplane) claim zero of the 91 curated commercial terms and don't appear on this leaderboard. Their positioning language sits entirely outside the buyer-research vocabulary — that absence is its own finding.

Datadog leads — the brand ranks on 50% of its six claimed terms. Incident.io is second, ranking on 42.9% of its seven claimed terms. These are the only two brands in the study that ship product-page content the AI Overview consistently agrees with. The other sixteen either don't rank at all, or rank on a small fraction of what they claim.

Every term, placed by demand and claim count

Demand versus claim quadrant. 84 whitespace terms, 2 battleground terms, 5 dead terms, 0 collective delusion terms
Ninety-two percent of the curated vocabulary is whitespace: buyer demand proven, competition negligible. Two terms are actively contested. Five are dead — nobody claims them and buyers don't ask.
The market-maturity read. A mature AEO category shows a large battleground bucket (many brands fighting for shared terms buyers actively research) and a small whitespace bucket. This category is the inverse: 84 whitespace terms, 2 battleground. Vendors are still coining unique vocabulary for branding reasons, not competing for buyer-research demand.

Why this matters, in one line

The invented-category disconnect

Brands invent categories to sound differentiated on their homepage. But every invented category is also a search term buyers might type. When they do, an AI Overview almost always triggers — and the brand that coined the term is cited almost never. This is the argument for why branding strategy and AEO strategy have to be built together, not sequentially.

What "someone else answers" looks like — one worked example

incident.io coined "incident response" as core positioning. When a buyer types incident response into Google today, the AI Overview cites cisa.gov (US federal cybersecurity), huntress.com (security vendor from an adjacent category), and ibm.com (generic knowledge base). The vendor whose homepage opens with that phrase is not in the answer.

Why this happens. AI Overviews are trained to prefer sources that explain a term over sources that brand it. incident.io's page says "AI SRE that investigates incidents like your most tenured engineer." IBM's page says "What is incident response? Incident response is an organization's process of…". The second gets cited because it answers the question the buyer is asking. The first sells to a buyer who has already decided.

The dead-vocabulary shortlist

Five terms in the study have zero AI Overview trigger — coined by a single brand, ignored by every buyer. These are pure branding-side inventions that produced no measurable search demand.

Coined termCoined byBusiness relevance
telemetry-native AI SREEdge Delta93.3
Intelligent Telemetry PipelinesEdge Delta93.3
Dependency Driven MonitoringBigeye93.3
AI-era observabilityOpenObserve63.3
costly data quality issuesDatafold80.0

The Qwen-scored "business relevance" of these terms is high — 93.3 out of 100 for three of them — because the vocabulary reads like something a buyer would type. But nobody does. The rubric measures whether a term sounds buyer-relevant. AI Overview trigger data measures whether it is. That gap is the branding-vs-AEO disconnect, quantified.

Who's inventing the most vocabulary — and losing it

Per-brand breakdown of solo-claimed vocabulary and what happened to it in AI Overviews. Column headings: Claims = solo-invented terms this brand owns. Won = brand ranks in the AIO for that term. Lost = AIO triggers but a competitor / generic source wins the citation. Dead = no AIO triggers at all.

Brand Solo claims Won Lost Dead
Informatica141130
Soda8080
New Relic7070
Snowflake7070
Edge Delta6042
OpenObserve6141
incident.io5230
Datadog5230
Rootly5050
Acceldata4130

Two shapes emerge. Informatica, Soda, New Relic, Snowflake, and Rootly invent heavily and win nothing — vocabulary produced for the homepage, unsupported by content the AI answer engine can cite. Edge Delta produces two dead terms (no buyer research at all), which is worse than losing — it means the coining effort didn't even reach a search box. incident.io and Datadog are the outliers who win any of their invented vocabulary at all, and each wins only 2 of 5. Nobody in this study wins more than 40% of what they coin.

The disconnect, restated. A brand's product-marketing function is measured on differentiation — "we own this category." AEO is measured on citation — "the answer engine cites us for the term buyers ask." These two measurements are treated as separate workstreams by most enterprise marketing teams. This section is one datapoint arguing they can't be. When branding and AEO are sequenced (brand first, then SEO retro-fit), the branded vocabulary lands in AI answers 8% of the time. The category-invention play only works if the content depth to support it lands at the same time as the vocabulary.

YouTube — a channel to invest in

When the observability + AI SRE category loses an AI Overview citation to a non-vendor, it usually loses to YouTube or IBM. The pattern is unambiguous and repeats across the top 15 non-vendor winners. What's more interesting is that most vendors in the study already have a YouTube channel — they just don't publish the kind of content that gets cited.

Who wins the industry's contested AI Overview share

Top 15 domains cited when a brand's claimed term is contested. IBM and YouTube tied at 17 each
Every time a brand claims a term and the AI Overview cites a different domain, that domain gets +1. Top 15 shown. Red = vendor in the study. Grey = non-vendor / generic source.

Every vendor already has a YouTube channel. Almost none publish for AI Overviews.

A quick audit of the brands in the study:

Channel Subs (approx) Content pattern
@Databricks ~100k Tutorials, listicles, branded and non-branded info content. The only channel in the study actively producing content the AI answer would cite.
@DatadogHQ ~30k Almost every video is brand-centric — product launches, customer stories. No topical explainer content. The channel isn't optimised for AEO discovery.
@EdgeDelta small Product demos, comparison videos. Low volume, brand-only.
@incident-io small Product-centric. Occasional practitioner interviews.
@acceldatainc small Webinar recordings. No topical explainer.
@AnomaloAi small Product walkthroughs, minimal reach.

A quick glance at either of the largest two channels tells the story: the top-viewed video on both Databricks and Datadog is a variant of "What is observability?" or "What is a lakehouse?". The single most-watched thing on each brand's channel is the piece of explainer content Google is already citing. Neither brand is producing more of it deliberately.

Why explainer format still wins, three years in

For the entire time I worked on SEO at Edge Delta, the pages that ranked in classic Google search for commercial terms were blog posts — not product or use-case pages. The AI Overview era hasn't changed that pattern, it has amplified it. What changed is the format the answer engine now expects: a definitional intro, followed by a comparison section, followed by an FAQ. Blogs already written that way get cited. Product pages don't get cited at all.

The bottleneck is org-chart, not technical. Enterprise product-marketing teams resist rewriting the product page to look like an explainer — it feels off-brand and dilutes the sales pitch. Fair concern when the average deal is 6-7 figures and decisions involve five stakeholders. But it means the AEO surface is being ceded to sources that have made that trade-off (Databricks channel, IBM knowledge base, YouTube tutorials). This is a fixable org problem, not a fixable content problem.

The dirty solution — a 10-day test

A short-term hack for enterprise brands unwilling to rewrite product pages: embed sales-qualifying CTAs inside the explainer content that already ranks. incident.io's blog post on the AI SRE definition ranks in both the classic SERP and the AI Overview — but the first fold contains no demo CTA, no lead-capture form, no in-content "book a call" link. A purely awareness-driven visitor with no conversion path.

A single 10-day test — add a first-fold demo CTA to the top three AIO-ranking blog posts, measure demo conversions — is the fastest way to determine whether AEO-earned traffic behaves like SEO-earned traffic for a given brand. Small effort, disproportionate signal, and the result answers a much bigger question: is search truly a helping-hand channel for this brand, or is it a real acquisition channel that has been under-instrumented?

Two paths — Datadog vs incident.io

The two brands with real AI Overview fidelity in this study take almost opposite paths to get there. Datadog covers every category surface with a product line — and still ranks in the AIO for only three of six terms. incident.io targets one narrow cluster (incident response & AI SRE) — and ranks in the AIO for three of seven. The comparison is the argument for targeted semantic map optimisation over broad category coverage.

Datadog

Broad category coverage · every product surface, everywhere
  • 6claimed terms in the 91-term study
  • 3brand ranks in AI Overview (50%)
  • 3competitor ranked instead
  • 7times cited across the whole industry — trails IBM (17) and YouTube (17)

Where Datadog ranks

  • Observability Pipelines
  • Observability Platform
  • Cloud Cost Management

Where Datadog loses the citation

  • AI-Powered Observability and Security
  • Security and Observability → Cisco, Dynatrace, Huntress
  • DevSecOps → IBM, GitLab, Red Hat, YouTube
The Datadog paradox. Datadog ships a product for nearly every term in the observability + AI SRE study. It's the biggest observability vendor in the world. And it's cited seven times across 91 terms. Product surface area does not translate to AI Overview fidelity. Content depth on specific pages does — Datadog's wins map to product pages that describe the category, not to product pages that launch a feature.

incident.io

Narrow semantic cluster · incident response + AI SRE, nothing else
  • 7claimed terms in the 91-term study
  • 3brand ranks in AI Overview (42.9%)
  • 4competitor / no answer
  • 97.1avg business relevance score of its claimed terms — highest of any brand

Where incident.io ranks

  • incident management platform
  • incident management software
  • AI SRE

Where incident.io loses the citation

  • end-to-end incident management
  • incident response → CISA, IBM, Huntress, SANS
  • agentic root cause analysis
  • AI-powered incident summaries
The incident.io pattern. Every one of the seven terms sits in the same semantic cluster — the incident-response / AI-SRE knowledge graph. The three wins all describe the core category ("incident management platform / software / AI SRE"). The four losses are further out in the cluster and go to entities with deeper explainer coverage (CISA for security compliance framing; IBM for the reference-definition; SANS for training material). Even the losses stay within the semantic neighbourhood the brand chose to own.

The read: targeted semantic map beats broad product surface

Both brands land in AI Overviews at roughly the same rate (50% and 43%). Both are the industry-leaders at what they do (Datadog by scale, incident.io by focus). But the cost of that fidelity is completely different. Datadog produces content across the entire observability + security stack and lands in three answers. incident.io produces content in one narrow neighbourhood and lands in three answers — with a 97.1 average business-relevance score on those terms, the highest of any brand in the study.

For a client with a fraction of Datadog's marketing headcount, the incident.io pattern is the only replicable one: pick a narrow semantic cluster, own every term within it end-to-end, resist the urge to expand until every high-relevance term in the cluster is either won or actively being contested. That's what "targeted semantic map optimisation" means in practice, and this section is the two-brand exhibit for it.

Non-vendor share of voice

Across all 91 curated commercial terms — the vocabulary these 20 vendors coined and put on their own product pages — Google's AI Overview cites non-vendor sources 87.7% of the time. The entire vendor category has effectively ceded its own answer real estate.

Donut chart. 87.7% of AI Overview citations go to non-vendor sources. 12.3% go to any vendor in the corpus.
One-in-eight citations across the 284 AIO references on 91 vendor-coined commercial terms lands on a vendor from the corpus. The rest goes to generic knowledge bases, tutorials, forums, and adjacent-category vendors.

Who's picking up the citations vendors won't

The top 15 non-vendor domains ranked by citation count across the 91-term study:

RankDomainCitationsWhat it publishes
1youtube.com19Vendor and independent tutorials; explainer video is the format AIO prefers for "what is X" queries
2ibm.com15The IBM knowledge base — encyclopedic definitions of every observability, security, and data term
3montecarlo.ai6Ex-corpus data observability vendor; still cited on data-quality terms via its resource centre
4dynatrace.com6Adjacent-category APM vendor; ranks on security/observability crossover terms
5google.com5Google Cloud docs; wins on cloud-cost / cloud-native terms
6splunk.com5Adjacent SIEM vendor with strong resource-page SEO history
7paloaltonetworks.com5Security incumbent; wins on incident-response / security cross-references
8reddit.com4Practitioner discussion threads; still ranks post-August-2026 update for niche technical queries
9actian.com4Data-management vendor; wins on data-integration / lineage terms
10ovaledge.com4Data governance vendor with a heavy explainer-blog strategy
11–15github.com · cyberhaven.com · linkedin.com · wiz.io · microsoft.com3 eachMix of security vendors and platform giants

Two patterns in one leaderboard

The top-10 non-vendor list breaks cleanly into two groups. Explainer platforms — YouTube, IBM, Reddit, GitHub — win when the query is definitional. Adjacent-category vendors — Dynatrace, Splunk, Palo Alto Networks, Cisco (below top 15) — win when the query straddles two categories that the corpus brands have chosen to differentiate against but not to publish about.

The finding, sharpened. Non-vendor sources aren't just picking up scraps. They are the primary answer for 88% of the vendor category's own vocabulary. This is not a distribution problem. It's a content-production problem: the vendors in this study collectively write about their categories in a way the AI Overview does not cite. Every AEO campaign in this space is competing with IBM's definition and YouTube's explainer video before it competes with a peer vendor.

Per-brand visibility scorecard

Every brand in the study reduced to four numbers and one name. Opportunity = claimed terms where an AI Overview actually triggers (the answer surface is there to be won). Actual = the brand is cited. Landed = actual ÷ opportunity. Losing to = the domain most often cited on this brand's contested terms.

Brand Opportunity Actual Landed Losing most often to
Informatica1417.1%accesscorp.com · atlan.com · claravine.com
Soda1000.0%ibm.com (4) · youtube.com (4) · montecarlo.ai (3)
incident.io7342.9%cisa.gov · huntress.com · ibm.com
Rootly700.0%augmentcode.com · clickhouse.com · datadoghq.com
New Relic700.0%clickhouse.com · datadoghq.com · github.com
Snowflake700.0%paloaltonetworks.com (2) · crashplan.com · informatica.com
Datadog6350.0%blackduck.com · gitlab.com · ibm.com
OpenObserve6116.7%datadoghq.com (2) · motadata.com (2) · youtube.com (2)
Edge Delta500.0%resolve.ai (2) · augmentcode.com · clickhouse.com
Great Expectations500.0%montecarlo.ai (3) · actian.com (2) · ibm.com (2)
Acceldata4125.0%acm.org · biomedit.ch · github.com
Anomalo400.0%—
Resolve AI3133.3%apple.com · google.com · youtube.com
dbt Labs300.0%ibm.com (2) · youtube.com (2) · actian.com
Datafold300.0%actian.com (2) · gartner.com · getcollate.io
Bigeye200.0%ibm.com (2) · montecarlo.ai (2) · youtube.com (2)
Collibra200.0%cyberhaven.com (2) · datahub.com · dataversity.net
Databricks100.0%—

Three groups fall out of the same number

Category-inventors (0% landed). Twelve brands claim commercial vocabulary and land in zero AI Overviews. Includes both the AI SRE cluster (Edge Delta, Rootly) and the data-quality cluster (Soda, Anomalo, dbt Labs, Great Expectations, Datafold, Bigeye). Each of these has coined vocabulary without producing the content to defend the answer slot.

Selective winners (25-50% landed). Six brands land in some AIOs. incident.io and Datadog top the list at 42-50%; Resolve AI and Acceldata cluster in the 25-33% range; OpenObserve and Informatica trail. Every one of them wins on narrowly-scoped terms and loses on broader ones — a consistent pattern across the whole scoreable population.

Under-instrumented (opportunity=1 or 2). Databricks, Collibra, Bigeye. Small footprint in the study means small denominator — not necessarily a marketing failure. The signal these brands would want to measure is outside the 91-term set (their real vocabulary sits in the terms we filtered out as too-branded or non-commercial). Which is itself the finding for those brands: their positioning language isn't the commercial vocabulary buyers type.

How this table is read as a content plan. Every 0%-landed row is a whitespace intervention — the terms are proven demand, the brand claims them, nobody currently owns the answer. Every 42-50% row shows where narrow content strategy has already worked and where the pattern can be extended (the incident.io and Datadog wins are the reference implementation). Every "losing most often to IBM / YouTube / Reddit" tells you what content format the AIO expects for that term — encyclopedic definition, video tutorial, or practitioner discussion. Match the format and the citation follows.

What this changes for content strategy

The argument this report makes: for enterprise B2B SaaS with long sales cycles and multi-stakeholder buying, AI visibility research is a stronger foundation for content strategy than classic SEO keyword research. Below is why the numbers in this study support that, and what a client engagement built on this framework would actually look like.

Why AI visibility beats classic SEO for this buyer profile

Classic SEO keyword research tells you which terms have volume. It does not tell you which stakeholder types the term, what pain the term signals, or whether the answer engine will cite a vendor for it. For a Datadog-scale purchase decision — 5-figure ACV minimum, five stakeholders across SRE / Platform / Security / Finance / Engineering Leadership, 6-12 month evaluation cycle — knowing "this term has 8,100 monthly searches" is a start, not a plan.

Every term in this study was scored against a published rubric on four dimensions before it was measured for AIO visibility:

That is four extra dimensions before you write a single word. Every content decision that comes out of this framework maps to a specific stakeholder in the buyer committee, a specific pain the term describes, and a specific lifecycle stage (definitional at the top, commercial at the bottom). That's how you turn "we should rank for observability" into "we should rank for the four AI-SRE-adjacent buyer terms our Platform Lead persona types at the evaluation stage, and here are the three IBM pages we'd need to displace on each."

What a content plan built from this framework contains

Three things classic SEO keyword lists don't have:

  1. Stakeholder mapping per term. Every term in the plan is tagged to the persona likely to search it. Marketing knows whether the piece is written for the IC evaluator or the budget-owner. This is impossible from a bare keyword list.
  2. Business-relevance weighting. A term at Pain=3, ICP=3, Stakeholder=3 gets 20× the attention of a term at Pain=1. This maps content investment to buying-committee value, not to monthly search volume. Search volume is downstream of business value in this market; buyer intent isn't.
  3. Answer-engine format guidance. The domain currently cited on each term is the format the AIO expects. "IBM cites for this term" → publish an encyclopedic explainer with a definition-first structure. "YouTube cites for this term" → publish a video-first companion. "A security vendor cites for this term" → the AIO believes this is a security query even if you sell into observability; the strategic call is whether to fight the framing or accept it. None of this signal is available from keyword volume alone.
The pitch line. In a market where 85% of vendor claims are answered by a competitor and 88% of the answer surface goes to non-vendors, the marketing team that continues to prioritise keyword-volume-first SEO is optimising for a channel that no longer converts. The marketing team that prioritises AI-visibility-first content is optimising for the channel the buyer actually uses. Same content budget, different denominator, different result.

How this scales beyond a single report

This report analysed 20 brands, 91 terms, 284 AIO citations. Every step — profile extraction, term deduplication, DataForSEO pulls, Qwen classification, priority quadrant — is fully reproducible from the source repo. Running the same pipeline against a new brand corpus (payments, cybersecurity, dev tooling) takes days, not weeks, and produces the same kind of stakeholder-mapped, pain-scored, AIO-measured content plan for that market. This report is the model. The next application is a client engagement.

Two applied examples

Two clusters from the study, run through the framework end-to-end. Each cluster is a coherent slice of vocabulary a client might realistically own. The point: this is the shape of the deliverable a client engagement would produce for a term set of their choosing.

Cluster 1 — Data Quality Automation

12 terms in the study cluster around data quality tooling and automation.

TermClaimed byRelevanceAIO status
Data Quality PlatformDatafold · Great Expectations93.3Competitor ranked
data quality solutionGreat Expectations93.3Competitor ranked
end-to-end solution for data qualityGreat Expectations93.3Competitor ranked
automated data quality monitoring platformAnomalo93.3Competitor ranked
Automated Record-level ResolutionSoda93.3Competitor ranked
data quality issuesSoda80.0Competitor ranked
data quality frameworkdbt Labs · Great Expectations80.0Competitor ranked
data quality and observabilityInformatica80.0Competitor ranked
data integrity issuesInformatica80.0Competitor ranked
AI-native Data QualitySoda70.0Competitor ranked
data quality testsGreat Expectations63.3Competitor ranked
costly data quality issuesDatafold80.0No AI Overview
Read of the cluster. High ICP, high pain, competitors visible, target-brand visibility zero. This is the textbook "attack first" scenario. Five brands are simultaneously investing in data-quality vocabulary and none is producing the content the AI Overview will cite. The winner is whichever brand publishes the definitive explainer for the highest-relevance terms (Data Quality Platform, data quality solution, end-to-end solution for data quality) first, in a format the AIO already prefers on similar queries. IBM's data-quality glossary + Monte Carlo's resource centre are the two competitor patterns to study.

Cluster 2 — Data & Systems Observability

10 observability-platform terms in the study — the core category vocabulary of the entire market.

TermClaimed byRelevanceAIO status
Observability PlatformDatadog · OpenObserve90.0Brand ranked
full-stack observabilityOpenObserve93.3Brand ranked
Data ObservabilityBigeye · Soda93.3Competitor ranked
Enterprise Data ObservabilityAcceldata93.3Competitor ranked
Real-Time ObservabilityAcceldata100.0Competitor ranked
unified observabilityOpenObserve83.3Competitor ranked
Intelligent ObservabilityNew Relic100.0Competitor ranked
All-in-one observability platformNew Relic90.0Competitor ranked
AI-Powered Observability and SecurityDatadog100.0Competitor ranked
AI-era observabilityOpenObserve63.3No AI Overview
Read of the cluster. Strong ICP, strong use case, high AIO activity — but a persistent content gap. Even Datadog only wins on the bare "Observability Platform" term; it loses on every modifier ("AI-Powered", "Security-and", etc.). The cluster's real lesson: the modifier layer of observability vocabulary is unclaimed answer surface. Six modifiers with proven demand, non-vendors currently cited, no brand ranks. Whichever vendor publishes the modifier-layer explainers (real-time observability, intelligent observability, unified observability) before its peers own the next round of category answers.

What a client would take from this report

Two clusters, run in about a day of pipeline time, produce a defensible content roadmap for two distinct product surfaces. The same pipeline extended to a specific client's brand + top 3 competitors produces a bespoke version of the same analysis for their exact term set. That's the model this report proves out — and the offer it makes visible.