Content Structure — Built for Scanning
Nightjar's alerts page is one long article of 1,200 words: the story of how the feature was built, then pricing, then the setup steps, buried in the sixth paragraph. Analytics show most visitors leave within twenty seconds. They did not fail to read. They scanned for the steps, did not see them, and left.
The rule
Readers scan before they read, so build the page for the scan.
Most readers of technical content arrive with a question and hunt for the answer. Structure is what lets them find it:
- Headings that say something. "Add an SMS channel" tells a scanning reader what is below it. "Overview 2" does not.
- The reader's goal first. What most readers came for goes near the top. Background comes later, or moves to its own page.
- Prerequisites before steps. Plan, permissions and tools come before step 1, not in the middle of step 4.
- The right container. Numbered lists for steps in order, bullets for items in no order, tables for comparisons, and warning boxes only for real dangers.
- Small chunks. Short paragraphs, each carrying one idea.
- Templates. When every how-to guide has the same skeleton, readers learn where to look.
Here is the alerts page after restructuring, shown as headings only:
# Set up alerts
## Choose an alert channel
## Add an email channel
## Add an SMS or Slack channel (Team plan)
## Send a test alert
## Alerts not arriving?The shortcut
Run the headings-only test: read nothing but the headings. Could a reader find their answer, and tell what order to do things in? If not, restructure before polishing a single sentence.
List what readers came to do
Pick a channel, add it, test it, and fix it when alerts do not arrive.
The trap is headings that follow the writer's filing system, such as "Background", "Details" and "Miscellaneous", instead of the reader's questions.
Drills
Answer fast — trust the rule.
Which heading passes the headings-only test?
Most visitors to the alerts page come to add a channel, but the page opens with the history of the feature. What should you do?
You need to compare the Free and Team plans on check interval, alert channels and monitor limit. Which container fits best?
Why give every how-to guide the same structure?
Remember
- Readers scan before they read, so build the page for the scan.
- Shortcut: the headings-only test: can a reader find their answer and the order of work from headings alone?
- Trap: headings that follow the writer's filing system instead of the reader's questions.