{"slug":"entity-clouds-seo","title":"Entity Clouds SEO — Zone Theory and BUTTER ZONE Entity Declaration","tags":["seo","entity-seo","zone-theory","entity-clouds","nlp"],"agent_summary":"Applies Zone Theory: BM25F 9-zone content optimization with BUTTER ZONE entity declaration at the zone boundary. Maps entity cloud architecture for topical authority building.","trigger_phrases":["entity clouds","zone theory","BUTTER ZONE","BM25F zones","entity placement zones","NLP zones","content zones SEO","entity zone optimization"],"runnable":true,"markdown":"\n## What Is Zone Theory?\n\nZone Theory is Mike Merlino's SEO framework mapping content into 9 zones based on BM25F field weighting. Each zone has different NLP signal strength. Entity placement in high-weight zones carries more relevance signal than placement in low-weight zones.\n\n## The 9 BM25F Zones\n\n| Zone | Field | BM25F Weight | Notes |\n|------|-------|-------------|-------|\n| 1 | URL slug | Highest | Entity in URL = strongest on-page signal |\n| 2 | Page title / H1 | Highest | Entity in title = site-wide topic declaration |\n| 3 | Meta description | Medium | Click signal correlation; not direct ranking |\n| 4 | First 100 words | High | Lead paragraph entity density critical |\n| 5 | H2 headings | High | Contextual section declarations |\n| 6 | H3-H4 headings | Medium | Sub-attribute context |\n| 7 | Body paragraph entities | Medium | Distributed across full content |\n| 8 | Image alt text | Low-Medium | Confirms entities to image-processing systems |\n| 9 | Anchor text of outbound links | Low | Context signals via co-citation |\n\n## The BUTTER ZONE\n\nThe BUTTER ZONE is the entity declaration point — the zone where the primary entity is declared explicitly for the first time in the content. In strong content, the BUTTER ZONE occurs in Zones 1-4 (URL through lead paragraph).\n\n**BUTTER ZONE rule:** The central entity must appear in:\n- Zone 1 (URL): Once\n- Zone 2 (H1): Once, as the first semantic unit\n- Zone 4 (Lead paragraph): Twice in first 100 words\n- Zone 5 (H2s): At least 3 of the first 5 H2s\n\nContent that misses the BUTTER ZONE — entity appearing first in Zone 7 (body paragraphs) — signals weak topical commitment to the entity.\n\n## Entity Cloud Architecture\n\nAn entity cloud is the set of semantically related entities that appear around the central entity in content. The cloud tells Google what the central entity IS by showing what it co-occurs with.\n\n**Building an entity cloud:**\n1. Identify the central entity (the topic of the page)\n2. Extract entities that typically co-occur with it in authoritative content (use Google NLP API, Metehan Entity Extractor, or competitor analysis)\n3. Categorize co-occurring entities: primary (direct attributes), secondary (supporting context), tertiary (broader contextual domain)\n4. Distribute primary entities across Zones 5-7\n5. Distribute secondary entities across Zones 6-7\n6. Use tertiary entities sparingly in Zone 7 only\n\n## Sentiment Signals in Entity Clouds\n\nFrom Mike Merlino's $100K testing: **for local rankings, review sentiment signals outweigh entity optimization.** Entity clouds must include sentiment-positive entities — reviews mentioning keywords, service quality signals, outcome language.\n\nThis means entity clouds for local content must include:\n- Service-specific entities (what you do)\n- Location entities (where you do it)\n- Outcome entities (results customers experience)\n- Trust entities (license numbers, years in business, certifications)\n\n## Zone Theory NLP Balance\n\nTarget NLP 60/40 ratio: 60% NLP-optimized entity placement, 40% natural human language. Content that reads as pure entity optimization fails quality signals. Content without entity optimization fails relevance signals.\n\nThe 60/40 balance is measured by reading a paragraph out loud. If it sounds like a list of keywords, it fails the human-language 40%. If it flows naturally but never explicitly names the central entity, it fails the entity-optimization 60%.\n\n## Cross-References\n\n- `entity-seo` — full entity SEO pipeline including Wikidata and Knowledge Panel\n- `koray-microsemantics` — sentence-level entity placement within zones\n- `schema-stack` — schema reinforces entity cloud through structured data\n- `eeat-audit` — E-E-A-T trust entities (credentials, institutions) in the cloud\n\n#seo-sop #seo #entity-seo #zone-theory #entity-clouds #nlp\n","html":"<h2>What Is Zone Theory?</h2>\n<p>Zone Theory is Mike Merlino's SEO framework mapping content into 9 zones based on BM25F field weighting. Each zone has different NLP signal strength. Entity placement in high-weight zones carries more relevance signal than placement in low-weight zones.</p>\n<h2>The 9 BM25F Zones</h2>\n<p>| Zone | Field | BM25F Weight | Notes |\n|------|-------|-------------|-------|\n| 1 | URL slug | Highest | Entity in URL = strongest on-page signal |\n| 2 | Page title / H1 | Highest | Entity in title = site-wide topic declaration |\n| 3 | Meta description | Medium | Click signal correlation; not direct ranking |\n| 4 | First 100 words | High | Lead paragraph entity density critical |\n| 5 | H2 headings | High | Contextual section declarations |\n| 6 | H3-H4 headings | Medium | Sub-attribute context |\n| 7 | Body paragraph entities | Medium | Distributed across full content |\n| 8 | Image alt text | Low-Medium | Confirms entities to image-processing systems |\n| 9 | Anchor text of outbound links | Low | Context signals via co-citation |</p>\n<h2>The BUTTER ZONE</h2>\n<p>The BUTTER ZONE is the entity declaration point — the zone where the primary entity is declared explicitly for the first time in the content. In strong content, the BUTTER ZONE occurs in Zones 1-4 (URL through lead paragraph).</p>\n<p><strong>BUTTER ZONE rule:</strong> The central entity must appear in:</p>\n<ul>\n<li>Zone 1 (URL): Once</li>\n<li>Zone 2 (H1): Once, as the first semantic unit</li>\n<li>Zone 4 (Lead paragraph): Twice in first 100 words</li>\n<li>Zone 5 (H2s): At least 3 of the first 5 H2s</li>\n</ul>\n<p>Content that misses the BUTTER ZONE — entity appearing first in Zone 7 (body paragraphs) — signals weak topical commitment to the entity.</p>\n<h2>Entity Cloud Architecture</h2>\n<p>An entity cloud is the set of semantically related entities that appear around the central entity in content. The cloud tells Google what the central entity IS by showing what it co-occurs with.</p>\n<p><strong>Building an entity cloud:</strong></p>\n<ol>\n<li>Identify the central entity (the topic of the page)</li>\n<li>Extract entities that typically co-occur with it in authoritative content (use Google NLP API, Metehan Entity Extractor, or competitor analysis)</li>\n<li>Categorize co-occurring entities: primary (direct attributes), secondary (supporting context), tertiary (broader contextual domain)</li>\n<li>Distribute primary entities across Zones 5-7</li>\n<li>Distribute secondary entities across Zones 6-7</li>\n<li>Use tertiary entities sparingly in Zone 7 only</li>\n</ol>\n<h2>Sentiment Signals in Entity Clouds</h2>\n<p>From Mike Merlino's $100K testing: <strong>for local rankings, review sentiment signals outweigh entity optimization.</strong> Entity clouds must include sentiment-positive entities — reviews mentioning keywords, service quality signals, outcome language.</p>\n<p>This means entity clouds for local content must include:</p>\n<ul>\n<li>Service-specific entities (what you do)</li>\n<li>Location entities (where you do it)</li>\n<li>Outcome entities (results customers experience)</li>\n<li>Trust entities (license numbers, years in business, certifications)</li>\n</ul>\n<h2>Zone Theory NLP Balance</h2>\n<p>Target NLP 60/40 ratio: 60% NLP-optimized entity placement, 40% natural human language. Content that reads as pure entity optimization fails quality signals. Content without entity optimization fails relevance signals.</p>\n<p>The 60/40 balance is measured by reading a paragraph out loud. If it sounds like a list of keywords, it fails the human-language 40%. If it flows naturally but never explicitly names the central entity, it fails the entity-optimization 60%.</p>\n<h2>Cross-References</h2>\n<ul>\n<li><code>entity-seo</code> — full entity SEO pipeline including Wikidata and Knowledge Panel</li>\n<li><code>koray-microsemantics</code> — sentence-level entity placement within zones</li>\n<li><code>schema-stack</code> — schema reinforces entity cloud through structured data</li>\n<li><code>eeat-audit</code> — E-E-A-T trust entities (credentials, institutions) in the cloud</li>\n</ul>\n<p>#seo-sop #seo #entity-seo #zone-theory #entity-clouds #nlp</p>\n"}