Skip to content
BloGrove
blogging

How to Plan a Month of Blog Content in One Afternoon

A repeatable planning system for solo bloggers — pick themes, batch ideas into clusters, schedule around real capacity, and stop deciding each morning.

BBloGrove Editorial4 min read
How to Plan a Month of Blog Content in One Afternoon

The most expensive part of blogging isn't writing — it's deciding. Every session that starts with a blank page and a question ("what should I post about?") burns twenty minutes of willpower before any real work happens. Multiply that by every publishing day and you get the quiet reason most blogs stall at post number eight.

Batching the decision once a month fixes this. One focused afternoon produces a plan that removes the daily negotiation entirely. Here's the system, start to finish.

Start with your clusters, not with topics#

Random topic lists produce random blogs. Search engines and readers both reward coherence — sites that go deep on a recognizable subject area. So the unit of planning is the topic cluster, not the individual idea:

  • A hub: one comprehensive pillar page covering a broad question your audience has
  • Spokes: narrower articles, each answering one sub-question in depth

If you've been publishing whatever came to mind, spend the first thirty minutes of planning mapping what you already have into loose clusters. Three or four clusters is plenty for a young blog. Everything you plan next belongs to one of them; ideas that fit none of them go on a someday list, not the calendar.

This structure pays twice: readers find a library instead of scattered posts, and internal linking between related articles becomes natural rather than forced.

The 90-minute ideation sprint#

With clusters chosen, generate next month's ideas in one pass:

  1. Set a quota per cluster — typically 2–3 posts each, so no cluster starves.
  2. Mine questions, not subjects. A title like "newsletter strategy" is a subject. "Why do subscribers stop opening newsletters?" is a post. Forums, comment sections, your own search console queries, and the "people also ask" boxes on search results are all question mines.
  3. Check against what exists. Ten seconds per idea: does the site already answer this? If yes, the idea becomes an update to the old post instead of a duplicate.
  4. Write the working title immediately. An idea without a title isn't planned — it's a vibe. Forcing the title now exposes vague ideas while they're still cheap to fix.

Ninety minutes of this reliably yields more usable posts than a month of opportunistic brainstorming, because you're judging ideas side by side instead of committing to whichever one showed up first.

Schedule against reality, not ambition#

Here is where most plans die. A calendar promising two posts a week when your real capacity is one is not a plan — it's a resignation letter with dates on it.

  • Count last month's actual output, then plan 80% of it. Slack absorbs the weeks life happens.
  • Assign each post a size: quick (500–800 words), standard (1,000–1,500), deep (2,000+). A month of four deep dives is unrealistic; a mix of sizes survives contact with reality.
  • Sequence deliberately. Lead with posts that support each other — publish a spoke right after its hub so internal links land on live pages. End the month with your strongest piece if you promote consistently, or mid-month if traffic spikes matter less than momentum.
  • Mark drafts vs. publishes. Drafting ahead decouples bad weeks from silent feeds. Even one post banked in advance converts a crisis week into a non-event.

A plain spreadsheet beats elaborate tools here: date, title, cluster, size, status. Five columns you'll actually maintain outperform a workspace you'll abandon by February.

Leave room for the unplanned#

Reserve roughly one slot — or one flex week — for reactive content: a breaking change in your niche, a question that keeps appearing, a follow-up to a post that unexpectedly resonated. Plans earn their keep by being 85% load-bearing and 15% elastic. Rigid calendars produce resentment; empty calendars produce nothing.

Then close the afternoon with two minutes of review hygiene: does every scheduled post belong to a cluster? Does every hub have at least one spoke live or planned? Any post whose only justification is "it seemed interesting"? That last category is where blogs drift — catch it on the calendar, not six months deep.

The payoff compounds#

The first monthly plan mostly saves time. The third one starts compounding: clusters fill in, older spokes begin ranking together, updating becomes routine instead of archaeology, and the blank-page tax disappears from your weekly life entirely.

Deciding is the expensive part. Decide once, then spend the month doing the part you actually enjoy.

Related: our guide to internal linking pairs naturally with cluster planning, and the pre-publish SEO checklist covers what to verify before each scheduled slot goes live.

Enjoyed this article?

Share it with your network.

Share

Keep reading

Blog Analytics: The Five Numbers That Actually Matter
blogging

Blog Analytics: The Five Numbers That Actually Matter

Stop staring at dashboards. The only blog metrics worth tracking — what each one means, where to find it, and the action each should trigger.

4 min read
Refreshing Old Posts: The Cheapest Traffic You'll Ever Buy
blogging

Refreshing Old Posts: The Cheapest Traffic You'll Ever Buy

Why updating existing articles outperforms publishing new ones — how to find decay, what to change, and a seasonal audit that keeps an archive earning.

4 min read