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
Strategy Map is the prioritization layer of HaloX. It turns keyword clusters and AI-search opportunities into a clear execution order by combining search volume, AIO, GEO, SEO, and GAP type.
Main tabs
| Tab | Use it for |
|---|
| List | Pick urgent clusters and GEO opportunities |
| Portfolio | Separate quick wins from long-term foundation work |
| Network | Understand topic relationships and competitor-source patterns |
How to use the list
| Column | How to read it |
|---|
| Cluster | A group of queries and questions with the same search intent |
| Keywords | The actual search terms and question candidates |
| Volume | Demand size, not the only priority signal |
| AIO | Google AI Overview opportunity/state |
| GEO | AI answer mention/source/citation opportunity |
| SEO | Traditional search ranking state |
| GAP type | Where competitors show up but you do not |
Practical prioritization
- High SEO + low GEO: strengthen existing pages with definitions, FAQ, comparison tables, and sources.
- Low SEO + high GEO opportunity: create new landing pages or topic hubs.
- Competitor-heavy cluster: analyze which competitor pages are cited and why.
- Low volume + high conversion intent: prioritize for B2B or high-intent verticals.
Next action
Move selected clusters into Content Factory and create citation-ready content, not isolated keyword-stuffed pages.
Read clusters as customer-meeting scenarios
A Strategy Map cluster is not just an internal analytics unit. It represents a group of customer questions that may need content, technical fixes, or reporting. Publicly safe meeting patterns map to clusters like this:
| Cluster type | Meeting problem | Signal in Strategy Map | Execution direction |
|---|
| Non-brand conversion | Teams want recommendation, comparison, and pre-purchase questions beyond brand search | medium demand but high AIO/GEO gap | comparison tables, beginner guides, pre-purchase FAQ |
| SEO recovery | A core keyword lost visibility after content operations paused | low SEO/rank signal and old content | refresh titles, metadata, categories, internal links before GEO expansion |
| PR/owned media | Brand teams need newsroom, leadership, issue, and YouTube questions covered | brand questions exist but official citations are weak | fact sheets, newsroom hubs, FAQ, leadership/issue pages |
| Local/multi-location | Regional recommendations, branch URLs, and foreign-language questions matter | location keywords and branch URLs are fragmented | branch landing pages, local FAQ, multilingual guide content |
| Fan-out opportunity | AI sub-queries cite competitors or third-party sources repeatedly | competitor/source gap appears across question paths | decompose the path with Fan-out search patterns |
For first-time users, explain a cluster as a group of questions AI may check together when forming an answer, not just a keyword bucket.
Feature use cases
Strategy Map is not only a keyword priority table. It turns customer-meeting problems into an execution order.
| Use case | Signal in Strategy Map | Decision |
|---|
| SEO recovery and GEO expansion happen together | Low SEO + GEO opportunity | Fix titles/meta/internal links first, then execute content. |
| Known brand is absent from comparison answers | Medium volume + competitor share + low GEO | Prioritize comparison, recommendation, and before-signup FAQ clusters. |
| PR team manages newsroom and issue questions | Brand questions exist but Source/Citation is weak | Build fact sheets, issue explainers, and official-source hubs. |
| Local business targets recommendations | Local keywords are scattered and branch URLs unclear | Pick priority branches/categories and create local FAQ content. |
| Agency prepares a proposal | Gap type and urgent clusters | Define the 2–4 week sprint scope and deliverables. |
Every selected cluster should become one of four actions: observe, improve an existing page, create new content, or fix technical readiness first.