14 Ways to Write Stunning Web Content

web-content-14-ways-improve

Ah, yes, writing for the web. So easy anyone can do it. Which may be the problem, of course.

Let’s rewind for a sec.

Ever read Blink? Malcolm Gladwell explains why we make critical decisions ‘in the blink of an eye’.

If you run an online business, or spend any time writing on the web, it’s worth thinking about this.

When a customer visits your website.

Blink.

What’s the first thing they notice?

Blink.

What’s the next thing they notice? Or. What did you want them to see, do, think, or feel?

Blinkkkk!

At this point, they’ve decided to hit the Back button or read on.

Of course, you can’t see this. But if you look at the stats closely enough, you should see where they leave and be able to work out why.

Why do they leave?

Different reasons.

But, for sure, writing for the web requires new a different approach than the way you wrote in high school, at work, or with your friends.

Also. NEVER. Never write as you speak.

This is arguably the worst writing advise ever.

Instead, write to affect the reader.

Before you start writing web content, try to understand the basics of information architecture, navigation, and micro-content.

As readers scan text on the Web, make sure that you:

  • Write short paragraphs instead of large blocks of text
  • Use bulleted lists to break out the key points
  • Give one subhead for each idea.
  • Add H2 and H3 to highlight the key points
  • Use simple, everyday language.

Using ‘Paper Models’ to Develop Better Web Content

If you use even half of the suggestions here, you’re 90% ahead of the rest:

  1. Remember, on the web, one print page requires two or three screens. So, refine your text for the web.
  2. Write small digestible chucks.
  3. Create a hierarchy for all the content you intend to develop. Think of it as a content pyramid.
  4. Outline your website as if you were preparing a printed publication. Create a Table of Contents and work outwards.
  5. Identify your site’s purpose and outline its main sections (e.g. the keywords people will use to navigate) and the links within those headings.
  6. Write headlines and links on Post-IT sticky notes and put them on a chart. Show the chart to sample readers.
  7. Run a usability test. Ask them how to get from one section to another.
  8. Draw the outline of each webpage on paper.
  9. Stack the pages and, sitting next to the user, ask them to “click” the headings to get there. If they chose the right pages, continue; otherwise go back and see what didn’t work.
  10. Don’t give any hints or clues on how to navigate.
  11. Sit back and watch. You’ll be amazed how their approach differs from what you had expected.
  12. Make notes for later revisions. This paper model helps you see how people navigate through the site.
  13. By writing concise, descriptive headings, you will lead users to the content that they are seeking. For example, do visitors expect to find phone numbers, under “Who we are” or “Contact us”?
  14. Planning is 80 percent of the work. Once you’ve created a good outline, the writing will have more impact.

What else would you add?

 

Thousands of templates to jump start your project

Acceptance Test Plan

Contingency Plan

Software Development Templates

Acquisition Plan

Conversion Plan

Software Requirements Specification

Action Plan

Cost Benefit Analysis

Software Testing

API Documentation

Database Design

Standard Operating Procedures (SOP)

Audience Analysis

Datasheet

Statement of Work

Availability Plan

Deployment Plan

System Administration Guide

Bill of Materials

Design Document

System Boundary

Business Case

Disaster Recovery Plan

System Design Document

Business Continuity

Disposition Plan

System Specifications

Business Plan

Documentation Plan

Technical Writing Templates

Business Process

Employee Handbook

Test Plan

Business Requirements

Error Message Guide

Training Plan

Business Rules

Expression of Interest

Transition Plan

Capacity Plan

Fact Sheet

Troubleshooting Guide

Case Study

Feasibility Study

Use Case

Change Management Plan

Functional Requirements

User Guide

Communication Plan

Grant Proposal

Verification and Validation Plan

Concept of Operations

Implementation Plan

White Papers

Concept Proposal

Installation Plan

Work Instructions

Configuration Management Plan

Interface Control Document

Software Development Templates

Acceptance Test Plan

Maintenance Plan

Software Requirements Specification

Acquisition Plan

Market Research

Software Testing

Action Plan

Marketing Plan

Standard Operating Procedures (SOP)

API Documentation

Needs Statement

Statement of Work

Audience Analysis

Operations Guide

System Administration Guide

Availability Plan

Policy Manual

System Boundary

Bill of Materials

Project Plan

System Design Document

Business Case

Proposal Manager Templates

System Specifications

Business Continuity

Proposal Template

Technical Writing Templates

Business Plan

Quality Assurance Plan

Test Plan

Business Process

Release Notes

Training Plan

Business Requirements

Request for Proposal

Transition Plan

Business Rules

Risk Management Plan

Troubleshooting Guide

Capacity Plan

Scope of Work

Use Case

Case Study

Security Plan

User Guide

Change Management Plan

Service Level Agreement (SLA)

Verification and Validation Plan

Communication Plan

Setup Guide

White Papers

Concept of Operations

Social Media Policy

Work Instructions

Concept Proposal

Contingency Plan

 

Configuration Management Plan

Conversion Plan