What this prompt does
This prompt generates a search-optimized blog post outline built to rank, not just fill space. It produces title-tag options under 60 characters, a meta description under 155 characters with a call to action, and an H1/H2/H3 heading structure that targets your [secondary_keywords]. For each section it specifies the key points to cover, a target word count, and internal-link opportunities, then identifies which section can win a featured snippet and adds a People-Also-Ask FAQ section.
The variables anchor the outline to your keyword and audience. [topic] and [primary_keyword] define the subject and the main term to rank for, while [search_volume] provides context on demand. [secondary_keywords] spread coverage across headings so the post captures related queries, and [faq_count] sets how many People-Also-Ask questions to include. [audience] keeps the depth and tone right — intermediate developers need different framing than beginners — and [word_count] sizes the whole piece. The result maps keyword, structure, and snippet target up front so a draft becomes something that ranks.
When to use it
- You are planning a technical post and want the keyword, headings, and snippet target mapped before writing.
- A draft idea needs an SEO skeleton so it ranks instead of just reading well.
- You want to target a featured snippet and need to know which section should win position zero.
- Covering
[secondary_keywords]across the heading structure to capture related searches. - Adding a People-Also-Ask FAQ section with
[faq_count]questions for extra query coverage. - Doing content-gap analysis to cover what competitors rank for but cover thinly.
Example output
Expect a complete outline: a few title-tag options under 60 characters, a meta description under 155 characters with a CTA, and an H1 with H2/H3 headings targeting your [secondary_keywords]. Each section lists key points, a target word count, and internal-link ideas. You also get a featured-snippet recommendation, a [faq_count]-question FAQ from People Also Ask, a schema-type suggestion, content-gap notes, image and alt-text ideas, and a CTA placement strategy.
Pro tips
- Get
[primary_keyword]right, since the title, headings, and snippet target all build around it; a vague keyword produces a vague, unfocused outline. - Use
[secondary_keywords]to broaden coverage across H2s and H3s, but keep them natural — the goal is related-query capture, not keyword stuffing. - Match
[audience]honestly to set depth; an outline for intermediate developers reads very differently from one for beginners, and mismatched depth loses readers. - Treat the featured-snippet recommendation seriously — structuring one section as a concise, direct answer is what wins position zero.
- Right-size
[word_count]to the topic and competition rather than padding; thin content and bloated content both underperform for different reasons. - Use the content-gap notes to go deeper than competitors on the points they cover thinly, which is often what earns the ranking.
