Headline Formulas for Technical Blog Posts

50+ proven headline structures organized by format type. Fill in the blanks with your topic. Test 3-5 variations for each post, then pick the one that balances clarity with curiosity.

Universal Rules for Technical Headlines

1. Specificity beats cleverness — "How to Reduce Docker Image Size by 80%" outperforms "Docker Images: A Better Way"

2. Include the technology name — Readers scan for their stack. "React" or "Postgres" in the title gets clicks from the right people.

3. Numbers create commitment — "7 Patterns" tells the reader exactly what they're getting

4. Promise a transformation — Before state → After state (implicitly or explicitly)

5. Front-load keywords — Search engines and readers scan left-to-right. Put the important word first.

Tutorial Headlines

Comparison Headlines

How-To Headlines

Opinion Headlines

Case Study Headlines

Listicle Headlines

Deep Dive Headlines

Announcement Headlines

Migration Story Headlines

Benchmark Headlines

X in Y Minutes Headlines

Troubleshooting Headlines

Architecture Breakdown Headlines

Headline Testing Tips

1. Write 5 headline variations for every post

2. Test the top 2 on Twitter (post both as tweets, see which gets more engagement)

3. Use the winning headline for the blog post

4. A/B test titles on your platform if it supports it (some CMSes do)

5. Revisit and update headlines on older posts if they're underperforming in search

SEO Checklist for Technical Blog Posts

Run through this checklist before hitting publish on every post. Not every item applies to every post, but skipping more than 3-4 means you're leaving organic traffic on the table.

Pre-Writing SEO

• [ ] Primary keyword identified — One specific phrase this post will rank for
• [ ] Search intent matched — Your content format matches what Google already ranks (informational query = guide, not product page)
• [ ] Keyword difficulty assessed — For new blogs (DA < 30), target KD below 40. Established blogs can go higher.
• [ ] 3-5 secondary keywords listed — Related terms to weave naturally into headings and body text
• [ ] Competitor content audited — Read the top 3 results. Know what they cover and what they miss.
• [ ] Content gap identified — Your unique angle, data, or depth that existing content lacks

Title & Meta

• [ ] Title contains primary keyword — Ideally within the first 60 characters
• [ ] Title is under 60 characters — Or at least the meaningful part is (Google truncates at ~60)
• [ ] Title creates curiosity or promises value — Not just a keyword — a reason to click
• [ ] Meta description written — 150-160 characters. Includes primary keyword. Answers "why click this?"
• [ ] URL slug is short and keyword-rich — /property-based-testing-guide not /2025/01/20/how-to-use-property-based-testing-in-your-projects
• [ ] URL uses hyphens, not underscores — Google treats hyphens as word separators

Content Structure

• [ ] H1 tag is the title — One H1 per page, matches or closely mirrors the title tag
• [ ] H2 headings used for main sections — Include keywords naturally where they fit
• [ ] H3 headings for subsections — Create a clear hierarchy (never skip from H2 to H4)
• [ ] Introduction answers the search query within 100 words — Don't bury the lede behind a long preamble
• [ ] Table of contents included (for posts > 2,000 words) — Helps readers and generates jump-link rich snippets
• [ ] Short paragraphs — 2-4 sentences max. Walls of text kill time-on-page.
• [ ] Lists and tables used where appropriate — These often become featured snippets

Keyword Usage

• [ ] Primary keyword in first 100 words — Signal to Google what this page is about early
• [ ] Primary keyword in at least one H2 — Naturally, not forced
• [ ] Secondary keywords used in body text — 1-2 uses each, naturally integrated
• [ ] No keyword stuffing — If it sounds unnatural when read aloud, rewrite it
• [ ] Semantic variations used — Don't repeat exact phrase 15 times. Use related terms, synonyms, acronyms.
• [ ] Keyword in image alt text (at least one image) — Describe the image AND include the keyword if natural

Internal Linking

• [ ] 2-3 internal links to related posts — Link to your other content on the same topic cluster
• [ ] Links use descriptive anchor text — "our guide to database indexing" not "click here"
• [ ] Link to your pillar page (if applicable) — Strengthens the topical cluster
• [ ] Link FROM older related posts TO this new post — Go back and add links. This is the most overlooked SEO tactic.
• [ ] No orphan pages — Every post should have at least one internal link pointing to it

External Linking

• [ ] 2-5 external links to authoritative sources — Link to documentation, research papers, original sources
• [ ] External links open in new tab — Don't navigate readers away from your site
• [ ] No broken external links — Verify URLs work before publishing
• [ ] Links go to canonical sources — Link to official docs, not random blog rehashes

Images & Media

• [ ] At least one image per post — Diagrams, screenshots, code output, architecture drawings
• [ ] Images have descriptive alt text — For accessibility AND image search. Describe what's shown.
• [ ] Images are compressed — Use WebP or compressed PNG. Large images kill page speed.
• [ ] Images have descriptive file names — database-indexing-btree-diagram.png not screenshot-2025-01-20.png
• [ ] Featured/social image set — This appears in Twitter cards, LinkedIn previews, etc.

Technical SEO

• [ ] Page loads in under 3 seconds — Check with browser devtools network tab
• [ ] Mobile-friendly layout — Code blocks scroll horizontally, images resize, text is readable
• [ ] Canonical URL set — Especially important for cross-posted content (Dev.to, Hashnode)
• [ ] Schema markup present — Article schema with author, date published, date modified
• [ ] No duplicate content issues — If cross-posting, ALWAYS set canonical back to your site
• [ ] Sitemap includes this URL — Most CMSes handle this automatically
• [ ] No noindex tag — Double-check your CMS isn't accidentally blocking search engines

Content Quality Signals (Indirect SEO)

• [ ] Word count matches intent — Is your content as thorough as (or more than) the top-ranking posts?
• [ ] Code examples are runnable — Copy-paste code should work. Broken code = high bounce rate.
• [ ] Content is original — Not rehashed from documentation or other blog posts
• [ ] Published date visible — Freshness signals. Readers and Google trust dated content.
• [ ] Author information present — Author bio with credentials builds E-E-A-T (Experience, Expertise, Authority, Trust)
• [ ] Updated date shown (for evergreen content) — "Last updated: January 2025" signals freshness

Post-Publish SEO

• [ ] Submit to Google Search Console — Request indexing for faster discovery
• [ ] Share on social media — Social signals don't directly rank, but they drive initial traffic and backlinks
• [ ] Monitor Search Console for impressions — After 1-2 weeks, check what queries this page appears for
• [ ] Track target keyword position — Weekly for the first month, then monthly
• [ ] Update older posts to link to this one — Cross-link within your content cluster
• [ ] Plan a content refresh — Set a calendar reminder to update this post in 6-12 months

Quick Reference: SEO Metadata Template

Title: [Primary Keyword]: [Value Proposition] (under 60 chars)
Meta Description: [Action verb] [what reader learns/gets]. [Specific detail]. [Outcome/benefit]. (150-160 chars)
URL: /[primary-keyword-short-form]
Canonical: https://yourblog.example.com/[slug]

Example:

Title: Property-Based Testing: Finding Bugs Unit Tests Miss
Meta Description: Learn property-based testing with real Python examples. Find bugs your unit tests miss using Hypothesis. Includes a decision framework.
URL: /property-based-testing-guide
Canonical: https://yourblog.example.com/property-based-testing-guide

Content Type SEO Quick Wins