Blog Outline Prompt Generator
Generate a structured, SEO-aware blog post outline prompt with specific H2 sections instead of generic “Introduction/Conclusion” headers.
A blog post that actually satisfies search intent needs an outline built around the specific question a reader is trying to answer, not just a list of subtopics related to the keyword. This tool builds an outline structured around answering that intent directly and completely, section by section.
How to use it
What the post needs to rank for and actually answer.
The specific intent behind the search shapes which subtopics actually belong in the outline.
Each section maps to a specific part of answering the reader's actual question.
Tips for better results
- Put the direct answer in the first section, not buried in the middle. Readers and search engines both reward content that answers the core question early, then expands.
- Cut sections that don't serve the stated intent. A related-but-tangential section dilutes the post's usefulness for the reader who searched this question.
- Include a specific example or case in at least one section. Outlines that are all abstract advice tend to produce posts that feel generic once actually written.
Example output
“For how to price freelance work, outlines: the direct answer first (hourly vs. project-based, and when each makes sense), then common pricing mistakes, then a worked example, then how to raise rates with existing clients.”
TL;DR
A blog post written from a vague prompt tends to wander — the AI guesses at structure as it goes, and the piece ends up needing a full rewrite anyway. An outline built first solves that: you decide the angle, audience, and section order before a single paragraph gets written.
Why an outline first beats asking for a full draft
Asking an AI model to “write a blog post about X” skips the planning that makes long-form content useful. Building the outline first means you’re making the structural decisions, and the model fills in supporting detail underneath choices you’ve already made.
This matters most for search-intent content specifically, since a post competing to rank has to actually answer the query better than the ten other results already on the page. An outline built around real sub-topics a reader would search for individually gives the finished post a structural advantage that’s hard to retrofit after the fact — it’s far easier to plan for comprehensive coverage than to notice a gap once 2,000 words are already written.
What each field is doing
- Goal changes section priority — an SEO goal front-loads the searchable sub-topics, while a persuade goal builds toward a decision.
- Angle decides structure — a listicle and a deep-dive guide organize the same topic very differently.
- Target keyword anchors the H1 and intro without forcing unnatural repetition throughout.
- Target length should match how much the topic genuinely needs — padding a short topic to hit a pillar word count reads as filler.
Describing a post on negotiating salary after a job offer, for early-career professionals, SEO goal, how-to angle produces:
“Create a detailed blog post outline about: how to negotiate your salary after a job offer.
Audience: early-career professionals who just received their first real offer.
Target SEO keyword: how to negotiate salary after job offer.
No generic filler headers like ‘Introduction’ or ‘Conclusion.'”
That produces specific, searchable H2 headers instead of generic section labels.
Using this across ChatGPT, Claude, and Gemini
Claude tends to give the most consistently specific H2 headers rather than generic ones — if another model’s output feels too broad, ask it to make each header something a person would actually search. ChatGPT sometimes adds an extra “Conclusion” header despite the instruction against it; just remove and rename it.
FAQ
Will this write the full blog post for me?
No — it generates the outline prompt. You or the AI, working section by section, still write the actual post.
What if I don’t have a specific SEO keyword yet?
Leave that field blank — the outline will still be built around the topic and goal.
How is this different from just asking for “a blog post outline”?
A bare request gives the model no information about audience, goal, or angle, so it defaults to a generic structure.
Can I use this for a pillar/cornerstone guide?
Yes — set length to “3000+ (pillar)” for a more comprehensive section structure.
Should I write the intro before or after the rest of the post?
Many writers find it easier to draft the body from the outline first, then come back and write a sharper intro once the actual argument is fully formed.