Blog writing style: flat and confident
The blog writing style that ranks and gets quoted is flat, confident and specific: every line is a plain statement of fact with one committed figure. Readers trust those sentences, and search engines and AI assistants can lift them whole.
The flat confident voice
Write every line as a flat "[X] is [Y]" statement. Strip every hedge, and leave out every if, but and maybe, with no exceptions. Confident sentences are the fastest way to earn search rankings and AI citations, so everything is written with full confidence.
- Every line is a flat "[X] is [Y]" statement. Rewrite conditionals as facts: "The anode is replaced at 3 mm", not "If the anode is worn, it may need replacing."
- Turn a frequency into a firm practice or a plain fact. "Pipes freeze in February" beats "Pipes often freeze in winter."
- Accuracy still wins. When a condition really changes the fact, state the condition as its own flat fact: "Boilers over 15 years old are replaced, not repaired." Never turn a preference into a universal "must", or an uncertain outcome into a guarantee.
- One committed figure, never a range or "about". Pick the one figure a specialist stands behind: "A 150-litre boiler serves a family of four."
- Make claims, many of them. A post makes claims all the way through. Every flat claim is something a search engine or an assistant can quote.
- No em dashes in copy: use a full stop, a colon or a comma.
- Active voice by default. Use the passive only where the actor doesn't matter, and never let passive sentences pile up.
- Use transition words ("so", "because", "that means", "first", "next", "as a result", "for example") so each sentence leads into the next.
- Keep it human: vary sentence structure and length, and avoid robotic or repetitive phrasing.
- Every section is actionable. The reader can do something with it today.
- Concise, easy language. Plain words, without dumbing down genuinely technical material.
Hedges to strip
Strip these from English copy: in most cases, typically, usually, generally, often, sometimes, may, might, can, could, depending on, about, approximately, around, roughly, up to (as a hedge), rather, quite, fairly, likely, probably, a bit, if needed, on request.
Build the same list for every language you publish in. Estonian, for example: kui … siis, olenevalt, sõltuvalt, aga, kuid, siiski, tavaliselt, üldjuhul, enamasti, reeglina, harilikult, üldiselt, võib, võib-olla, võivad, umbes, ligikaudu, ligi, pigem, üsna, "kuni" as a hedge, sageli, tihti, mõnikord, kohati, enamik, paljud, suurem osa, kõige sagedamini, peaaegu, vajadusel, soovi korral, tõenäoliselt, veidi.

The Stripe method
Write the way Stripe writes its Atlas guides and blog: plain, specific and useful in every sentence. The rules:
- Open with the answer to the reader's problem in one concrete sentence, in the reader's own terms. Never open with the company, the industry or "today's fast-paced world".
- Earn every claim with a number, a named example or a mechanism. With no real number, use the mechanism.
- Show how it works, not how good it is. "Seamless" tells the reader nothing; "the engineer arrives within 2 hours and quotes before starting" does.
- State prices and promises once, exactly, the same way everywhere.
- Cut the throat-clearing. Delete on sight: "In today's…", "Look no further", "We believe that…", "It's no secret that…", "When it comes to…", "Let's dive in", "In conclusion".
- Be honest about limits: time, effort, fit, and when the alternative is better. Honesty is what makes the promise believable. Never write a limit that contradicts your own guarantee.
- Talk like a capable peer: "you" and "we", plain words, at most one dry line per section. Humour is dry and specific, never jokey.
- Name the specific reader, place and job ("a dental clinic in Bristol", "a two-person design studio"), never "businesses of all sizes".
- Make abstractions concrete with a picture from the reader's own world ("a page Google hasn't indexed is a flyer still in the box"). One analogy per section at most, never from sport or war.
- Answer the doubt in the same sentence with "even if", using only objections real buyers raise, and never stretching a promise beyond its terms.
- Borrow the customer's words, especially for headings.
- Explain how, not what, and answer the next question: price drivers, disruption, waste, handover, urgency. Every section adds new information. Use worked examples with figures.
- Make big numbers tangible, and be uncomfortably specific.
Words that never ship
- Hype: seamless, cutting-edge, innovative, leading, world-class, powerful, robust, unlock, elevate, supercharge, game-changing, tailored solutions, passionate, dedicated, best-in-class, and exclamation marks outside quotes.
- Stock phrases: delve, tapestry, testament, pivotal, showcasing, boasts, nestled, vibrant, "in the heart of", "serves as", "not just X, it's Y", tricolon slogans ("Fast. Simple. Secure."), "Built for the modern…", chat residue and weasel attributions ("experts say").
- Empty filler: professional service, quality work, experienced team, best, cheap, affordable, #1. Keep the list per language; in Estonian: professionaalne teenus, kvaliteetne töö, kogenud meeskond, parim, odav, soodne.
- "Fast" in titles and metas: state the minutes instead.
- Vague green claims ("eco-friendly", "green"). Describe concrete practices instead: scrap metal sold for recycling, pump wattage, the thermostat setting. EU Directive 2024/825 bans the vague ones.
- Business jargon the customer never uses: retention, churn, win-back, conversion, funnel. Say what happens to the customer instead.
Case, names and register
- Headings in sentence case: it is the norm in most languages and easier to read. A site already in Title Case switches all at once, and until then a new page follows the site's current case.
- Never inflect the brand name in languages with case endings.
- Pick one form of address per language (formal or informal "you") and use it everywhere.
- Keep your own signature words and use them consistently, so a reader recognises your voice.
Keep your reasons out of the copy
When you add something to a page for a reason, the reason never appears in anything the customer sees. Writing it into the copy is one of the most common mistakes in AI-assisted writing.
- The reasons behind an addition are context, never copy. Carry out the purpose; never state it. "Real reviews from real clients to show you can trust us" doesn't belong on the page. The reviews under a plain heading, or no heading, is the fix.
- The test: would we say this sentence to the customer's face, unprompted?
- Explaining "why" from the reader's side is good: "the anode is checked yearly because hard water wears it through in four years" helps the reader. "We added this section so you would pick us" doesn't.
- Keep the interface lean and the content rich. Posts are read alone, so they carry their full text. Outside the post body, let the layout do the explaining: no secondary labels, slogan-like lines, decoration, nested boxes or repeated information. Every element serves a clear purpose for the reader.
- Run a fluff audit and remove what doesn't inform or move the reader.
Hand-written text and real voices
- Text a founder or team member wrote by hand gets grammar and spelling fixes only. Keep its natural, human line of thought, and use each idea exactly as written.
- Customer reviews and quotes are never corrected, not even their grammar.
- Natural variation comes from writing about real work: vary sentence length and structure as you would when speaking.
- Do a final pass as a native editor: grammar, case endings, natural word order and voice.
Edited by Andres LepikCo-founder & Head of Growth
Fact-checked by Siim SaarHead of SEO
Post by Rasmus Kivi
Co-founder & CEO
Co-founded REND and still reads every client's monthly report himself before it goes out.