Why writing for the web matters more than it looks

This is cheap to get right at the start and expensive to retrofit. Writing for the web is easy to treat as a detail, and that is exactly why it is worth a few minutes of attention.

Writing for the web is largely an editing job: the first draft is always longer than it needs to be. It is worth deciding this deliberately rather than inheriting whatever the last person set up.

What is actually at stake

People scan before they read. The reasoning matters more than the rule, because the rule has exceptions. The version that survives contact with a real deadline is the simple one.

Short paragraphs and clear subheadings do the heavy lifting. That sounds obvious written down. It is still the thing most often skipped. It rarely shows up as a line item, which is exactly why it slips.

What to watch for

Cut the throat-clearing and start with the point. The teams that handle this well are rarely the ones with the biggest budgets. Write the reasoning down alongside the decision, because the reasoning is what changes first.

How to tell if yours is fine

Pages that answer a real question outlive pages written to fill a slot in a sitemap. Three things worth confirming about writing for the web before you move on:

• Someone can say what the current setup is without going to look
• People scan before they read — and you know whether that is true here
• There is a way to tell whether the last change to this helped

Worth checking on your own setup before it becomes someone else's problem to fix.