{
  "slug": "serp-brand-mentions",
  "name": "Brand mentions on the results page",
  "aliases": [
    "Total SERP mentions",
    "Brand mention count"
  ],
  "definition": "How often a brand is mentioned across a segment's observed results pages, counted per domain from the brand-mention dataset.",
  "category": "Competitive SERP",
  "type": "raw measure",
  "unit": "mentions",
  "direction": "higher-better",
  "verification": "review",
  "aggregation": "Would be a count summed across the segment's observed results pages for one domain at a time.",
  "grain": "One domain × segment × period × medium.",
  "dimensions": [
    "competitor domain",
    "intent",
    "brand",
    "country",
    "device"
  ],
  "requiredFilters": [
    "segment_id",
    "selected_period",
    "source_medium"
  ],
  "sources": [
    "rank-tracking"
  ],
  "reports": [],
  "skills": [
    "serp-feature-watch",
    "competitor-deep-dive"
  ],
  "verbs": [
    "competitive_overview",
    "competitive_trends"
  ],
  "rungs": [
    "R2",
    "R4"
  ],
  "levers": [
    "L6"
  ],
  "questions": [
    "How often is our brand mentioned across these results pages?",
    "Is a rival mentioned more than we are?"
  ],
  "caveats": [
    "The family is gated in code: both verbs throw a not-yet-supported error before any read.",
    "The dataset, the mention measure and the per-competitor domain dimension all resolve in the semantic layer, so what is missing is the reconciliation against the product, not the fields, and a check found the figures several times off.",
    "The measure is defined as a sum of a validated-visible mention column that falls back to a legacy machine-generated count, so two periods can be counted on different bases without saying so.",
    "The customer-side measure name is carried in the registry as a hypothesis.",
    "The tenant used to confirm the fields returned no rows for this family, so field validity was established without data volume behind it."
  ],
  "freshness": "~1 day behind, Daily observation, available the following day.",
  "failureModes": [
    "Publishing a mention count that has not been reconciled, which reads as authoritative because the field resolves.",
    "Treating a results-page mention as an answer-engine mention, different surfaces entirely."
  ],
  "notSameAs": [
    {
      "slug": "serp-mention-polarity",
      "why": "This is the total; polarity counts split the same population by tone and are separate measures with their own reconciliation status."
    },
    {
      "slug": "ai-mention-count",
      "why": "On-SERP brand mentions are observed in Google search results. AI-answer mentions are counted inside answer-engine responses. A brand can be mentioned constantly on the SERP and never inside an answer."
    },
    {
      "slug": "serp-brand-coverage",
      "why": "Mentions are a count of occurrences; coverage claims to describe spread across pages, and the two cannot be derived from each other until the coverage scale is defined.",
      "mirroredFrom": "serp-brand-coverage"
    }
  ],
  "related": [
    "serp-mention-polarity",
    "serp-sentiment-share",
    "serp-brand-coverage"
  ],
  "workflows": [],
  "lastVerified": "2026-08-04"
}