Content Coverage and Distribution
The Content Coverage and Distribution treemap reveals how content is balanced across topic clusters—highlighting which areas dominate the strategy and which need attention.
Quick start
- Select the target Project from the dropdown
- Set Published Status to filter by content state
- Review the treemap—larger blocks indicate greater coverage
- Hover over any block to see exact percentages and counts
- Click a cluster block to focus analysis on that area
Understanding the display
The treemap visualises content distribution using proportional rectangles. Each block represents a topic cluster, sized by its weighted coverage percentage.
How to read the chart
| Element | Meaning |
|---|---|
| Block size | Proportional to coverage percentage—larger blocks have more content weight |
| Block colour | Unique colour per cluster for easy identification |
| Percentage label | Share of total weighted content coverage |
| Topic count | Number of top-level topics in the cluster |
| Subtopic count | Number of nested subtopics within topics |
Coverage weighting
Coverage percentages reflect both quantity and depth. Topics carry full weight, while subtopics contribute partial weight. Deeper content hierarchies receive additional weighting, rewarding comprehensive topic coverage.
What should I do next?
The distribution pattern indicates where to focus content efforts:
| Pattern | Action |
|---|---|
| One block dominates (>40%) | Content is concentrated. Consider expanding other clusters to balance coverage. |
| Even distribution | Healthy balance. Maintain current strategy and monitor for drift. |
| Several empty or tiny blocks | Gaps exist. Prioritise creating content for underserved clusters. |
| Many small blocks, few large | Fragmented coverage. Consider consolidating related clusters or deepening existing ones. |
| Cluster shows 0 Topics | Cluster exists but has no assigned content. Add topics or review cluster relevance. |
Using the filters
Project
Select the project to analyse. Only clusters and content within the selected project appear in the treemap.
Published status
| Option | Shows |
|---|---|
| All | Both published and draft content combined |
| Published | Only live content currently visible to readers |
| Draft | Only unpublished content in progress |
Comparing Published vs Draft views reveals pipeline health—a large Draft percentage indicates content awaiting review or publication.
Cluster
Select a specific cluster to focus the analysis. When selected, the treemap shows only that cluster at full scale, useful for examining a single area in detail.
Interactive features
Hover over any block to see a tooltip with cluster name, exact coverage percentage, and topic/subtopic counts.
Export via the menu icon (⋮) to download the chart as PNG, JPEG, or SVG for reports and presentations.
Troubleshooting
No data available
The selected filters return no results. This occurs when:
- No clusters exist for the selected project—create clusters first
- No topics are assigned to any cluster—add topics to clusters
- Published Status filter excludes all content—try "All" instead
Cluster missing from treemap
Clusters with zero topics (after filters apply) do not appear. Check the Published Status filter or verify topics are assigned to the cluster.
Percentages seem wrong
Coverage uses weighted calculations that factor in content depth. A cluster with fewer but deeply nested topics scores higher than many shallow topics. This rewards comprehensive coverage over simple counts.
Chart not updating
After changing filters, the chart refreshes automatically. If it does not, refresh the page. Ensure the project selector shows the correct project.
FAQ
How is coverage percentage calculated?
Coverage reflects weighted content contribution. Topics receive full weight, subtopics receive partial weight, and deeper nesting adds additional weight. The percentage shows each cluster's share of the total weighted score.
Why does a cluster with fewer topics show higher coverage?
Depth matters. A cluster with well-developed topic hierarchies (topics with multiple levels of subtopics) scores higher than a cluster with many standalone topics. This design rewards thorough topic coverage.
Can I see historical distribution trends?
The treemap shows current state only. For trend analysis, export snapshots periodically and compare them manually, or use the Content Journey timeline features.
What happens when I click a cluster block?
Clicking filters the view to that single cluster, showing it at full scale. Clear the Cluster filter to return to the full distribution view.
Why are some clusters showing 0 subtopics?
Topics in those clusters have no child subtopics assigned. This is normal for flat content structures. Consider adding subtopics for more comprehensive coverage of complex subjects.
Getting help
Contact support for persistent data or display issues