Professional Technical Blog Post Generator (Reusable Template)

You are a skilled technical writer. Create a polished, well-structured blog post following the instructions and placeholders below. If any placeholder is missing, infer sensible defaults and proceed.

Inputs

[TOPIC]: e.g., “[ENERGY-EFFICIENT ALGORITHMS]”

[INDUSTRY/DOMAIN]: e.g., “[WEB DEVELOPMENT]”, “[HEALTHCARE AI]”

[TARGET AUDIENCE]: e.g., “[BEGINNER FRONTEND DEVS]”, “[CTOs]”

[GOAL]: e.g., “[EDUCATE]”, “[PERSUADE]”, “[LEAD GEN]”

[DESIRED LENGTH]: e.g., “[1200–1500 WORDS]”

[TONE & VOICE]: e.g., “[CLEAR, PRACTICAL, AUTHORITATIVE]”

[READING LEVEL]: e.g., “[GRADE 9]” or “[ADVANCED]”

[PRIMARY KEYWORDS]: e.g., “[KEYWORD A, KEYWORD B]”

[SECONDARY KEYWORDS]: e.g., “[KEYWORD C, KEYWORD D]”

[DEPTH]: “[BEGINNER | INTERMEDIATE | ADVANCED]”

[INCLUDE ELEMENTS]: e.g., “[CHECKLIST, CODE SNIPPET IN [LANGUAGE], COMPARISON TABLE, METRICS, CASE STUDY]”

[EXAMPLES/CONTEXT]: e.g., “[2 REAL-WORLD EXAMPLES]”

[CTA]: e.g., “[DOWNLOAD GUIDE]”, “[TRY THE TOOL]”

[INTERNAL LINKS]: e.g., “[/docs/performance, /blog/caching]”

[EXTERNAL SOURCES]: e.g., “[3 HIGH-QUALITY SOURCES]”

[CONSTRAINTS/EXCLUSIONS]: e.g., “[NO JARGON, NO SALESY LANGUAGE]”

Output Requirements

Metadata (before the article)

Meta Title (≤ 60 chars)

Meta Description (140–160 chars)

URL Slug

Target Keywords (primary + secondary)

Social Share Text (Twitter/LinkedIn)

Suggested OG Image Concept + Alt Text

Article (Markdown)

# H1: Compelling headline using [TOPIC] and primary keyword.

Hook (2–3 sentences): State the problem/opportunity for [TARGET AUDIENCE].

Key Takeaways (3–5 bullets): crisp, outcome-focused.

Table of Contents (auto-generated list of H2s).

## Background / Why it matters: Brief context aligned to [INDUSTRY/DOMAIN] and [GOAL].

## Core Principles / Concepts: 3–6 subheads with clear explanations; align depth to [DEPTH].

## Practical Techniques / Steps: numbered steps; include mini-checklist.

## Examples or ## Mini Case Study: at least [EXAMPLES/CONTEXT]; quantify impact where possible.

## Tools & Resources: include [INTERNAL LINKS] and curated [EXTERNAL SOURCES].

## Pitfalls & How to Avoid Them: 3–5 common mistakes + fixes.

## Metrics & Measurement: define success KPIs and simple tracking approach.

## Conclusion & Next Steps: summarize and include [CTA] with a natural, non-pushy close.

Optional Elements (include if listed in [INCLUDE ELEMENTS])

Code Block (with language tag) demonstrating a core idea.

Comparison Table contrasting approaches/solutions.

Checklist for quick implementation.

Diagram/Image Prompt describing what to illustrate (no image generation needed).

Linking & Citations

Weave in [INTERNAL LINKS] contextually.

Cite [EXTERNAL SOURCES] inline with (Author/Org, Year) and include a short References section at the end with titles and links.

Avoid low-credibility sources.

Style & Formatting

Use short paragraphs, scannable subheads, and descriptive H2/H3s.

Prefer active voice and concrete verbs.

Define jargon on first use; add a one-sentence TL;DR where helpful.

Include at least one numbered list and one bulleted list.

Maintain consistency with [TONE & VOICE] and [READING LEVEL].

Quality Checklist (append at end, do not include in word count)

 Headline is clear, specific, and benefit-led.

 Intro frames a real problem for [TARGET AUDIENCE].

 Each section answers a “why/what/how” question.

 Examples are concrete and (where possible) quantified.

 All claims are supported or caveated.

 Internal/external links added; no dead ends.

 Keywords used naturally; no stuffing.

 CTA aligns with [GOAL].

Return the final response in this order:

Metadata

Article (Markdown)

References (if used)

Quality Checklist