Pillar guide

The six blog formats, and how to write each one

Almost every blog post that ranks or gets cited is a variation on one of six underlying shapes. Pick the wrong shape for the topic and no amount of polish fixes it — pick the right one and the structure does most of the work for you.

⚡ Quick answer

Most blog content falls into six formats — how-to, comparison, product review, roundup, informational and refresh — and each has a structure that decides whether it ranks and gets cited.

How-to guide

A how-to guide answers "how do I do X," and its structure should mirror that: a clear sequence of steps, in order, each one doable on its own. It ranks and gets cited when the steps are specific enough to actually follow — exact settings, exact wording, exact numbers — rather than vague advice restated six different ways. Use this format whenever the reader's goal is an action, not an understanding of the topic in the abstract.

ButterBlogs writes this format from its own research pass, so the steps reflect what's currently true rather than a template filled in from memory, and it adds the internal links and schema that let search engines and AI answer engines lift individual steps directly into their own answers.

Comparison post

A comparison post exists because the reader is deciding between two or more specific things, not looking for a single recommendation. The structure that works: pick a small, fixed set of criteria that actually matter for the decision, score or describe every option against the same criteria, and put the result in one table a reader can scan in seconds rather than reconstruct from paragraphs.

It ranks when it stays even-handed — naming a real downside for every option, including a favored one — because both search engines and readers treat a comparison that only ever favors one side as marketing copy rather than a genuine comparison.

Product review

A review covers one thing in depth: what it does, who it's for, where it falls short, and whether it's worth the cost. The format that survives E-E-A-T scrutiny is specific rather than generic — naming the exact feature that worked or didn't, not "great features overall" — and it states real limitations instead of only positives, since a review with no downsides reads as unreliable rather than enthusiastic.

Use this format when the reader has already narrowed their decision down to one option and needs confirmation, not a comparison across several.

Roundup / listicle

A roundup covers several options side by side, aimed at a reader who's still exploring a category rather than deciding between two finalists. It ranks when each entry earns its place with a real distinguishing reason — what this one is actually best for — rather than a repeated list of generic features restated under each heading with a different product name swapped in.

The failure mode of this format is sameness: if every entry in the list could be swapped for any other with no loss of meaning, neither readers nor AI answer engines have a reason to treat any single entry as the right pick for a given need.

Informational post

An informational post explains a concept — "what is X," "how does X work" — for a reader who wants to understand the topic, not complete a task or make a purchase decision. The structure that gets cited by AI answer engines leads with a direct, self-contained answer in the first few sentences, then expands with the reasoning and detail underneath, rather than building up to the definition at the end.

This is the format most often written badly by padding it with filler, and most often rewarded when it isn't: a tight, direct answer up top is exactly what an AI engine or a featured snippet is looking to extract.

Refresh an existing article

Refreshing isn't a separate topic — it's a maintenance format applied to one of the five above. The structure is: keep what still holds up, replace what's gone stale (dates, product details, ranking factors), and add whatever a competitor now covers that the original post doesn't. It's the right call when a post already targets the exact intent and either used to rank or is close, rather than when the topic needs an entirely new angle.

ButterBlogs' Revise Existing Post mode is built for exactly this: it works from what's already published rather than starting over, which is usually faster and safer than replacing a page that already has some ranking history.

Which format ButterBlogs writes

All six formats run through the same pipeline: keyword research, an analysis of what's currently ranking for the topic, a draft written in your trained persona, then internal links, schema and meta data added before publishing. See how it works for the full pipeline, or browse real posts written with ButterBlogs across all six formats. This page is the format layer that sits under the broader AI blog writing guide — pricing for any format is the same pay-per-post token model, detailed on the pricing page.

Frequently asked questions

Which blog format should I use?
Start from what the reader is actually trying to do, not what format feels easiest to write. Someone trying to complete a task wants a how-to. Someone deciding between two paths wants a comparison. Someone about to buy one specific thing wants a review. Someone exploring a category wants a roundup. Someone trying to understand a concept wants an informational post. Match the format to the intent first, and the structure follows naturally.
What makes a comparison post rank?
A comparison post ranks when it commits to a small number of clear, consistent criteria and applies them evenly to every option — including the one the writer might prefer. A single accurate table beats several paragraphs of vague impressions, and a post that's honest about tradeoffs (this one's cheaper, that one's more flexible) reads as more trustworthy than one that quietly favors a single answer throughout.
How do I write an EEAT-safe product review?
Be specific about what was actually tested or used, and for how long, rather than writing in generalities that could apply to any product. State real limitations alongside real strengths — a review with zero cons reads as unreliable, to readers and to search engines. If there's a financial relationship with the product, disclose it plainly. Specificity and honesty about tradeoffs are what E-E-A-T is actually checking for, not a particular word count.
When should I refresh instead of writing new?
Refresh when a post already exists on the exact topic and either used to rank and has slipped, or is close to ranking but is thin, outdated, or missing something competitors now cover. Write new when the search intent isn't covered by anything you've published, or when the angle is different enough that editing the old post would confuse its existing readers. ButterBlogs' Revise Existing Post mode is built for the first case, so refreshing doesn't mean starting from a blank page.

Let ButterBlogs write the right format, every time

Tell it the topic — it researches what's ranking, picks the structure that fits, writes in your voice, and publishes with the links and schema already in place.