The SEO Blog Engine: A Teardown of the n8n Workflow That Writes My Drafts

Description and use

An n8n workflow generates SEO blog drafts, fixing keyword stuffing, invented outlines, and formatting drift by adding readability scoring, source‑cited outlines, and a JSON schema guard before Markdown rendering.

Problem

Automated LLM workflow produced drafts with keyword stuffing, invented outlines, and formatting drift, causing unreadable content and CMS import failures.

Outcome

The workflow now produces SEO‑ready drafts that are readable, source‑referenced, and CMS‑compatible, reducing manual editing time to about 6 minutes per article.

Workflow

• Keyword input → research pass pulls top‑ranking pages’ subheadings
• Outline node generates H2s citing each subheading
• Draft node writes sections against a style contract
• Schema guard validates structured JSON before Markdown rendering
• Publish‑ready Markdown output

Evidence

The first drafts read like 2012. The model had absorbed a decade of "SEO writing" and produced sentences like "this n8n automation workflow template helps you automate workflows with automation." Technically keyword-rich. Unreadable.

Source

The fix was a readability penalty in the scoring rubric: every draft gets scored on a 0–10 scale where keyword stuffing and repeated phrases subtract points, and the draft only ships at 7+. The prompt didn’t change much — the judge changed.

Source

The outline must cite its sources line by line. Every H2 carries a reference to a real subheading from the research pass, and the draft node is forbidden from introducing new H2s.

Source

The fix was a schema guard before the Markdown render: the draft is produced as structured JSON (sections, headings, code blocks, tables as typed fields), validated against a schema, and only then rendered to Markdown.

Source