Local SEO vs. technical/organic SEO — how the wiki’s two “SEOs” relate
Asked: 2026-07-01 | Confidence: high (synthesis of well-supported pages)
Answer
The wiki contains two distinct disciplines that both call themselves “SEO,” and conflating them causes bad advice. They target different search surfaces with different levers, but meet at a few real intersection points.
They’re different games
| Local SEO (Caleb Ulku corpus, James Dooley) | Technical / organic SEO (Pagepro, Smashing Magazine) | |
|---|---|---|
| Surface | The map pack / [[google-business-profile | GBP]], “near me”, local intent |
| You rank… | the GBP (the website corroborates it — GBP–Website Alignment (Consistency Signals)) | URLs/pages (crawlability, indexing) |
| Dominant levers | proximity, [[local-link-building | local trust]], reviews, [[core-30 |
| Content stance | ”don’t blog”; transactional service pages | pillar-cluster content + internal linking |
| Best for | local service businesses (HVAC, legal, plumbing) | B2B SaaS, content sites, publishers |
Where they genuinely intersect
- Schema Markup (Structured Data) — the clearest shared node: LocalBusiness JSON-LD (local lens) vs. Organization/FAQPage/Article JSON-LD (technical lens). Same tool, two vocabularies.
- Core Web Vitals — a ranking/UX signal for both, though local ranking is GBP-dominated so CWV matters less for the map pack than for competitive organic.
- Entity-Based SEO — both are entity-centric: local declares business↔service↔location entities; technical uses schema/structured data to declare Organization/Article entities. James Dooley’s Semantic Triples (Entity–Attribute–Value) sit here.
- Site architecture as ranking strategy — Core 30 (mirror the GBP) and the pillar-cluster model (Technical SEO from Architecture) are the same idea (information architecture = ranking lever) applied to different surfaces.
- AI search — local AEO and technical “AI Overviews steal 30–70% of clicks” are the same trend from two angles.
Where they’d give conflicting advice (and how to resolve)
- Blogging. Local says no (blogs don’t help the map pack); technical/content says yes (pillar-cluster content ranks organically). Resolution: pick by business model + intent. A plumber chasing “emergency plumber near me” gains nothing from blog posts; a SaaS chasing informational queries lives on them. Not a contradiction — different search intent.
- What the website is for. Local: the site exists to corroborate the GBP. Technical: the site is the product’s organic surface. Both true for their context.
Bottom line: These aren’t competing theories of one thing — they’re two toolkits for two surfaces. Choose the primary lens by business type and target surface, and apply the intersection items (Schema Markup (Structured Data), Core Web Vitals, clean architecture, entity clarity) regardless, because they help on every surface.
Caveats
- The local corpus is creator-heavy (mostly Caleb Ulku); the technical corpus is thin (one vendor guide + Smashing articles). Both lenses need more independent/official sources.
- Real businesses often need both (a local service brand with a content strategy) — the “pick one lens” framing is a simplification for clarity, not a mandate.
- Neither corpus deeply covers e-commerce SEO or large-scale international/organic SEO — those may not fit either lens cleanly.
Next Steps
- Ingest an official Google source (Search Central) to arbitrate the blogging/duplicate/CWV-weight questions independent of creators/vendors.
- Add a hybrid case source (a local business that also runs organic content) to test how the two toolkits combine in practice.
- Expand the web-dev/technical pillar beyond one vendor guide to grade its framework-specific claims.