Order headings around the ideas
Write down the page's main question and the supporting questions needed to answer it. Choose headings that describe the content that follows. A heading level is not a font-size choice; it shows how a section relates to the rest of the page.
Read only the headings. Can you understand the sequence? If two sections with the same heading address different decisions, distinguish them. Do not skip levels just to achieve a visual style.
Name links by their destination
A link labeled Read more does not identify the resource. Add its subject, such as Read the guide to testing form receipt. If nearby text already explains the destination unambiguously, a shorter link may work.
Do not turn an entire sentence into a link when only one resource is relevant. After editing content, check that the link still describes its destination. A descriptive name that leads to the wrong page is still a poor route.
Review both the isolated list and full text
Try the heading list and links as if you do not know the subject. Can you choose the right detail? Then read each section in order. A link may be clear in a list yet interrupt a sentence, so both views are useful.
W3C WAI explains how headings support page structure and why link text should describe its purpose or function. Use that guidance, then assess the actual page experience.
| Weak pattern | Better review question |
|---|---|
| Several headings: Services | Which distinct decision does each section explain? |
| Link: Read more | Can the destination be identified by its name? |
| Heading level chosen for appearance | Does it express the content hierarchy? |
| Old link after a page change | Does it still lead to the right resource? |