> ## Documentation Index
> Fetch the complete documentation index at: https://developers.scrunch.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Brand Presence & Visibility

> Starter MCP prompts that calculate your AI visibility score and establish where your brand stands across tracked prompts, platforms, and reporting cycles.

Start here. These four prompts give you a complete picture of \[brand name]'s visibility across all tracked prompts and platforms before you dig into gaps or competitive analysis.

Replace `[brand name]` with the brand you're analyzing and paste directly into Claude with Scrunch connected.

***

<AccordionGroup>
  <Accordion title="Calculate Your AI Visibility Score">
    Overall visibility rate across all tracked prompts and platforms, ranked by AI model.

    ```text theme={null}
    For [brand name] in Scrunch, calculate the brand's overall AI visibility rate.

    1. Pull the total number of prompt variants tracked for [brand name] — count only
    2. Pull the count of variants where brand_present = true — count only
    3. Calculate the visibility rate: (brand present / total) × 100
    4. Break this down by platform — run the same brand_present=true count filtered to each LLM (ChatGPT, Perplexity, Claude, Gemini, Grok, Meta)
    5. Rank platforms from highest to lowest visibility rate

    Present the overall rate, the platform breakdown, and flag any platform where [brand name] is significantly above or below its average.
    ```
  </Accordion>

  <Accordion title="See Exactly Where You're Winning">
    Which queries and topics is \[brand name] already appearing in? What patterns explain those wins?

    ```text theme={null}
    For [brand name], pull prompt variants filtered to brand_present = true. Limit to 50 results.

    For this set, tell me:
    1. Which platforms have the most brand presence
    2. Which tags or topic categories appear most frequently — what topics does [brand name] win on?
    3. Are these primarily branded queries (someone asking directly about [brand name]) or unbranded category queries?
    4. What does the brand appear to be doing well based on the types of prompts where it appears?
    ```
  </Accordion>

  <Accordion title="Check Branded Query Coverage">
    Is \[brand name] showing up every time someone asks an AI about it directly? It should be — flag if not.

    ```text theme={null}
    For [brand name], pull prompt variants filtered to:
    - branded = true (queries specifically asking about [brand name])
    - brand_present = false

    Count how many branded queries exist where [brand name] is NOT appearing in AI responses. This should be zero or near-zero for a healthy brand — flag if it's significant. List up to 20 of these prompts so I can see which branded queries the brand is missing.
    ```
  </Accordion>

  <Accordion title="Compare Visibility Across AI Platforms">
    Side-by-side visibility rates for every platform — which are strong, which are priority gaps?

    ```text theme={null}
    For [brand name], run the following and report counts for each:
    1. Total prompt variants (no filter)
    2. brand_present = true, platform = chatgpt
    3. brand_present = true, platform = perplexity
    4. brand_present = true, platform = claude
    5. brand_present = true, platform = gemini
    6. brand_present = true, platform = grok
    7. brand_present = true, platform = meta

    For each platform, calculate the visibility rate vs. total variants on that platform. Rank platforms. Flag any where visibility is under 20% — those are priority gaps.
    ```
  </Accordion>
</AccordionGroup>

***

<CardGroup cols={2}>
  <Card title="Visibility Gaps & Content Opportunities" icon="magnifying-glass" href="/mcp/prompts/visibility-gaps">
    Find where the brand is absent and which gaps are most urgent to address.
  </Card>

  <Card title="Weekly AI Brief → Notion & Slack" icon="calendar" href="/mcp/workflows/weekly-ai-brief">
    Use these numbers in an automated weekly brief saved to Notion and posted to Slack.
  </Card>
</CardGroup>