Auditing TBO Tek's Blog Archive for Cluster Candidates
Objective: Given a 16-post blog archive export with URL, current rank, and monthly traffic, group the posts into pillar/cluster candidates using the lesson's Step 2 (audit what exists) framework, then flag which posts are orphans that belong to no coherent cluster.
You're the content marketer at TBO Tek, the B2B travel distribution platform serving 147,000+ travel agents worldwide. Eighteen months of ad-hoc blogging produced 16 posts with no cluster structure. Before your team writes a single new article this quarter, leadership wants to know how many real clusters already exist in that archive, and what's just noise.
Tag every post by the subtopic it actually addresses, group subtopics with enough posts into cluster candidates, and flag the orphans in writing.
How many real content clusters already exist buried in this archive, and which posts are orphans with no cluster fit?
Before you start
What you'll need
- —Basic spreadsheet sorting and grouping
- Cluster candidate
- a subtopic with enough existing posts (3 or more) to be retrofitted into a pillar-and-cluster structure, rather than requiring brand-new content.
- Orphan post
- a post whose subtopic has no siblings in the archive, and therefore doesn't belong to any coherent cluster.
Free path (everything below is enough to finish)
Free, no account friction, sufficient for a 16-row sort-and-group exercise
Free, shows real search demand rather than guessing which cluster to build first
The process
1 step
Step 01 of 01
The lesson's Step 2 says most sites already have the raw material for 2-3 clusters buried in old posts, and retrofitting existing content into clusters often delivers faster gains than publishing brand-new articles.
Sixteen posts, no structure. Which subtopics already have enough posts to call a cluster, and which posts are orphans with no siblings at all?
Procedure
- Import the 16-row export into Sheets and freeze the header row
- Read each title and tag it with the broad subtopic it addresses (API integration, agent onboarding, distribution pricing, etc.)
- Sort by the tag column and count how many posts share each tag
- Mark any tag with 3+ posts as a cluster candidate; mark any tag with exactly 1 post as an orphan
TBO Tek blog archive audit (16 posts) TAG: API integration (5 posts) -> CLUSTER CANDIDATE How to Connect Your Booking Engine to a Travel API API Rate Limits Explained for Travel Agents Sandbox vs. Production: Testing Your TBO Integration 3 Common API Integration Errors and How to Fix Them Webhooks vs. Polling for Real-Time Inventory Updates TAG: agent onboarding (4 posts) -> CLUSTER CANDIDATE Getting Started as a TBO Travel Agent Partner Agent Verification: What Documents You'll Need Your First 30 Days on the TBO Platform How Agent Tiers and Commission Structures Work TAG: distribution pricing (3 posts) -> CLUSTER CANDIDATE Net Rate vs. Markup: A Quick Primer Currency Conversion Fees, Explained Dynamic Pricing in B2B Travel Distribution ORPHANS (1 post each, no cluster): 'TBO Tek Wins Travel Innovation Award', 'Our Office Holiday Schedule', 'Meet the Team: Engineering Spotlight', '5 Travel Documentaries Worth Watching', 'A Note on Our New Logo'
Healthy
Two clear cluster candidates (API integration, agent onboarding) go into this quarter's content brief; the pricing tag needs 2-3 more posts before it's a full cluster; the 5 orphans get left alone, not retrofitted into a cluster they don't belong to.
Unhealthy
Forcing the 5 orphan posts into the nearest cluster just to make the numbers look tidier, or starting new clusters from scratch while ignoring the 5 posts already sitting one subtopic away from being one.
What this means
A subtopic with 3+ existing posts is a retrofit opportunity, not a blank page. The orphans aren't failures, they're just posts that were never meant to be part of a cluster (an award announcement has no cluster to join).
So what do I do about it?
| Symptom | Action | Effort |
|---|---|---|
| Leadership wants a content calendar for next quarter and assumes everything starts from zero | Show the audit table first, retrofit the API integration and agent onboarding tags into pillar-cluster structures before commissioning new articles | 30 min |
| The pricing tag has only 3 posts, barely a cluster | Brief 2-3 new articles to round it out (e.g. 'How Multi-Currency Settlement Works') before calling it done | half day |
Analyze your findings
What to look for
- Subtopic consistency
- Does each post's tag reflect what it actually covers, not just a keyword in the title?
- Cluster threshold
- Does a subtopic have 3 or more posts, the minimum to call it a cluster candidate?
- Genuine orphans
- Is a single-post subtopic really unrelated to every other post, or does it belong to a cluster that just needs a different tag?
- Retrofit vs. new content
- Can the cluster be built from what already exists, or does it need 2-3 new posts to round it out?
Make the call
The archive audit shows API integration (5 posts), agent onboarding (4 posts), distribution pricing (3 posts), and 5 single-post orphans (an award announcement, an office holiday note, etc.). What should this quarter's content plan prioritize?
Recommendation · Priority: High
“Retrofit the API integration (5 posts) and agent onboarding (4 posts) subtopics into pillar-and-cluster structures this quarter, since both already clear the 3-post cluster threshold. Brief 2-3 additional articles for the distribution pricing subtopic to round it out to a full cluster, and leave the 5 single-post orphans alone rather than forcing them into a cluster they don't fit.”
Common mistakes
What trips people up
Treating every existing post as needing a new cluster written around it — the lesson's Step 2 point is that most of the raw material already exists; auditing first avoids commissioning duplicate content.
Forcing orphan posts into the nearest cluster tag — an award announcement or office holiday post has no genuine subtopic overlap with a cluster; forcing the fit signals scattered, not authoritative, coverage.
Ignoring a 3-post tag because it's not yet a large cluster — 3 posts already clears the cluster-candidate threshold; treating it as too small to matter misses a fast retrofit opportunity.
Final deliverable
A tagged archive sheet plus a one-paragraph recommendation: which 2 subtopics to retrofit into clusters this quarter, and which posts to leave alone.
See a reference example
YETI blog archive audit (excerpt) TAG: cooler care (4 posts) -> CLUSTER CANDIDATE, recommend retrofit first TAG: campfire cooking (3 posts) -> CLUSTER CANDIDATE, needs 1-2 more posts ORPHANS: 'YETI Ambassador Spotlight: Q3', 'Our New Colorway Drop' -> leave alone, no cluster fit
Success criteria
You're done when you can:
- Correctly tags all 16 posts by subtopic
- Identifies exactly the 2 tags with 3+ posts as cluster candidates
- Does not force the 5 single-post orphans into an artificial cluster
Key takeaway
Before commissioning new content, audit what already exists: most archives already contain the raw material for 2-3 real clusters. Tagging and grouping by subtopic surfaces genuine retrofit opportunities and keeps true orphans from being force-fit into clusters they don't belong to.