Core Concept: What Is Contextual Structure?
Contextual structure is HOW you organize information within a page and across pages. It controls what entities appear near each other, in what order, and with what connective tissue. Google's language models evaluate not just what entities are present, but how they are spatially and semantically arranged relative to each other.
Poor contextual structure: correct entities, wrong order, no bridges between sections. Strong contextual structure: entities appear in sequence matching user intent progression, with explicit bridges linking sections.
Main Content vs. Supplementary Content
Every web page contains two zones:
Main Content (MC)
- The primary purpose zone — why the page exists
- Must appear above the fold or within the first scroll
- Gets full E-E-A-T weight from quality raters
- Must match the declared Central Search Intent for the site
Supplementary Content (SC)
- Navigation, sidebars, related articles, footer links
- Important for user experience but not evaluated as E-E-A-T proof
- Can drain contextual focus if over-weighted relative to MC
Rule: Main Content must be the dominant zone by word count AND by keyword/entity concentration.
Contextual Hierarchy Within an Article
Structure articles as a descending hierarchy of contextual specificity:
- Macro Context — Establish the broadest context first (the entity category, the central search intent)
- Meso Context — Narrow to the attribute being discussed
- Micro Context — The most specific answer (numeric value, comparison, procedure)
Each transition must be bridged. A contextual bridge is a sentence or phrase that explicitly connects the previous section's conclusion to the next section's premise.
Example bridge:
"Understanding how [X] affects [Y] leads directly to the question of how [Y] varies across [Z], which is what the next section addresses."
Internal Linking Architecture (Contextual Model)
Links are not just navigation — they are contextual signals. Each internal link declares: "these two pages share a contextual relationship."
Koray's rules for internal linking:
| Rule | Rationale | |------|-----------| | Link from outer sections to core section | Establishes topical authority flow | | Anchor text must match the target page's Entity + Attribute | Not generic "click here" or "learn more" | | Supplementary nodes link up, never down | Direction reinforces hierarchy | | Quality nodes receive the most inbound internal links | Amplifies their ranking signal | | Never link two pages that share zero contextual overlap | Dilutes relevance signal |
Contextual Coverage Balance
Each section of a page must carry proportional weight to its role in the contextual hierarchy:
- Introduction: macro context setup (10-15% of word count)
- Main sections: meso + micro context (70-80% of word count)
- Closing: synthesis + CTA (5-10% of word count)
Pages where the introduction consumes 30%+ of word count fail contextual balance — the macro dominates and micro never delivers.
Contextual Borders
Contextual borders separate what belongs in main content from what belongs in supplementary content. Common violations:
- Putting FAQs inside main content when they belong in supplementary
- Adding case studies in sidebars where they should be in main content
- Navigation links embedded inside body paragraphs
Maintain hard borders. MC is the primary delivery zone. SC is the support zone. Never mix their roles.
Cross-References
koray-semantic-seo-master— macro framework for all Koray skillskoray-contextual-vector— heading-level structure within an articlekoray-microsemantics— sentence-level optimization within sectionsinternal-linking-optimizer— execution tool for implementing the link architecture
#seo-sop #seo #semantic #koray #content-structure #internal-linking