Choosing a Blog Subject You Can Sustain
The advice is usually "find your passion". More useful: find something you can still write a hundredth post about without resenting it.
The standard advice is "pick a niche", usually followed by a list of profitable ones. That skips the part that actually determines whether you'll still be writing in two years: whether the subject can hold your attention across a hundred posts.
Why narrow wins
A narrow subject helps in three concrete ways, and none of them is really about search engines.
It tells a reader what they're getting. "Notes on Postgres performance" sets an expectation. "Thoughts on tech and life" doesn't, so nobody has a reason to return.
It makes writing easier, not harder. This is the counterintuitive one. A broad subject means every post starts with "what should this be about?" A narrow one means the subject supplies the questions and you just answer the next.
It's how you get found. A new site will not rank for "web development". It might reasonably rank for a specific question that few people have answered well. Narrow subjects produce specific questions.
The opposite failure
Less discussed, and just as common: choosing something so specific that it's exhausted after eight posts.
The distinction worth drawing is between a subject and a topic. "How to configure Nginx caching" is a topic — that's one post. "Running small sites on your own server" is a subject: caching is one post, backups another, TLS certificates another, and it keeps generating them.
A workable test: can you list twenty post titles without straining? Under ten and it's a topic, not a subject. If the twenty have nothing in common, it's too broad to build an audience around.
Test it before committing
The mistake is treating this as a decision to make once, in your head, before starting. It's cheaper to test.
Take your two or three candidates and, for each, actually write one post. Not an outline — a finished piece you'd be willing to publish. Then notice three things:
- How long it took. If a post on a subject you supposedly know well takes three painful evenings, that's information about the next hundred.
- Whether you had more to say at the end. Finishing with a list of follow-ups is the strongest signal available. Finishing relieved is also a signal.
- Whether you'd read it. Set it aside a week, then read it as a stranger.
A week or two of this is cheaper than eighteen months of resenting a subject you picked because a list said it was profitable.
"Follow your passion" isn't the whole answer
It's not wrong, it's incomplete. Enthusiasm gets you through the first ten posts and nothing beyond that.
What sustains a subject over years is closer to ongoing involvement. If you work with something regularly, you keep encountering real problems, and real problems are what good posts are made of. That's why "what I actually do" tends to outlast "what I find interesting".
It also produces better writing. A post about a problem you genuinely hit contains specifics — the error message, the thing you tried that didn't work — that research-only writing never has.
Where passion does matter: it decides which of several viable subjects you'll still tolerate on a bad week. Use it as a tiebreaker, not the whole criterion.
Subjects are allowed to move
The thing that makes this decision feel heavier than it is: people treat it as permanent. It isn't.
Most long-running blogs have drifted substantially from where they started, because the author's work changed and the writing followed. Readers who came for the original subject mostly stay if the quality holds, and the old archive keeps being useful to people arriving from search.
What genuinely constrains you later is the domain name, not the subject — which is a good argument for a name that describes you rather than one narrow topic. A subject can evolve; nginx-caching-tips.com cannot.
Pick something you can sustain for a year. A year of consistent writing tells you far more than any amount of deliberation, and by then you'll have evidence instead of guesses. How to Start a Blog That's Still Running in 10 Years covers the rest of the setup.
Launching a website? Use the Website Launch Checker →