blog-title-generator
Blog Title Generator
Generate 10 blog title variations, each with a title tag and H1, scored across 5 dimensions with a short explanation of why it works.
Shared Input Handling
Assume the user has a blog draft, blog file, or at least a blog idea. Do not generate titles from a bare keyword alone.
- If the user provides a blog file such as
abc.md, read it and use it as the primary context - If the user provides a blog draft, outline, idea, or blog URL, use that as the content context
- If the user provides only a keyword or short query, do not continue yet; ask what blog they plan to write so you have the actual post context
Only continue into a mode after blog context is available.
Phase 0: Choose Mode
Ask the user (AskUserQuestion): "Want SERP-grounded titles first? That requires authenticating RankEarly MCP and may consume RankEarly credits. Or I can generate quick titles right away without analyzing SERP."
- If the user wants SERP analysis -> read
references/serp-mode.mdand follow it, then return here for Phase 1 - If the user wants quick titles -> read
references/quick-mode.mdand follow it, then return here for Phase 1
Phase 1: Score, Annotate, and Present
After generating 10 title variations (from either mode), apply the following to each title.
Dual output per variation
For each of the 10 variations, produce:
- Title Tag — CTR-optimized for SERP display. Usually aim for 50-65 characters, but go longer when clarity wins. Front-load the primary phrase when possible.
- H1 — Reader-optimized for on-page experience. No character cap. Can be more conversational, descriptive, or provocative.
In SERP mode, optimize each title around the confirmed keyword and the blog context. In quick mode, optimize around the user's blog context.
Score each title
Evaluate each title tag across 5 dimensions using qualitative labels (not numeric scores — labels are immediately actionable):
| Dimension | What to evaluate | Labels |
|---|---|---|
| Primary Phrase Placement | Is the chosen keyword for that title (SERP mode) or main topic phrase (quick mode) in the first 3 words? First half? Second half? | Front-loaded / Mid-placed / Buried |
| Character Length | Character count relative to the usual 50-65 char target range | Strong (50-65) / Acceptable (40-49 or 66-75) / Long (76+) |
| Power Words | Proven engagement words: definitive, proven, free, steal, easy, fast, etc. | Strong (2+) / Present (1) / None |
| Specificity | Numbers, percentages, timeframes, platform names, audience qualifiers | High / Moderate / Low |
| Emotional Sentiment | What emotion does the title trigger? | Positive / Negative / Neutral — plus the specific emotion (curiosity, fear, aspiration, urgency) |
Also show:
- Exact character count for the title tag
- Note when the title tag is longer than 65 characters
Annotate each title
Add a 1-2 sentence annotation explaining the copywriting technique and why it works. Be specific about the effect; avoid generic comments like "uses a number and a power word."
Per-title output format
### Title [N]: [Format Type]
**Title Tag** (XX chars): [title tag version]
**H1**: [H1 version]
**Scores:**
- Primary Phrase Placement: [label]
- Character Length: [label] — XX chars
- Power Words: [label] — [list the power words]
- Specificity: [label] — [what elements]
- Sentiment: [label] — [specific emotion]
**Why this works:** [1-2 sentence annotation]
Recommendations
Close with 3-5 sentences highlighting:
- Which 2-3 titles are strongest and why
- Any trade-offs the user should consider
More from rankearly/rankearly-skills
blog-creator
Umbrella skill for ANY blog-related task — research, outline, write, audit, humanize, illustrate. Use when the user mentions blog posts, outlines, drafts, blog images, or wants to audit/humanize/rewrite blog content.
14blog-image
Generate a Nanobanana Pro prompt for blog images - either a scroll-stopping cover or an explanatory in-post illustration. Use when the user asks for a "blog cover", "blog image", "post thumbnail", "illustration for my blog", "header image", or wants to create a visual for a blog post or article section.
11seo-memory
Maintain a project knowledge file for SEO content creation. Use when the user shares critical context about their project — product renames, new/removed features, service changes, subproduct launches, pricing updates, audience shifts, or any factual change that SEO content should reflect. Also triggers on "update seo memory", "remember this for content", "initialize seo memory from domain", or when the user corrects a factual detail about their product/service. Even small updates matter — stale project facts in published content erode trust.
10topic-research
Expand topics into keywords or cluster a keyword library into topics and keyword clusters using RankEarly. Use when the user asks for keyword expansion, topic clustering, content clusters, topic maps, keyword research, or content planning tied to a keyword library.
10serp-gap-analysis
Analyze a live Google SERP for keyword winnability and competitor gaps. Use when the user asks for SERP analysis, real-result keyword difficulty, SEO competitor analysis, content gap analysis, or a brief or content plan for a specific keyword or query.
10content-researcher
Collect what high-ranking content covers about a topic, surface under-discussed subjects, and discover information gains (unique takes). Use when the user wants to research before writing — "research X for me", "find information gains for X", "find content gaps about X", "what are competitors missing about X", or any request to analyze what's already ranking.
7