I have published over a hundred articles across various platforms. The single biggest predictor of whether something gets read is not the quality of the writing. It is the title. I have seen mediocre articles with great titles outperform excellent articles with bland titles by 10x.
This is not speculation. On Medium, you can see the view-to-read ratio. On Dev.to, you can track impressions versus clicks. The pattern is consistent: the title does 80% of the work of getting someone to start reading.
What makes a title work
After analyzing which of my articles performed best and studying headline patterns across successful publications, I have identified a few consistent principles.
Specificity beats generality. "How to Write Better Code" is vague. "The 3 Refactoring Patterns That Cut My Bug Rate in Half" is specific. Specificity implies the author has actual experience and concrete knowledge to share, not just opinions.
Numbers work. "Tips for Better Sleep" vs. "7 Sleep Changes That Fixed My 3 AM Wake-Ups." Numbers set expectations for length and structure. They promise a scannable article. They also signal that the author has distilled their knowledge into a finite, organized set.
Tension and curiosity. "Understanding React Hooks" vs. "The React Hook I Regret Using in Every Project." The second creates a gap between what the reader knows and what they want to know. That gap drives clicks. But the curiosity must be honest -- clickbait titles that do not deliver destroy trust.
Problem-first framing. Leading with the problem the reader has, rather than the solution you built, creates immediate relevance. "New CSS Grid Tutorial" speaks to what you made. "Why Your Layouts Break on Mobile (and the CSS Fix)" speaks to what the reader struggles with.
The anatomy of a bad title
Bad titles share common patterns:
Too broad. "JavaScript Tips" -- which tips? For whom? At what level? There is no reason for any specific person to click this.
Too clever. Puns and wordplay that require context to understand. If the reader has to think about what the title means, they will not click. Clarity beats cleverness every time.
No benefit signaled. "My Experience with Docker" tells me nothing about what I will gain by reading. "How Docker Simplified My Deployment from 4 Hours to 15 Minutes" tells me exactly what value awaits.
Passive voice. "React Hooks Were Used to Build a Dashboard" vs. "I Built a Real-Time Dashboard with Three React Hooks." Active voice is more engaging and more human.
Genre-specific title patterns
For fiction and creative writing, the rules shift. Story titles serve a different purpose -- they set tone, evoke atmosphere, and hint at theme.
Literary fiction tends toward evocative, often single-word or short-phrase titles that become meaningful after reading. "Beloved." "Atonement." "The Road."
Genre fiction tends toward titles that signal the genre clearly. Thriller titles imply danger and stakes. Romance titles suggest relationships. Sci-fi titles hint at the world.
Short stories benefit from titles that create intrigue with minimal words. "The Lottery" by Shirley Jackson. "Cathedral" by Raymond Carver. The title gains meaning in retrospect.
The testing approach
For non-fiction, I test titles before publishing. I will write 5-10 candidate titles, then evaluate each against four criteria:
- Does it clearly signal what the reader will learn or gain?
- Does it create a curiosity gap without being dishonest?
- Is it specific enough to target a real audience?
- Would I click on this if I saw it in a feed?
If a title does not pass all four, I iterate. This takes 10-15 minutes and is the highest-leverage time investment in the entire publishing process.
Generating starting points
Coming up with initial title candidates is the hardest part. Staring at a blank line is unproductive. I built a story title generator at zovo.one/free-tools/story-title-generator that generates title variations based on genre, theme, and tone. I use it as a brainstorming accelerator -- not to use titles verbatim, but to break through the blank-page problem and find angles I had not considered.
A great title does not write itself. But starting from a set of structured suggestions is far more productive than starting from nothing.
I'm Michael Lip. I build free developer tools at zovo.one. 500+ tools, all private, all free.
Top comments (0)