> ## 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.

# Configuration & Maintenance

> Audit your Scrunch setup, find duplicate prompts, check platform coverage, standardize tags, and clean up stale configuration with conversational MCP prompts.

A clean configuration produces accurate data. Use these prompts to audit your setup before a reporting cycle, clean up stale or duplicate prompts, and ensure your tag structure stays consistent as brands and teams grow.

***

<AccordionGroup>
  <Accordion title="Full Configuration Audit">
    Are the right competitors, tags, and prompts in place? Flag gaps that would skew your visibility data.

    ```text theme={null}
    For [brand name], run a full configuration audit:
    1. List all competitors — are any major players missing from the industry?
    2. Get all tags — do the tags represent the full scope of how buyers research this category?
    3. Pull total variant count — are there enough prompts to generate statistically meaningful data?
    4. Pull branded = true variant count — do branded queries make up a reasonable share of tracking?
    5. Pull branded = false variant count — are enough unbranded category queries being tracked?

    Flag any gaps in configuration that would skew the visibility data.
    ```
  </Accordion>

  <Accordion title="Find and Remove Duplicate Prompts">
    Identify near-duplicate prompts within a tag group before they inflate counts and distort visibility rates.

    ```text theme={null}
    For [brand name], pull all seed prompts tagged as [tag name]. Review the prompt text for duplicates, near-duplicates, or prompts so similar they're tracking the same query twice. List candidates for archiving. Do not archive anything without my confirmation.
    ```
  </Accordion>

  <Accordion title="Check Platform Coverage Gaps">
    Are any prompts running on some platforms but not others when they should be everywhere?

    ```text theme={null}
    For [brand name], pull seed prompts and their variant_scenarios field. Identify any seed prompts that are not running on all platforms (e.g., running on ChatGPT and Perplexity but not Gemini or Grok). List these coverage gaps by seed prompt. Flag whether the missing platform coverage appears intentional or like an oversight.
    ```
  </Accordion>

  <Accordion title="Standardize Your Tag Structure">
    Find orphaned tags, overlapping names, and uncategorized prompts — then get a recommended structure.

    ```text theme={null}
    Get all tags for [brand name]. Identify:
    1. Tags with fewer than 5 prompts — likely orphans or misfiled
    2. Tags whose names overlap in meaning (e.g., "competitors" vs. "alternatives" vs. "compare")
    3. Tags with no clear category alignment

    Suggest a consolidated tag structure. Then, for any tag with fewer than 5 prompts, list those prompts so I can decide whether to reassign them.
    ```
  </Accordion>

  <Accordion title="First-Week Baseline">
    Establish a Day 1 reading for a brand that just went live, to compare every future report against.

    ```text theme={null}
    For [brand name], establish a baseline reading now that the brand just went live in Scrunch.

    1. Pull total variant count and confirm data has started collecting (variants should show non-zero observation counts within 24-48 hours of setup)
    2. Get presence, position, and sentiment metrics for the data collected so far
    3. List all tags and confirm prompts are distributed across them as expected

    Present this as a "Day 1" baseline I can compare all future reports against. Flag anything that looks like it isn't collecting data yet.
    ```
  </Accordion>

  <Accordion title="Prompt Coverage Audit">
    Platform coverage isn't the only gap worth checking — confirm prompts span the full buying journey too.

    ```text theme={null}
    For [brand name], check whether our tracked prompts actually cover the full buying journey, not just one stage.

    1. Get all tags and identify which represent funnel stages (awareness, consideration, decision) versus topic/product tags
    2. Pull variant counts for each funnel-stage tag
    3. Flag if any stage is significantly under-tracked relative to the others (e.g., dozens of awareness-stage prompts but almost no decision-stage prompts)

    Recommend which funnel stage most needs new prompts added, and roughly how many.
    ```
  </Accordion>
</AccordionGroup>

***

<CardGroup cols={2}>
  <Card title="New Brand Live in One Conversation" icon="rocket" href="/mcp/workflows/new-brand-live">
    Starting from scratch? Configure a brand, competitors, and prompts in a single chat.
  </Card>

  <Card title="Feature Reference" icon="wrench" href="/mcp/tools">
    See everything available via MCP with descriptions and example prompts.
  </Card>
</CardGroup>