Why Your Copy Isn’t Converting: Marketers Miss the Standards

There is a quiet fight going on inside almost every website project. On one side, the designer. On the other side, the marketer and the copywriter. Most of the time nobody wins, and the user is the one who loses. The reason is simple. Almost nobody on the team knows the website copywriting standards that decide whether the copy is readable or not.

Here is what I keep seeing. Most copywriters want to make garbage by adding tons of text. They think more words means more value. They explain the product, then explain it again, then add a few more lines just to be safe. But they never stop and ask one simple question. Is that really helpful for the user?

Because here is the truth. Users don’t want to read a lot. Not anymore. Today a user wants tons of information from short copy. They are not interested in the deep technical part, they don’t want to read every word you wrote. That is the game right there. A few sharp words create interest, that interest creates intent, and that intent is what makes them actually read. But if your copy feels boring, heavy, or annoying, most users just skip it. Gone.

So scannability is your best friend. And the good UX is simple: less text, understand more.

Most of your words never get read

And this is not just my opinion. Nielsen Norman Group studied more than 45,000 page visits and found that on an average page a user reads at most 28 percent of the words, and more realistically about 20 percent. They don’t even read in order. Their eyes move in an F shape, scanning across the top, running down the left side, grabbing bits in between. So when a copywriter fills a page with tons of text, most of it is never read. You are not writing for a reader. You are writing for a scanner.

Let me show you a real one. Not long ago I was looking at a SaaS page. Big bold headline, then a wide intro paragraph sitting next to a testimonial box, then four neat numbered cards under it. The four cards read perfectly. But that Heading and intro paragraph stretched almost edge to edge, one line was around 150 characters wide. My eyes got tired on the second line. I tried to explain this to the marketer and the copywriter, why that copy hurts the reader. They ignored it. Not because they are careless, but because they have little idea about this topic. Many people write web copy without knowing this exists. And it hits the conversion directly.

If a user has to read a lot just to understand what you are trying to say, then your UX is the worst part of your website. So let me hand you the standards nobody taught them. This is the stuff every designer, marketer, and copywriter should know before writing a single word to sell a product.

The one rule that fixes half of this: the 65ch rule

Most marketers and copywriters have never heard of it. Even some designers ignore it. So let me explain it in plain words.

CSS has a unit called ch. One ch is equal to the width of the character “0”, the zero, in whatever font you are using (MDN). So when a designer writes max-width: 65ch on a text block, the browser keeps that block at roughly 60 to 65 characters per line. On every screen. At every zoom level. It just works on its own.

Why 65? Because reading research has said the same thing for years. The comfortable line length is 50 to 75 characters, spaces included. Baymard Institute says 50 to 75. Pimp My Type says 60 to 80. The number sitting right in the middle, around 65, is the safe zone.

And this is not a new trend. The typographer Robert Bringhurst wrote it decades ago.

“Anything from 45 to 75 characters is widely regarded as a satisfactory length of line for a single-column page. The 66-character line (counting both letters and spaces) is widely regarded as ideal.”

• Robert Bringhurst, The Elements of Typographic Style

So 65ch is not random. It is one of the oldest rules in typography, just written in modern CSS. The innovation is the oldest, but the usage is future friendly.

Why a wide line quietly kills your copy

When your text block is too wide, the reader’s eyes have to travel a long way from the end of one line back to the start of the next. On that trip they lose the line. They re-read the same line, or they skip one. That is eye strain. And it is exactly what the copywriter never sees, because he is reading his own words in a Google Doc, not on the live page.

In pixels, at a normal 16px font, 50 to 75 characters is about 580 to 720px wide (Khoa Le on line length). So a block of body text should almost never go past 720px. Past that, the line crosses 80 characters and the eye starts skipping.

So the fix is one line of CSS, and here is the part people get wrong. You put the limit on the text element, not the page container.

.intro-text {
  max-width: 65ch;   /* caps the block at about 65 characters wide */
  margin: 0 auto;    /* centers it inside the layout */
}

So your container can stay 1200px. The text now sits in a calm 600px column in the middle, with air on both sides. Suddenly the page feels premium and easy.

So, one more rule to pass to your writer. Always left align body text. That ragged right edge gives the eye an anchor to find the next line. Never justify web copy, it creates ugly rivers of white space. Center only for short headlines of one to three lines, never a full paragraph.

The Holy Trinity of web typography

Text width is never a solo decision. It works together with two more things. Designers call these three the Holy Trinity of web typography: font size, line length, and line height (Pimp My Type, Teo Yu Siang).

“Web Design is 95% Typography.”

• Oliver Reichenstein, iA

The rule is simple. A wider line needs a bigger font. A bigger font needs more line height. For a wide 700px block, go 18 to 20px font with about 1.6 line height. For a tight 350px card, 16px with about 1.4 is fine. Longer lines need more line height, shorter lines need less.

And this is not only about taste. It is also the law. WCAG 1.4.12, the accessibility standard from the W3C, says your layout must not break when a user forces these spacings:

• Line height: at least 1.5 times the font size
• Paragraph spacing: at least 2 times the font size
• Letter spacing: at least 0.12 times the font size
• Word spacing: at least 0.16 times the font size

If your text overlaps or clips when a user adjusts spacing for their own comfort, your site fails an accessibility audit. For a business, that is a real risk, not a design opinion.

Your words live inside elastic boxes

Here is the part copywriters really need to hear. Your words do not float in empty space. They live inside boxes, and every box has a limit.

In fact, most websites are built on a 12-column grid. Each section is a box on that grid, and each box has a word budget. Write past the budget and you break the design.

These are the rough word limits designers actually work with:

• Hero headline: 5 to 9 words. Subhead: 15 to 30 words.
• The 3 second rule: keep the top of the page under 30 words total, so a scanning user gets what you do right away.
• Button: 1 to 4 words. Any longer and it wraps on mobile.
• Feature card heading: 2 to 4 words. Card body: about 25 words max.
• Small cards, like integrations or micro-features: 10 to 15 words, that is it.

Word counts mapped to the grid

Here is the same thing as a map, so a marketer and a designer can finally agree before anyone writes a word. This is how word counts sit inside the 12-column grid:

Layout	Column span	Best copy for it	Word limit
Hero / full banner	12 columns	Main value proposition (H1 + subhead)	Headline 5 to 9 words, subhead 15 to 30 words
Split 50/50	6 columns	A feature or an image paired with a benefit	50 to 70 words per column
Three-card feature grid	4 columns per card	Benefit callouts, core services, pricing highlights	Heading 2 to 4 words, body 25 words max
Four-card grid	3 columns per card	Integrations, feature lists, micro points	Micro-copy only, 10 to 15 words per card

Remember that SaaS page from the start? The reason the four numbered cards read so well, while the wide intro paragraph felt like a wall, is simple. Each card was around 250 to 280px wide, so the line length landed near 35 to 45 characters, right in the zone. The paragraph was set free across the full width. Same page, same writer, two completely different reading experiences. The box made the difference.

Not every text block is a paragraph

But here is where people misread the 65ch rule. They think 50 to 75 characters is the answer for everything. It is not. That range is for body text, the long stuff people actually read line by line. Other text types have their own limits, because they do a different job.

Keep these in your head:

• Body text: 50 to 75 characters, about 65ch. The reading zone.
• Large headings and hero text: 30 to 40 characters, about 35ch. Big font, so a long line just waters down the message. Short and punchy hits harder.
• Buttons and microcopy: 20 to 35 characters. A button is a decision, not a sentence. Say the action, nothing more.
• Tooltips and annotations: 25 to 35 characters. Keep it hugging the thing it explains, no extra tail.
• Sub-headings and pull-quotes: 40 to 60 characters. Long enough to carry an idea, short enough to break up the page.

So, same page, five different jobs, five different limits. A copywriter who knows this stops writing “one size” copy and starts writing for the exact spot the words will live in.

The same rule fits every layout

The nice part is that once you get this, it works everywhere. You do not learn a new rule for every page type. You just apply the same reading zone to the shape in front of you.

• Blog and FAQ pages: this is pure reading, so give the content a frame wide enough for comfort and no wider. When lines stop stretching edge to edge, people actually finish the article instead of bouncing halfway.
• Product cards and grids: match the width of every card. If one card runs 40 characters a line and the next runs 70, the eye keeps re-adjusting and scanning gets tiring. Same width, same rhythm.
• Dashboards and app screens: these mix reading and action, so zone the layout. One column for text to read, another for the buttons and controls, and let the leftover space breathe with charts or just rest. Do not cram.
• Responsive: on a big screen, the 65ch cap is your safety rope, it stops text from spreading into an unreadable strip. On mobile the narrow screen already limits the width for you, so there your job is just to keep paragraphs short.

One rule, every screen. That is why it is worth learning once.

The internationalization trap

This one almost nobody thinks about, and it breaks real products.

For example, you write “Submit” for a button. Six letters, fits perfectly. Then the site goes to German and “Submit” becomes “Absenden”. Your button breaks. This is called text expansion, and it has real numbers behind it. The W3C, using IBM’s localization guide, shows that short English strings expand the most. A string under 10 characters can need 100 to 200 percent extra space when translated, while long passages need around 30 percent. The shorter the text, the more it can grow. So a fixed-width button built for exactly six English letters is a bug waiting to happen.

But there is a second trap. Not all letters are equal. The letter “W” takes far more space than the letter “I”. So a strict 15-character limit can still overflow if the words are wide. Good UX writers test with the widest word combinations, not just the count.

Even if you never translate your site, the lesson holds. Never trust a character count alone. Write and design for a box that can flex.

Frameworks are the skeleton, not the meat

Okay, so short copy, tight boxes, safe width. But short does not mean empty. Your few words still have to sell. That is where copywriting frameworks come in. They are the skeleton that holds your short copy up. A framework is a sequencing template, not a script. It tells you the order the information should arrive in, not the exact words to use. And remember what we said at the top, most of your sentences never get read. So the framework has to do its job fast, before the reader loses interest.

You don’t need all thirteen of them. Just know these families (Articos, Digitaloft):

• Attention first: AIDA (Attention, Interest, Desire, Action) and ACCA (Awareness, Comprehension, Conviction, Action).
• Problem led: PAS (Problem, Agitate, Solution) and PASTOR (Problem, Amplify, Story, Testimony, Offer, Response).
• Story based: BAB (Before, After, Bridge) and Star, Story, Solution.
• Feature to benefit: FAB (Features, Advantages, Benefits) and the 4 Cs (Clear, Concise, Compelling, Credible).
• Objection handling: PPPP (Picture, Promise, Prove, Push).

So pick one per section. Fill it with the fewest words that do the job. Drop it into the right box. The framework gives you the order, the 65ch rule gives you the shape. Together they make copy a user can scan and still get everything.

Why this is a business problem, not a design nitpick

Now for the founders, CEOs, and product managers reading this. Why should you care about a character count?

Because all of this is conversion. Every rule here is about one thing. Can the user read and act without friction?

“We don’t read pages. We scan them.”

• Steve Krug, Don’t Make Me Think

So think about what happens on your page. Your copy is good. You explained the product well. You explained the value well. Now what is the benefit if your user gets eye strain reading it? What is the benefit if they lose focus jumping from one long line to the next, and quietly leave? The words were right, but the box was wrong, and the sale was gone. These issues look very minor, but they take a massive effect on your website.

Split it by the kind of business you run:

1. Physical product or service business. Your website is your storefront. If the about page and product pages are walls of wide text, visitors skim, get tired, and bounce. Cut the copy. Put it in 65ch columns. Lead every section with a 5 to 9 word headline that says the benefit first. Let the buyer get the point in three seconds.

2. Digital product or SaaS. Here it is even sharper, because you have onboarding, pricing, and feature pages full of text. Use tight cards, short scannable lines, and one clear CTA per section. On my own website revamps at WPManageNinja, cleaning up hierarchy and readability like this drove an average conversion lift of around 35 percent. And I could watch it happen in Microsoft Clarity: fewer rage clicks, more people actually reading and scrolling, instead of bouncing at the first wall of text.

That is the whole point. The good UX is less text, understand more.

Your website copywriting standards checklist

Keep this next to you before you write or design a single section:

• Body text: 50 to 75 characters a line. Cap it with max-width: 65ch.
• Body width in pixels: 580 to 720px at a 16px font. Never past 720px.
• Headings and hero text: 30 to 40 characters, about 35ch.
• Buttons and microcopy: 20 to 35 characters, 1 to 4 words.
• Tooltips and annotations: 25 to 35 characters.
• Sub-headings and pull-quotes: 40 to 60 characters.
• Hero headline: 5 to 9 words. Subhead 15 to 30 words. Keep the top of the page under 30 words total.
• Line height: 1.5 to 1.6 for body. A bigger font and a wider line need more.
• WCAG 1.4.12: the layout must survive line height 1.5x, paragraph spacing 2x, letter spacing 0.12x, and word spacing 0.16x the font size.
• Alignment: left align body text, never justify, center only for 1 to 3 line headlines.
• Localization: leave room to grow. Short strings can need 100 to 200 percent more space.
• Framework: pick one per section (AIDA, PAS, BAB, FAB, or PPPP). Order first, fewest words second.
• The reason for all of it: users read about 20 percent of your words, so make every one easy to catch.

---

Good copy is not the copy with the most words. It is the copy a user can read without even thinking about it. So before you write a single word to sell your product, make sure your designer, your marketer, and your copywriter all know these standards. You worked hard for that traffic. Don’t lose a single conversion to a line that was just too wide.

---

References (strongest sources):

• Readability: the Optimal Line Length – Baymard Institute
• Line Length and Line Height – Pimp My Type
• Understanding WCAG 1.4.12 Text Spacing – W3C
• Text size in translation – W3C
• CSS length and the ch unit – MDN
• How Little Do Users Read? – Nielsen Norman Group
• F-Shaped Pattern For Reading Web Content – Nielsen Norman Group

FAQ