The strongest reason to create a new page is a distinct reader job. A guide that explains how to evaluate a service and a checklist used after purchase serve different moments, even when they share vocabulary. A second article that answers the same question with a slightly different title may add maintenance work without adding much value.
Before drafting, write a one-sentence promise for the proposed page and the closest existing resource. If those promises are effectively identical, investigate a refresh first.
Compare the two paths
| Situation | Consider | Why |
|---|---|---|
| The same answer needs current facts | Refresh | The reader’s job is stable |
| The existing page has a useful foundation but weak examples | Refresh | Depth can improve without splitting the answer |
| A different audience has different constraints | New page | The decision may need its own treatment |
| The format supports a different activity | New page or companion asset | A worksheet and an explanation can play distinct roles |
| Several pages repeat the same answer | Consolidation review | The collection needs a clearer primary resource |
Inspect the existing resource before deciding
Read the page as a visitor would. Is the answer easy to find? Are the examples still relevant? Does the page make a promise the body does not fulfill? The issue may be structure rather than missing topics. Adding another page would leave that problem in place.
Review where the page is linked and how the team uses it. Sales or customer success may depend on a specific explanation. Preserve useful material during a revision and communicate major changes to people who share the resource. Technical URL changes require their own implementation review; they should not happen as an incidental writing decision.
Document the decision
For a refresh, name the sections that will change and the evidence needed. For a new page, explain the distinct job and how it relates to the existing resource. Decide which page answers the broad question and which handles the specialized task.
After publication, review the collection together. The reader should be able to move between related resources without repeatedly encountering the same introduction. A strong archive feels like a set of connected answers, not a sequence of pages competing to explain the same thing.