Scribe Discovery foundation / AI readiness owner tier names
This commit is contained in:
@@ -11,3 +11,6 @@ Running definitions for industry terms used in geolocal.io planning.
|
|||||||
| **Bing Places** | Microsoft’s local business listing for Bing and related Microsoft surfaces. |
|
| **Bing Places** | Microsoft’s local business listing for Bing and related Microsoft surfaces. |
|
||||||
| **Core listings** | Owner-facing term for the main places customers (and AI) look a business up. Prefer this over “citations” / “directories” with owners. |
|
| **Core listings** | Owner-facing term for the main places customers (and AI) look a business up. Prefer this over “citations” / “directories” with owners. |
|
||||||
| **Core 3** | The common US min-bar listing set: GBP, Apple Business Connect, Bing Places. Genre/market adds (Yelp, Facebook, TripAdvisor, vertical dirs) are separate. |
|
| **Core 3** | The common US min-bar listing set: GBP, Apple Business Connect, Bing Places. Genre/market adds (Yelp, Facebook, TripAdvisor, vertical dirs) are separate. |
|
||||||
|
| **Discovery foundation** | Owner-facing name for tier 1: Core listings + NAP/hours/category/contact consistency (internally: “2017”). |
|
||||||
|
| **AI readiness** | Owner-facing name for tier 2: known-for / recommendability scorecard and structured presence when ready (internally: “2027”). |
|
||||||
|
|
||||||
|
|||||||
@@ -91,7 +91,13 @@ Keep to **three top-line outcomes**, each with plain “why not yet” underneat
|
|||||||
|
|
||||||
**Agreed essence so far:** scorecard is owner-plain (exist / know what you do / would recommend), not a long SEO audit. How we *measure* “would recommend” (heuristics vs live assistant checks, free vs paid depth) is still open discussion — do not treat packaging ideas as POR until Ty says they stick.
|
**Agreed essence so far:** scorecard is owner-plain (exist / know what you do / would recommend), not a long SEO audit. How we *measure* “would recommend” (heuristics vs live assistant checks, free vs paid depth) is still open discussion — do not treat packaging ideas as POR until Ty says they stick.
|
||||||
|
|
||||||
### 2017 good-enough foundation (working direction — essence)
|
### Discovery foundation + AI readiness (working direction — essence)
|
||||||
|
|
||||||
|
**Two tiers, one product story** (owner language):
|
||||||
|
1. **Discovery foundation** — Core listings + NAP/hours/category/contact consistency (internal: “2017”)
|
||||||
|
2. **AI readiness** — known-for queries, exist / know what you do / would recommend, structured presence when ready (internal: “2027”)
|
||||||
|
|
||||||
|
Measure both early; *fix* foundation first when broken.
|
||||||
|
|
||||||
Owner vocab (use these terms going forward):
|
Owner vocab (use these terms going forward):
|
||||||
- **Core listings** — main places customers (and AI) look the business up
|
- **Core listings** — main places customers (and AI) look the business up
|
||||||
@@ -164,6 +170,7 @@ If something here conflicts with `CANONICAL_STRATEGY.md`, resolve on purpose in
|
|||||||
| 2026-09-15 | Process note: scribe essence of agreed direction only — exploratory packaging stays out of POR until it sticks |
|
| 2026-09-15 | Process note: scribe essence of agreed direction only — exploratory packaging stays out of POR until it sticks |
|
||||||
| 2026-09-15 | Essence: validation gate before tool use (prove you represent the business); plan tier numbers still open |
|
| 2026-09-15 | Essence: validation gate before tool use (prove you represent the business); plan tier numbers still open |
|
||||||
| 2026-09-15 | Essence: owner vocab Core listings / Core 3; 2017 foundation six-point bar checked on Core 3 + site |
|
| 2026-09-15 | Essence: owner vocab Core listings / Core 3; 2017 foundation six-point bar checked on Core 3 + site |
|
||||||
|
| 2026-09-15 | Essence: two tiers — Discovery foundation → AI readiness (owner names); measure both early, fix foundation first when broken |
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user