Do not split a page simply because it is long. Length can indicate a problem, but it does not identify what the problem is, and a long guide with one clear purpose beats four short pages that make the user jump between them.
Split when the content serves distinct user needs that can stand independently:
- The page answers two or more substantially different questions.
- Different sections belong to different documentation types, and each has enough depth to work on its own.
- Different audiences need meaningfully different workflows.
- A troubleshooting section has grown large enough to distract from the main task.
- Users are likely to search directly for a section rather than encounter it as part of the wider page.
- One section changes on a different schedule from the rest.
- The page has become hard to scan because several independent purposes compete for attention.
Keep it together when
- A short prerequisite explanation sits before a procedure
- A warning affects the task being performed
- Brief definitions are needed to understand the instructions
- Optional branches sit within the same overall workflow
- Platform-specific differences can be presented clearly in separate sections
- A short troubleshooting section relates directly to the procedure
- Small amounts of stable information would otherwise require another click
The test is practical: does splitting the material make the user's task easier? If not, keep it together.
