Calls to action, explained without the jargon

The advice here is unglamorous, which is probably why it gets skipped. Here is calls to action without the vocabulary that usually surrounds it.

Pages that answer a real question outlive pages written to fill a slot in a sitemap. The failure mode is not doing it wrong, it is doing it once and assuming it stays done.

The short version

One clear next step beats several options. The cost of getting this wrong is rarely visible on the day it happens. The version that survives contact with a real deadline is the simple one.

Why people complicate it

Most of the confusion comes from tooling rather than from the idea itself. There is a version of this that is over-engineered, and it is worth avoiding.

Say what happens after the click. Getting it slightly wrong is survivable. Ignoring it entirely is not. The teams that stay on top of it are the ones who put it on a calendar rather than a wish list.

Making it stick

Reduce the sense of risk near the button. This is the sort of thing that compounds, quietly, in both directions. The version that survives contact with a real deadline is the simple one.

The short version

Writing for the web is largely an editing job: the first draft is always longer than it needs to be. Three things worth confirming about calls to action before you move on:

• Someone can say what the current setup is without going to look
• One clear next step beats several options — and you know whether that is true here
• There is a way to tell whether the last change to this helped

Most of the value here comes from doing the first two things, not all of them.