Ty_Tech/geolocal-io
6
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Document one-to-many fan-out limits; link umbrella SoTs.

Browse Source 
Capture Localeze/Data Axle/Yext-class fan-out caveats as architect
guidance, and hyperlink Data Axle, Localeze/TransUnion, and
Foursquare Places to their canonical pages in that section.
This commit is contained in:
grokbot_ty
2026-10-01 10:45:56 -07:00
parent 95cd0a18e8
commit 44c2d6c7a7
1 changed files with 20 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/SELF_SERVE_AI_DISCOVERABILITY_CONCEPT.md
+20 -7
View File
@@ -91,7 +91,7 @@ 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, Localeze / TransUnion, and Foursquare’s place graph so long-tail directories, libraries, and many nav / GPS consumers stop regenerating stale NAP.
- **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.
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.
@@ -102,13 +102,13 @@ Umbrella-only leaves the Core 3 and Yelp wrong. Platform-only leaves the black b
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.
4. **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/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).
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.
6. **Data Axle Local Listings** (Lane A). Claim the business at the Data Axle Local Listings portal with a business email and / or ownership docs. Edit NAP (and hours) once in that central record. Wait for Data Axle’s verification and syndication batch — 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 begin reflecting the update on their next pull.
7. **Localeze / TransUnion Digital Business Profile** (Lane A). Claim at the TransUnion / Localeze 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.
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.
@@ -116,7 +116,7 @@ Umbrella-only leaves the Core 3 and Yelp wrong. Platform-only leaves the black b
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.
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, Localeze, Foursquare) 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 / 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.
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.
@@ -131,11 +131,24 @@ A muffin shop’s Tuesday hours are wrong on the public web. The owner runs our
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** — 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** — 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.
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).
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.
#### 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.
**[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.
**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.
**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.
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.
---