Writer

The writer agent takes the next ticket from To do, reads its brief, and writes a full article. It writes answer-first, at a low reading grade, with a TL;DR, screenshots, an FAQ and a call to action. The writer never publishes. Every draft goes to the QA gate first.

When the writer runs

If the ticket has no brief yet, the brief agent writes one first.

What every article contains

The writer follows a fixed structure:

1. TL;DR at the very top. For a listicle, every item with a link and a one-line value. For a how-to, a 2 to 3 sentence summary. For a comparison, who should pick what.
2. Answer-first block: 2 to 4 sentences that directly answer the main query.
3. Short intro of 2 to 3 short paragraphs. No scene-setting.
4. Main sections with H2 and H3 headings from the brief. Each H2 opens with a direct answer of 60 words or fewer.
5. Conclusion with a clear call to action that links to a conversion page.
6. FAQ with 3 to 6 questions and answers.

It also produces a title, slug, meta title (60 characters or fewer), meta description (120 to 160 characters), excerpt, FAQ data, schema type and writer notes for QA.

Writing rules

• Simple words and short sentences, aimed at a 7th-grade reading level.
• Paragraphs of 1 to 3 sentences.
• No em dashes. No AI filler phrases. Your Banned words and phrases apply too.
• Product facts, prices, limits and trial length copied exactly from Approved product facts. Never invented.
• Privacy, security and data claims link to a page from Documentation pages in the same paragraph.
• Links only to real URLs from your site and to named tools on first mention.

Warning: The writer cannot know facts you did not give it. If your approved facts are thin, articles stay vague, and QA fails drafts that add numbers you did not approve. Fill in Settings > Business profile carefully.

Images

The writer adds images in two ways:

Up to 6 new screenshots are taken per draft. A screenshot of the same URL from the last 30 days is reused. If a screenshot fails, the image is removed and the reason goes into the writer notes.

Tip: Upload product screenshots to the Image library. Describe each one well: "What the image shows" becomes the alt text. QA fails product articles that use no approved product screenshot when your library has images.

See Screenshots for the screenshot services.

Schema

The app builds JSON-LD from the draft: an Article (or HowTo) entry and, when the article has an FAQ, a FAQPage entry. Ghost receives it in the page head. Webhook receivers get it as schemaJsonLd.

Rewrites

When QA fails a draft, the writer gets the draft and the QA report, and writes a new version that fixes the required items. Each version is kept. On the ticket page, the Draft card shows each version as v1, v2 and so on, with a check mark or a cross for its QA result.

Choose the writer model

The writer is the job where model quality matters most. The AI model for the writer is set by AgenticSEO, so article quality is the same on every plan. See AI is included.

Teach the writer

Add lessons for Writer on the Lessons page or from the Teach the agents card on a ticket. Example: "Our customers are HR managers, not accountants. Avoid tax jargon." Every later draft follows it.

Get the article out by hand

On the Draft card you can:

• Click Copy Markdown.
• Download HTML or .md.
• Download each image.

Note: If you copy an article by hand, download the images and upload them to your website too. Image links point at the app until your CMS hosts them.