Google Doesn’t Read Your Page. It Reconciles It.
Most SEOs treat on-page optimization as a checklist: keyword in the title, the H1, the first paragraph, a few subheadings, done. That framing is close enough to be dangerous. It produces pages where every individual signal looks correct but the aggregate signal Google actually uses is confused or internally contradictory.
Google doesn’t rank on a single signal. It builds a probabilistic model of what your page is about by weighing dozens of on-page signals against each other — and when those signals disagree, the model doesn’t split the difference. It anchors on whichever signal carries the most weight for that query class, and your page either ranks for something adjacent to your intent or gets suppressed in favor of a more coherent competitor.
Knowing which signals carry the most weight, and why they sometimes pull against each other, is one of the more underrated diagnostic skills in technical SEO.
The Signals Google Actually Weighs
Google’s quality documentation and patents are imperfect maps, but they’re not useless. The signals that recur across them — and that match what we see when diagnosing real ranking problems — fall into a few distinct layers.
The Title and H1 Are the Loudest Signals, But They Can Lose the Argument
Your <title> tag and H1 carry outsized weight, but only when they’re coherent with the body content. A title optimized for one keyword variant while the body is written around a different variant creates a mismatch that’s surprisingly common and surprisingly damaging.
Example: a page titled “Enterprise Project Management Software” that spends 60% of its body copy discussing features aimed at freelancers. Google will index it. It may even rank it. But it will rank it for the query the body content actually serves, not the title. The body outvotes the title by volume and coherence.
The fix isn’t always rewriting the title. Sometimes the body copy is right and the title is aspirational. Know which one you actually want to rank for, then make sure both are pointing at it.
Heading Hierarchy as a Topical Outline
Google’s passage indexing, which started surfacing in 2021, made heading hierarchy more important rather than less. A clear H2/H3 structure lets Google identify discrete sub-topics and map individual passages to specific query variants. A flat or inconsistent hierarchy makes the page harder to decompose into rankable passages.
When the structure is flat, Google tends to treat the whole page as competing for one primary topic, which concentrates weight on the title and reduces the body content’s semantic range. For long pages covering several related sub-topics, that’s a ranking miss — passage-level potential left on the table.
One concrete audit: count how many of your H2s could plausibly serve as standalone search queries. If the answer is zero, your heading structure is organizational rather than topical, and it’s not helping Google understand the page’s scope.
The First 200 Words Are the Strongest Body Signal
The opening is where most pages establish their framing, and crawlers and feature extraction pipelines have historically weighted early content more heavily when building snippets and topical signals. This isn’t a fixed-length rule — it’s a byproduct of how framing works.
The failure mode is burying the actual topic after a generic intro. “Project management is a complex discipline with many tools available…” tells Google almost nothing. “This page compares Asana, Monday.com, and Linear specifically for software teams managing sprint-based workflows” tells Google a lot. The second version is also just better writing, which isn’t a coincidence.
Internal Links as Topical Context Signals
How a page is linked from the rest of your site carries real weight in how Google classifies it. People tend to think of internal links as PageRank plumbing — which they also are — but the anchor text and surrounding context of links pointing to a page are part of how Google builds its model of what that page is about.
We ran into this directly working through keyword cannibalization between two competing properties under the same ownership. The issue wasn’t just two pages targeting the same query — the internal link profiles of both pages were contradicting their intended topical focus. Links from posts about Topic A were pointing to a page meant to rank for Topic B, confusing the classifier on both ends.
Audit the anchor text distribution of internal links pointing to your most important pages. If the dominant anchor text doesn’t match your target keyword, that’s a signal problem, not just a UX problem.
Where Signals Conflict Most Often
Three specific conflict patterns come up repeatedly when diagnosing pages that rank for the wrong thing or underperform despite decent content.
Title vs. Body Mismatch
The most common pattern by a wide margin. Usually happens when a page was written for one audience and the title was later optimized for a different query without updating the body — or the reverse, a solid title with body copy written before the keyword strategy was clear.
Schema Markup That Contradicts Page Content
Schema is supposed to reinforce and clarify what’s already on the page. When it misrepresents it — marking up a generic blog post as a HowTo when the page has no discrete steps, or using Product schema on a category page — you’re not helping Google resolve ambiguity. You’re adding a contradictory signal. Google’s structured data documentation is explicit that markup should reflect visible content, not describe what you wish the page was.
The practical consequence: a schema mismatch can suppress rich result eligibility while doing nothing to hurt organic ranking, making it an invisible problem. Check Search Console’s rich results report against what’s actually live on the page.
Image Alt Text Optimized for a Different Keyword
Underestimated. Alt text is a genuine topical signal, not just an accessibility attribute. When images are optimized for a keyword variant that doesn’t match the rest of the page’s focus — usually because someone applied image SEO in isolation from the content strategy — it adds noise to the classifier’s input. Not catastrophic on its own, but on pages where other signals are already weak or ambiguous, it tips the balance.
How to Actually Diagnose a Conflicting Signal Problem
Pull a page you care about and run this process:
- List what your title, H1, opening paragraph, H2s, and internal link anchor text each suggest the page is about. Write them down separately.
- If you got six different answers, you have a signal conflict problem. If you got one coherent answer that doesn’t match your target query, you have a content-strategy problem.
- Check your schema against visible page content manually — not just through a validator, which only checks syntax.
- Run the same exercise on the top 3 ranking competitors for your target query. Look for where their signals are more coherent than yours, not where their word count is higher.
Word count comparison is the wrong reflex. A 600-word page with coherent signals routinely outranks a 2,000-word page with conflicting ones. We see this pattern often enough that it’s become our first diagnostic frame, not our last.
One Caveat That Actually Matters
Google’s signal weighting isn’t static across query types. Navigational queries weight title and brand signals heavily. Informational queries weight body content and heading structure more. Transactional queries weight schema, structured page sections, and user signals differently again. The same conflict that’s invisible for one query class can be decisive for another.
Before you prioritize which conflict to fix, know which query type you’re competing in. Fixing your H2 hierarchy is a good use of time for an informational page. For a product page, your Product schema and conversion signals matter more — the H2 audit can wait.
Pick one page sitting at position 6–10 for your target query. Map its signals. Find the one conflict you can resolve without rewriting the whole page. Fix that, wait three to four weeks, then move to the next. A tight loop on one page tells you more than a site-wide content audit ever will.