SEO
SEO title generator for blog posts and guides
By Charles Summers · Updated · Free, no signup
Short answer
A blog title that fits cleanly in a search results snippet can still get cut in an odd place inside Google Discover, because Discover renders headlines over a larger card with less consistent width than a text-only SERP. This tool generates five blog title options built to survive both contexts, front-loads the specific claim rather than a generic hook, and checks description length against the 150 to 158 character range that resists mid-sentence truncation on both surfaces.
Use the seo meta tag generator
Why blog posts need a different approach
A blog post has to earn a click in two different visual contexts that most title advice treats as one. A classic search results page shows a title as a single line of text at a fixed pixel width. Google Discover shows the same headline as an overlay on a card with an image, often at a wider point size, which means the same title can wrap or truncate at a completely different character than it does in search.
This variant of the generator keeps the blog template but orders title options so the specific claim, the part that actually earns the click, sits in the first 40 to 50 characters rather than after a generic hook phrase like "the complete guide". Front-loading the specific detail protects the title if Discover truncates it earlier than a search snippet would, since the part most likely to survive the cut is the part readers see first either way.
It runs entirely in your browser. Nothing you type is sent to a server, no account is required, and there is no usage limit, because there is no cost per run to control.
The title tag and the H1 are two different promises
Almost every CMS sets them to the same string by default, and on editorial content that default costs you both ways. The H1 is read by someone who has already committed a click and wants to feel they arrived somewhere written by a person. The title tag is read by someone comparing ten options in a list, who wants to know what they will get and how long it will take. Those are different jobs and one sentence rarely does both.
The practical division is that the H1 can carry the voice and the title tag carries the specification. An H1 of Nobody reads your onboarding emails is a good editorial opening and a poor title tag. A title tag of Onboarding Email Sequence: 7 Examples and a Template is a poor headline and an excellent result listing. Write both, let them differ in tone, and make sure they do not contradict each other on subject.
There is a mechanical reason not to write a clever H1 without a solid title tag. The H1 is one of the sources drawn on when a title gets replaced in results, so a piece of wordplay you intended for readers can end up as your snippet. If your titles are being substituted on editorial content, look at the H1 before blaming the title.
What an informational searcher is actually scanning for
Someone with a commercial query is choosing a supplier. Someone with an informational query is choosing a source, and they are triaging fast because a results page for a how-to query contains ten pieces that all appear to answer it. What separates the clicked result is almost never persuasion. It is evidence of shape and freshness, delivered in a handful of words.
Expectations should be set honestly here too. Informational results sit under featured snippets, video carousels and generated summaries, so a good title collects a smaller pool of clicks than the same title would on a commercial query. That is a reason to write for the searcher who still needs the full answer, rather than to chase a number that the page layout has already capped.
- The format word. Template, checklist, examples, script, calculator. It promises a shape, and shape is what a scanner is sorting on.
- A count. A specific number implies the piece has been organised rather than written at length, and it is easy to compare against the result above it.
- The year, but only where it genuinely matters. On changing topics it signals currency. On evergreen ones it dates your page the moment January arrives.
- The searcher's phrasing, not your house style. Matched terms get bolded, and mirroring the query is free visual weight in a list of results that mostly do not.
- The exclusion. Without a developer, for teams under ten, free tools only. Narrowing loses you clicks you did not want and wins the ones you did.
Mistakes that quietly cost you results
- Letting the CMS copy the H1 into the title tag on every post
- Editorial headlines rely on curiosity and context that a results listing does not provide, so they underperform badly out of context. Treat them as two fields with two jobs, and only merge them where the H1 happens to be plainly descriptive.
- Writing the description as a summary of the article
- A description that restates the intro gives a scanner no reason to prefer you. Say what the reader will be able to do afterwards, or name the specific thing in the piece that the other nine results do not have.
- Hard-coding the year and never revisiting it
- An old year in a result is the fastest way to lose a click to a fresher-looking competitor. Either keep a genuine annual update cycle on those posts or leave the year out, because the half-maintained version is worse than neither.
What does the output look like?
This is the exact output the tool produces from the example inputs. It is generated by the same code that runs when you click the button, so what you see here is what you get.
Frequently asked questions
How is a Google Discover headline different from a search results title?
A search results title is plain text at a fixed pixel width, truncated at roughly 580 pixels. A Discover headline sits over a larger image card, often at a different point size depending on device, so the same title can wrap onto a second line or get cut at a different character count. A title tuned only for search can read oddly in Discover.
Why does my blog title look fine in search but get cut oddly in Discover?
Because Discover is not bound by the same pixel-width truncation rule as a classic snippet, it is rendering the headline over an image card whose available width varies by device and layout. The fix is to put the specific, load-bearing part of the title in the first 40 to 50 characters, so the part most likely to survive either truncation point is the part that matters.
Should a blog title include the year?
Only when the content is genuinely time-sensitive, such as pricing, regulation or a "best of" list that changes annually. A year in the title signals freshness for that kind of content, but on evergreen how-to content it adds characters without adding a reason to click, and it needs updating every twelve months or it starts working against you.
Does the meta description matter if Google usually pulls its own snippet from the body text?
Yes, because Google using your written description is common on informational content when it closely matches the query, and it is what displays for branded searches regardless. Writing a complete, on-target sentence in the 150 to 158 character range improves the odds it gets used rather than replaced with a body-text fragment.
Related free tools
- SEO Meta Tag Generator SEO
- SEO Meta Tag Generator for ecommerce product pages SEO
- SEO Meta Tag Generator for local business SEO
- SEO Meta Tag Generator for comparison pages SEO
- Schema Markup Generator for software apps SEO
- Schema Markup Generator for breadcrumbs SEO
- SEO Traffic Forecaster SEO
- CAC Payback Period Calculator for ecommerce Analytics
- CAC Payback Period Calculator for marketplaces Analytics
Some links on this site are affiliate links, which means Hacking Demand may earn a commission if you buy through them at no extra cost to you. This does not influence which tools are listed. The tools on this page are free and have no affiliate relationship of any kind.