Skip to content

Writing for the Web: 10 Rules Every Writer Must Know

Why web writing needs its own rules

People read web pages differently from printed pages: they arrive with a task, scan for the part that answers it, and leave when they find it or give up. Writing for the web means making that scan succeed. Put the answer first, make headings and links say what they lead to, keep sentences and paragraphs short, and cut anything the reader didn’t come for.

This isn’t new advice. In a 1997 study, Jakob Nielsen of the Nielsen Norman Group found that 79% of test users always scanned any new page they came across (How Users Read on the Web, checked on 2026-10-14). The study is old, so treat the number as history. The advice it led to, such as meaningful subheadings, bulleted lists, one idea per paragraph and the inverted pyramid, still underpins most web style guides. The ten rules below turn it into practical edits, each with a before-and-after example.

The ten rules at a glance

Rule Quick check
1. Put the answer first Does the first paragraph answer the reader’s question?
2. Write headings that say something Do the headings alone tell the story?
3. Keep paragraphs short One idea each, no more than five sentences?
4. Use short sentences and plain words Any sentence over 25 words? Any word with a plainer twin?
5. Front-load Do the first words of each line carry the meaning?
6. Use lists and tables Are steps numbered and comparisons in a table?
7. Describe the link destination Does every link make sense out of context?
8. Use the active voice and “you” Is it clear who does what?
9. Be specific Could a competitor paste this sentence onto their page unchanged?
10. Make it accessible Headings in order, alt text, nothing conveyed by color alone?

1. Put the answer first

Use the inverted pyramid: conclusion first, then the supporting detail, then background. A reader who stops after the first paragraph should still leave with the main point. This matters most for how-to, pricing, policy and support pages, where the reader has a specific question.

Before After
Since our company was founded, we have always believed that customers deserve flexibility, which is why, after a great deal of consideration, we have updated our returns policy. You can now return any item within 60 days, up from 30. Here’s how the new policy works.

Start drafting from the question your reader typed into the search box, and answer it in the first two sentences.

2. Write headings that say something

Scanners read headings first and decide from them whether to read the section. A heading that only names a topic (“Overview,” “Details,” “Pricing”) makes them dig; a heading that states the point lets them skip or stop. Clever or punny headings are worse still, because they hide the content.

Before After
  • Overview
  • The Nitty-Gritty
  • What About Cost?
  • How the import works
  • Which file types you can upload
  • Plans start at $8 a month

Read your H2s in order without the body text. If they tell the whole story, the page is scannable. Our guide to writing better headlines covers titles in more depth, and the Headline Analyzer scores length and word choice.

3. Keep paragraphs short and focused

One idea per paragraph. On a phone, a 150-word paragraph becomes a wall of text that readers skip. GOV.UK’s clear language guidance (checked on 2026-10-14) says paragraphs should have no more than five sentences; we aim for two to four on most web pages. One-sentence paragraphs are fine for emphasis, but a page made only of them reads like a list without bullets.

Before After
A single paragraph that explains what the feature does, who it is for, how to switch it on, what it costs and what to do if it fails. Five short paragraphs, or a short intro followed by a list, each covering one of those points.

The Paragraph Counter flags paragraphs over 150 words, and the editor’s Long paragraphs highlight marks them in place.

4. Use short sentences and plain words

Long sentences force readers to hold several ideas at once; formal words slow them down without adding meaning. The same GOV.UK guidance tells writers to try to split sentences over 25 words and to prefer short, everyday words, such as “help” instead of “assist.”

Before After
In the event that you are unable to access your account, it is recommended that you utilize the password reset functionality located on the sign-in page. Can’t sign in? Use “Forgot password” on the sign-in page.

Swap formal words for plain ones: utilize → use, commence → start, facilitate → help, approximately → about, purchase → buy, sufficient → enough. The Readability Checker lists your longest sentences and most frequent complex words with plain alternatives. For a full treatment, see the plain language guide.

5. Front-load sentences, links and list items

Scanners often read only the first few words of each line. Put the information-carrying words there, and push context to the end.

Before After
  • To make sure your changes are not lost, it’s a good idea to save regularly.
  • In the settings menu, you’ll find the export option.
  • Save regularly so you don’t lose changes.
  • Export is in the settings menu.

The same goes for list items (“Export to PDF, Word or Markdown,” not “You can also choose to export…”) and for link text (rule 7).

6. Use lists and tables for steps, options and comparisons

If the content is a sequence, use a numbered list. If it’s a set of options or features, use bullets. If readers compare items on several attributes, use a table. Prose is for explanation and argument, not for data the reader wants to look up.

Before After
To install the add-on, first open the settings and go to the add-ons tab, then search for the name and click install, after which you need to restart the app.
  1. Open Settings → Add-ons.
  2. Search for the add-on and click Install.
  3. Restart the app.

Keep lists parallel (every item starts the same way, such as with a verb) and short enough to scan, usually no more than seven or eight items before you group them.

7. Write link text that describes the destination

Many readers, and all screen-reader users who pull up a list of links, see link text out of context. “Click here,” “read more” and “this page” tell them nothing. Describe where the link goes, and mention the file type if it isn’t a web page.

Before After
To see our pricing, click here. For the full guide, read more. See pricing for teams. Download the setup guide (PDF, 2 MB).

Link text is shown in italics.

Descriptive anchor text also helps search engines understand the linked page, so it serves both audiences at once.

8. Use the active voice and talk to the reader

Active sentences say who does what, which makes them shorter and clearer. Addressing the reader as “you” turns abstract rules into instructions they can follow.

Before After
Applications must be submitted by the applicant before the deadline. Late submissions will not be accepted. Send your application by March 31. We can’t accept late applications.

Passive voice still has its place, for example when the actor is unknown or unimportant (“The file was deleted”). Our guide to active vs passive voice explains when to keep it.

9. Be specific and cut the filler

Vague claims (“fast,” “easy,” “world-class”) cost words and earn nothing, because every competitor says the same. Specifics are shorter to scan and easier to trust: a number, a time, a name, a real example. Delete introductions that announce what the page will do, and summaries that repeat it.

Before After
Our amazing, easy-to-use tool helps you save lots of time on your writing tasks every single day. Paste your draft and see word count, reading time and readability in under a second.

If you can’t make a claim specific, consider whether it belongs on the page at all.

10. Make it accessible to everyone

Accessible writing is better writing for all readers, not a separate task:

  • Use real heading levels in order (H2, then H3 inside it), so screen-reader users can jump between sections.
  • Give images alt text that says what the image shows and why it matters; leave purely decorative images with empty alt text.
  • Don’t rely on color alone. “Fields in red are required” fails for readers who can’t see red. Add a label or symbol.
  • Spell out abbreviations the first time you use them, and avoid jargon your readers may not know.
  • Caption or transcribe audio and video content.
  • Avoid instructions based on position or shape (“click the round button on the right”), which break on small screens and for screen-reader users.
Before After
Click the green button on the right to continue. Select Continue to go to the payment step.

A bonus rule: every page is page one

Print readers usually start at the beginning. Web readers land wherever a search result or a shared link sends them, often in the middle of your site. Write each page so it stands on its own:

  • Define a key term on every page that uses it, or link to the definition, instead of writing “as explained earlier.”
  • Link to prerequisites (“You’ll need an account first; create one here”) rather than assuming the reader came from the previous page.
  • Don’t point to other pages with “in the previous chapter” or “as shown earlier.” Link to the page or section by name instead.
  • Make the page title and H1 make sense in a search result, a browser tab and a bookmark list, where the rest of your site isn’t visible.

Pages written this way are also easier to update, because each one depends less on the others.

Check your page before you publish

  1. The five-second test: look at the top of the page for five seconds. Can you tell what it’s about and what to do next?
  2. The heading test: read only the headings. Do they tell the story?
  3. The phone test: open the page on a phone. Are paragraphs short, tables scrollable and buttons easy to tap?
  4. The numbers test: run the Sentence Counter and fix sentences over 25 words; check the Readability Checker score.
  5. The link test: read every link text on its own. Does each one say where it goes?

You can do the measuring in one place: the WritePadPro editor highlights hard sentences, passive voice, complex words and long paragraphs as you write, and everything stays on your device.

Frequently Asked Questions

How is writing for the web different from writing for print?

Web readers usually arrive with a task and scan for the answer rather than reading from top to bottom. Web writing therefore puts the main point first, uses descriptive headings and links, keeps paragraphs short, and breaks steps and comparisons into lists and tables that are easy to scan on a phone.

How long should a paragraph be on a web page?

Short enough to cover one idea. GOV.UK’s guidance says no more than five sentences, and many web pages work best with two to four. WritePadPro’s Paragraph Counter flags paragraphs over 150 words, which can fill a phone screen on their own.

What reading level should web content target?

There is no single standard; it depends on your audience. For general audiences, many writers aim for plain language that most adults can read quickly, often around grade 8 on the Flesch–Kincaid scale. Specialist audiences can handle more technical terms, but they still benefit from short sentences and clear structure.

Why shouldn’t I use “click here” as link text?

Link text is often read out of context, for example when a screen-reader user lists all links on a page or when someone scans for links. “Click here” gives no clue where the link goes. Descriptive text such as “pricing for teams” helps every reader and also tells search engines what the linked page is about.

Do web writing rules help with SEO?

Indirectly. Google’s documentation asks for content that is easy to read and well organized, with descriptive titles, headings and link text. The same habits that help scanners, such as answering the question early and using clear headings, also make it easier for search engines to understand the page.

Try These Tools

Related Articles