A Developer Blog on a Static Site: Keyword Planning Without Sounding Robotic
Balancing what you love to write with what people actually search for is not a betrayal of your voice—it is how posts get read.
Sometimes we write about topics we care about while search traffic clusters around other people’s problems. There is nothing wrong with writing for yourself first, but if you want the blog to reach people who are looking for answers, you need a lightweight keyword map that does not turn every paragraph into a checklist. I treat it like a small chart: posts that prove depth, posts that answer recurring questions, and a little room to experiment.
Interest keywords versus demand keywords
“Interest” keywords shape identity—they show how you think, what you try, what caught your attention. “Demand” keywords shape reach—people type specific queries when something is blocking them. A strong blog holds both: your voice stays visible, yet titles and intros still signal which layer of the problem you are solving for humans and for search.
Linking each article to one home base
Your home or about page is the hub that should explain who you are in seconds. Articles are the spokes: each one can gently point to what you actually ship without turning into an ad. One closing line that ties the topic to your offer usually beats ten scattered links.
A quick pre-publish checklist
- Does the title communicate the angle, not just the domain?
- Does the intro answer “why read this now?”
- Did you include one clear term that matches a real query without awkward repetition?
- Would the page still help someone who has never heard of you?
Keywords are a compass, not a cage. Write the way you would explain things to a teammate, then revisit the title and snippet with a tired reader’s eyes.
Parting question: What is one topic you love writing about, and how might a stranger phrase it as a Google search?