How to Write Better Headlines: 12 Practical Rules

Twelve practical rules for writing clearer, more clickable headlines that still deliver on the promise in the article.

Match one search intent per headline

Each page should answer one primary question: informational (“what is…”), comparative (“X vs Y”), or transactional (“free tool for…”). Headlines that blend intents (“Best Title Case Tool and Complete History of English”) dilute the snippet and confuse crawlers about the main topic.

Put the primary keyword early

Place the core phrase near the start when it reads naturally: “Title Case Rules for Blog Editors” beats “Blog Editors: Here Are Rules for Title Case” for quick SERP scanning. Do not stuff keywords—read the headline aloud once.

Use specificity over hype

Numbers, time frames, and constraints build trust: “7 APA Title Case Rules” outperforms vague “Amazing Title Case Secrets.” Specificity also earns long-tail queries without extra pages.

Promise only what the body delivers

Misleading headlines increase bounce rate, which hurts engagement signals. If the article covers three rules, say three—not “complete guide” unless you truly cover edge cases, exceptions, and examples.

Keep length practical for SERPs

Aim for roughly 50–65 characters for the core promise so Google is less likely to truncate awkwardly. Put differentiators (year, audience, tool name) after the main clause if space is tight.

Edit capitalization last

Draft in sentence case for speed, then apply title case or your house style once the wording is final. Automated converters save time but always fix proper nouns and product names manually.

Front-load the outcome for tool and how-to pages

Utility pages convert better when the headline names the job: “Random Number Generator” or “Title Case Converter” beats clever metaphors. Pair the H1 with one supporting sentence that states the range, format, or audience, then put proof (examples, FAQs) below the fold.

Reuse a capitalization system across the cluster

If blog posts use title case and tool H1s use sentence case (or the reverse), SERP snippets from the same brand look inconsistent. Document one default for marketing pages and one for product UI, then run drafts through a title case or sentence case converter before publish.

Link the promise to a working tool

When a headline claims “free online formatter,” the first viewport should expose the tool. Internal links from related guides (headline rules, case comparisons) should point at the live converters readers will actually use—not only at more articles.

Frequently asked questions

How long should SEO headlines be?

There is no fixed limit, but concise titles that state the benefit in the first half tend to perform better in search and social previews.

Should headlines include the brand name?

Add the brand when it helps recognition or disambiguation (“| Case Modify”). Skip it on very long titles where the brand pushes critical words out of the snippet.

Should tool pages use different headline rules than blog posts?

Often yes: tool H1s stay literal and short; blog titles can carry numbers, years, or audience cues. Keep capitalization consistent within each template.

Explore Case Modify

Case Modify publishes free browser-based text converters, code formatters, encoders, random generators, and unit calculators. Each page runs locally after load unless a tool page states otherwise.

  • Case convertersTitle case, sentence case, uppercase, lowercase, camelCase, PascalCase, snake_case, and kebab-case tools.
  • Code & DataJSON, HTML, CSS, JavaScript, XML, YAML, Markdown, GraphQL, TypeScript, and SCSS formatters.
  • JSON toolsFormat, minify, escape, stringify, and edit JSON in the browser.
  • Text toolsFind and replace, duplicate line removal, sorting, encoding, and cleanup utilities.
  • ConvertersLength, weight, temperature, time, volume, area, energy, and related conversion calculators.
  • Font stylesBold, italic, bubble, aesthetic, and platform-specific Unicode text generators.
  • Random generatorsRandom numbers, letters, passwords, UUIDs, dates, and related generators.
  • BlogGuides on title case, camelCase, JSON formatting, and developer naming conventions.

Machine-readable summaries: llms.txt, llms-full.txt, agents.txt.