Blogging That Works - Part 1: Build a Topic Map Before You Write

Most blogs fail for a scheduling reason disguised as a talent reason: the author runs out of things to write about that feel connected. A topic map fixes that before it happens. It is a one-page document that says what your blog is about, who it is for, and what you will publish for the next few months.

Why Keyword Lists Fall Short

A list of keywords tells you what people search for. It does not tell you:

• Whether you can write about it credibly.
• How this post relates to the last ten.
• What the reader should do next.

The result is a blog that reads like a pile of articles. Search engines forgive that; readers do not.

Start With the Reader’s Problem

Instead of “topics I could write about,” write down the problems your reader is trying to solve. For a developer-focused blog they might look like:

• “My site is slow and I do not know where to start.”
• “I want to self-host, but the server setup scares me.”
• “I publish posts, but nobody finds them.”

Each problem becomes a pillar: a broad theme you can return to for years. Three to five pillars is plenty. More than that and none of them get enough attention.

Cluster Posts Into Themes

Inside each pillar, outline clusters: three to eight posts that go deep on one slice of the problem. A cluster around self-hosting might be:

• Choosing a VPS plan
• Hardening a fresh server
• Deploying with containers
• Backups and monitoring

That is not a coincidence in this series — it is the shape a cluster takes when the posts are planned together. Clusters also give you internal links for free: every post links back to the pillar, and the pillar links out to each post.

Map Search Intent, Not Just Topics

Tag every planned post with the job it does:

Intent	Reader state	Example
Informational	Learning	“How SSH keys work”
Practical	Doing	“Hardening a fresh VPS”
Comparative	Deciding	“KVM vs. container VPS”
Navigational	Returning	“The Astro series index”

A healthy blog mixes intents. If every post is informational, readers learn a lot and never act.

A Worked Example

Here is the map for a blog about building and running web projects, compressed to one screen:

Pillar: Web Development
  Cluster: Astro from scratch        (5 posts)
  Cluster: Performance and SEO       (3 posts)
Pillar: Self-Hosting
  Cluster: VPS fundamentals          (4 posts)
  Cluster: Deployment and ops        (3 posts)
Pillar: Blogging
  Cluster: Strategy and workflow     (3 posts)
  Cluster: Distribution              (2 posts)

Twenty posts are now planned instead of staring back at a blank calendar. Each one has a home, a neighbor, and a reader problem to solve.

Keep It Alive

Revisit the map every quarter:

• Promote what worked. A cluster with traffic deserves more posts.
• Retire what did not. Do not keep a pillar alive out of guilt.
• Fill gaps before starting new pillars. Depth beats breadth for a blog with limited time.

Conclusion

A topic map turns writing from a weekly decision into a repeatable process. Once it exists, the next problem is execution — which is exactly what Part 2 covers: a writing workflow that gets posts out the door without waiting for inspiration.