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

# Strategy Map: choose cluster priorities and execution scope

> Strategy Map combines SEO, AIO, GEO, gap type, urgency, and network context to choose which prompt and content clusters to execute first.

<Frame>
  <img src="https://mintcdn.com/afterworklab/5NGf7Fi0rCLZYAc3/images/concepts/page-thumbnails/en-features-strategy-map.png?fit=max&auto=format&n=5NGf7Fi0rCLZYAc3&q=85&s=e13fa5a7ef4561f6fa9fb840e16bca44" alt="HaloX Features page thumbnail summarizing Strategy Map: Strategy Map: choose cluster priorities and execution scope as five cards" width="1600" height="900" data-path="images/concepts/page-thumbnails/en-features-strategy-map.png" />
</Frame>

## What is this feature?

**Strategy Map** is the prioritization layer for choosing which prompt and content clusters to execute first using SEO, AIO, GEO, gap, urgency, and network signals. 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

Strategy Map is the <strong>Pro-mode strategy screen</strong> for choosing this week's clusters and content scope across list, network, matrix, and detail views. Start from the diagnosis summary, then use the view controls to narrow what the meeting should decide.

<Frame caption="Strategy Map diagnosis summary and matrix context">
  <img src="https://mintcdn.com/afterworklab/MYxPZSW1ds3BlC36/images/app/strategy-map-summary-portfolio-context-v2.png?fit=max&auto=format&n=MYxPZSW1ds3BlC36&q=85&s=f39be288440e42469f17af8ebdd8e963" alt="HaloX Strategy Map app screenshot showing 41 competitor-dominated AI answer areas, status counts, and matrix context" width="1000" height="505" data-path="images/app/strategy-map-summary-portfolio-context-v2.png" />
</Frame>

*The representative Strategy Map screenshot keeps the summary card and matrix context together instead of showing a chart-only crop, so the team can decide which clusters to review first.*

<Frame caption="Strategy Map controls and view switcher">
  <img src="https://mintcdn.com/afterworklab/pTX7n5mUtWKjTcAd/images/app/strategy-map-controls-crop.png?fit=max&auto=format&n=pTX7n5mUtWKjTcAd&q=85&s=3f2855a5e8de7d6b2817240d7ac10ed7" alt="HaloX Strategy Map controls for switching list, network, and portfolio views with prioritization filters" width="1015" height="537" data-path="images/app/strategy-map-controls-crop.png" />
</Frame>

*The controls turn the same cluster data into different decision views before a meeting or planning session.*

Strategy Map is the core Pro-mode strategy screen.

## Actual views and subfeatures

| View/panel           | What to inspect                                         | How to use it                                             |
| -------------------- | ------------------------------------------------------- | --------------------------------------------------------- |
| List view            | Cluster urgency, volume, SEO/AIO/GEO status             | Choose this week's priority clusters.                     |
| Network view         | Cluster relationships and neighboring topics            | Plan topic groups instead of one isolated article.        |
| Matrix view          | Relative opportunity size and difficulty                | Separate quick wins, strategic bets, and defensive areas. |
| Timeline             | Historical snapshots and current movement               | Use movement as report evidence.                          |
| Cluster detail panel | Strategy<br />trend<br />keywords<br />and prompts tabs | Move the selected cluster into a brief or site-fix task.  |

## 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 Strategy Map 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 the Strategy Map summary cards

| Metric           | What it means                                                | Basis                              | Example reading                                   |
| ---------------- | ------------------------------------------------------------ | ---------------------------------- | ------------------------------------------------- |
| Total Keywords   | Total keywords included in strategy clusters                 | Sum of cluster member counts       | Shows whether the map is broad or focused.        |
| Total Volume     | Combined search volume across clusters                       | Sum of cluster volume              | High volume plus high gap should raise priority.  |
| Click Upside     | Potential additional click opportunity after improvement     | Sum of cluster click-upside values | Use it with volume to prioritize execution.       |
| Gap Distribution | Count of CRITICAL, GEO\_GAP, SEO\_GAP, and FORTRESS clusters | Aggregates cluster gap types       | Shows which problem type dominates the portfolio. |

## The four gap types and the SEO/GEO matrix

| Type     | SEO state | GEO state | Meaning                                           | Next action                                                  |
| -------- | --------- | --------- | ------------------------------------------------- | ------------------------------------------------------------ |
| CRITICAL | Weak      | Weak      | Both search and AI visibility are weak            | Improve core content and source credibility together.        |
| GEO\_GAP | Strong    | Weak      | Search visibility exists, but AI citation is weak | Add FAQ, evidence sentences, and official source structure.  |
| SEO\_GAP | Weak      | Strong    | AI visibility exists, but organic rank is weak    | Improve SEO structure, titles, internal links, and clusters. |
| FORTRESS | Strong    | Strong    | Search and AI visibility are defended             | Monitor and track competitors.                               |

## Priority sorting criteria

| Sort             | Basis                                                                                  | When to use it                                             |
| ---------------- | -------------------------------------------------------------------------------------- | ---------------------------------------------------------- |
| Urgent-first     | CRITICAL, then GEO\_GAP, then SEO\_GAP, then FORTRESS; higher volume first within type | Use when reducing largest risk first.                      |
| Easy-first       | GEO\_GAP, then SEO\_GAP, then CRITICAL, then FORTRESS                                  | Use when trying to create fast wins from an existing base. |
| Channel coverage | SEO Top 10, AIO Citation, and GEO prompt coverage                                      | Use to identify the bottleneck channel.                    |

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