General Guidelines

Less is more. People reading online are likely to be skimming and you rarely have their full attention. Use short, clear, and concise sentences where possible. Don't cram a bunch of different keywords into one sentence, too many and it starts to sound forced and confusing. Relentlessly edit and trim complicated messaging until it’s skimable and easy to understand.

Instead of:

We are delighted to have the opportunity to help you save, organize, and share all of your precious family memories for your lifetime plus 100 years – guaranteed – with a goal of many generations beyond.

Try:

We are delighted to help you save your family memories for generations.

Avoid talking about future features when at all possible. Plans change quickly, and talking about future changes that may never come to be is a recipe for distrust. If it becomes necessary to discuss specifics, don't commit to any sort of timeline unless the dev team is nearly finished with that particular feature.

Example:

Upload your cherished photos, children’s artwork, scrapbook pages (and soon videos, recipes, and more), and celebrate them with the people that matter most.

Just take out the parenthetical. Qualifying existing features with future ideas doesn't sound confident and it just complicates the message. It also paints us into an awkward corner if (or when) plans change.

We're trustworthy, but we don't explicitly say that to our readers. Trust is something we earn. Anyone can say they're trustworthy, but it rarely comes off well. What we do and how we do it is what really matters.

Instead of:

Forever is a permanent, secure, trustworthy place in the cloud.

Frame it in terms of benefits to the reader:

Forever is dedicated to helping people by providing permanent, simple and secure cloud storage.

Before publishing, ask yourself three questions:

(Taken from <%= link_to("Nicely Said","http://www.nicelysaid.co/")%>, which you should definitely read if you're interested in writing for the web.)

Keywords

[DRAFT]

These are words to keep in mind. Don't force it, but where they naturally fit, use them.