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

# Build Your Prompt Library from SEO Keywords

> Compare your SEO keyword list against existing Scrunch prompts, cluster the gaps, and create new tracking prompts in one conversation.

Your SEO keyword research already tells you what buyers search for. This workflow maps those keywords against your current Scrunch prompt coverage, finds the gaps, converts them into natural-language AI queries, and adds them to Scrunch — so your AI visibility tracking matches your SEO strategy.

<Info>
  **Tools used in this workflow**

  | Tool                            | Required? | Used for                                        |
  | ------------------------------- | --------- | ----------------------------------------------- |
  | Scrunch MCP                     | Required  | Listing existing prompts, creating new ones     |
  | Keyword data                    | Required  | Paste from any source — see input options below |
  | Google Search Console MCP       | Optional  | Pull queries directly without exporting         |
  | Ahrefs / SEMrush / Keyword tool | Optional  | Paste a CSV export into the prompt              |
</Info>

***

## Keyword input options

You don't need a specific tool connected. Claude can work with keyword data in any of these forms:

<Tabs>
  <Tab title="Paste a keyword list">
    Copy your keywords from any tool (Ahrefs, SEMrush, Keyword Planner, Clearscope, etc.) and paste them directly into the prompt in Step 2.

    ```text theme={null}
    Here are the keywords to analyze:
    best project management software
    project management tools for remote teams
    asana vs monday.com
    how to manage remote team tasks
    ...
    ```
  </Tab>

  <Tab title="Google Search Console">
    If you have Google Search Console connected as an MCP, replace Step 2 with:

    ```text theme={null}
    Pull the top 100 queries by impressions from Google Search Console for [domain] over the last 90 days. Filter to queries with more than 50 impressions. Use those as the keyword input for the gap analysis.
    ```
  </Tab>

  <Tab title="CSV from an SEO tool">
    Export a keyword report from Ahrefs, SEMrush, or Moz as CSV. Paste the contents or upload the file and reference it in Step 2:

    ```text theme={null}
    I've attached a keyword export from [tool name]. Use the "Keyword" column as the input for the gap analysis. Ignore any keywords with fewer than [X] monthly searches.
    ```
  </Tab>
</Tabs>

***

## The workflow

<Steps>
  <Step title="Pull existing prompt coverage from Scrunch">
    ```text theme={null}
    List all active prompt variants for [brand name] in Scrunch. I want to see the full seed prompt text for each one so I can map it against keyword data.
    ```
  </Step>

  <Step title="Run the gap analysis">
    ```text theme={null}
    Here is a list of SEO keywords and questions we're targeting for [brand name]:

    [paste your keyword list here]

    Compare these against the Scrunch prompts you just pulled. Classify each keyword into one of three buckets:

    1. Already covered — there's an existing Scrunch prompt that tracks this topic or a close equivalent
    2. Partially covered — we're tracking the general topic but missing this specific angle or intent
    3. Not covered — no existing prompt comes close to this keyword

    Show me the "partially covered" and "not covered" keywords — those are the gaps.
    ```
  </Step>

  <Step title="Cluster the gaps and generate prompts">
    ```text theme={null}
    Take the gap keywords from the previous step and:

    1. Group them into topic clusters — keywords that are semantically related and could be addressed by similar content
    2. For each cluster, write 2–4 natural-language questions that a user would actually type into an AI assistant to get information on this topic. These should sound like real questions, not keyword strings.
    3. For each prompt, note whether the intent is awareness (general research), consideration (comparing options), or decision (ready to choose)

    Show me the clusters and proposed prompts before creating anything — I want to review them first.
    ```
  </Step>

  <Step title="Create the approved prompts in Scrunch">
    Once you've reviewed the proposed prompts:

    ```text theme={null}
    Create the following new prompts for [brand name] in Scrunch. Tag each with its funnel stage (awareness / consideration / decision) and also add the tag "[seo-import]" so I can track this batch separately.

    [list the prompts you approved in the previous step]
    ```
  </Step>

  <Step title="Confirm and check coverage">
    ```text theme={null}
    List all prompts for [brand name] tagged "[seo-import]" to confirm they were created correctly. How many prompts did we add? What's the breakdown by funnel stage?
    ```
  </Step>
</Steps>

***

## Tips

<AccordionGroup>
  <Accordion title="How many keywords to analyze at once">
    Claude handles up to a few hundred keywords in a single prompt well. For larger keyword sets (1,000+), run the analysis in batches by topic cluster or funnel stage — it produces cleaner output and avoids truncation.
  </Accordion>

  <Accordion title="Prioritizing which gaps to fill first">
    After the clustering step, ask: "Rank these gap clusters by commercial relevance for \[brand name] — which topics represent the highest-value buyers if we appear in AI responses for them?" This focuses your new prompts on business impact, not just coverage volume.
  </Accordion>

  <Accordion title="Running this quarterly">
    SEO keyword priorities shift. Run this workflow every quarter with a fresh export. Use the `[seo-import-q[quarter]-[year]]` tag convention so you can track each batch's performance separately and see which keyword-sourced prompts improve your visibility over time.
  </Accordion>

  <Accordion title="What makes a good AI tracking prompt vs. an SEO keyword">
    SEO keywords are often short ("project management software") while effective AI prompts are full questions ("What's the best project management software for a team of 20?"). Claude handles this conversion in Step 3, but you can adjust the output by adding: "Make the prompts more specific — include use-case context, team size, or industry where it makes the question more realistic."
  </Accordion>
</AccordionGroup>

***

<CardGroup cols={2}>
  <Card title="Create Content That Gets AI Citations" icon="pen-nib" href="/mcp/workflows/create-content-for-citations">
    Once you've added the prompts, use this workflow to create the content that fills those gaps.
  </Card>

  <Card title="Find Visibility Gaps Worth Fixing" icon="magnifying-glass" href="/mcp/workflows/find-visibility-gaps">
    Find gaps from the Scrunch data side — which prompt categories already have the lowest visibility.
  </Card>
</CardGroup>