Everybody writes down what a page is about. Almost nobody writes down what it isn’t.
That second half is where overlap gets prevented, and it’s the half that gets skipped, because the positive version feels like the work. You’ve got a keyword, you’ve got a topic, you’ve got a one-sentence job for the page. That feels finished. So you go write.
How Overlap Actually Happens
You’re writing a page about improving email open rates. You’ve got the one-sentence job. You start.
Halfway through, you get into subject lines, because subject lines affect open rates. Then a bit on segmentation, because segmented sends open better. Then something about the spam folder, because if it doesn’t land in the inbox it doesn’t get opened.
Every one of those felt like it belonged. For completeness.
Now you’ve got four pages’ worth of topic on one page, and three future pages with nothing left to say. That’s how overlap happens. Not on purpose. One paragraph at a time.
Why This Isn’t A Discipline Problem
Here’s the part worth sitting with, because it changes how you fix it.
When the only thing written down is what the page is about, the page has no edges. And a page with no edges can’t be violated. So nothing you add while drafting feels like a mistake. Every addition passes the only test available to you in that moment, which is “is this related to the topic,” and the answer is always yes. That’s why the drift feels reasonable while it’s happening.
Scope creep isn’t a failure of focus. It’s the default behavior of a page whose boundary was never written down. Without one, the boundary gets decided by whoever is drafting, on the day they’re drafting, based on what occurred to them. Next month, a different day and a different mood produce a different boundary on the page next door, and the two of them overlap in a spot nobody chose.
Naming what the page leaves out is what gives you something to fail. It converts “is this related” into “is this mine,” which is a question with a real answer.
What It Looks Like On Paper
It’s three lines. Under the page’s one-sentence job, list the nearby topics that belong somewhere else.
For the email open rates page:
Job: Show what actually moves open rates and how to improve them.
Not this page:
- Subject line writing (its own page)
- List segmentation (its own page)
- Deliverability and spam filters (its own page)
That’s it. Thirty seconds of work. And now when you’re drafting and subject lines start pulling at you, you’re not deciding in the moment whether it belongs. You already decided. The decision was made calmly, looking at the whole cluster, instead of in the middle of a paragraph where everything looks related.
The names matter more than the count. “Don’t go too broad” isn’t negative scope, it’s a mood. “Subject line writing belongs on its own page” is negative scope, because you can check a paragraph against it.
Deciding Where Each One Goes
Naming a nearby topic raises the obvious next question, so answer it while you’re there: does this get a sentence, a section, or its own page?
A rough rule that holds up:
A sentence if the reader just needs to know it exists and isn’t covered here. One line and a link.
A section if the page’s job can’t be understood without it. If someone reading your open rates page genuinely can’t act on the advice without knowing one thing about deliverability, that one thing lives here, in a section, scoped tightly to what this page needs.
Its own page if someone would search for it by itself. That’s the cleanest test available. Nobody searches “the deliverability part of open rates.” They search “why are my emails going to spam.” Separate search, separate page, and if you absorb it into this one, you’ve built a page that competes with the page you’re going to write later.
The trap is the middle option. A section is the compromise that feels safe and creates the most overlap, because a “short section” on a topic that deserves its own page is exactly the thing that makes two pages fight later. If it could be a page, make it a page and link to it.
The Mid-Draft Moment
You’ll still feel the pull while writing. That’s fine, and it’s not a sign the plan was wrong.
When a topic on the not-this-page list comes up mid-draft, you get one sentence and a link. Acknowledge it, point to where it’s handled, keep moving.
What you don’t do is give it three paragraphs while you’re here. That’s the move that undoes the whole thing. The three paragraphs are always well-intentioned, they’re usually pretty good, and they’re the reason the other page never ranks.
Running It Backwards On A Site You Already Have
Everything above assumes you’re planning. Most of the time you’re not. You’ve got a site with pages already on it, two of them fighting over the same queries, and no map that ever said what either one was supposed to leave alone.
You can write negative scope after the fact, and it works as a diagnostic.
Take the two competing pages. For each one, write the one-sentence job and the three nearby topics that belong elsewhere. Do it honestly, based on what each page is actually best at, not what you wish it were.
Then look at where the two lists collide. One of two things happens.
Both lists want to claim the same topic. That’s your overlap, named. Now ask which page could state that topic as its one-sentence job without contradicting itself. That page owns it. The other one gets a sentence and a link, and you go cut the paragraphs that were doing the competing.
Neither list can put it down. Both pages think they need it, and neither can name a job without it. That usually means you’ve got one page’s worth of topic spread across two URLs, and the fix is a merge rather than a boundary.
Either way you’ve turned “these two pages seem to overlap” into a specific decision about a specific topic. That’s a much easier thing to act on than a vague sense that your cluster is muddy.
The Point
Negative scope takes thirty seconds per page and prevents the problem that can take months to unwind. It’s the cheapest thing in content planning and the least done, for the same reason: it produces nothing. There’s no deliverable. You write three lines about topics you’re not going to cover and then go do the work you were going to do anyway.
Except the work comes out different, because now the page has an edge, and you can tell when you’re about to cross it.
That’s what a topical map actually enforces. Not what each page covers. What each page leaves alone.
