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

# Keyword Clusters: turn question groups into content work

> Keyword Clusters group related search intents and AI prompt contexts so teams can prioritize Strategy Map, Content Factory, and reporting work.

<Frame>
  <img src="https://mintcdn.com/afterworklab/5NGf7Fi0rCLZYAc3/images/concepts/page-thumbnails/en-features-keyword-clusters.png?fit=max&auto=format&n=5NGf7Fi0rCLZYAc3&q=85&s=e04e2157576012a30f0faa6e721353b4" alt="HaloX Features page thumbnail summarizing Keyword Clusters: Keyword Clusters: turn question groups into content work as five cards" width="1600" height="900" data-path="images/concepts/page-thumbnails/en-features-keyword-clusters.png" />
</Frame>

## What is this feature?

**Keyword Clusters** is the feature for grouping related search intents and AI prompt contexts into execution units. It is a decision point in the HaloX `diagnose → measure → prioritize → execute → report` loop. Teams use it to read the current signal, split the cause, and decide the next content, source, technical, or reporting action.

## HaloX app location

<Frame>
  <img src="https://mintcdn.com/afterworklab/6BCxNsplfUWn2A0v/images/app/keyword-status-network-shell-context-live-20260507.png?fit=max&auto=format&n=6BCxNsplfUWn2A0v&q=85&s=557d35ad3c15c61eff0eecf3448ccd4a" alt="HaloX Pro mode Keyword Clusters screen showing cluster priority, representative keywords, AVI, citation status, and next actions" width="1280" height="553" data-path="images/app/keyword-status-network-shell-context-live-20260507.png" />
</Frame>

*The Keyword Clusters screen prioritizes search-intent groups, citation status, and content work units rather than isolated keyword rows.*

Keyword clusters are inputs for Pro-mode strategy decisions. Use list views for priority, network views for relationships, then pass selected clusters into Strategy Map and content briefs.

## Inputs and outputs

| Area    | What it includes                                                               | Example                                                                         |
| ------- | ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------- |
| Inputs  | Site<br />brand<br />strategic prompts<br />clusters<br />source candidates    | Brand name<br />non-branded prompts<br />competitors<br />owned URLs            |
| Signals | Scores<br />answers<br />sources<br />citations<br />web health<br />gap types | AVI<br />citation rate<br />source visibility<br />urgency<br />GEO opportunity |
| Outputs | Next priority and reporting sentence                                           | Technical fix<br />content brief<br />source work<br />weekly report note       |

## What should you look at first?

<Steps>
  <Step title="1. Summarize the state in one sentence">
    Replace “the score is low” with a cause-based sentence such as “official citations are weak for non-branded comparison prompts.”
  </Step>

  <Step title="2. Split the cause into four work types">
    Move technical blockers to Site Audit. Send question gaps to Prompt Analysis, source gaps to Citation Tracking, and content gaps to Content Factory.
  </Step>

  <Step title="3. Choose one next action">
    Turn the signal into one next action: a cluster update, page edit, FAQ, source task or weekly report note.
  </Step>
</Steps>

## Main cards, tabs, or metrics

| Area           | What to inspect                                                   | Decision standard                         |
| -------------- | ----------------------------------------------------------------- | ----------------------------------------- |
| Current signal | Score<br />card<br />answer<br />source<br />or page issue        | Baseline and week-over-week movement      |
| Gap            | Weak prompt<br />source<br />content<br />or competitor advantage | Why the team should act                   |
| Priority       | Urgency<br />GEO opportunity<br />AIO fit<br />SEO foundation     | What should happen this week              |
| Next action    | Content<br />technical<br />source<br />or report work            | Whether it can have an owner and deadline |

## Practical use cases

| Situation                    | What to do with this feature                            | Output                            |
| ---------------------------- | ------------------------------------------------------- | --------------------------------- |
| Before a customer meeting    | Find weak prompt sets and source gaps.                  | One-page diagnostic summary       |
| Internal execution meeting   | Choose this week’s content, technical, or source tasks. | Ticket or content brief           |
| Executive/customer reporting | Explain cause and next action, with the score.          | Weekly report or export           |
| SEO/GEO strategy             | Read SEO foundation and AI answer signals together.     | Strategy Map and keyword clusters |

## How to explain it in meetings

“This feature shows how far the brand travels inside AI search answers and what content, source, or technical action should happen next.” Avoid customer names, real URLs, and internal KPIs in public documentation.

## FAQ

### Does this feature complete the decision by itself?

No. HaloX features are connected. A signal in Keyword Clusters should move into Site Audit, Strategy Map, Content Factory, Citation Tracking, or weekly reporting.

### Do scores map directly to business results?

Most GEO metrics are leading indicators. Mentions and citations usually move first; traffic, branded search and conversion prompts are checked later.

## Related guides and concepts

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/en/introduction/quickstart">Start the first 30-minute workflow.</Card>
  <Card title="Reading scores" icon="chart-line" href="/en/guides/reading-scores">Translate metrics into meeting language.</Card>
  <Card title="GEO glossary" icon="book-open" href="/en/glossary/index">Understand GEO, AVI, citation rate, and source visibility.</Card>
  <Card title="Reports" icon="file-chart-column" href="/en/guides/reports">Turn movement into reporting language.</Card>
</CardGroup>

## How to read cluster card metrics

| Metric                                 | What it means                                              | Basis                                     | Next action                                                      |
| -------------------------------------- | ---------------------------------------------------------- | ----------------------------------------- | ---------------------------------------------------------------- |
| Keyword count                          | Number of keywords in the cluster                          | Member count                              | If high, plan Pillar and Support content instead of one article. |
| Volume sum                             | Combined search demand across cluster keywords             | Volume sum                                | High-demand clusters deserve priority review.                    |
| Opportunity Score                      | Summary score for execution opportunity                    | Cluster opportunity score                 | High score plus high gap makes it a content candidate.           |
| Gap type                               | SEO/GEO state combination                                  | CRITICAL, GEO\_GAP, SEO\_GAP, or FORTRESS | Decides which channel to improve first.                          |
| Brand and competitor GEO citation rate | How often the brand or competitors are cited in AI answers | Cluster GEO citation percentages          | If competitor share is high, compare source pages first.         |

## Pillar vs Support

| Role            | Meaning                                            | When to use it                                           |
| --------------- | -------------------------------------------------- | -------------------------------------------------------- |
| Primary keyword | Keyword that represents the cluster                | Represents the main intent and demand.                   |
| Pillar          | Main content page for the cluster                  | Covers the broad topic and central intent.               |
| Support         | Supporting content around the Pillar               | Handles FAQ, comparison, how-to, and detailed questions. |
| Existing Jobs   | Content Factory jobs already linked to the cluster | Avoid duplicates and continue from current progress.     |

## Example decisions

| Situation                                 | Interpretation                                      | Next action                                                  |
| ----------------------------------------- | --------------------------------------------------- | ------------------------------------------------------------ |
| Volume is high, but GEO citation is low   | Demand exists, but AI answers do not cite the brand | Strengthen the Pillar content and official evidence pages.   |
| Many keywords and many support candidates | The cluster needs a content set, not one page       | Send one Pillar and several Support jobs to Content Factory. |
| FORTRESS cluster                          | SEO and GEO are both strong                         | Keep it in monitoring and competitor tracking.               |

## If you need the service metric definitions

Terms such as `rank`, `search volume`, `trend`, `AI`, `PAA`, `Citation Rate`, `Share of Voice`, and `gap type` are explained in the [screen metrics glossary](/en/glossary/screen-metrics). Use it when a KPI on this page needs a plain-language definition and a link back to the screen where it appears.