{"slug":"koray-contextual-vector","title":"Koray Contextual Vector — Heading Structure and Content Flow","tags":["seo","semantic","koray","content-structure","headings"],"agent_summary":"Builds H1-H4 heading structures using Koray's contextual vector methodology: ordered sequences that create uninterrupted contextual flow and maximize featured snippet eligibility.","trigger_phrases":["contextual vector","heading structure","Koray headings","H1-H4 optimization","content flow order","heading hierarchy SEO","section ordering","semantic heading structure"],"runnable":true,"markdown":"\n## Core Concept: What Is a Contextual Vector?\n\nA contextual vector is the ordered sequence of headings (H1 through H4) in a web document that creates a single, uninterrupted line of contextual flow. Unlike typical SEO heading structures that jump between unrelated topics, a contextual vector flows as a whole — a straight line from first heading to last heading.\n\nEvery heading must contextually justify the next heading. If a reader cannot predict the general theme of the next section from the current heading, the vector is broken.\n\n## Why Heading Order Matters for Rankings\n\nGoogle's language models process headings as a structural signal before evaluating body content. The heading sequence tells the model:\n\n1. What entities this page covers\n2. In what order (progression signals intent fulfillment)\n3. At what depth (specificity signals topical authority)\n\nA broken heading vector — one where headings jump between unrelated attributes — signals poor topical organization even if the body content is strong.\n\n## Building a Contextual Vector\n\n### Step 1: Establish the H1 (Macro Context)\n\nThe H1 must contain:\n- The Central Entity\n- The primary attribute being addressed\n- Language matching the Central Search Intent\n\nExample (visa site): \"Germany Work Visa Requirements for Non-EU Citizens\"\nNot: \"Everything About Germany Visas\" (too broad)\nNot: \"Germany Visa Application Tips\" (wrong attribute focus)\n\n### Step 2: H2s Define the Meso Context\n\nH2s are the main topical compartments. They must:\n- Each address a distinct sub-attribute of the H1 topic\n- Be ordered by user intent progression (what questions arise naturally, in order)\n- Collectively cover the full scope declared in the H1\n\nOrdering rule: Start with definitional/qualifying questions (What is X?), progress to procedural questions (How do I get X?), end with evaluative/comparative questions (What happens if X is denied?).\n\n### Step 3: H3s Deliver the Micro Context\n\nH3s are the answer delivery layer. They must:\n- Map directly to the specific question answerable in that subsection\n- Be phrased as question-format headings where featured snippet opportunity exists\n- Contain the attribute term from the parent H2\n\nQuestion-format H3 example:\n- H2: Germany Work Visa Processing Times\n- H3: How Long Does a German Work Visa Take to Process?\n- H3: Can You Expedite a German Work Visa Application?\n\n### Step 4: H4s for Exceptions and Variants\n\nH4s handle edge cases, regional variations, or entity subtypes that do not warrant their own H3. Use sparingly. If H4 content is long, promote to H3 with its own contextual vector.\n\n## Featured Snippet Optimization via Contextual Vector\n\nGoogle extracts featured snippets from passages that:\n1. Immediately follow a question-format heading\n2. Contain a direct, declarative answer in the first sentence\n3. Are 40-60 words at the most\n\nDesign every H3 as a featured snippet target:\n- H3: How Long Does It Take to Get a German Work Visa?\n- First sentence after H3: \"A German work visa typically takes 4-8 weeks to process from the date of application submission at the German embassy.\"\n\n## Anti-Patterns\n\n| Anti-Pattern | Problem |\n|-------------|---------|\n| All H2s with no H3s | Eliminates featured snippet opportunities |\n| H3s that don't relate to parent H2 | Breaks contextual flow |\n| H2s in alphabetical order | Ignores user intent progression |\n| Generic H2s (\"Introduction\", \"Conclusion\") | No contextual signal |\n| Keyword-stuffed headings with no answer signal | Spam signal, not context signal |\n\n## Cross-References\n\n- `koray-semantic-seo-master` — the three principles underlying all Koray methodology\n- `koray-contextual-structure` — page-level architecture decisions before building headings\n- `koray-microsemantics` — sentence-level optimization within each heading section\n- `koray-content-brief` — brief template that encodes the contextual vector for writers\n- `featured-snippet-optimizer` — dedicated featured snippet targeting workflow\n\n#seo-sop #seo #semantic #koray #content-structure #headings\n","html":"<h2>Core Concept: What Is a Contextual Vector?</h2>\n<p>A contextual vector is the ordered sequence of headings (H1 through H4) in a web document that creates a single, uninterrupted line of contextual flow. Unlike typical SEO heading structures that jump between unrelated topics, a contextual vector flows as a whole — a straight line from first heading to last heading.</p>\n<p>Every heading must contextually justify the next heading. If a reader cannot predict the general theme of the next section from the current heading, the vector is broken.</p>\n<h2>Why Heading Order Matters for Rankings</h2>\n<p>Google's language models process headings as a structural signal before evaluating body content. The heading sequence tells the model:</p>\n<ol>\n<li>What entities this page covers</li>\n<li>In what order (progression signals intent fulfillment)</li>\n<li>At what depth (specificity signals topical authority)</li>\n</ol>\n<p>A broken heading vector — one where headings jump between unrelated attributes — signals poor topical organization even if the body content is strong.</p>\n<h2>Building a Contextual Vector</h2>\n<h3>Step 1: Establish the H1 (Macro Context)</h3>\n<p>The H1 must contain:</p>\n<ul>\n<li>The Central Entity</li>\n<li>The primary attribute being addressed</li>\n<li>Language matching the Central Search Intent</li>\n</ul>\n<p>Example (visa site): \"Germany Work Visa Requirements for Non-EU Citizens\"\nNot: \"Everything About Germany Visas\" (too broad)\nNot: \"Germany Visa Application Tips\" (wrong attribute focus)</p>\n<h3>Step 2: H2s Define the Meso Context</h3>\n<p>H2s are the main topical compartments. They must:</p>\n<ul>\n<li>Each address a distinct sub-attribute of the H1 topic</li>\n<li>Be ordered by user intent progression (what questions arise naturally, in order)</li>\n<li>Collectively cover the full scope declared in the H1</li>\n</ul>\n<p>Ordering rule: Start with definitional/qualifying questions (What is X?), progress to procedural questions (How do I get X?), end with evaluative/comparative questions (What happens if X is denied?).</p>\n<h3>Step 3: H3s Deliver the Micro Context</h3>\n<p>H3s are the answer delivery layer. They must:</p>\n<ul>\n<li>Map directly to the specific question answerable in that subsection</li>\n<li>Be phrased as question-format headings where featured snippet opportunity exists</li>\n<li>Contain the attribute term from the parent H2</li>\n</ul>\n<p>Question-format H3 example:</p>\n<ul>\n<li>H2: Germany Work Visa Processing Times</li>\n<li>H3: How Long Does a German Work Visa Take to Process?</li>\n<li>H3: Can You Expedite a German Work Visa Application?</li>\n</ul>\n<h3>Step 4: H4s for Exceptions and Variants</h3>\n<p>H4s handle edge cases, regional variations, or entity subtypes that do not warrant their own H3. Use sparingly. If H4 content is long, promote to H3 with its own contextual vector.</p>\n<h2>Featured Snippet Optimization via Contextual Vector</h2>\n<p>Google extracts featured snippets from passages that:</p>\n<ol>\n<li>Immediately follow a question-format heading</li>\n<li>Contain a direct, declarative answer in the first sentence</li>\n<li>Are 40-60 words at the most</li>\n</ol>\n<p>Design every H3 as a featured snippet target:</p>\n<ul>\n<li>H3: How Long Does It Take to Get a German Work Visa?</li>\n<li>First sentence after H3: \"A German work visa typically takes 4-8 weeks to process from the date of application submission at the German embassy.\"</li>\n</ul>\n<h2>Anti-Patterns</h2>\n<p>| Anti-Pattern | Problem |\n|-------------|---------|\n| All H2s with no H3s | Eliminates featured snippet opportunities |\n| H3s that don't relate to parent H2 | Breaks contextual flow |\n| H2s in alphabetical order | Ignores user intent progression |\n| Generic H2s (\"Introduction\", \"Conclusion\") | No contextual signal |\n| Keyword-stuffed headings with no answer signal | Spam signal, not context signal |</p>\n<h2>Cross-References</h2>\n<ul>\n<li><code>koray-semantic-seo-master</code> — the three principles underlying all Koray methodology</li>\n<li><code>koray-contextual-structure</code> — page-level architecture decisions before building headings</li>\n<li><code>koray-microsemantics</code> — sentence-level optimization within each heading section</li>\n<li><code>koray-content-brief</code> — brief template that encodes the contextual vector for writers</li>\n<li><code>featured-snippet-optimizer</code> — dedicated featured snippet targeting workflow</li>\n</ul>\n<p>#seo-sop #seo #semantic #koray #content-structure #headings</p>\n"}