Central Entity + Source Context = Central Search Intent
Every search query is, at its core, a request for information about an entity from a specific perspective. The entity is the subject. The source context is the lens. Together, they define the central search intent — the exact informational need your page must satisfy.
Defining the Components
Central Entity
The primary subject the searcher wants to learn about. For "best running shoes for flat feet," the central entity is "running shoes" (specifically, the subset appropriate for flat feet).
Source Context
The perspective or use-case lens applied to the entity. In the same query, "flat feet" is the source context — it constrains which attributes of "running shoes" the searcher cares about (arch support, stability, cushioning) and which they do not (aesthetic design, color options).
Central Search Intent
The intersection: running shoe attributes that specifically address flat foot biomechanics. Your page must cover exactly these attributes to satisfy the intent — not generic running shoe information, and not a medical page about flat feet.
Why This Framework Changes Content Design
Most content targets keywords, not intent structures. The result is content that:
- Covers too many entities (diluted focus)
- Misses the source context (irrelevant attributes)
- Addresses the wrong depth level (too broad or too specific)
Google's patent on query understanding (US Patent 9,158,846) describes how search systems decompose queries into entity and context components. Content that aligns with this decomposition ranks because it matches the system's understanding of what the searcher needs.
Applying the Framework: A Step-by-Step Process
Step 1: Identify the Central Entity
What is the query fundamentally about? Strip away modifiers and context words. The entity is what remains.
Step 2: Identify the Source Context
What constrains or specifies the entity? This is usually an audience, use case, condition, comparison, or geographic scope.
Step 3: Map the Relevant Attributes
Which attributes of the central entity are relevant given the source context? Only these attributes belong on your page.
Step 4: Define Core Sections vs. Outer Sections
Core sections directly address the entity-context intersection. They are the heart of your page and must be comprehensive.
Outer sections provide supporting information — background on the entity, explanation of the context, related topics. They support but do not replace the core.
Step 5: Prioritize by Demand
Use Search Console data and query analysis to determine which attributes searchers most frequently seek. Cover high-demand attributes first and most thoroughly.
A Practical Example
Query: "CRM software for real estate agents"
- Central entity: CRM software
- Source context: Real estate agents
- Central search intent: CRM features and capabilities specifically relevant to real estate workflows
Core sections (must cover):
- Lead management for property inquiries
- Contact management for buyers, sellers, agents
- Transaction tracking and pipeline management
- Property listing integration
- Follow-up automation for showing schedules
Outer sections (supporting):
- What is CRM software (brief)
- Why real estate agents need CRM (brief)
- Pricing comparison for real estate CRMs
How Patnick Implements This
Our Content Depth dimension scores every page against the central-entity-plus-source-context framework. We analyze whether your pages correctly identify and cover the right entity-context intersection, and whether core sections receive appropriate depth while outer sections remain appropriately brief.
This is the difference between content that ranks and content that does not. Search systems reward pages that precisely match the structural intent behind queries — not pages that vaguely touch on the right topic.