\r \r

GEO Local Optimizer\r

\r A workflow skill for local-business GEO optimization, focusing specifically on AI-powered local\r search scenarios.\r \r The goal is to take the user from “I have / plan a local business presence” to a structured local GEO\r plan that:\r \r

• Makes each location and service area easy for AI models to understand and safely cite\r
• Aligns web pages + map/listing profiles + reviews + Q&A + local content into one coherent entity\r
• Works for both classical search + map packs and ChatGPT / Perplexity / Gemini / Claude style\r local answers\r \r This skill focuses on strategy, structure, and workflows. It should coordinate with other GEO\r skills rather than replace them.\r \r ---\r \r

When to use this skill\r

\r Invoke this skill whenever:\r \r

• The user runs or supports a local business, for example:\r
  • Food & beverage: cafes, restaurants, bakeries, bubble tea shops, snack bars\r
  • Everyday services: gyms, salons, laundries, pet stores, repair shops, home services\r
  • Medical & professional services: clinics, dentists, counseling centers, law firms, training centers\r
  • Retail stores: convenience stores, boutiques, electronics stores, bookstores\r
• The user’s goal explicitly or implicitly involves local discovery, such as:\r
  • “near me” style queries\r
  • city / district / neighborhood + service (e.g. "Downtown Toronto dentist", "Brooklyn personal trainer")\r
  • landmark-based searches (e.g. "coffee near Shibuya station", "gym near Central Park")\r
• The conversation touches on:\r
  • store / location pages, store detail pages, store finders, location landing pages\r
  • map / listing / review / food delivery / local directory presence\r
  • local reviews, Q&A, UGC, and reputation\r
  • how to make AI answers for local queries more likely to mention this business\r \r Do not limit triggering only to explicit “local SEO” wording. If the user:\r \r
• Describes one or more locations with clear geography, and\r
• Wants local customers to find them more easily in search or AI answers,\r \r then this skill should be strongly considered.\r \r ---\r \r

Relationship to other GEO skills\r

\r When available, this skill should coordinate with:\r \r

• geo-site-audit: for overall technical + content GEO readiness of the website\r
• geo-studio: for higher-level GEO strategy and prioritization across regions or markets\r
• geo-schema-gen: to generate local-business-oriented schemas\r
• geo-llms-txt: to expose local pages and location hubs to AI crawlers\r
• geo-multimodal-tagger: to optimize store photos, menu images, environment shots, etc.\r
• high-repeat-small-goods-ops: for fast-moving local retail or F&B with high repeat purchase\r
• high-ticket-trust-conversion: for high-ticket, trust-sensitive local services (medical, education,\r home renovation, etc.)\r \r If some skills are not present, still follow the same workflow shape and clearly explain what would\r be done, providing concrete, copy-pastable outputs.\r \r ---\r \r

Local AI search mindset\r

\r Before starting the workflow, briefly reason about the local AI search context:\r \r

• Typical queries combine intent + geography + constraints, for example:\r
  • “brunch cafe near [landmark], kid-friendly, outdoor seating if possible”\r
  • “[city/area] dentist that opens late after work”\r
• AI answers need:\r
  • Clear entity definitions (business type, brand, locations)\r
  • Stable name / address / phone / hours / service area / price level / who it is for\r
  • Rich but structured factual descriptions and typical scenarios\r
• Map / listing systems care about:\r
  • NAP consistency (Name, Address, Phone)\r
  • Categories, tags, photos, review volume and freshness\r
  • Citations and mentions across the web\r \r Keep in mind: the goal is to make it easy and safe for models to “recommend” this place to others, not\r just to stuff keywords.\r \r ---\r \r

High-level workflow\r

\r When this skill is used, follow this 8-step workflow unless the user explicitly asks for only a\r subset.\r \r

1. Capture business and locality context\r

\r Clarify the minimal but sufficient context for local optimization:\r \r

• Business basics:\r
  • Category / industry (e.g. "specialty coffee shop", "community grocery", "dental clinic",\r "personal training studio")\r
  • Single location vs. multi-location / franchise\r
• Geography and service area:\r
  • Full address for each location (city / district / neighborhood / street / building, plus landmarks)\r
  • Service area: walkable radius, drive-time radius, or named areas / zip codes\r
  • Whether on-site, on-premise, or remote / at-home services are offered\r
• Target customers and languages:\r
  • Core audiences (commuters, families with kids, students, seniors, expats, etc.)\r
  • Languages supported (e.g. local language + English)\r
• Key offers & positioning:\r
  • Core services / hero products / packages\r
  • Price band (budget / mid-range / premium)\r
  • Differentiators (ambience, expertise, speed, convenience, family-friendliness, etc.)\r
• Existing digital assets:\r
  • Website, landing pages, store finder, mini-apps, social channels, PDFs / decks\r
  • Existing map / review / delivery / directory listings (Google Maps, Apple Maps, Yelp,\r Tripadvisor, local review apps, food delivery platforms, etc.)\r \r Output a ## Local Business Brief section with 6–10 bullet points summarizing this.\r \r

2. Audit current local presence\r

\r Based on the information and URLs provided by the user:\r \r

• Check NAP consistency:\r
  • Brand / store naming conventions\r
  • Address, phone, website, hours across platforms\r
• Map / listing profiles:\r
  • Whether major platforms have claimed / verified listings\r
  • Accuracy of categories and attributes\r
  • Photo quality (storefront, interior, key products / services, atmosphere)\r
  • Presence of a concise, informative business description and highlights\r
• Website & store pages:\r
  • Whether each location has its own landing page (or a location finder + subpages)\r
  • Whether pages clearly display: name, address, phone, hours, service area, price level,\r directions / transport hints\r
  • Presence of local FAQs and scenario-based descriptions\r
• Reviews & Q&A:\r
  • Review volume, average ratings, recency\r
  • Common themes in questions (parking, wait times, booking, kid-friendly, etc.)\r \r Output a ## Local Presence Snapshot with:\r \r
• 1–2 short paragraphs on overall status\r
• A markdown table summarizing key surfaces, for example:\r \r

| Surface / Platform | Status (Good/OK/Poor/Missing) | Key issues / notes                  |\r
|--------------------|-------------------------------|-------------------------------------|\r
| Website store page | OK                            | Has address but lacks detailed FAQ  |\r
| Google / Apple map | Good                          | Photos ok, but no English summary   |\r
| Local review app   | Poor                          | Few reviews, category mis-specified |\r
```\r
\r
### 3. Design local entity and page strategy\r
\r
Turn the brief + audit into a **concrete entity & page plan**:\r
\r
- Decide what counts as a distinct **local entity**:\r
  - Single-store: each location is a separate local entity\r
  - Multi-location + service areas: locations plus city / area-level service pages\r
  - Person + organization: key practitioners or founders linked to the business\r
- Plan the **core local GEO pages**:\r
  - Brand / site-level hub pages (as canonical anchors and store finders)\r
  - Location pages (one landing page per store / location)\r
  - Service-area pages (e.g. "Downtown home appliance repair", "Midtown personal training")\r
  - Local FAQ / resource pages (e.g. "Family-friendly weekend guide for [area]" featuring the business)\r
- For each planned page, define:\r
  - **Primary intent** (what query / question it should answer)\r
  - **Target geography** (city / district / neighborhood / service area)\r
  - **Primary entity type** (LocalBusiness subtype / Organization / Person / Service)\r
  - **Canonical URL suggestion** (e.g. `/stores/downtown-cafe` or `/city/area/service`)\r
\r
Output a `## Local Entity & Page Plan` section with:\r
\r
- A table for core pages\r
- Brief bullets explaining how this plan helps AI answer local, scenario-based queries with this business.\r
\r
### 4. Craft AI-local landing structures\r
\r
For each key local page type, propose a **reusable structure**.\r
\r
For **single store / location pages**, suggest a template like:\r
\r
```markdown\r
# [Brand / Location Name] – [City / Area] [Clear category keyword]\r
## Summary\r
- 2–4 bullets: who you are, where you are, who it’s for, what makes it special.\r
\r
## About the business\r
Explain the business type, main services / products, and positioning in a few short paragraphs.\r
\r
## Who we serve\r
- Typical customer profiles (commuters, families, students, fitness enthusiasts, etc.)\r
- Typical visit / usage scenarios (weekday lunch, after-work training, weekend brunch, etc.)\r
\r
## Where we are\r
- Full address + nearby landmarks\r
- How to get there by walking / public transport / driving\r
\r
## Opening hours & booking\r
- Weekday / weekend / holiday hours\r
- Reservation / booking methods (phone, website form, app, messaging, etc.)\r
\r
## Products & services\r
- Core offerings list (name + short description + who it’s best for)\r
- Optional: indicative price ranges or popular bundles\r
\r
## FAQ\r
Q1: [common local question]\r
A1: [short but informative answer]\r
\r
Q2: ...\r
\r
## Tips\r
- Parking / waiting times / peak hours\r
- Kid / pet friendliness\r
- Any other local tips\r
```\r
\r
For **service-area pages**, adapt the template to focus on coverage area and how on-site / remote\r
service works.\r
\r
Output a `## Local Page Structures` section that:\r
\r
- Includes at least one concrete template for location pages\r
- Optionally includes variants for:\r
  - Single-location vs. multi-location brands\r
  - High-repeat, low-ticket retail vs. high-ticket, trust-heavy services\r
\r
### 5. Local structured data & listing alignment\r
\r
Use or conceptually apply `geo-schema-gen` to design **structured data** for local entities and pages:\r
\r
- Recommend appropriate `@type` selections:\r
  - `LocalBusiness` or specific subtypes such as `Restaurant`, `CafeOrCoffeeShop`, `Store`,\r
    `MedicalClinic`, `Dentist`, `HealthClub`, `EducationalOrganization`, etc.\r
  - `Service` for at-home / remote services\r
  - `Person` for key practitioners or experts when relevant\r
- For each key page type, specify required fields:\r
  - `name`, `image`, `url`, `telephone`\r
  - `address` (with postal address fields)\r
  - `geo` (latitude / longitude, if available)\r
  - `openingHoursSpecification`\r
  - `areaServed` / `serviceArea`\r
  - Industry-specific fields such as `servesCuisine`, `priceRange`, `amenityFeature`\r
  - `sameAs` linking to main map / listing profiles and strong social profiles\r
\r
Output a `## Local Structured Data Package` section with:\r
\r
- 1–2 example JSON-LD blocks for typical local scenarios (e.g. a single cafe + a city-level service page)\r
- A table mapping `Page URL pattern → Schema types → Key fields to fill`\r
\r
Also align **map / listing profiles**:\r
\r
- For each major platform (Google Maps, Apple Maps, local map apps, review sites, food delivery apps):\r
  - Suggest category and attribute choices\r
  - Suggest cover / hero photos and supporting images\r
  - Suggest a short, consistent description and key highlights, aligned with the website copy\r
\r
### 6. Reviews, Q&A, and local UGC engine\r
\r
Design a **sustainable local reputation engine** so search engines and AI models keep receiving fresh,\r
high-quality signals:\r
\r
- Reviews:\r
  - Provide simple, natural review invitation scripts (offline and online)\r
  - Provide a “high-information review” template that gently encourages:\r
    - Visit / usage context (when they came, with whom)\r
    - Specific services / products used\r
    - Perceived value and who this is good for\r
  - Provide a response structure for negative reviews: empathize → explain (if needed) → offer a\r
    constructive resolution.\r
- Q&A:\r
  - List 5–15 of the most common questions for this type of business and location\r
  - Provide “standard answer” drafts suitable for map / listing Q&A and website FAQ pages, using\r
    clear, factual language that local search can understand\r
- UGC & social:\r
  - Suggest 3–5 local content themes for short videos / posts (e.g. “day in the life”, “neighborhood\r
    guide”, “behind the scenes”)\r
  - Suggest photo / content angles that strongly tie the business to the local area and typical use cases\r
\r
Output a `## Local Reputation & Q&A Plan` section with:\r
\r
- Review invitation scripts\r
- Example “good review” patterns\r
- Top FAQs + standard answer drafts\r
\r
### 7. AI & crawler signaling for local content\r
\r
Focus on how new or improved local content gets **discovered and trusted** by search engines and AI:\r
\r
- Sitemaps:\r
  - Recommend including store pages, service-area pages, and local hubs in XML sitemaps\r
  - For multi-city or multi-language sites, suggest a clean sitemap structure\r
- `llms.txt` and AI index pages:\r
  - Use or conceptually apply `geo-llms-txt` to:\r
    - Add sections such as “Local / Locations / Stores / Clinics”\r
    - Point to key local hub pages and representative location pages\r
  - If no `llms.txt` exists, propose a minimal starter structure\r
- Internal linking:\r
  - Recommend internal links from:\r
    - About / story pages\r
    - Product or service descriptions\r
    - Local guides / blog posts\r
  - Ensure anchor text combines **geography + scenario + category** wherever reasonable\r
- External citations:\r
  - Suggest priority local citation sources: local directories, industry associations, local media,\r
    partner sites, community organizations, etc.\r
\r
Output a `## Local AI & Crawler Signaling Plan` section with:\r
\r
- A concise checklist of recommended actions\r
- A small table mapping `URL → Sitemaps / llms.txt / Internal links / External citations`\r
\r
### 8. Measurement and iteration loop\r
\r
Define what **success** means for local GEO in the age of AI, and how to iterate:\r
\r
- Potential metrics:\r
  - Impressions and clicks for local queries in search tools (if the user has access)\r
  - Navigation / directions requests to locations\r
  - Calls, bookings, inquiries attributed to organic / local discovery\r
  - Orders, visits, or signups from local customers (including repeat visits)\r
  - Frequency of brand / location mentions in AI answers for relevant queries (if sampled manually\r
    or via tools)\r
- Iteration rhythm:\r
  - Recommend a light “local GEO review” every 1–3 months\r
  - Check: business info changes, review volume & quality, FAQ relevance, new photos or content needs\r
\r
Output a `## Measurement & Iteration` section that:\r
\r
- Lists 5–10 actionable metrics\r
- Suggests a simple review cadence and division of responsibilities (e.g. store managers vs. HQ team)\r
\r
---\r
\r
## Output format\r
\r
Unless the user explicitly requests a different format, structure your answer as:\r
\r
1. `## Local Business Brief`\r
2. `## Local Presence Snapshot`\r
3. `## Local Entity & Page Plan`\r
4. `## Local Page Structures`\r
5. `## Local Structured Data Package`\r
6. `## Local Reputation & Q&A Plan`\r
7. `## Local AI & Crawler Signaling Plan`\r
8. `## Measurement & Iteration`\r
\r
Use:\r
\r
- **Markdown headings and tables** for structure\r
- Bulleted lists instead of dense paragraphs\r
- Short, actionable sentences that local owners or operators can copy into task trackers or docs\r
\r
If the user only asks for a **subset** (e.g., “just the store page structure and review scripts”), still\r
keep the headings but clearly mark skipped sections (e.g., “Not in scope for this request”).\r
\r
---\r
\r
## Example triggering prompts (for reference)\r
\r
These are **example user prompts** that should trigger this skill (for reference; not user-facing):\r
\r
- “I run three coffee shops in one city and want ChatGPT and Perplexity to be more likely to recommend\r
  us when people ask for good work-friendly cafes near our neighborhoods. Help me design a local GEO\r
  plan across our website, map listings, and reviews.”\r
- “We’re a small dental clinic that relies on local search. Please help us restructure our site,\r
  location pages, and Google Maps profile so that AI assistants and search engines can clearly\r
  understand who we serve, where we are, and when we’re open.”\r
- “I offer personal training in two districts and also do at-home sessions. I want a clear plan for\r
  local landing pages, service-area content, structured data, and reviews so that AI tools can\r
  confidently recommend me when users ask for trainers in my area.”\r
\r
You do **not** need to surface this list directly to the user; it exists only to clarify intent.\r
\r