Blog Post Generation Prompt Template

Use this template with Claude or GitHub Copilot to generate blog posts with consistent structure and SEO optimization.

Template Variables

Replace these placeholders with your specific requirements:

• TOPIC: [Main subject of the blog post]
• AUDIENCE: [Target readers: beginners, intermediate, advanced developers]
• KEY_POINTS: [3-5 main points to cover]
• TONE: [Professional, conversational, technical, tutorial-style]
• WORD_COUNT: [Target word count: 800-1500 recommended]
• CALL_TO_ACTION: [What should readers do after reading?]

Generation Prompt

Write a blog post about  for .

Target Audience: 
Tone: 
Target Length:  words

Key Points to Cover:


Call to Action:


Structure Requirements:
1. Engaging introduction that hooks the reader (2-3 paragraphs)
2. Main content divided into clear sections with H2/H3 headings
3. Code examples with syntax highlighting where appropriate
4. Practical examples or case studies
5. Best practices and common pitfalls
6. Conclusion with summary of key takeaways
7. Call to action

SEO Optimization:
- Include the primary keyword in the title and first paragraph
- Use semantic headings (H2, H3) with relevant keywords
- Add internal and external links where relevant
- Include alt text suggestions for any recommended images
- Optimize for featured snippet potential (use lists, tables, or definitions)

Frontmatter:
Generate appropriate frontmatter following this schema:
- title: (50-60 characters, include primary keyword)
- date: 
- author: 
- description: (150-160 characters, compelling meta description)
- meta_description: (if different from description)
- tags: (5-7 relevant tags)
- keywords: (primary and secondary SEO keywords)
- category: 
- reading_time: (estimated minutes)

Content Guidelines:
- Start with a hook that addresses a problem or question
- Use short paragraphs (2-4 sentences) for readability
- Include bullet points and numbered lists
- Add code blocks with language specification
- Include real-world examples
- Address common questions or misconceptions
- Use transition phrases between sections
- End with actionable next steps

Format the output as:
1. Frontmatter in YAML format
2. Blog post content in Markdown
3. SEO checklist at the end

Example Usage

Example 1: Tutorial Post

Write a blog post about Getting Started with GitHub Actions for beginners.

Target Audience: Developers new to CI/CD
Tone: Tutorial-style, friendly, step-by-step
Target Length: 1200 words

Key Points to Cover:
1. What are GitHub Actions and why use them
2. Setting up your first workflow
3. Understanding triggers and events
4. Common workflow patterns
5. Best practices for beginners

Call to Action:
Try creating your first GitHub Actions workflow and share your experience

[Rest of template filled in...]

Example 2: Deep Dive Technical Post

Write a blog post about Advanced Kubernetes Networking for advanced developers.

Target Audience: DevOps engineers and platform architects
Tone: Technical, detailed, authoritative
Target Length: 2000 words

Key Points to Cover:
1. Network policies and security
2. Service mesh integration (Istio/Linkerd)
3. CNI plugins comparison
4. Network troubleshooting techniques
5. Performance optimization

Call to Action:
Download our Kubernetes networking troubleshooting guide

[Rest of template filled in...]

Content Structure Guidelines

Introduction (2-3 paragraphs)

• Hook: Start with a compelling question, statistic, or problem statement
• Context: Explain why this topic matters
• Preview: Briefly outline what the post will cover
• Value Proposition: What will readers learn or be able to do?

Main Sections

Section Pattern

## Clear, Descriptive Heading

Brief introduction to this section (1-2 sentences).

### Subsection 1: Specific Topic

- Explanation of concept
- Code example or diagram
- Real-world use case
- Best practices

### Subsection 2: Related Topic

[Same pattern...]

Code Examples

Here's how to implement [feature]:

\`\`\`python
# Code with comments
code example here
\`\`\`

**Key points:**
- Explanation of what the code does
- Why this approach is recommended
- Common pitfalls to avoid

Conclusion

• Summary: Recap main points in 2-3 sentences
• Key Takeaways: Bullet list of 3-5 main lessons
• Next Steps: What should readers do next?
• Call to Action: Link to related content, tools, or resources

SEO Optimization Checklist

After generating content, verify:

• Title is 50-60 characters with primary keyword
• Meta description is 150-160 characters and compelling
• First paragraph includes primary keyword naturally
• Headings (H2, H3) use semantic keywords
• 5-7 relevant tags selected
• 3-5 keywords identified (primary and secondary)
• Internal links to related content (if available)
• External links to authoritative sources
• Alt text suggestions for images
• Code blocks have language specification
• Reading time estimated accurately
• URL slug is descriptive and keyword-rich

Image Recommendations

Suggest 3-5 images with descriptions and alt text:

1. Featured Image: [Description] - Alt: “[Descriptive alt text with keyword]”
2. Diagram/Screenshot: [What it shows] - Alt: “[Descriptive alt text]”
3. Code Example Visual: [Context] - Alt: “[Descriptive alt text]”

Related Content Suggestions

Suggest 3-5 related topics for internal linking:

1. [Related Topic 1] - Why it’s relevant
2. [Related Topic 2] - Connection to current post
3. [Related Topic 3] - Natural progression for readers

Revision Checklist

Before finalizing:

• Content flows naturally with good transitions
• Technical accuracy verified
• Code examples tested and working
• Links are valid and relevant
• Tone is consistent throughout
• Grammar and spelling checked
• Formatting is consistent
• Frontmatter is complete and valid
• SEO elements optimized
• Call to action is clear and compelling

Notes for AI Assistants

When using this template:

1. Replace all with actual values
2. Ensure generated content follows the schema in schemas/blog.schema.yml
3. Validate frontmatter meets all required fields
4. Optimize for both readability and SEO
5. Include practical, actionable advice
6. Use real-world examples where possible
7. Maintain consistent tone throughout
8. Add appropriate code examples with syntax highlighting
9. Suggest relevant images with alt text
10. Provide internal/external link suggestions

License

This template is part of the Personal GitHub Ecosystem project. Licensed under MIT License.