The SEO Blog Engine: A Teardown of the n8n Workflow That Writes My Drafts
Описание и применение
Автоматизированный рабочий процесс n8n генерирует SEO‑статьи, устраняя проблемы с ключевыми словами, вымышленными заголовками и форматированием, используя оценку читабельности, обязательные ссылки и схему валидации JSON перед Markdown.
Задача
Automated LLM workflow produced drafts with keyword stuffing, invented outlines, and formatting drift, causing unreadable content and CMS import failures.
Результат
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.
Рабочий процесс
- 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
Доказательства
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.
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.
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.
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.
- Дата записи: 2026-10-16T22:41:15.166Z