Writing styles

What is a style profile?

A style profile bundles a name + tone description + audience + length target + optional sample paragraph. Every article generated under that profile inherits these constraints. They live in AI AutoBlogger → Styles.

Anatomy of a profile

• Name — internal label (e.g. “Tech editorial”, “Friendly how-to”)
• Tone — 1–2 sentences (e.g. “Authoritative but approachable. Like a senior engineer explaining to a junior.”)
• Audience — who’s reading (e.g. “WordPress site owners with intermediate technical knowledge”)
• Length target — word count window (e.g. 1,800–2,400)
• Sample paragraph (optional but powerful) — paste 1–2 paragraphs of writing you want GPT to mimic

Common style templates

“Tech editorial”

Tone: Authoritative, slightly opinionated. Treats the reader as smart. Includes concrete numbers and examples. Mild dry humor allowed.
Audience: Developers and technical product people.
Length: 1,800–2,400 words.

“Friendly how-to”

Tone: Warm, encouraging. Acknowledges this stuff is confusing. Lots of “you” and “we”, short sentences, occasional asides.
Audience: WordPress beginners.
Length: 1,200–1,800 words.

“Recipe blog”

Tone: Personal, story-led intro then methodical instructions. Specific times, temps, quantities. Optimistic.
Audience: Home cooks of mixed skill levels.
Length: 1,000–1,500 words.

Assigning styles to categories

In AutoPilot → Source categories, each category has a Style profile dropdown. Pick your profile, save. AutoPilot uses it for all articles generated under that category. Manual generation also lets you pick a style per-article from the same dropdown.

The humanizer pass

Every article goes through a humanizer pass after the main expansion — a second GPT call that rewrites for natural rhythm, variable sentence length, and removes the giveaway “AI tells” (overuse of “delve”, “tapestry”, em-dashes). Toggle in SEO Settings → Generation → Humanizer. Adds ~30% to generation cost, but the readability difference is large.