# Clusters (https://app.infrasity.com/docs/content-planning/sprints/clusters)





Clusters is a tab within a specific sprint's detail view, reached from [Sprints](/content-planning/sprints), that groups that sprint's topics by keyword theme. On a sprint with a large topic list, it's the view to reach for when you want to see which content areas a cycle is actually weighted toward, developer marketing versus product documentation versus case studies, for example, rather than scanning one flat list of topic titles.

<Screenshot src="/images/sprint-clusters.png" alt="Keyword Clusters tab showing total clusters, total MSV, topics clustered, cannibalization risks, and per-cluster progress cards" caption="Keyword Clusters, with 3 clusters covering 8 of 25 sprint topics." />

<Callout type="gotcha" title="Not the same Clusters as the GEO Dashboard">
  This is a distinct, content-planning concept from [GEO Dashboard Clusters](/geo-dashboard/clusters), which groups AI-citation *prompts* by theme for visibility tracking rather than grouping topics you're planning to write. The two features share a name and a general "group by theme" idea, but track different things: one is about what you're producing, the other is about how AI models cite what's already published. Whether a sprint's clusters here are linked to or shared with GEO Dashboard clusters isn't confirmed here.
</Callout>

## Header [#header]

* **↻ Re-cluster with AI** — re-runs clustering across the sprint's current topic list.

<Callout type="gotcha" title="Stale-clustering banner">
  A warning banner ("Topics have changed since last clustering — re-cluster to update") appears when topics have been added, moved, or edited since the last clustering run, with its own **Re-cluster** button. Clustering isn't automatic — it only reflects the topic list as of whenever it was last run.
</Callout>

## Summary stats [#summary-stats]

Four stat cards across the top:

* **Total Clusters** — how many keyword clusters this sprint has been grouped into.
* **Total MSV** — combined monthly search volume across all clustered topics.
* **Topics Clustered** — `X/Y` of the sprint's topics that have been assigned to a cluster. Topics can sit unclustered.
* **Cannibalization Risks** — flagged in red; topics whose keywords overlap closely enough to compete with each other in search rather than complement each other.

## Cluster cards [#cluster-cards]

Each cluster shows:

* **Name** — a generated theme label (e.g. "DevTools & Technical Marketing Services Coverage").
* **Coverage percentage** and a **progress bar**.
* **"X of Y sprint topics published"** — how many of the cluster's topics are live.

<Callout type="gotcha" title="Coverage percentage basis is unverified">
  It's not confirmed here whether the coverage percentage is published topics ÷ topics in that specific cluster, or some other calculation (e.g. weighted by MSV). Confirm against a cluster with a nonzero percentage before documenting the exact formula.
</Callout>

<RelatedPages
  pages="[
{ title: &#x22;Sprints&#x22;, description: &#x22;Plan and execute content in organized sprint cycles, think of sprints as your content team's weekly planning board.&#x22;, href: &#x22;/content-planning/sprints&#x22; },
{ title: &#x22;Topics&#x22;, description: &#x22;Manage individual content topics across all your sprints.&#x22;, href: &#x22;/content-planning/topics&#x22; },
{ title: &#x22;Analytics&#x22;, description: &#x22;Analytics for a single sprint's content performance.&#x22;, href: &#x22;/content-planning/sprints/analytics&#x22; },
{ title: &#x22;GEO Dashboard Clusters&#x22;, description: &#x22;Group related prompts into clusters for theme-level analysis.&#x22;, href: &#x22;/geo-dashboard/clusters&#x22; },
]"
/>
