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

# Keyword Organization

> Review SEO keyword clusters and assign them to product lines.

# Keyword Organization

Use this guide after product line classification (multi-product sites) or after SEO module setup (single-product sites) to review how your keyword clusters are organized and make sure the right clusters are attached to the right products.

## What You'll Need

| Requirement           | Details                                                                                                     |
| --------------------- | ----------------------------------------------------------------------------------------------------------- |
| SEO module            | Must be enabled under Settings > Modules                                                                    |
| Google Search Console | Connected and synced (optional, but clusters are richer with GSC data)                                      |
| Product lines         | Required only for multi-product sites — complete [Product Line Setup](/onboarding/product-line-setup) first |

<Info>If Google Search Console is not connected, keyword clusters are derived from your existing content and ad keywords. The clusters will still be usable, but ranking data and query volumes won't be available until GSC is linked.</Info>

## The Prompt

Paste this into Claude to begin:

```
Review keyword clusters for [website] and suggest product line assignments for each.
```

Replace `[website]` with your website name or domain. If you're on a single-product site, omit the product line framing:

```
Review keyword clusters for [website] and flag any overlapping or redundant clusters.
```

## What Claude Will Do

Claude will run three tool calls in sequence:

1. **`get_seo_overview`** — loads your SEO module configuration, connected integrations, and top-level performance summary
2. **`get_keyword_rankings`** — pulls ranked keywords, search volumes, and current page assignments from GSC (if connected)
3. **`list_entities`** (type: keyword clusters) — fetches all existing clusters with their member keywords and current metadata

From there, Claude will:

* Summarize how many clusters exist and how evenly they distribute across topics
* Identify which clusters clearly map to a single product or service line
* Flag clusters that span multiple products (brand terms, broad service terms)
* Propose assignments for each cluster — either to a product line or to a shared "brand" bucket

Review the proposed assignments before applying them. Claude will not write anything until you confirm.

## Applying the Assignments

Once you've reviewed and agreed on assignments, Claude can apply them in bulk:

```
Apply the proposed product line assignments to the keyword clusters.
```

Claude will use **`batch_tag_product_line`** to tag each cluster with its product line ID (max 50 clusters per call — Claude will batch automatically if you have more). For individual adjustments, it will use **`update_entity_metadata`**.

<Tip>You don't have to assign every cluster in one session. It's fine to handle the clear ones now and revisit ambiguous clusters after you've seen a few weeks of data.</Tip>

## Single-Product Sites

Skip product line assignments entirely. Instead, focus the review on cluster quality:

* Are there clusters that are too broad to be useful (e.g., "marketing")?
* Are there near-duplicate clusters that should be merged?
* Are high-value clusters missing keywords they should contain?

Use this prompt to get a quality-focused review:

```
Review my keyword clusters for [website] and identify any that are too broad, overlapping, or missing important keywords.
```

## Multi-Product Sites

Product-scoped keyword clusters mean that SEO intelligence — ranking trends, content gap analysis, keyword opportunities — flows to the right product team and runners instead of being aggregated across the entire site.

A `spend-analyst` runner scoped to Product Line A will only see clusters tagged to that product line. Without assignments, runners and reports treat all keywords as undifferentiated.

```
Assign keyword clusters for [website] to product lines. Focus on the [product name] product line first.
```

## Common Edge Cases

**Brand or company name keywords.** These belong to all products — do not assign them to a single product line. Leave them unassigned or use a shared "brand" tag if your setup supports it.

**Very small cluster counts (fewer than 5 clusters).** This usually means GSC hasn't been connected long enough to generate clusters, or the site is new. Complete [SEO module setup](/onboarding/seo-setup) first and return after 2–4 weeks of GSC data collection.

**A cluster contains keywords from two products.** Split it. Ask Claude: "Split the \[cluster name] cluster into two clusters — one for \[product A] and one for \[product B]."

**Clusters with zero ranked keywords.** These are opportunity clusters — keywords you're not yet ranking for. Keep them; they're used by the content planner to surface new topic ideas.