Content & Messaging
Plain Language & Readability
Plain, direct language is understood faster and trusted more — jargon and complexity are barriers.
Where it comes from
The plain-language movement has deep roots in government and legal reform — the US Plain Writing Act, the UK's Plain English Campaign — all built on a simple finding: clear, direct writing is understood faster and trusted more than dense, technical prose.
Why it matters for your website
Plain language converts. Content written at a clear, accessible reading level is understood faster, trusted more, and acted on more readily than technically accurate but dense language. The goal is to be understood on the first read — not to demonstrate expertise.
Complexity is a barrier even when it's accurate. A sentence the reader has to decode is a sentence that costs attention and breeds doubt — and on the web, doubt is a click away from departure. Plain language isn't dumbing down; it's removing the work between the reader and the meaning.
It's worth saying that plain doesn't mean simplistic. The aim is to be understood on the first read by your actual audience — which for a specialist audience may include specialist terms, but never gratuitous jargon, padding, or sentences engineered to sound impressive. Clarity, not register, is the target.
Wrong vs right
Dense, jargon-laden copy ('leverage our synergistic platform to operationalise outcomes') that the reader has to decode.
Plain, direct language ('our tool helps your team get more done') understood on the first read.
Long, clause-heavy sentences that bury the point.
Short, direct sentences that put the meaning up front.
Writing to demonstrate expertise, at the cost of being understood.
Writing to be understood, which builds more trust than sounding clever.
Understanding Plain Language & Readability
Plain language is writing that's clear, direct, and easy to understand on the first read. The principle, formalised by movements like the US plain-language initiative, rests on consistent evidence: people understand plain writing faster, trust it more, and act on it more readily than dense or technical prose — even when the dense version is perfectly accurate.
The reason is that complexity is friction. Every convoluted sentence, unnecessary jargon term, or padded phrase is work the reader has to do to extract the meaning, and that work costs attention and breeds doubt. On a web page, where leaving is effortless, asking the reader to decode your message is asking them to choose whether it's worth the effort.
Crucially, plain language isn't about dumbing down or writing to a low reading level for its own sake. The goal is to be understood on the first read by your actual audience — which means cutting jargon, padding, and sentences built to impress, not removing necessary substance. Clarity beats the appearance of expertise. It connects to scannability, the match between system and real world, and value-proposition clarity.
How Kweri checks it
Plain language is partly assessable and partly a judgement. Kweri can flag some measurable signals — long sentences, dense paragraphs, jargon, and a reading level that may exceed the audience's — and prompt you toward clearer phrasing. What it can't fully judge is whether a given term is appropriate jargon for your specific audience or gratuitous complexity, since that depends on who you're writing for. So Kweri surfaces likely readability problems it can measure, and prompts the 'would my actual reader understand this on first read?' question, while the final call on register is yours.
FAQ
What is plain language?
Plain language is clear, direct writing that readers can understand on the first read. It avoids unnecessary jargon, padding, and complexity, prioritising being understood over sounding impressive or technically exhaustive.
Why does plain language matter for conversion?
Because clear writing is understood faster, trusted more, and acted on more readily than dense prose. Complexity is friction — every sentence a reader has to decode costs attention and breeds doubt, and on the web doubt leads to departure.
Does plain language mean dumbing down?
No. The goal is to be understood on the first read by your actual audience, which may include necessary specialist terms. It means cutting gratuitous jargon, padding, and impress-the-reader complexity — not removing real substance.
How do I write in plain language?
Use short, direct sentences; put the main point first; cut jargon and padding; prefer common words; and write to be understood rather than to demonstrate expertise. Test whether your actual reader would grasp it on a single read.
Is plain language an accessibility issue?
Yes, partly. Clear, simple language helps everyone, but it especially helps people with cognitive disabilities, non-native speakers, and anyone reading under pressure. Plain language is part of making content broadly accessible.
Related principles
People scan web pages rather than read them — structure content so scanners still get the point.
The brain has a limited processing budget — demand too much and performance collapses.
Content structured as a story is processed as if lived, engaging far more of the brain than lists or facts — and is retained longer.
Every label, button, error, tooltip, placeholder, confirmation, and notification is a piece of copy that either builds trust and guides action or creates confusion and erodes it — the language inside a product is part of the design, not an afterthought.
Attribution & sources
Identified by Plain-language movement (plainlanguage.gov). Catalogued from plainlanguage.gov.
Grounded in the plain-language movement in government and legal reform; the linked site is the reference used here.
See Plain Language & Readability on your own site
Run a free Kweri audit — a plain-English review of your site’s speed, accessibility, SEO and design, ranked by what to fix first. No login, no jargon.
Run a free audit →