Content Coverage and Distribution
Content Coverage shows how a project's Content Bank topics and subtopics are distributed across clusters. Use the table to spot subject areas with a large or small share of the content plan, then review the actual items in Content Bank before deciding whether to reorganise or create content.
This is a read-only planning view. It measures the number and distribution of Content Bank records, not their traffic, rankings, conversions or quality.
Open Content Coverage
- Open Content Dashboard and select the relevant workspace and project.
- Find Content Coverage. The table starts on All, with clusters ordered by Share of content from highest to lowest.
- Check the dashboard's content-status selection. The usual starting value is Published; change it if you want to examine another part of the content workflow.
The selected project and content status determine which records are counted. When a single status is selected, only records with that status contribute. A record without a saved status is treated as Idea.
The dashboard's cluster and market selections do not narrow this table. Content Coverage compares clusters represented by matching records across the project, and it does not use search-market data. If a project or status has no matching Content Bank records, the table shows an empty state.
Read the table
| Column | What it means |
|---|---|
| Cluster | The cluster assigned to matching Content Bank records. Records without a valid cluster in this project display as Uncategorised. |
| Share of content | The cluster's percentage of all matching top-level topics in the project. |
| Topics | Matching top-level records without a parent topic. |
| Subtopics | Matching records connected to a parent topic. A dash means zero subtopics. |
Share of content is calculated as topics in the cluster ÷ topics across all clusters × 100. For example, five topics in a project with 20 matching topics give that cluster a 25% share. Subtopics appear in their own column and do not increase the percentage. If the selected records contain only subtopics, every cluster's share is 0% because there are no top-level topics to divide between clusters.
The percentage is rounded to one decimal place, so the displayed values may not add to exactly 100%. The pink bar compares each cluster with the largest cluster in the current project and status selection. The largest cluster gets the longest bar; read the percentage label for its actual share of all topics.
Compare coverage bands
The tabs divide clusters by their share of top-level topics. The number in each tab label counts clusters, not topics:
| Tab | What it shows |
|---|---|
| All | Every cluster represented by the selected project and content status. |
| Top quarter | Clusters at or above the upper share threshold. |
| Middle half | Clusters between the lower and upper thresholds. |
| Bottom quarter | Clusters below the lower threshold. |
The thresholds come from the distribution of cluster percentages in the current result. They are not fixed percentage ranges. Clusters with the same percentage stay together, so the tabs need not contain exactly a quarter, half and quarter of the clusters. If all clusters have the same share, they can all appear in Top quarter while the other bands are empty.
A cluster in Bottom quarter is a prompt to review its role, not proof that it needs more content. A small cluster may be appropriate for a narrow subject. Likewise, a large share shows how the content is organised; it does not show that those pages perform well.
Sort and move through clusters
Select Cluster, Share of content, Topics or Subtopics to sort by that column. Select the same heading again to reverse the order. The table returns to page one when you change the sort or coverage band.
Use Show to display 10, 25, 50 or All clusters, and use the arrow or page controls to move through longer results. The range beside Show refers to clusters in the selected band. Its subtopic total covers all matching clusters for the project and content status, even when you are viewing just one band. Sorting, coverage bands and pagination do not change the underlying share calculation.
Use the results
- Start with All to see the complete cluster distribution.
- Check Bottom quarter for subject areas that matter to your audience but have few top-level topics.
- Compare Topics with Subtopics to see whether a cluster has broad coverage, supporting depth, or both.
- Check Top quarter for concentrated areas that may deserve a closer editorial review.
- Open Content Bank to inspect the actual records before changing their cluster, parent topic or status. Use Journey × Intent × Cluster Matrix to assess stage and intent coverage, and Content Performance to evaluate published pages using performance signals.
The table does not save a separate report or change a Content Bank record. Changes you make in Content Bank become part of the next result after the dashboard reloads. A recent change can still appear unchanged briefly because coverage results are cached for up to ten minutes for each project, workspace and status selection.
If the table looks wrong
- No clusters appear: Check the workspace, project and selected content status. A project with no matching Content Bank records has no coverage result.
- A cluster is missing: Check whether it contains a matching topic or subtopic and whether the records still belong to the selected project and cluster.
- A record appears under Uncategorised: Check its cluster assignment in Content Bank. The saved cluster may be missing or may belong to another project.
- The percentage looks too low: Check the Topics count. Subtopics are counted separately, and the bar is relative to the largest cluster rather than a 100% scale.
- The result has not changed after an edit: Reload Content Dashboard and allow for the short coverage cache to expire.