Content Pipeline
Content Pipeline shows how a project's Content Bank topics and subtopics are spread across the workflow, from Idea through Published, Unpublished and Archived. Use it to see where work is accumulating and which parts of a cluster need attention. The chart describes saved workflow status; it does not measure page performance or change the connected website.
Open Content Pipeline
- Open Content Dashboard and select the relevant workspace and project.
- Find Content Pipeline. Leave the dashboard's Cluster selection clear to see the whole project, or select one cluster to focus on it.
- Compare the Topics and Subtopics rows, then read the summary badge below them.
- Hover over a coloured segment to see its status, count and percentage.
You need access to the project in the active workspace. The chart counts the project's Content Bank records in the eight recognised workflow statuses. It always includes every recognised status, even if the dashboard's content-status selector is set to Published or another value. Changing the search market also has no effect.
Read the two rows
Topics are top-level Content Bank records without a parent topic. Subtopics are records connected to a parent topic. The number at the right of each row is its total across all recognised statuses in the selected project or cluster.
Each coloured segment represents one status from the legend. Its width is the status's share of that row:
status count ÷ Topics or Subtopics row total × 100
For example, eight Published topics out of ten topics make an 80% segment in Topics. Two Published subtopics out of five subtopics make a 40% segment in Subtopics. The rows use separate totals, so compare them separately. A status with no records has no visible segment. Smaller segments may have no percentage printed inside; hover to read their count and rounded percentage.
If you select a cluster, a subtopic without its own cluster can be counted under its parent topic's cluster when the parent belongs to the same project. A record with no matching cluster remains in the project-wide chart but cannot appear in a selected cluster's view.
Understand the statuses
The segments and legend follow this workflow order:
| Status | What it indicates in Content Bank |
|---|---|
| Idea | A recorded content opportunity. Records without a saved status also count here. |
| Approved | An accepted content idea. |
| Brief Ready | The brief or outline is ready for the next writing step. |
| Draft Ready | A draft is ready for review or further editing. |
| Needs Review | The item needs a decision or check before moving on. |
| Published | The record is marked published in Content Bank. |
| Unpublished | The record is marked unpublished in Content Bank. |
| Archived | The record is retained outside the active workflow. |
Published is a Content Bank status. It does not, by itself, verify that the page's URL is currently live. Likewise, Unpublished identifies the saved status; check the record and website before concluding why a page is unavailable. Content Pipeline does not change any item's status. Use Content Bank to review or edit records.
Read the summary badge
The badge combines the Topics and Subtopics rows:
- Published is the combined count of published topics and subtopics.
- In progress combines Idea, Approved, Brief Ready, Draft Ready and Needs Review.
- Hidden combines Unpublished and Archived. This part of the badge appears only when its count is above zero.
The badge colour reflects the percentage of all counted records that are Published. The chart rounds this percentage to a whole number before choosing its colour: below 33%, 33% to 65%, or 66% and above. This is a quick view of workflow mix, not a quality or performance score. A project with a large planned backlog can reasonably show a low published share.
Use the chart to plan work
- Start with the whole project and compare the two row totals. A high Idea share may point to a planning backlog; a high Needs Review share may point to an editorial queue.
- Compare the largest segments in Topics and Subtopics. This can show whether supporting content is progressing alongside its parent topics.
- Read In progress and, when shown, Hidden in the badge for a project-wide summary.
- Select an important cluster and repeat the comparison. Clear the cluster selection to return to the whole project.
- Open Content Bank to inspect the records behind an unexpected count and update their statuses or relationships there.
The chart does not save a separate report. Use Content Coverage to compare cluster sizes, Journey × Intent × Cluster Matrix to inspect content purpose and journey stages, and Content Performance to evaluate published pages using traffic, conversions and visibility data.
Updates and missing results
The chart reads current Content Bank records when it loads. Changing project or cluster reloads it; switching workspace clears the previous result until you select a project in that workspace. A new project starts without the previous chart's cluster filter. Changes saved in Content Bank appear after the chart reloads; reselect the project or cluster, or refresh Content Dashboard after editing.
- No chart appears: Confirm the workspace and project, then clear the cluster selection. If there are no matching topics or subtopics, the chart says No topics or subtopics exist for this selection.
- A cluster looks empty: Check that it belongs to the project and that its records are assigned to it. A subtopic may use its parent's cluster when it has none of its own.
- An item appears as Idea: Check whether its Content Bank status is missing; blank statuses count as Idea.
- The badge differs from a row: The badge combines both rows, while each bar calculates its percentages from its own row total.
- Changing content status or market has no effect: The chart always shows the complete recognised workflow for the selected project or cluster and does not use market data.