---
title: "AI Citation Rankings Need the Questions Behind Them: CrowdStrike in MRI's October 1 Comparisons"
description: "In MRI's October 1 cybersecurity comparisons, 17 of crowdstrike.com's 24 citations answered questions naming CrowdStrike. Two measurements, read separately."
canonical: "https://machinerelations.ai/research/segment-rank-question-set-named-brand-citations"
---

# AI Citation Rankings Need the Questions Behind Them: CrowdStrike in MRI's October 1 Comparisons

In MRI's October 1 cybersecurity comparisons, 17 of crowdstrike.com's 24 citations answered questions naming CrowdStrike. Two measurements, read separately.

Canonical URL: https://machinerelations.ai/research/segment-rank-question-set-named-brand-citations
Published: 2026-10-03
Research type: Reference
Published by: Machine Relations Research, founded by Jaxon Parrott
Data: release mri_score_v2.0+2026-10-01+b215170b2762 of the Machine Relations Index, created by Jaxon Parrott, CC BY 4.0.
Tags: measurement, citations, ai-search, methodology, cybersecurity

## Current Index data

Updated from the Index release through **2026-11-17** (mri_score_v2.1); observation window 2026-05-10–2026-11-17. This card updates with the published dataset.

- [huntress.com](https://machinerelations.ai/index/domains/huntress.com): 0.52% citation rate; 209 of 40,578 observed runs, tier B.
- [crowdstrike.com](https://machinerelations.ai/index/domains/crowdstrike.com): 0.38% citation rate; 153 of 40,578 observed runs, tier B.
- [reviewed.com](https://machinerelations.ai/index/domains/reviewed.com): 0.10% citation rate; 41 of 40,578 observed runs, tier C.
- [Cybersecurity](https://machinerelations.ai/index/categories/cybersecurity): 7 of 7 measurable question shapes clear the published evidence floor.

[Explore the Index](https://machinerelations.ai/index) · [Read the latest weekly report](https://machinerelations.ai/research/machine-relations-index-report).

## Source Body

AI citation rankings need the questions behind them. In MRI's October 1 cybersecurity comparison sample, crowdstrike.com was cited in 24 of 137 answers. Seventeen of those citations came in answers to questions that named CrowdStrike. That separates two useful measurements: being consulted when buyers evaluate a named vendor, and being selected when they have not named it.

Both are legitimate. When a buyer asks an engine to compare CrowdStrike with a rival, the vendor's own site is a reasonable source to cite, and being consulted there matters. Being chosen when the buyer has not named the vendor is a different result. A single segment rank combines the two, so reading it well means knowing how many of its questions name the brand. This page is a case study of one release of the [Machine Relations Index](https://machinerelations.ai/machine-relations-index) showing how to do that.

## Release and sources

Every figure on this page is from release `mri_score_v2.0+2026-10-01+b215170b2762`, window 2026-05-10 to 2026-10-01. No figure from any later release is used.

The question counts, topics and named/unnamed splits in this case come from the Index's internal run records for that release and are preserved in the evidence file below. The public API and linked Index pages serve the current release, not this historical snapshot. For current question context, inspect the returned fields as explained under **Running the public side yourself**; their availability depends on the release being served.

## The evidence

| Segment and domain | Runs whose question names CrowdStrike | Runs whose question does not |
|---|---|---|
| Comparisons (`x_vs_y`), crowdstrike.com | 17 of 32 | 7 of 105 |
| Comparisons (`x_vs_y`), huntress.com | 0 of 32 | 9 of 105 |
| News-driven (`news_topic`), crowdstrike.com | 9 of 14 | 42 of 609 |

| Segment | Questions behind it |
|---|---|
| Each cybersecurity segment other than news (best tools, how to choose, comparisons and the rest) | 7 |
| Cybersecurity news-driven | 32 |

A run is one question asked of one engine on one day, so many runs can come from few questions. In comparisons, 2 of the 7 questions name CrowdStrike, and they account for 32 of the 137 runs. In news, 1 of 32 questions names CrowdStrike, and it accounts for 14 of 623 runs.

Evidence file: [segment-rank-question-set-2026-10-01.csv](https://machinerelations.ai/data/research/segment-rank-question-set-2026-10-01.csv), sha256 `1c4726d8cf49ea7b5ca3102f024d01f400c7da039a97069880f33fc64dab1113`, 20 rows, all from release `mri_score_v2.0+2026-10-01+b215170b2762`. The 14 rows marked `public_artifact` give runs observed and runs citing the domain for crowdstrike.com and huntress.com across all seven cybersecurity question shapes, taken from the October 1 public artifact (sha256 `b215170b2762f837a6aa42c04e6a63a44bd693e89c48fef844d1384d664045ed`). The 6 rows marked `internal_run_records` hold the named/unnamed splits and question counts in the tables above, which come from the Index's internal run records.

## Two measurements, read separately

**Consulted on named evaluations.** On comparison questions that named CrowdStrike, crowdstrike.com was cited in 17 of 32 runs; on the one news question naming it, 9 of 14. This is what a vendor wants when a buyer is already evaluating it: the engine goes to the vendor's own material.

**Selected when unnamed.** On the 105 comparison runs whose question did not name CrowdStrike, we can examine which sources engines cited without naming CrowdStrike in the question. This does not establish that those questions named no other brands. On those 105 runs, CrowdStrike received seven citations and Huntress nine. These counts alone do not establish a general advantage for either domain. In news, crowdstrike.com was cited in 42 of the 609 runs whose question did not name it.

The combined figure, 24 of 137, is an accurate count. It describes the mix of questions the segment happened to contain. Change how many questions name a brand and that combined figure moves, with no change in how engines treat the brand. That is a reason to report the two parts, not a reason to distrust the count.

## Why the question set matters

A segment with seven questions describes those seven questions, not a market. Survey researchers have long known that [question wording and selection shape the answer](https://www.pewresearch.org/writing-survey-questions/), and that [questionnaire design](https://www.pewresearch.org/methods/u-s-survey-research/questionnaire-design/) is part of the result, which is why polling standards require [disclosing the exact questions asked](https://aapor.org/standards-and-ethics/disclosure-standards/). A citation index built on prompts inherits the same property. Language model answers can shift with [prompt formatting alone](https://arxiv.org/abs/2310.11324), and the work that framed [generative engine optimization](https://dl.acm.org/doi/10.1145/3637528.3671900) measured visibility per query for the same reason: the query set defines what is measured. How much rewording or repeating a question changes the sources an engine cites is measured in [a later Index analysis of reworded and repeated questions](/research/does-rewording-a-prompt-change-ai-cited-sources).

The Index publishes a rate only above an [evidence floor](https://machinerelations.ai/research/collecting-is-not-zero-citation-rate) of 10 observed runs on 7 distinct dates, and each segment here clears it. Clearing the floor means the number was measured. It does not mean the number generalises past the questions that produced it. Changes to how the Index reports question sets are recorded in its [methodology and update log](https://machinerelations.ai/research/ai-citation-index-correction-record-2026), on the model of [Google's Search Console data anomalies log](https://support.google.com/webmasters/answer/6211453). Index data is published under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), so the release identifier travels with any figure you quote.

## Running the public side yourself

An agent can pull the published, combined figures from the Index's [Model Context Protocol](https://modelcontextprotocol.io/specification/2025-06-18) server at `https://machinerelations.ai/mcp using standard [`tools/call` requests](https://modelcontextprotocol.io/specification/2025-06-18/server/tools) over [JSON-RPC 2.0](https://www.jsonrpc.org/specification), no authentication, or from the plain HTTP API. Two copy-and-run commands:

```bash
curl -s https://machinerelations.ai/api/mri/v2/domains/crowdstrike.com | jq '.segments[] | select(.category=="cybersecurity") | {questionShape, runsCited, runsObserved, rank}'
```

Lists crowdstrike.com's cybersecurity segments with question shape, runs cited, runs observed and rank.

```bash
curl -s -X POST https://machinerelations.ai/mcp -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"mri_get_domain","arguments":{"domain":"crowdstrike.com"}}}'
```

Returns the same domain record through the MCP tool `mri_get_domain`: overall citation rate, runs cited and observed, engines citing it, a confidence tier, rank, and per-segment rows.

Both commands return the current release, not October 1, so their counts will not match this page. Check `source.release.releaseId` and `artifactSha256` before combining results. The REST `release` parameter checks that the current release matches the one you hold; it does not retrieve an older release.

Read the live interpretation rules in `source.guidance`. Where a release includes them, `questionContext`, each segment's `questionSet`, and `naming` describe aggregate question counts and target-specific named, not-named and unresolved runs. Missing or null fields mean context is unavailable for that release, not zero. Read the returned method, review coverage and limitations before comparing sources. The exact question texts remain unpublished.

Each source's current naming buckets are relative to that source's reviewed names. They need not cover the same questions for two different sources. This historical table instead partitions **both** CrowdStrike and Huntress by whether a question names **CrowdStrike**. Do not substitute Huntress's own current naming split for that shared partition. The frozen evidence file is the record of this case; current aggregate API results cannot independently replay it.

## What this case does and does not show

It shows that, in this release, most of crowdstrike.com's comparison citations came from questions naming CrowdStrike, and that the segment's combined count mixes two measurements worth reading separately.

It does not show why engines cited any domain, which vendor security buyers should trust, or anything about specific pages. The Index measures domains; it stores which page was cited for each event but does not publish page-level results. A different question set would produce different counts, which is the point.

## FAQ

**Is it wrong for an engine to cite crowdstrike.com when the question names CrowdStrike?**
No. A question that names a vendor legitimately draws on that vendor's own site. Those citations measure being consulted on named evaluations, which is useful in its own right.

**Does this mean CrowdStrike is cited less than the Index says?**
No. The published counts are accurate observations. The split shows what kind of question produced them.

**Is CrowdStrike or Huntress ahead on unnamed comparison questions?**
On the 105 unnamed runs, CrowdStrike received seven citations and Huntress nine. These counts alone do not establish a general advantage for either domain.

**Can I get the named/unnamed split from the API or MCP server?**
For the current release, inspect `questionContext` and each segment's `naming` in the returned record: populated fields provide aggregate splits with their method and limitations; missing or null fields mean unavailable. The October 1 table on this page is preserved in the linked evidence CSV, not served as a historical API query. Follow the current [agent-access guidance](https://machinerelations.ai/index#use-with-ai-agents) and the rules included in each response.

## The short version

- A segment rank describes its questions. Find out how many there are and what they ask.
- Split a vendor's citations by whether the question names it: consulted on named evaluations, selected when unnamed.
- Quote one release, and say which.
- Small unnamed counts are a starting point, not a ranking.

## Attribution

Cite this research: Machine Relations Research, founded by Jaxon Parrott. "AI Citation Rankings Need the Questions Behind Them: CrowdStrike in MRI's October 1 Comparisons." October 3, 2026. https://machinerelations.ai/research/segment-rank-question-set-named-brand-citations

Data: release mri_score_v2.0+2026-10-01+b215170b2762 of the Machine Relations Index, created by Jaxon Parrott, CC BY 4.0.

This research is published by Machine Relations Research, the research program of machinerelations.ai — the public research initiative that publishes the glossary, research, evidence, and measurements for the Machine Relations discipline. Provenance and editorial standards: https://machinerelations.ai/about

## Machine-readable related links

### Related concepts

- [Machine Relations Index (MRI)](https://machinerelations.ai/glossary/machine-relations-index)
- [MRI Score](https://machinerelations.ai/glossary/mri-score)
- [Machine Relations (MR)](https://machinerelations.ai/glossary/machine-relations)
- [Citation Rate](https://machinerelations.ai/glossary/citation-rate)

### Supporting research

- [Do AI Citation Leaderboards Change Between Daily Releases? What the Machine Relations Index Re-Measures](https://machinerelations.ai/research/ai-citation-leaderboard-movement-between-releases-2026)
- [How Many Sources Does a Typical AI Answer Actually Cite? Published Counts Range From 2 to 22](https://machinerelations.ai/research/ai-citation-density-per-answer-denominator-2026)
- [Machine Relations Index Update Log: Known Data Issues and Methodology Changes](https://machinerelations.ai/research/ai-citation-index-correction-record-2026)
- [Only 508 of 22,377 AI-Cited Domains Are Cited Often Enough to Score](https://machinerelations.ai/research/ai-citation-evidence-floor-scoreable-domains-2026)

### Framework context

- [Machine Relations Index](https://machinerelations.ai/index)
- [Machine Relations Stack](https://machinerelations.ai/stack)
- [Evidence Base](https://machinerelations.ai/evidence)
