A how-to page is a set of ordered steps with everything a reader needs before the first one. The shape is fixed and unglamorous, and following it is most of what separates a guide that gets used from one that gets abandoned.
Short answer
A how-to page states what the reader will end up with, lists what they need beforehand, gives numbered steps in order with one action each, and closes with how to tell it worked. Steps belong in ordered list markup rather than in paragraphs, and any step that needs its own explanation should link out instead of expanding.
Open by saying what the reader will have when they finish, how long it should take, and what could go wrong. Someone deciding whether to start needs those three facts before anything else on the page.
This also gives an answer engine something to lift. A guide that opens with a paragraph about why the subject matters offers no summary, so anything quoting it has to assemble one from the middle of the page.
Be honest about difficulty. A guide that promises something simple and then requires an afternoon and a permit loses the reader at the point they have already committed, which is worse than warning them at the top.
Tools, materials, access, accounts, permissions. Everything that has to exist before step one, gathered in one place where it can be checked in a few seconds rather than discovered at step four.
This section saves more abandoned attempts than any other part of a guide. It is also the part most often skipped by writers, because the author already owns everything and forgets that the reader might not.
Where an item needs explaining, name it here and link to the explanation rather than teaching it inline. That keeps the steps moving and gives the linked page a reason to exist in its own right.
A step should contain a single action with a single visible result. If a step has an and in the middle, it is usually two steps that were merged because they felt small at the time.
Say what should happen after each one. The reader needs a way to know they are still on track, and the confirmation is what turns a list of instructions into something a person can actually follow.
Number the steps using ordered list markup rather than typing the numbers into paragraphs. The markup states the order as a fact, which matters for screen readers and for anything parsing the page.
Every how-to page we publish follows the same outline. It is not creative and that is the point. A reader who has used one of your guides should recognize the shape immediately in the next one.
Screenshots that carry the only instruction. A picture of a settings screen with a circle around a button tells a reader nothing if they cannot see it, and tells an answer engine nothing at all. Write the step in words as well.
Steps that assume a state the reader may not be in. Now click the third tab assumes a particular screen, a particular version and a particular account type, none of which were stated in the requirements.
And the guide that stops at success. Most readers who need help are the ones where something went wrong, so the troubleshooting section is often the most valuable part of the page.
Structured markup exists for step-by-step content and is worth adding where the page is genuinely a procedure. It states the number of steps and their order, which removes any guesswork from a parser.
Only use it for real procedures. A sales page arranged as three steps is not a how-to, and marking it up as one is the kind of mismatch our page on structured data warns against.
Keep the markup generated from the same content the visitor sees. Hand-maintained step markup drifts the moment a step is added, and nothing will tell you that it has happened.
A how-to page rarely stands alone. It should link up to the subject hub it belongs to, sideways to the related procedures, and onward to the service page for readers who decide they would rather not do it themselves.
Put those links inside the sentences where the subject comes up. Our page on internal linking covers why a link in context is followed far more often than a list of links at the foot.
That last link matters commercially. A guide that ends without an obvious route to hiring you has done the teaching and handed the work to whoever the reader searches for next.
Use ordered list markup. Typing numbers into paragraphs looks the same on screen but states nothing to a screen reader or a parser. The markup makes the order a fact about the page rather than a visual convention.
As long as the procedure genuinely needs. Padding a short procedure to hit a word count makes it worse. Where a single step needs several hundred words of its own, that step should become a linked page.
They help readers who can see them, provided the instruction is also written in words. A screenshot carrying the only instruction excludes anyone using a screen reader and disappears entirely when the page is parsed.
Some readers will do it themselves, and many of those were never going to hire anyone. The rest see that you know the job. End the guide with a clear route to your service and the trade is usually favorable.
15-day free trial. Card required. Cancel before day 15 and you pay nothing.