From 967ba9a3b0a53876b9c3b3d2b548e40328fc1e51 Mon Sep 17 00:00:00 2001 From: grokbot_ty Date: Thu, 1 Oct 2026 10:48:11 -0700 Subject: [PATCH] =?UTF-8?q?Hyperlink=20all=201=E2=80=9314=20platforms=20to?= =?UTF-8?q?=20canonical=20pages=20in=20concept=20SoT.?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Also keep one-to-many fan-out findings (Localeze/Data Axle caveats, Yext-class 200+ pipes, no free public fan-out API, one-click = ticket set). --- docs/SELF_SERVE_AI_DISCOVERABILITY_CONCEPT.md | 82 ++++++++++--------- 1 file changed, 42 insertions(+), 40 deletions(-) diff --git a/docs/SELF_SERVE_AI_DISCOVERABILITY_CONCEPT.md b/docs/SELF_SERVE_AI_DISCOVERABILITY_CONCEPT.md index 91713d8..68f41e8 100644 --- a/docs/SELF_SERVE_AI_DISCOVERABILITY_CONCEPT.md +++ b/docs/SELF_SERVE_AI_DISCOVERABILITY_CONCEPT.md @@ -30,13 +30,13 @@ A local business is not a single record on the internet. It is a **cloud of copi Over years, real life moves. You change suite numbers. The town renumbers a road. The phone company swaps an area code. You get a new mobile for the shop. You update the website. Each of those changes is ordinary. What is not ordinary is what happens next. -Every major place that stores local businesses keeps **its own copy** of your name, address, and phone — the boring facts people call **NAP** (name, address, phone). Google Business Profile has a copy. Apple has a copy. Bing has a copy. Yelp has a copy. Foursquare’s place graph has a copy. Underneath many of them, **data aggregators and syndicators** (companies such as Data Axle and Localeze / TransUnion) hold yet another copy and push it out to directories, maps, navigation apps, and anything that buys “local listings” feeds. +Every major place that stores local businesses keeps **its own copy** of your name, address, and phone — the boring facts people call **NAP** (name, address, phone). [Google Business Profile](https://business.google.com) has a copy. [Apple](https://business.apple.com) has a copy. [Bing](https://www.bingplaces.com) has a copy. [Yelp](https://www.yelp.com) has a copy. [Foursquare](https://foursquare.com)’s place graph has a copy. Underneath many of them, **data aggregators and syndicators** (companies such as [Data Axle](https://www.data-axle.com/marketing-solutions/local-listings-management/) and [Localeze / TransUnion](https://neustarlocaleze.biz/)) hold yet another copy and push it out to directories, maps, navigation apps, and anything that buys “local listings” feeds. Nobody is paid to keep all of those copies honest with each other. So the copies **drift**. One still has the old area code. One still has the storefront you left three years ago. One has the right street but the wrong suite. Search engines and AI assistants do not magically know which copy is you today. They see a black box of conflicting facts and pick whatever their ranking and training happen to trust that week. -When an owner finally **claims** Google Business Profile and fixes it, that is powerful — GBP is usually the strongest **claim surface** an owner can touch. But it is not the only voice. Syndicated feeds can still broadcast the old NAP. Those stale copies can show up in search results and in AI answers **alongside or even above** the listing the owner just cleaned up. From the owner’s chair it feels like: “I fixed it — why does the world still lie about me?” +When an owner finally **claims** [Google Business Profile](https://business.google.com) and fixes it, that is powerful — GBP is usually the strongest **claim surface** an owner can touch. But it is not the only voice. Syndicated feeds can still broadcast the old NAP. Those stale copies can show up in search results and in AI answers **alongside or even above** the listing the owner just cleaned up. From the owner’s chair it feels like: “I fixed it — why does the world still lie about me?” That is the problem in one line: **the owner cannot control what the world believes about their business**, because the world is not one database. It is a black box of unreconciled copies. @@ -59,11 +59,11 @@ Think of it as three frames: (the black box) (source of truth) (reconciled world) ``` -**Frame one — left.** The black box: several disagreeing copies (Google, Apple, Bing, Yelp, Foursquare, and whatever else still carries an old feed). The owner did not ask for five versions of themselves. The market produced them. +**Frame one — left.** The black box: several disagreeing copies ([Google](https://business.google.com), [Apple](https://business.apple.com), [Bing](https://www.bingplaces.com), [Yelp](https://www.yelp.com), [Foursquare](https://foursquare.com), and whatever else still carries an old feed). The owner did not ask for five versions of themselves. The market produced them. **Frame two — middle.** The claim: one clean NAP the owner stands behind. That is the only version we treat as authoritative for *this* business. Fixing GBP still matters — it is often the best place to start the claim — but the point is the **declared truth**, not loyalty to any one logo. -**Frame three — right.** Corrections flowing out. The system’s job is to make the other copies **match the claim**, including the ugly middle layer most owners never see: **syndication**. Aggregators and platforms that feed directories and assistants — Yelp, Bing, Foursquare, and the rest — routinely **stomp on** a small business’s source of truth with stale hours, old phone numbers, and leftover addresses. If you only polish the claim surface and ignore those copies, the black box regenerates overnight. +**Frame three — right.** Corrections flowing out. The system’s job is to make the other copies **match the claim**, including the ugly middle layer most owners never see: **syndication**. Aggregators and platforms that feed directories and assistants — [Yelp](https://www.yelp.com), [Bing](https://www.bingplaces.com), [Foursquare](https://foursquare.com), and the rest — routinely **stomp on** a small business’s source of truth with stale hours, old phone numbers, and leftover addresses. If you only polish the claim surface and ignore those copies, the black box regenerates overnight. Matching NAP is the floor — **presence** with consistent facts. **Recommendability** (would an assistant pick you for a real customer question in your genre) still needs categories, relevance, and the rest of this product story. Opening the black box is how we stop the floor from moving under the owner’s feet. @@ -75,15 +75,15 @@ The direction above is the bet. Below is the **solution we still have to design #### 1. Every audit finding becomes a correction ticket -Today an owner who sees wrong hours on Yelp, a dead phone on Bing, and an old suite on Foursquare has to decode three different “suggest an edit” paths. That is the chore we remove. +Today an owner who sees wrong hours on [Yelp](https://www.yelp.com), a dead phone on [Bing](https://www.bingplaces.com), and an old suite on [Foursquare](https://foursquare.com) has to decode three different “suggest an edit” paths. That is the chore we remove. -For each platform that still shows stale or wrong data, the product turns the audit finding into a **correction ticket** with the same shape every time: which field is wrong, what value is showing, what the right value is, and a link to **Google Business Profile** (or the owner’s claimed truth) as proof. Then the owner files that platform’s own correction channel — Yelp’s suggest-an-edit page, Foursquare’s suggest-edit API (`POST /places/{id}/suggest/edit`), Bing Places feedback, and the same pattern for others as we map them. Claim it is wrong. Show proof. Wait. +For each platform that still shows stale or wrong data, the product turns the audit finding into a **correction ticket** with the same shape every time: which field is wrong, what value is showing, what the right value is, and a link to **[Google Business Profile](https://business.google.com)** (or the owner’s claimed truth) as proof. Then the owner files that platform’s own correction channel — [Yelp](https://www.yelp.com)’s suggest-an-edit page, [Foursquare](https://foursquare.com)’s suggest-edit API (`POST /places/{id}/suggest/edit`), [Bing Places](https://www.bingplaces.com) feedback, and the same pattern for others as we map them. Claim it is wrong. Show proof. Wait. Our side of the architecture: **mint that ticket automatically from the audit** — pre-filled, one click to file — instead of making the owner hunt which form goes where. The platforms still own their review queues. We own the translation from “your Presence score is broken here” into “here is the exact correction this platform will accept.” #### 2. Held verification across platforms is the moat -Business verification is the tax. Every platform re-verifies **independently**. Yelp wants its documents. Bing wants its own proof of ownership. Foursquare has its own checks. There is **no shared credential** and no way to say “I already proved this to Google.” Each review takes **days to weeks**, and without standing as a verified actor, corrections get slow-walked or quietly reverted when the next stale feed arrives. +Business verification is the tax. Every platform re-verifies **independently**. [Yelp](https://www.yelp.com) wants its documents. [Bing](https://www.bingplaces.com) wants its own proof of ownership. [Foursquare](https://foursquare.com) has its own checks. There is **no shared credential** and no way to say “I already proved this to Google.” Each review takes **days to weeks**, and without standing as a verified actor, corrections get slow-walked or quietly reverted when the next stale feed arrives. A white-label correction service that **holds verified status per platform** — and files on the owner’s behalf without re-uploading a lease five times — is what makes corrections **stick**. That held, multi-platform verified status is the **moat**: the audit finds the drift; the ticket files the fix; the held verification is why the fix does not get stomped again tomorrow. @@ -91,63 +91,65 @@ A white-label correction service that **holds verified status per platform** — Umbrella aggregators and end-user platforms are **not** the same job. Architecture needs **two lanes**: -- **Lane A — umbrella submissions.** Write once into [Data Axle](https://www.data-axle.com/marketing-solutions/local-listings-management/), [Localeze / TransUnion](https://neustarlocaleze.biz/), and [Foursquare](https://docs.foursquare.com/data-products/docs/how-does-places-work)’s place graph so long-tail directories, libraries, and many nav / GPS consumers stop regenerating stale NAP. -- **Lane B — per-platform tickets.** Claim or suggest-edit on Google, Apple, Bing, Yelp, and other surfaces that keep their **own** databases and often prefer verified owner data over a feed. +- **Lane A — umbrella submissions.** Write once into [Data Axle](https://www.data-axle.com/marketing-solutions/local-listings-management/), [Localeze / TransUnion](https://neustarlocaleze.biz/), and [Foursquare](https://foursquare.com)’s place graph so long-tail directories, libraries, and many nav / GPS consumers stop regenerating stale NAP. +- **Lane B — per-platform tickets.** Claim or suggest-edit on [Google](https://business.google.com), [Apple](https://business.apple.com), [Bing](https://www.bingplaces.com), [Yelp](https://www.yelp.com), and other surfaces that keep their **own** databases and often prefer verified owner data over a feed. -Umbrella-only leaves the Core 3 and Yelp wrong. Platform-only leaves the black box regenerating from Layer 1 feeds. Both lanes mint the same ticket shape (field, wrong value, right value, GBP or claimed truth as proof). Rank below is **most → least important** for small-business local discoverability and for how hard a miss should hit the Presence / audit score. Each item is an **owner-facing workflow we still have to architect** — not a label and not a shipped feature. +Umbrella-only leaves the Core 3 and [Yelp](https://www.yelp.com) wrong. Platform-only leaves the black box regenerating from Layer 1 feeds. Both lanes mint the same ticket shape (field, wrong value, right value, GBP or claimed truth as proof). Rank below is **most → least important** for small-business local discoverability and for how hard a miss should hit the Presence / audit score. Each item is an **owner-facing workflow we still have to architect** — not a label and not a shipped feature. -1. **Google Business Profile** (Lane B — claim hub / Core 3). Sign in to the GBP dashboard for that location. Open the wrong field (hours, phone, address, category). Enter the correct value and save. Attach documents only when Google asks — typically for large moves, ownership disputes, or category jumps, not for a routine hours tweak. Wait for the listing to refresh (often minutes to a day). **Success:** Maps / Search show the new value, and that GBP URL becomes the proof link on every other ticket. +1. **[Google Business Profile](https://business.google.com)** (Lane B — claim hub / Core 3). Sign in to the GBP dashboard for that location. Open the wrong field (hours, phone, address, category). Enter the correct value and save. Attach documents only when Google asks — typically for large moves, ownership disputes, or category jumps, not for a routine hours tweak. Wait for the listing to refresh (often minutes to a day). **Success:** Maps / Search show the new value, and that GBP URL becomes the proof link on every other ticket. -2. **Apple Business Connect** (Lane B — Core 3). Sign in to Apple Business Connect, find the place card, edit the field, submit. Apple may review and email if more proof is needed. Wait for the place card to update across Maps and related Apple surfaces. **Success:** Apple Maps shows the corrected hours / NAP matching the claim. +2. **[Apple Business Connect](https://business.apple.com)** (Lane B — Core 3). Sign in to [Apple Business Connect](https://business.apple.com), find the place card, edit the field, submit. Apple may review and email if more proof is needed. Wait for the place card to update across Maps and related Apple surfaces. **Success:** Apple Maps shows the corrected hours / NAP matching the claim. -3. **Bing Places** (Lane B — Core 3). Sign in at the Bing Places portal, open the listing, edit the field. Attach proof that matches GBP — utility bill or lease with the same business name and address when Bing asks for ownership evidence. Submit and wait for Bing’s review queue (often days). **Success:** Bing local (and Copilot-adjacent local answers that lean on Places) show the corrected value. +3. **[Bing Places](https://www.bingplaces.com)** (Lane B — Core 3). Sign in at the [Bing Places](https://www.bingplaces.com) portal, open the listing, edit the field. Attach proof that matches GBP — utility bill or lease with the same business name and address when Bing asks for ownership evidence. Submit and wait for Bing’s review queue (often days). **Success:** Bing local (and Copilot-adjacent local answers that lean on Places) show the corrected value. -4. **[Foursquare Places](https://foursquare.com/resources/blog/developer/digitizing-real-world-pois-with-foursquare-places/)** (Lane A + B). Two paths, same outcome: (a) Placemaker suggest-edit — pick the place, choose the field, enter wrong vs right, submit; or (b) our white-label one-click that calls `POST /places/{id}/suggest/edit` pre-filled, with the GBP URL as the cited source. Wait for Placemaker / Foursquare resolution (status via suggest-status). **Success:** the FSQ place record shows the new value (and downstream licensees that refresh from FSQ can follow). +4. **[Foursquare Places](https://foursquare.com)** (Lane A + B). Two paths, same outcome: (a) Placemaker suggest-edit — pick the place, choose the field, enter wrong vs right, submit; or (b) our white-label one-click that calls `POST /places/{id}/suggest/edit` pre-filled, with the GBP URL as the cited source. Wait for Placemaker / [Foursquare](https://foursquare.com) resolution (status via suggest-status). **Success:** the FSQ place record shows the new value (and downstream licensees that refresh from FSQ can follow). -5. **Yelp** (Lane B). Open the business page → **Suggest an edit**. Pick the field, type the correction, add a short note citing the GBP listing as proof, submit. Yelp reviews manually. Wait days to weeks. **Success:** the Yelp page shows the corrected field and stops contradicting the claim. +5. **[Yelp](https://www.yelp.com)** (Lane B). Open the business page → **Suggest an edit**. Pick the field, type the correction, add a short note citing the GBP listing as proof, submit. [Yelp](https://www.yelp.com) reviews manually. Wait days to weeks. **Success:** the [Yelp](https://www.yelp.com) page shows the corrected field and stops contradicting the claim. -6. **[Data Axle](https://www.data-axle.com/marketing-solutions/local-listings-management/) Local Listings** (Lane A). Claim the business at the [Data Axle Local Listings](https://www.data-axle.com/marketing-solutions/local-listings-management/) portal with a business email and / or ownership docs. Edit NAP (and hours) once in that central record. Wait for [Data Axle](https://www.data-axle.com/marketing-solutions/local-listings-management/)’s verification and syndication batch (scale / API path: [Local Listings Premium docs](https://local-listings-premium.data-axle.com/docs)) — hours to ~two weeks for hard cases. **Success:** the Local Listings record matches the claim; long-tail / nav partners that consume Data Axle begin reflecting the update on their next pull. +6. **[Data Axle](https://www.data-axle.com/marketing-solutions/local-listings-management/) Local Listings** (Lane A). Claim the business at the [Data Axle Local Listings](https://www.data-axle.com/marketing-solutions/local-listings-management/) portal with a business email and / or ownership docs. Edit NAP (and hours) once in that central record. Wait for [Data Axle](https://www.data-axle.com/marketing-solutions/local-listings-management/)’s verification and syndication batch (scale / API path: [Local Listings Premium docs](https://local-listings-premium.data-axle.com/docs)) — hours to ~two weeks for hard cases. **Success:** the Local Listings record matches the claim; long-tail / nav partners that consume [Data Axle](https://www.data-axle.com/marketing-solutions/local-listings-management/) begin reflecting the update on their next pull. 7. **[Localeze / TransUnion](https://neustarlocaleze.biz/) Digital Business Profile** (Lane A). Claim at the [TransUnion / Localeze](https://neustarlocaleze.biz/) portal, correct NAP once, complete their verification. Wait for push out to their 80–100+ publisher network (often weeks for some partners). **Success:** the claimed profile matches GBP; sample downstream publishers no longer show the stale twin. -8. **YP / Thryv** (Lane B, feeds long-tail). Claim via YP / Thryv listing management, edit the wrong field, save. Wait for their network to refresh. **Success:** the YP listing matches the claim; long-tail sites fed by that stack stop showing the old value when they next sync. +8. **[YP / Thryv](https://www.yellowpages.com)** (Lane B, feeds long-tail). Claim via [YP / Thryv](https://www.yellowpages.com) listing management, edit the wrong field, save. Wait for their network to refresh. **Success:** the YP listing matches the claim; long-tail sites fed by that stack stop showing the old value when they next sync. -9. **Tripadvisor** (Lane B — vertical). Claim via Tripadvisor for Business, open the field, submit the correction for review. Wait for their moderation. **Success:** the Tripadvisor listing matches the claim when travel / food recommendability cares about that surface. +9. **[Tripadvisor](https://www.tripadvisor.com)** (Lane B — vertical). Claim via [Tripadvisor](https://www.tripadvisor.com) for Business, open the field, submit the correction for review. Wait for their moderation. **Success:** the [Tripadvisor](https://www.tripadvisor.com) listing matches the claim when travel / food recommendability cares about that surface. -10. **Facebook / Meta** (Lane B — low weight). In Meta Business Suite, open the Page → contact / location info, edit hours or phone, publish. Usually no separate proof upload for small edits. **Success:** the Page info card matches GBP; treat as secondary Presence, not Core 3. +10. **[Facebook / Meta](https://www.facebook.com/business)** (Lane B — low weight). In [Meta Business Suite](https://www.facebook.com/business), open the Page → contact / location info, edit hours or phone, publish. Usually no separate proof upload for small edits. **Success:** the Page info card matches GBP; treat as secondary Presence, not Core 3. -11. **MapQuest / HERE / in-car nav / long-tail directories** (Lane A by default). There is usually **no** owner correction form. Path: file umbrella tickets ([Data Axle](https://www.data-axle.com/marketing-solutions/local-listings-management/), [Localeze](https://neustarlocaleze.biz/), [Foursquare](https://docs.foursquare.com/data-products/docs/how-does-places-work)) and **monitor** those surfaces after syndication settles. Open a direct ticket only if a real claim URL exists and the miss survives umbrella propagation. **Success:** re-audit shows the nav / directory copy matches the claim without chasing each site by hand. +11. **[MapQuest](https://www.mapquest.com) / HERE / in-car nav / long-tail directories** (Lane A by default). There is usually **no** owner correction form. Path: file umbrella tickets ([Data Axle](https://www.data-axle.com/marketing-solutions/local-listings-management/), [Localeze](https://neustarlocaleze.biz/), [Foursquare](https://foursquare.com)) and **monitor** those surfaces after syndication settles. Open a direct ticket only if a real claim URL exists and the miss survives umbrella propagation. **Success:** re-audit shows the nav / directory copy matches the claim without chasing each site by hand. -12. **Dun & Bradstreet** — Low priority for consumer local. Skip unless a B2B path is in scope; if needed, update through D&B’s business profile tools with legal-entity proof. **Success:** firmographic record matches when that lane matters. +12. **[Dun & Bradstreet](https://www.dnb.com)** — Low priority for consumer local. Skip unless a B2B path is in scope; if needed, update through D&B’s business profile tools with legal-entity proof. **Success:** firmographic record matches when that lane matters. -13. **CityGrid** — Legacy. Only if the audit surfaces a CityGrid-fed copy still stomping the claim; then follow whatever claim / correction URL still exists, else rely on overlapping umbrellas. **Success:** that copy disappears or matches. +13. **[CityGrid](https://www.citygrid.com)** — Legacy. Only if the audit surfaces a [CityGrid](https://www.citygrid.com)-fed copy still stomping the claim; then follow whatever claim / correction URL still exists, else rely on overlapping umbrellas. **Success:** that copy disappears or matches. -14. **Yext / Uberall / BrightLocal (pipes)** — Not destinations. If the owner already pays one, route the same tickets **through that pipe** into Lanes A and B instead of a parallel write. **Success:** the pipe’s dashboard shows the jobs filed and publishers reporting the new value — we still score Presence on the publishers, not on the pipe brand. +14. **[Yext](https://www.yext.com) / [Uberall](https://www.uberall.com) / [BrightLocal](https://www.brightlocal.com) (pipes)** — Not destinations. If the owner already pays one, route the same tickets **through that pipe** into Lanes A and B instead of a parallel write. **Success:** the pipe’s dashboard shows the jobs filed and publishers reporting the new value — we still score Presence on the publishers, not on the pipe brand. #### Day in the life (workflow to architect) -A muffin shop’s Tuesday hours are wrong on the public web. The owner runs our audit, sees three red rows (GBP already correct, Foursquare stale, Data Axle still syndicating the old Tuesday close), and hits **one** “fix these” button. +A muffin shop’s Tuesday hours are wrong on the public web. The owner runs our audit, sees three red rows (GBP already correct, [Foursquare](https://foursquare.com) stale, [Data Axle](https://www.data-axle.com/marketing-solutions/local-listings-management/) still syndicating the old Tuesday close), and hits **one** “fix these” button. Three pre-filled things fire — not three scavenger hunts: 1. **GBP** — if anything still drifts there, a deep link into the hours editor with Tuesday pre-filled to the claimed value; otherwise we skip and reuse the live GBP URL as proof. -2. **[Foursquare](https://foursquare.com/resources/blog/developer/digitizing-real-world-pois-with-foursquare-places/)** — a one-click Placemaker suggest-edit (`POST /places/{id}/suggest/edit`) with field = hours, wrong = old Tuesday, right = claimed Tuesday, source = GBP URL (white-label Managed User when we file for them). +2. **[Foursquare](https://foursquare.com)** — a one-click Placemaker suggest-edit (`POST /places/{id}/suggest/edit`) with field = hours, wrong = old Tuesday, right = claimed Tuesday, source = GBP URL (white-label Managed User when we file for them). 3. **[Data Axle](https://www.data-axle.com/marketing-solutions/local-listings-management/)** — a Lane A claim / update ticket at Local Listings with the same NAP + hours payload so the umbrella stops stomping the claim on the next syndication cycle. -The owner attaches proof once where a portal demands it, then waits on each queue. Re-audit later is the success check: Tuesday matches everywhere that mattered. That is the workflow to architect — audit → tickets → wait → prove — not a pile of unlabeled “go fix Yelp” links. +The owner attaches proof once where a portal demands it, then waits on each queue. Re-audit later is the success check: Tuesday matches everywhere that mattered. That is the workflow to architect — audit → tickets → wait → prove — not a pile of unlabeled “go fix [Yelp](https://www.yelp.com)” links. #### 4. One-to-many fan-out — useful lane, not the whole backbone True one-to-many correction **exists**, but nothing is reliable enough to be the **only** spine of a one-click product. Research takeaways to architect around: -**[Localeze / TransUnion](https://neustarlocaleze.biz/)** markets claim-once → **80–100+** publishers. In practice publishers decide *what* and *when* to show: many partners sit on a **monthly publish** cycle (**~30–90 days**); sync partners can be faster; Localeze does **not** control partner acceptance. Fast Google updates via Localeze require a **separate Google verify/sync** inside their product — not the feed alone. Some partners need extra OAuth (e.g. link Facebook). Distribution status reporting exists because fan-out is partial, not guaranteed. +**[Localeze / TransUnion](https://neustarlocaleze.biz/)** markets claim-once → **80–100+** publishers. In practice publishers decide *what* and *when* to show: many partners sit on a **monthly publish** cycle (**~30–90 days**); sync partners can be faster; [Localeze](https://neustarlocaleze.biz/) does **not** control partner acceptance. Fast Google updates via [Localeze](https://neustarlocaleze.biz/) require a **separate Google verify/sync** inside their product — not the feed alone. Some partners need extra OAuth (e.g. link [Facebook](https://www.facebook.com/business)). Distribution status reporting exists because fan-out is partial, not guaranteed. -**[Data Axle](https://www.data-axle.com/marketing-solutions/local-listings-management/)** Local Listings / [Local Listings Premium](https://local-listings-premium.data-axle.com/docs) is the same *shape*: one verified submit → search, directories, libraries, nav, assistants. Processing can be hours to ~two weeks when human verification kicks in. Publisher lists **overlap** Localeze on many big names but are **not identical** (citation vendors still sell both). Treat them as complementary Lane A tickets, not duplicates. +**[Data Axle](https://www.data-axle.com/marketing-solutions/local-listings-management/)** Local Listings / [Local Listings Premium](https://local-listings-premium.data-axle.com/docs) is the same *shape*: one verified submit → search, directories, libraries, nav, assistants. Processing can be hours to ~two weeks when human verification kicks in. Publisher lists **overlap** [Localeze](https://neustarlocaleze.biz/) on many big names but are **not identical** (citation vendors still sell both). Treat them as complementary Lane A tickets, not duplicates. -**Other fan-out:** Paid listing managers ([Yext](https://www.yext.com/platform/listings)-class — often 200+ *direct* publisher APIs with per-publisher status) are the strongest productized one-edit→many-majors path — route through them when the owner already pays (rank 14). **Google Business Profile does not syndicate NAP outbound** to Apple/Yelp/Bing. **Apple Business Connect** writes the Apple ecosystem (and partner APIs *into* Apple), not rival platforms. [Foursquare Places](https://docs.foursquare.com/data-products/docs/how-does-places-work) suggest-edit updates FSQ’s graph (and later licensees), not a general directory blast. +**Other fan-out:** Paid listing managers ([Yext](https://www.yext.com)-class — often 200+ *direct* publisher APIs with per-publisher status) are the strongest productized one-edit→many-majors path — route through them when the owner already pays (rank 14). **[Google Business Profile](https://business.google.com) does not syndicate NAP outbound** to Apple/[Yelp](https://www.yelp.com)/Bing. **[Apple Business Connect](https://business.apple.com)** writes the Apple ecosystem (and partner APIs *into* Apple), not rival platforms. [Foursquare Places](https://foursquare.com) suggest-edit updates FSQ’s graph (and later licensees), not a general directory blast. -**Ceiling:** One Localeze (or Data Axle) correction may move a **fraction** of consumer-visible surfaces in week one and more over 1–3 months; Core 3 claim surfaces often stay wrong without Lane B. So one-click means **one button that mints a ticket set** (GBP proof + Lane A umbrellas + Lane B majors) — not one submission that rewrites the internet. +There is **no free public one-to-many fan-out API** an SMB can call to rewrite every major surface at once; [Localeze](https://neustarlocaleze.biz/) and [Data Axle](https://www.data-axle.com/marketing-solutions/local-listings-management/) are sales- or portal-gated claim/submit products, and [Yext](https://www.yext.com)-class pipes are paid. + +**Ceiling:** One [Localeze](https://neustarlocaleze.biz/) (or [Data Axle](https://www.data-axle.com/marketing-solutions/local-listings-management/)) correction may move a **fraction** of consumer-visible surfaces in week one and more over 1–3 months; Core 3 claim surfaces often stay wrong without Lane B. So one-click means **one button that mints a ticket set** (GBP proof + Lane A umbrellas + Lane B majors) — not one submission that rewrites the internet. Longer term, the Northstar — the destination we aim at but do not build first — is an **industry graph**: a shared, structured map of local businesses that many products and assistants could use. That is not version one. Version one earns the right to that graph by helping owners see how AI sees them today and fix what is broken, with their consent. @@ -187,23 +189,23 @@ So for version one, the highest priority is an **interactive web app** the owner A **taxonomy** here means the set of categories used to say what kind of business something is — plumber versus restaurant versus hotel — so listings, maps, and assistants know what queries it belongs to. -There is no single industry-wide taxonomy that Apple, Google, Bing, Yelp, and the listing aggregators all use. Each keeps its own list (or feeds someone else’s). +There is no single industry-wide taxonomy that [Apple](https://business.apple.com), [Google](https://business.google.com), [Bing](https://www.bingplaces.com), [Yelp](https://www.yelp.com), and the listing aggregators all use. Each keeps its own list (or feeds someone else’s). **NAICS** (North American Industry Classification System) is the U.S. government’s statistical system for classifying businesses by what they produce. It is good for reports and some B2B software. It is not how someone searches “plumber near me” on a map. **SIC** is the older system NAICS replaced for federal stats. -**Google Business Profile** has its own category IDs (often looking like `gcid:…`), available through Google’s Business Information API (`categories.list`, region US / language en). That official list is a **flat catalog of roughly 4,050 leaves** — not a hierarchy that matches our genre parents. Google does not publish a downloadable tree that says “these GCIDs belong under service-area trades.” A public September 2026 compilation of **4,053** US English GCID names (with third-party industry buckets used only for structure) is useful for research; those buckets are **not** Google’s official parents. We use GBP GCIDs as **outbound presence-check maps** and fix suggestions, not as our spine. In practice GBP is usually the **richest** owner-facing surface (categories, services, attributes, photos). +**[Google Business Profile](https://business.google.com)** has its own category IDs (often looking like `gcid:…`), available through Google’s Business Information API (`categories.list`, region US / language en). That official list is a **flat catalog of roughly 4,050 leaves** — not a hierarchy that matches our genre parents. Google does not publish a downloadable tree that says “these GCIDs belong under service-area trades.” A public September 2026 compilation of **4,053** US English GCID names (with third-party industry buckets used only for structure) is useful for research; those buckets are **not** Google’s official parents. We use GBP GCIDs as **outbound presence-check maps** and fix suggestions, not as our spine. In practice GBP is usually the **richest** owner-facing surface (categories, services, attributes, photos). -**Apple Maps / Business Connect** has its own primary category (one main label) plus optional extras; the public docs have been shifting as Apple folds Connect into a broader “Apple Business” offering. Owner-facing field labels are documented; partner API schemas are often gated. Mid richness versus GBP — good for place card truth, weaker 1:1 parity on things like GBP `serviceItems`. +**[Apple Maps / Business Connect](https://business.apple.com)** has its own primary category (one main label) plus optional extras; the public docs have been shifting as Apple folds Connect into a broader “Apple Business” offering. Owner-facing field labels are documented; partner API schemas are often gated. Mid richness versus GBP — good for place card truth, weaker 1:1 parity on things like GBP `serviceItems`. -**Bing Places for Business** is Microsoft’s local listing surface (feeds Bing / Microsoft local experiences). Categories use Bing’s own IDs (`BPCategoryId` + name); owners can attach multiple categories with one primary. The trusted-partner API is certificate-gated, not a public crawl API — field maps on this branch already treat Bing as the **thinnest** of a “Core 3” with GBP and Apple (`docs/product/genre-packs/`). Bing still matters for Presence: wrong or missing Bing categories are a real “are you on the map?” miss, especially where Copilot / Microsoft surfaces lean on Bing Places data. Do not pretend Bing’s category tree equals Google’s. +**[Bing Places for Business](https://www.bingplaces.com)** is Microsoft’s local listing surface (feeds Bing / Microsoft local experiences). Categories use Bing’s own IDs (`BPCategoryId` + name); owners can attach multiple categories with one primary. The trusted-partner API is certificate-gated, not a public crawl API — field maps on this branch already treat Bing as the **thinnest** of a “Core 3” with GBP and Apple (`docs/product/genre-packs/`). Bing still matters for Presence: wrong or missing Bing categories are a real “are you on the map?” miss, especially where Copilot / Microsoft surfaces lean on [Bing Places](https://www.bingplaces.com) data. Do not pretend Bing’s category tree equals Google’s. -**Yelp** keeps its own hierarchy of category **aliases** (developer APIs expose the tree). Yelp is both a discovery surface consumers still use and a signal assistants and third parties often scrape or cite. Alias mismatch (e.g. cuisine or trade labels that do not line up with GBP) is a classic consistency failure. Yelp is not a map pin in the same way as GBP/Apple/Bing, but it belongs in outbound maps when we score “would an AI trust this entity’s type?” +**[Yelp](https://www.yelp.com)** keeps its own hierarchy of category **aliases** (developer APIs expose the tree). [Yelp](https://www.yelp.com) is both a discovery surface consumers still use and a signal assistants and third parties often scrape or cite. Alias mismatch (e.g. cuisine or trade labels that do not line up with GBP) is a classic consistency failure. [Yelp](https://www.yelp.com) is not a map pin in the same way as GBP/Apple/Bing, but it belongs in outbound maps when we score “would an AI trust this entity’s type?” -**Data aggregators / syndicators** sit underneath many of those surfaces. Companies such as **Data Axle** (local listings / formerly Infogroup-class syndication), **Localeze / TransUnion** digital business profiles, **Foursquare** Places (place graph / POI metadata), and similar players push NAP and rich fields out to search engines, directories, navigation apps, and assistants. Owners often never touch them directly — a “listing management” vendor or the platform itself does. For our product that means: Presence is not only “did you claim GBP?” It can also be “does the aggregator-fed copy of you disagree with the claim you just made?” Aggregators are **not** a ninth genre parent; they are a **distribution layer for facts**. Which aggregators we check in v1 (if any) is still open — but ignoring them entirely would understate how local data actually spreads. +**Data aggregators / syndicators** sit underneath many of those surfaces. Companies such as **[Data Axle](https://www.data-axle.com/marketing-solutions/local-listings-management/)** (local listings / formerly Infogroup-class syndication), **[Localeze / TransUnion](https://neustarlocaleze.biz/)** digital business profiles, **[Foursquare](https://foursquare.com)** Places (place graph / POI metadata), and similar players push NAP and rich fields out to search engines, directories, navigation apps, and assistants. Owners often never touch them directly — a “listing management” vendor or the platform itself does. For our product that means: Presence is not only “did you claim GBP?” It can also be “does the aggregator-fed copy of you disagree with the claim you just made?” Aggregators are **not** a ninth genre parent; they are a **distribution layer for facts**. Which aggregators we check in v1 (if any) is still open — but ignoring them entirely would understate how local data actually spreads. -**schema.org’s LocalBusiness** types are an open vocabulary used widely on the web for structured data (the markup that helps search engines understand a page). That is the best spine for an AI-era product that also wants to publish clear web facts: owner-friendly genres inside our product, keyed to schema.org where they fit, optional NAICS when a statistical code helps, and **outbound maps** — translation tables — from our genres to Google, Apple, Bing, Yelp, and (where useful) aggregator category codes when we check presence or suggest fixes. +**schema.org’s LocalBusiness** types are an open vocabulary used widely on the web for structured data (the markup that helps search engines understand a page). That is the best spine for an AI-era product that also wants to publish clear web facts: owner-friendly genres inside our product, keyed to schema.org where they fit, optional NAICS when a statistical code helps, and **outbound maps** — translation tables — from our genres to [Google](https://business.google.com), [Apple](https://business.apple.com), [Bing](https://www.bingplaces.com), [Yelp](https://www.yelp.com), and (where useful) aggregator category codes when we check presence or suggest fixes. -We should not treat any single platform or aggregator list as our internal source of truth. They drift and they disagree. Building those maps ourselves is normal; nobody publishes an official multi-way concordance. On this branch, genre-pack work already sketches a **Core 3** field map (GBP richest → Apple mid → Bing thinnest); extend that pattern to Yelp aliases and aggregator feeds only where Presence scoring needs them. +We should not treat any single platform or aggregator list as our internal source of truth. They drift and they disagree. Building those maps ourselves is normal; nobody publishes an official multi-way concordance. On this branch, genre-pack work already sketches a **Core 3** field map (GBP richest → Apple mid → Bing thinnest); extend that pattern to [Yelp](https://www.yelp.com) aliases and aggregator feeds only where Presence scoring needs them. This taxonomy approach is a **hypothesis** until we score real businesses and see where the maps break. @@ -277,12 +279,12 @@ This doc’s product flow already assumes many owners **start themselves** (incl ## Decisions still open -Ty still needs to lock: which cluster pack we ship first; whether version one is web-only or also embeds in a chatbot; which providers feed the Presence score (Core 3 GBP/Apple/Bing, plus Yelp and/or aggregators such as Data Axle / Localeze / Foursquare — or claim-only first); how we measure Recommendability without overclaiming (simple heuristics versus live checks inside assistants); where the “email on file” for verification comes from; free versus paid; what never goes to a human versus when escalation is allowed; whether **veterinary** rides with healthcare/regulated or gets its own call if in scope (GBP research dump: separate Pets bucket, ~59 leaves, not folded into Health & Medical); and whether **v1 demand** is ads/self-start only, intermediate-first (tourism boards / chambers / partners), or both. +Ty still needs to lock: which cluster pack we ship first; whether version one is web-only or also embeds in a chatbot; which providers feed the Presence score (Core 3 GBP/Apple/Bing, plus [Yelp](https://www.yelp.com) and/or aggregators such as [Data Axle](https://www.data-axle.com/marketing-solutions/local-listings-management/) / [Localeze](https://neustarlocaleze.biz/) / [Foursquare](https://foursquare.com) — or claim-only first); how we measure Recommendability without overclaiming (simple heuristics versus live checks inside assistants); where the “email on file” for verification comes from; free versus paid; what never goes to a human versus when escalation is allowed; whether **veterinary** rides with healthcare/regulated or gets its own call if in scope (GBP research dump: separate Pets bucket, ~59 leaves, not folded into Health & Medical); and whether **v1 demand** is ads/self-start only, intermediate-first (tourism boards / chambers / partners), or both. --- ## What we are treating as hypotheses -Until we score real businesses, treat these as educated bets, not finished truth: that eight top-level clusters plus a hybrid flag is the right split (including destination workshop separate from service-area trades, and beauty separate from healthcare); that schema.org plus outbound maps to Google, Apple, Bing, Yelp, and selected aggregators is the right labeling spine — not any one platform’s leaf list as internal SoT; that two version-one packs are enough to prove cluster-specific rubrics; and that a web app beats an MCP-first distribution story for owners in the near term (revisit in about three months). +Until we score real businesses, treat these as educated bets, not finished truth: that eight top-level clusters plus a hybrid flag is the right split (including destination workshop separate from service-area trades, and beauty separate from healthcare); that schema.org plus outbound maps to [Google](https://business.google.com), [Apple](https://business.apple.com), [Bing](https://www.bingplaces.com), [Yelp](https://www.yelp.com), and selected aggregators is the right labeling spine — not any one platform’s leaf list as internal SoT; that two version-one packs are enough to prove cluster-specific rubrics; and that a web app beats an MCP-first distribution story for owners in the near term (revisit in about three months). Nothing in this doc is locked until Ty says so. Amend this file when decisions land — do not start a second near-named document.