{"slug":"geo-relevance-semantic-mastery","title":"GEO Relevance Semantic Mastery — Local Semantic Optimization","tags":["seo","local-seo","semantic","geo","location-pages"],"agent_summary":"Optimizes local content for geographic relevance using semantic entity signals: location entity embedding, proximity signals, service-area language patterns, and local co-occurrence entities that strengthen local pack rankings.","trigger_phrases":["geo relevance","geographic SEO","local semantic SEO","location entity optimization","geo signals","local content optimization","geographic entity signals","local semantic"],"runnable":true,"markdown":"\n## Core Principle: Local Rankings Are Entity Proximity Signals\n\nLocal pack rankings respond to semantic proximity between the business entity and location entities. A business that explicitly declares its relationship to a city through entity co-occurrence in content, schema, citations, and GMB signals will outrank a business with more links but weaker local entity signals.\n\nFrom Mike Merlino's $100K testing: **review sentiment signals outweigh entity optimization for local pack.** Entity optimization is the foundation; reviews are the differentiator.\n\n## The Three-Layer Local Semantic Stack\n\n**Layer 1: Business Entity Declaration**\n- The business entity (name + type) explicitly declared in H1, first paragraph, and schema\n- Entity type matches GMB category (not approximate — exact match)\n- sameAs links connecting business entity across 10+ platforms\n\n**Layer 2: Location Entity Embedding**\n- City name in: H1, first paragraph, at least 2 H2s, schema areaServed, GMB location name\n- Neighborhood/district names where relevant (not just city — hyper-local signals)\n- Local landmarks, streets, zip codes in content (creates geographic entity co-occurrence)\n- State abbreviation AND full state name (captures both search patterns)\n\n**Layer 3: Service + Location Semantic Proximity**\n- Service entities and location entities must appear in the same sentence or adjacent sentences\n- Not just \"we serve Tampa\" plus \"we do roofing\" on separate paragraphs\n- Required: \"roofing [service entity] in Tampa [location entity] including neighborhoods of Ybor City, Seminole Heights, and South Tampa [hyper-local entities]\"\n\n## Location Entity Enrichment Sources\n\nFor each city served, identify and embed these entities in location page content:\n\n| Entity Type | Examples |\n|-------------|---------|\n| Landmarks | \"near Busch Gardens\", \"serving the Riverwalk area\" |\n| Neighborhoods | \"Ybor City, Seminole Heights, Hyde Park\" |\n| Zip codes | Include 3-5 most common zip codes for the service area |\n| Local regulations | \"Florida Building Code Section X\", \"Hillsborough County permit requirements\" |\n| Local institutions | \"licensed with the City of Tampa\", \"Better Business Bureau of West Florida member\" |\n| Local events | \"after Hurricane Ian damage\" (temporal local signal) |\n\n## GMB Signal Alignment\n\nLocation page content must align with GMB signals for the same location:\n\n| GMB Signal | Location Page Match |\n|-----------|---------------------|\n| Business name | Exact match in H1 and first paragraph |\n| Primary category | Same entity type in page schema |\n| Service area | All listed cities mentioned in content |\n| Description keywords | Reflected in page meta description |\n| Photos | Location-specific photos referenced in alt text |\n\n## Review Sentiment Keyword Targets\n\nSince review sentiment outweighs entity optimization for local pack, target these sentiment patterns in review acquisition:\n\n- Service quality: \"excellent work\", \"professional team\", \"great quality\"\n- Location specificity: \"[city] roofing\", \"Tampa area\", \"local company\"\n- Outcome: \"fixed our roof\", \"replaced completely\", \"passed inspection\"\n- Trust: \"honest pricing\", \"no surprises\", \"showed up when promised\"\n\nRequest: ask customers to mention the service performed and the city. Provide a simple text prompt they can customize.\n\n## Local Semantic Content Checklist\n\nFor each location page, verify:\n- [ ] City name in H1 within first 5 words\n- [ ] City name in first paragraph within first 50 words\n- [ ] 3-5 neighborhood or district names in content body\n- [ ] Local zip codes mentioned at least once\n- [ ] Local regulation or permit authority named\n- [ ] Service entities and location entities co-occurring in the same sentences\n- [ ] GMB embed (if GMB exists for this location)\n- [ ] LocalBusiness schema with `geo` coordinates for the specific location\n- [ ] `areaServed` in schema listing all cities served from this location\n\n## Cross-References\n\n- `local-seo-silo-generator` — silo architecture that this content populates\n- `location-page-builder` — full location page production workflow\n- `daryl-local-seo` — schema cascade that amplifies local entity signals\n- `entity-seo` — entity declaration strategy underlying local optimization\n\n#seo-sop #seo #local-seo #semantic #geo #location-pages\n","html":"<h2>Core Principle: Local Rankings Are Entity Proximity Signals</h2>\n<p>Local pack rankings respond to semantic proximity between the business entity and location entities. A business that explicitly declares its relationship to a city through entity co-occurrence in content, schema, citations, and GMB signals will outrank a business with more links but weaker local entity signals.</p>\n<p>From Mike Merlino's $100K testing: <strong>review sentiment signals outweigh entity optimization for local pack.</strong> Entity optimization is the foundation; reviews are the differentiator.</p>\n<h2>The Three-Layer Local Semantic Stack</h2>\n<p><strong>Layer 1: Business Entity Declaration</strong></p>\n<ul>\n<li>The business entity (name + type) explicitly declared in H1, first paragraph, and schema</li>\n<li>Entity type matches GMB category (not approximate — exact match)</li>\n<li>sameAs links connecting business entity across 10+ platforms</li>\n</ul>\n<p><strong>Layer 2: Location Entity Embedding</strong></p>\n<ul>\n<li>City name in: H1, first paragraph, at least 2 H2s, schema areaServed, GMB location name</li>\n<li>Neighborhood/district names where relevant (not just city — hyper-local signals)</li>\n<li>Local landmarks, streets, zip codes in content (creates geographic entity co-occurrence)</li>\n<li>State abbreviation AND full state name (captures both search patterns)</li>\n</ul>\n<p><strong>Layer 3: Service + Location Semantic Proximity</strong></p>\n<ul>\n<li>Service entities and location entities must appear in the same sentence or adjacent sentences</li>\n<li>Not just \"we serve Tampa\" plus \"we do roofing\" on separate paragraphs</li>\n<li>Required: \"roofing [service entity] in Tampa [location entity] including neighborhoods of Ybor City, Seminole Heights, and South Tampa [hyper-local entities]\"</li>\n</ul>\n<h2>Location Entity Enrichment Sources</h2>\n<p>For each city served, identify and embed these entities in location page content:</p>\n<p>| Entity Type | Examples |\n|-------------|---------|\n| Landmarks | \"near Busch Gardens\", \"serving the Riverwalk area\" |\n| Neighborhoods | \"Ybor City, Seminole Heights, Hyde Park\" |\n| Zip codes | Include 3-5 most common zip codes for the service area |\n| Local regulations | \"Florida Building Code Section X\", \"Hillsborough County permit requirements\" |\n| Local institutions | \"licensed with the City of Tampa\", \"Better Business Bureau of West Florida member\" |\n| Local events | \"after Hurricane Ian damage\" (temporal local signal) |</p>\n<h2>GMB Signal Alignment</h2>\n<p>Location page content must align with GMB signals for the same location:</p>\n<p>| GMB Signal | Location Page Match |\n|-----------|---------------------|\n| Business name | Exact match in H1 and first paragraph |\n| Primary category | Same entity type in page schema |\n| Service area | All listed cities mentioned in content |\n| Description keywords | Reflected in page meta description |\n| Photos | Location-specific photos referenced in alt text |</p>\n<h2>Review Sentiment Keyword Targets</h2>\n<p>Since review sentiment outweighs entity optimization for local pack, target these sentiment patterns in review acquisition:</p>\n<ul>\n<li>Service quality: \"excellent work\", \"professional team\", \"great quality\"</li>\n<li>Location specificity: \"[city] roofing\", \"Tampa area\", \"local company\"</li>\n<li>Outcome: \"fixed our roof\", \"replaced completely\", \"passed inspection\"</li>\n<li>Trust: \"honest pricing\", \"no surprises\", \"showed up when promised\"</li>\n</ul>\n<p>Request: ask customers to mention the service performed and the city. Provide a simple text prompt they can customize.</p>\n<h2>Local Semantic Content Checklist</h2>\n<p>For each location page, verify:</p>\n<ul>\n<li>[ ] City name in H1 within first 5 words</li>\n<li>[ ] City name in first paragraph within first 50 words</li>\n<li>[ ] 3-5 neighborhood or district names in content body</li>\n<li>[ ] Local zip codes mentioned at least once</li>\n<li>[ ] Local regulation or permit authority named</li>\n<li>[ ] Service entities and location entities co-occurring in the same sentences</li>\n<li>[ ] GMB embed (if GMB exists for this location)</li>\n<li>[ ] LocalBusiness schema with <code>geo</code> coordinates for the specific location</li>\n<li>[ ] <code>areaServed</code> in schema listing all cities served from this location</li>\n</ul>\n<h2>Cross-References</h2>\n<ul>\n<li><code>local-seo-silo-generator</code> — silo architecture that this content populates</li>\n<li><code>location-page-builder</code> — full location page production workflow</li>\n<li><code>daryl-local-seo</code> — schema cascade that amplifies local entity signals</li>\n<li><code>entity-seo</code> — entity declaration strategy underlying local optimization</li>\n</ul>\n<p>#seo-sop #seo #local-seo #semantic #geo #location-pages</p>\n"}