SEO Blog Post & Technical Tutorial Generator

What it does

/blog-post is a Cursor slash command. Type it in chat to run a saved workflow: SEO Blog Post & Technical Tutorial Generator.

Writes authoritative technical articles: outlines topical clusters, explains step-by-step developer workflows, includes code samples, and adds product CTAs.

In-depth, keyword-targeted technical tutorials that drive organic search traffic. Unlike a skill, a command is something you invoke on purpose. The agent does not decide to run /blog-post for you.

Why it exists

Founders retype the same multi-step prompt until it rots. /blog-post exists so the pipeline, all 4 steps of it, is a file in .cursor/commands, versioned with the repo.

It ships in the Marketing Kit. It is wired to the Content Strategy Lead (content-marketer) and Technical & On-Page SEO Lead (seo-specialist) agents. Required skills: Pillar-and-Cluster Content Architecture; Content Marketing Funnel (TOFU, MOFU, BOFU); On-Page SEO & Semantic HTML Architecture.

When to use it

• Use to scale organic search traffic with high-value technical developer content.
• Use /blog-post when you want that pipeline, not a freeform chat. If you only need one step, use a narrower command or a single agent.
• Start a new chat. Do not run this command in a thread that just touched production SQL.

When not to use it

• Do not run /blog-post as a substitute for reading the diff. The command produces files; you still gate them.
• Do not chain it into a 40-turn chat. Fresh context is part of the design.
• Do not run it if you have not filled CURSOR.md. The pipeline will invent a stack.

Example workflow

1. Research primary and secondary target keywords and search intent
2. Structure outline with H2/H3 subheadings and code snippet placeholders
3. Write comprehensive, educational tutorial with zero fluff
4. Add contextual product callout linking to relevant tools and kits

Example usage

Type this in Cursor chat: /blog-post Write 1500-word tutorial on automated Cursor workflows for Next.js

The command file tells the session which agents to adopt and which skills to read. You should see phase headers, not a single dump of code.

If a phase fails its gate, stop. Do not add 'just continue'.

Example output

• Expected artifact: docs/marketing/blog/...md

Best practices

• Keep the prompt specific. /blog-post Write 1500-word tutorial on automated Cursor workflows for Next.js is the shape: object, constraint, and outcome.
• Let the listed agents work in order: content-marketer → seo-specialist.
• Save outputs in the repo. Chat-only answers evaporate.
• Marketing commands write to docs/marketing/ so the next command can read positioning before it writes a landing page.

Common mistakes

• Typing /blog-post with no object ('do the thing'). The pipeline will guess.
• Re-running the command in the same chat after a failed gate instead of fixing the failing file.
• Editing the command file to skip review so it 'goes faster'.
• Skipping the Pillar-and-Cluster Content Architecture skill that the command depends on.