✍️ Blog Generator Prompt

A blog generator prompt directs an LLM to produce SEO-optimized, well-structured blog posts that match a specific tone, audience, and content strategy. The difference between a mediocre AI blog post and a great one lies entirely in the prompt.

Why This Matters

Content marketing drives 67% more leads than traditional marketing. But search engines penalize thin, generic content. A production-quality blog prompt ensures every post has a clear structure, targets real search intent, and reads like it was written by a domain expert — not a chatbot.

The Production Prompt

Blog Generator — Full System Prompt

You are an expert content strategist and SEO copywriter with 10+ years of experience writing for B2B SaaS audiences.

**Task:** Write a complete blog post based on the brief below.

**Blog Brief:**
- Topic: {{topic}}
- Primary keyword: {{primary_keyword}}
- Secondary keywords: {{secondary_keywords}}
- Target audience: {{audience}}
- Tone: {{tone}} (e.g., professional yet conversational, authoritative, friendly)
- Word count: {{word_count}} words
- Goal: {{goal}} (e.g., educate, convert, build authority)

**Structure Requirements:**
1. **Title:** Create an engaging H1 title (under 60 characters) that includes the primary keyword.
2. **Meta description:** Write a 150–160 character meta description with the primary keyword.
3. **Introduction (100–150 words):** Hook the reader with a surprising stat, question, or pain point. State what the post will cover.
4. **Body (organized with H2 and H3 subheadings):**
   - Use 3–5 main sections with descriptive H2 headings
   - Include H3 subheadings where sections are complex
   - Naturally embed primary keyword 3–5 times and each secondary keyword 1–2 times
   - Include at least one bulleted or numbered list
   - Add one concrete example or case study per section
5. **Conclusion (80–120 words):** Summarize key takeaways and include a clear call-to-action.
6. **FAQ section:** Add 3 frequently asked questions with concise answers (for featured snippet eligibility).

**SEO Rules:**
- Primary keyword in: title, first paragraph, one H2, meta description, conclusion
- Use semantic variations throughout — avoid exact-match keyword stuffing
- Write short paragraphs (2–4 sentences max)
- Use transition words between sections

**Output:** Markdown format with proper heading hierarchy.

Bad vs. Improved Prompts

❌ Bad Prompt

Write a blog post about prompt engineering.

Why it fails: No keyword strategy, no audience, no structure, no tone guidance, no word count. The output will be a bland, unranked, unfocused wall of text.

✅ Improved Prompt

You are an expert content writer specializing in AI and developer education.

Write a 1,500-word blog post targeting the keyword "prompt engineering best practices".

Audience: Software developers who are new to working with LLMs.
Tone: Professional but approachable — like a senior engineer mentoring a junior.

Structure:
- H1 title under 60 characters including the keyword
- Meta description (155 chars) with the keyword
- Introduction with a hook about why most developers write bad prompts
- 4 main H2 sections covering: clarity, context, examples, iteration
- Each section: explanation + concrete before/after prompt example
- Conclusion with 3 key takeaways and CTA to try the techniques
- 3 FAQs for featured snippet targeting

SEO: Use "prompt engineering best practices" 4 times naturally. Include semantic variants: "writing better prompts", "LLM prompt tips", "AI prompt techniques".

Output in Markdown.

Try It Yourself

🧪 Try It Yourself

Edit the prompt and click Run to see the AI response.

You are an expert content writer specializing in AI and developer education. Write a 1,500-word blog post targeting the keyword "prompt engineering best practices". Audience: Software developers new to working with LLMs. Tone: Professional but approachable — like a senior engineer mentoring a junior. Structure: - H1 title under 60 characters including the keyword - Meta description (155 chars) with the keyword - Introduction with a hook about why most developers write bad prompts - 4 main H2 sections: clarity, context, examples, iteration - Each section: explanation + before/after prompt example - Conclusion with 3 key takeaways and CTA - 3 FAQs for featured snippets SEO: "prompt engineering best practices" 4x naturally. Variants: "writing better prompts", "LLM prompt tips". Output in Markdown.

Tips for Customization

Customization	How to Modify the Prompt
Tone shift	Change the tone field: "witty and informal" for consumer brands, "authoritative and data-driven" for enterprise
Content type	Swap "blog post" for "listicle", "how-to guide", "comparison post", or "pillar page"
Internal linking	Add: "Naturally reference and link to these existing posts: [URL1], [URL2]"
Content upgrades	Append: "Suggest a downloadable lead magnet idea related to this topic"
Multi-language	Add: "Write the post in {{language}} while keeping SEO keywords in English for URL slugs"

Practice Challenge

Challenge

Pick a topic you know well. Write a blog brief using the template above, then generate the post. Now evaluate it:

1. Does the primary keyword appear in the title, first paragraph, one H2, and the conclusion?
2. Are paragraphs under 4 sentences?
3. Is there at least one concrete example per section?
4. Would you actually publish this? What would you change?

Real-World Scenario

Scenario: A SaaS company needs to publish 20 blog posts per month to support their content marketing funnel.

Implementation approach:

1. Content team creates blog briefs in a spreadsheet (topic, keyword, audience, goal)
2. Each brief is injected into the blog generator prompt template via API
3. LLM generates first drafts with temperature: 0.7 (balanced creativity)
4. Automated checks: keyword density, readability score (Flesch-Kincaid), heading structure
5. Human editor reviews, adds brand-specific examples, and approves for publication
6. Published with automated internal link insertion and schema markup

This reduces per-article production time from 4 hours to under 45 minutes while maintaining quality.

Interview Question

Interview Question

Q: How do you prevent AI-generated blog content from sounding generic or being flagged as AI-written?

A: Three strategies work together:

1. Inject specificity into the prompt — include real company data, case studies, and named examples rather than letting the model invent generic ones
2. Control tone with a reference sample — include 2–3 sentences of the brand's existing writing and say "match this voice"
3. Post-processing — have the model generate a draft, then run a second prompt that says "rewrite this to sound more like a human expert sharing hard-won lessons — add one personal anecdote and remove any overly polished transitions"
4. Temperature tuning — use 0.7–0.9 for creative sections (intros, hooks) and 0.3–0.5 for factual sections (technical explanations)

Summary

Summary

• A blog generator prompt must specify keyword targets, audience, tone, structure, and word count
• Always require proper heading hierarchy (H1 → H2 → H3) and short paragraphs for readability
• Include explicit SEO rules: keyword placement in title, first paragraph, H2, and conclusion
• Request concrete examples in every section to avoid generic output
• Use moderate temperature (0.6–0.8) for blog content — you want creativity within structure