Strategy

Over-optimization: when your page tries to cover too much

June 2, 20265 min readIntentFit

Most content advice is about adding. But pages can also fail by covering too much — mixing intents, over-serving, and burying the answer in off-intent noise. Here's how the focus component catches it, and when to split a page versus cut a section.

Almost every piece of content advice points in one direction: add more. More headings, more sections, more depth, more entities. It's good advice right up until it isn't — because a page can also fail by trying to do too much.

A page that answers six different jobs at once answers none of them cleanly. The reader who came for one thing wades through five others. The crawler trying to understand what the page is about gets a muddy signal. That's over-optimization, and it's the failure mode the focus component is built to catch.

What focus measures

IntentFit scores intent satisfaction across three components — coverage, depth, and focus. Coverage and depth are about enough: do you address the intents in demand, and do you answer them completely? Focus is the opposite pressure. It measures how little off-intent noise the page carries — how much of the content actually serves the demand the page receives, versus material that's there for some other reason.

A page with high coverage and high depth but low focus is doing the right work and the wrong work in the same place. It answers the question, then keeps going into three adjacent topics nobody on that page was asking about.

  • Coverage58

    How many of the distinct intents in real demand the page addresses at all.

  • Depth71

    For the intents it covers — how completely it answers them.

  • Focus84

    The opposite of over-serving — how little of the page is off-intent noise.

Strong depth on its core topic, but a sprawling page mixing three unrelated intents pulls the score down through focus.

Why off-intent noise hurts

The damage runs in two directions at once.

For readers, off-intent content is friction. Someone arrives for "how to calculate notice period," finds the answer in paragraph two, then has to scroll past sections on employment contracts, severance, and remote-work policy to confirm there's nothing more for them. Every off-intent section is a chance to bounce — and bounce is exactly the behavior answer engines and ranking systems read as this page didn't satisfy the search.

For crawlers, the problem is signal dilution. When a page tries to rank for everything, it gives search engines a weak read on what it's primarily about. A focused page that answers one cluster of intents thoroughly sends a clean topical signal. A sprawling page splits that signal across topics it half-covers, and tends to lose to pages that picked a lane. This is also why aligning a page to the dominant SERP intent matters: when the results page is built around one job and your content is built around five, the mismatch is the problem.

Over-serving looks like effort

The dangerous part is that a bloated page feels thorough. It's long, it's detailed, it took work. But length spent on intents the page doesn't actually receive demand for isn't depth — it's noise that drags focus down.

How over-optimization happens

It's rarely one bad decision. It accumulates.

A page ranks for its topic, so over a year you keep bolting on sections to "capture more keywords." A product page absorbs a comparison, an FAQ, a pricing breakdown, and a use-case gallery until it's four pages wearing one URL. An evergreen guide gets updated by three different writers who each add their own angle. None of these moves is wrong in isolation. Together they produce a page that's optimized for a keyword list instead of an intent.

The tell is always the same: the page receives demand for one or two dominant intents, but most of its word count serves intents that barely show up in the data — or don't show up at all.

Split or cut: the decision

When focus is low, you have two tools. Knowing which to reach for is the whole skill.

Cut when the off-intent material has no real demand of its own. If a section exists because a writer thought it was relevant, but Search Console shows the page gets no meaningful impressions for that intent, it's pure noise. Remove it. The page gets tighter, the core answer rises, and you've lost nothing the audience was actually asking for.

Split when the off-intent material has its own demand. If a section is dragging focus down but the data shows real impressions behind that intent, it doesn't belong in the trash — it belongs on its own page. Carve it out, give it a URL that targets that intent directly, and now you have two focused pages instead of one diluted one. Each sends a clean signal, each answers its cluster completely, and your total coverage across the property goes up.

The deciding question is never "is this section good?" It's "does the demand for this intent live on this page, somewhere else, or nowhere?"

Let the data pick the surgery

Pull the page's real query demand first. Sections with their own impression volume get split into dedicated pages; sections with none get cut. The same focus problem has two opposite fixes, and only the demand tells you which.

Focus is a feature, not a constraint

It's tempting to treat focus as the component that just tells you to delete your hard work. It isn't. Focus is what keeps coverage and depth honest. Without it, the optimization loop only ever pushes you to add — and "add until it ranks" is exactly how pages become unfocused in the first place.

A page that scores well on all three components is doing something specific: it covers the intents in real demand, answers them deeply, and spends almost none of itself on anything else. That's not a thin page. It's a page that knows what it's for. For the full picture of how the three components work together — and why a single score built from them is more actionable than a one-number grade — see coverage, depth, and focus as a content quality model.

Try it on your own site

Score any page on coverage, depth, and focus against its real Search Console demand — and see exactly which sections to keep, expand, split, or cut.

Put it into practice

Score your own pages

Connect Search Console and see exactly which pages miss the intent — and what to fix first.

Related reading