Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Content Marketing › Intermediate

Building Content Pillars for an HR Software Company

Practice turning an unsorted idea list into a plan. You sort an invented rota software company's topic ideas and queries into pillars and clusters, choose a hub for each pillar, merge the duplicates, set aside the ideas that are not pillars at all and sequence a quarter's calendar that fits the team's hours.
ExerciseIntermediate levelModule 1: Pillars, calendars and clusters5 minUpdated

Why this matters

Teams rarely lack ideas; they lack a structure saying which ideas belong together, which page leads and what gets made first. The content pillars and calendar guide derives pillars and sizes the calendar, the topic clusters framework turns a search-led pillar into a hub and cluster pages, and the keyword mapping tutorial gives every query one owner URL. This exercise runs all three over one messy list.

The topic list

Rotaline is an invented company selling rota software to small cafés, restaurants and shops. Its content goal is trial sign-ups from managers who build rotas by hand, which puts most of the weight in the consideration stage of the Funnel. The founder proposes four pillars: rotas and shift planning, holiday and absence, onboarding, and product news. The marketing lead has pooled ideas from sales calls, support tickets and a keyword export.

Illustrative example — not a real result

Rotaline: the unsorted topic list

Idea or querySourceEst. monthly searchesWhat the results page shows
how to make a staff rotaKeyword export2,900Step-by-step guides
staff rota templateKeyword export1,600Spreadsheet templates
free rota template excelKeyword export880Same pages as "staff rota template"
employee scheduling softwareKeyword export1,900Product pages and comparison lists
rota software for cafésSales calls260Comparison articles
shift planning for restaurantsKeyword export390Guides for managers
how to handle shift swapsSupport tickets210Guides and forum threads
how to reduce no-shows on shiftsSupport tickets170Practical guides
absence management policyKeyword export480Policy templates and guides
managing sickness absenceKeyword export320Mostly the same pages as "absence management policy"
holiday entitlement for part-time staffKeyword export1,300Official guidance and calculators
holiday pay for shift workersSupport tickets720Mostly the same pages as the query above
return to work interview questionsKeyword export590Question lists and form templates
onboarding checklist for new staffKeyword export1,000Checklists and templates
first day plan for hourly staffSales calls90Blog posts, few of them relevant
our new mobile app releaseProduct teamnoneNot a search topic
interview with our head of productFoundernoneNot a search topic

Existing pages: /features/scheduling ranks on page two for "employee scheduling software"; /blog/rota-tips, a short list post, ranks at position 18 for "how to make a staff rota".

Capacity: the marketing lead and a freelance writer have 50 hours a month for content. A hub guide costs 14 hours, a cluster article 8, a template page 6. The lead reserves 8 hours a month for refreshes and reactive work.

Grouping into pillars

Work in three passes. First, collapse duplicates: queries whose results pages largely share URLs need one page. Second, sort the rest by audience problem, not product feature, and test each candidate pillar on whether it could fill a regular calendar slot for a year. Third, pick the broadest query in each pillar as the hub and treat the specific ones as cluster pages. Ideas that fail every test belong to another channel, not the bin.

Task

  1. Merge the ideas that should share a page.
  2. Decide which of the founder's proposed pillars survive, with a reason for each that does not.
  3. For each pillar, name the hub, its head query and its cluster pages.
  4. Give every query one owner URL and decide what happens to /blog/rota-tips.
  5. Say where the non-pillar ideas go.
  6. Sequence the quarter's calendar within the team's hours.

Worked answer

Duplicates. "Free rota template excel" joins "staff rota template"; "managing sickness absence" joins "absence management policy"; "holiday pay for shift workers" joins "holiday entitlement for part-time staff". The results pages overlap, so a second page would only compete.

Pillars. Two survive. Rotas and shift planning has the most demand, sits closest to the product and has questions for a year. Holiday and absence has steady demand and support questions, though every page needs a qualified reviewer because readers act on it. Onboarding fails the depth test: one strong query and one weak one make a page, not a pillar, so the checklist joins the rota pillar. Product news is named after the org chart and serves existing customers, not searchers.

Clusters and owners.

  • Rotas hub: a guide at /guides/staff-rota owning "how to make a staff rota". /blog/rota-tips is too thin to be the hub; its useful tips move into the guide and it redirects there.
  • Rota cluster pages: the template, shift planning for restaurants, shift swaps, reducing no-shows, the onboarding checklist and a "rota software for cafés" comparison. /features/scheduling keeps "employee scheduling software" as the pillar's next step.
  • Absence hub: a guide with a policy template owning "absence management policy". Cluster pages: holiday entitlement and return-to-work interview questions.

Hubs and cluster pages link both ways, and SEO sets each format from its results page: the template query gets a template, not an essay.

Not pillar content. The app release goes to the customer newsletter; the interview runs as a newsletter feature or social post, outside the pillar slots.

Calendar. Hubs first, because cluster pages link up to them; then the pages closest to a trial.

Illustrative example — not a real result

Rotaline: the quarter in hours

Available after the reserve: 42 hours a month.

MonthPiecesHours
Month 1Rotas hub (14), rota template page (6), café software comparison (8), absence hub with policy template (14)42
Month 2Shift planning for restaurants (8), holiday entitlement (8), return-to-work questions (8), shift swaps (8), onboarding checklist (6)38
Month 3Reducing no-shows (8), internal-link pass and refresh of the features page (6), first pillar review14 plus review

Rotas takes 7 of the 10 new pieces, matching its weight in the goal. Month 3 is light on purpose: subject review of the absence pages often slips, and the slack absorbs it.

Common mistakes

  • Keeping a pillar because the founder proposed it. Onboarding and product news fail the tests; say so.
  • One page per wording. Queries with the same results page need one page.
  • Promoting the thin post to hub because it ranks a little. A hub covers the whole subject.
  • Filling every hour. A calendar with no slack breaks on the first late review.

Next, take the pillars and calendar checkpoint or return to the intermediate content marketing level.

Pages this lesson applies

Terms used on this page

Also related

Related