Content Coverage and Distribution

Content Coverage shows how the selected project’s content is distributed across its Content Bank clusters.

Overview

Use Content Coverage to see which subject areas contain the largest share of your content and which clusters may need further development.

For every cluster, the table shows:

its share of the project’s top-level topics;
the number of top-level topics; and
the number of subtopics.

Content Coverage is a planning view. It does not measure traffic, rankings, conversions or content quality, and it does not change anything in Content Bank or on the connected website.

Access and scope

Content Coverage is workspace- and project-aware.

The active workspace controls which projects are available.
The selected project controls which clusters and Content Bank records are included.
The content-status selector controls which Content Bank records contribute to the calculation.
Published is selected by default.

The report is project-wide. The dashboard’s cluster selector does not restrict Content Coverage because selecting one cluster would make that cluster represent 100% of the result and remove the comparison.

Markets do not affect Content Coverage. A market controls a website’s search location, device and search engines, but this report describes the selected project’s Content Bank structure rather than ranking data.

Before you begin

For a meaningful report:

Select the correct workspace.
Select the project you want to review.
Organise the project’s Content Bank records into clusters.
Confirm that the records have the appropriate content status.
Add parent relationships when an item should be treated as a subtopic rather than a top-level topic.

Projects with no matching Content Bank records show an empty state.

Quick start

Open Content Dashboard.
Select the relevant workspace.
Select the project.
Leave the content status as Published to assess live content, or select another available status when reviewing a different part of the content plan.
Start with All to compare every cluster.
Use Top quarter, Middle half or Bottom quarter to focus on clusters with similar levels of coverage.
Select a column heading to change the sort order.
Use the page-size selector or pagination controls when the project contains many clusters.

Understand the table

Cluster

Shows the Content Bank cluster name.

Content that belongs to the project but cannot be matched to a valid cluster is grouped under Uncategorised. This is a prompt to check its placement in Content Bank.

Shows the percentage of the project’s matching top-level topics assigned to the cluster:

cluster top-level topics ÷ all matching top-level topics × 100

For example, if a project contains 20 published top-level topics and 5 belong to one cluster, that cluster’s share is 25%.

The percentage uses top-level topics only. Subtopics are shown separately and do not increase the share-of-content percentage.

The pink bar is scaled against the largest cluster in the current project to make relative differences easy to compare. The percentage label is the actual share of all matching topics.

Topics

Shows the number of matching top-level Content Bank topics in the cluster.

A top-level topic is a topic without a parent topic.

Subtopics

Shows the number of matching Content Bank items that have a parent topic.

A dash means the cluster has no matching subtopics. It does not mean that the data failed to load.

Use the coverage bands

The tabs organise clusters by their relative share of content.

All

Shows every cluster represented in the current project and content-status scope.

Top quarter

Shows clusters at or above the upper coverage threshold. These are the project’s most heavily represented clusters.

Middle half

Shows clusters between the lower and upper coverage thresholds.

Bottom quarter

Shows clusters below the lower coverage threshold. These are the least represented clusters and may warrant review.

The bands are based on the distribution of cluster percentages, not fixed percentage ranges. Clusters with equal percentages stay together, so a band can contain slightly more or fewer than exactly one quarter of the clusters.

A cluster appearing in the bottom quarter is not automatically deficient. Its appropriate size depends on the project strategy, audience, search demand and role in the customer journey.

Sort and navigate the results

Select a column heading to sort by:

cluster name;
share of content;
topic count; or
subtopic count.

Select the same heading again to reverse the order.

Use Show to display 10, 25, 50 or all clusters. The information beside the selector shows the visible range, total clusters in the selected coverage band and total subtopics in the current project result.

Changing pagination does not alter the coverage calculation.

Interpret Content Coverage

One cluster dominates

A very large share can indicate strong topical depth, but it can also mean that the project is overly concentrated. Compare the result with the project’s intended subject areas and customer journey.

Several clusters have similar shares

This suggests a relatively balanced content inventory. Balance is only useful when the clusters reflect genuine strategic priorities.

A cluster has topics but no subtopics

The cluster has breadth at the top level but no recorded supporting content beneath those topics. Review whether some existing items should be organised as subtopics or whether supporting content is needed.

A cluster has many subtopics

This can indicate good supporting depth. Open Content Bank to check whether the parent-child structure is intentional and easy to navigate.

Content is Uncategorised

One or more records cannot be connected to a valid cluster in the selected project. Open Content Bank and assign or correct their cluster placement.

A practical coverage-review workflow

Review All to understand the full distribution.
Open Bottom quarter and identify strategically important clusters with limited coverage.
Compare topic and subtopic counts to distinguish a lack of breadth from a lack of supporting depth.
Check Top quarter for clusters that may be overrepresented or ready for consolidation.
Open Content Bank to review the actual topics in a cluster.
Use topic or subtopic ideation when an important gap needs new content ideas.
Use the Journey × Intent × Cluster Matrix to check whether coverage also supports the required journey stages and search intents.
Review Content Performance before deciding which published pages to update, consolidate or protect.

Data timing

Content Coverage reads the selected project’s stored Content Bank structure.

Changes to topic status, cluster placement or parent relationships may not appear until the report is refreshed. The report may also briefly use a cached result after a recent change.

Switching workspace or project clears the previous result while the new project is loaded. An unfinished older request is discarded so that it cannot overwrite the newly selected project.

What should I do next?

Use Content Bank to inspect or change cluster placement.
Use Suggest topics to expand an important cluster.
Use Suggest subtopics when a topic needs supporting depth.
Use the Journey × Intent × Cluster Matrix to assess journey-stage and intent balance.
Use Content Pipeline to review editorial progress.
Use Content Performance to evaluate published pages using traffic, conversion and visibility signals.

Troubleshooting

No coverage appears

Confirm the correct workspace and project are selected.
Confirm the project contains Content Bank records with the selected status.
Leave the status set to Published when reviewing live content.
Check that topics are assigned to the selected project.
Refresh the page after recent Content Bank changes.

A cluster is missing

Confirm the cluster belongs to the selected project.
Confirm it contains at least one topic or subtopic with the selected status.
Check whether its content has been moved, archived or marked unpublished.
Open Content Bank and verify the cluster placement.

The percentages do not include subtopics

This is expected. Share of content is calculated from top-level topics. Subtopics are displayed in their own column.

The percentages do not total exactly 100%

The individual values are rounded to one decimal place, so the displayed total can differ slightly from 100%.

The pink bar looks like 100% but the label is lower

The longest bar represents the largest cluster relative to the other clusters. Read the percentage label for its actual share of all topics.

The quarter tabs do not contain equal numbers of clusters

Clusters with equal coverage remain in the same band. This can make a band larger or smaller than an exact quarter.

Changing the market has no effect

This is expected. Content Coverage is based on project and Content Bank structure, not market-specific ranking data.

Changing the cluster selector has no effect

This is expected. The report deliberately remains project-wide so that clusters can be compared with each other.

Frequently asked questions

Does Content Coverage measure content quality?

No. It measures how matching topics and subtopics are distributed across clusters.

Does a large cluster automatically perform well?

No. Use Content Performance to evaluate traffic, conversions, visibility and engagement.

Does a bottom-quarter cluster always need more content?

No. Review its strategic importance, audience need and intended role before expanding it.

Are markets required?

No. Markets are not used by Content Coverage.

Are archived and unpublished records included?

Only when that status is deliberately selected. The default view uses Published content.

Can I change a cluster from this table?

No. Use Content Bank to add, move, rename or reorganise content.

Does this report change the connected website?

No. It is a read-only planning report.