Install
openclaw skills install geo-local-optimizer-2Local business-focused GEO optimization orchestrator for AI-powered local search. Use this skill whenever the user mentions local shops, clinics, restaurants, service providers, offline stores, franchise locations, or service areas and wants to rank better in AI answers or map-style results for queries like "near me", city/area + service, or landmark-based searches. Always consider this skill when the request combines GEO, local SEO, maps/listings, store pages, reviews, or service areas, even if the user does not explicitly say "GEO" or "local SEO".
openclaw skills install geo-local-optimizer-2A workflow skill for local-business GEO optimization, focusing specifically on AI-powered local search scenarios.
The goal is to take the user from “I have / plan a local business presence” to a structured local GEO plan that:
This skill focuses on strategy, structure, and workflows. It should coordinate with other GEO skills rather than replace them.
Invoke this skill whenever:
Do not limit triggering only to explicit “local SEO” wording. If the user:
then this skill should be strongly considered.
When available, this skill should coordinate with:
geo-site-audit: for overall technical + content GEO readiness of the websitegeo-studio: for higher-level GEO strategy and prioritization across regions or marketsgeo-schema-gen: to generate local-business-oriented schemasgeo-llms-txt: to expose local pages and location hubs to AI crawlersgeo-multimodal-tagger: to optimize store photos, menu images, environment shots, etc.high-repeat-small-goods-ops: for fast-moving local retail or F&B with high repeat purchasehigh-ticket-trust-conversion: for high-ticket, trust-sensitive local services (medical, education,
home renovation, etc.)If some skills are not present, still follow the same workflow shape and clearly explain what would be done, providing concrete, copy-pastable outputs.
Before starting the workflow, briefly reason about the local AI search context:
Keep in mind: the goal is to make it easy and safe for models to “recommend” this place to others, not just to stuff keywords.
When this skill is used, follow this 8-step workflow unless the user explicitly asks for only a subset.
Clarify the minimal but sufficient context for local optimization:
Output a ## Local Business Brief section with 6–10 bullet points summarizing this.
Based on the information and URLs provided by the user:
Output a ## Local Presence Snapshot with:
| Surface / Platform | Status (Good/OK/Poor/Missing) | Key issues / notes |
|--------------------|-------------------------------|-------------------------------------|
| Website store page | OK | Has address but lacks detailed FAQ |
| Google / Apple map | Good | Photos ok, but no English summary |
| Local review app | Poor | Few reviews, category mis-specified |
Turn the brief + audit into a concrete entity & page plan:
/stores/downtown-cafe or /city/area/service)Output a ## Local Entity & Page Plan section with:
For each key local page type, propose a reusable structure.
For single store / location pages, suggest a template like:
# [Brand / Location Name] – [City / Area] [Clear category keyword]
## Summary
- 2–4 bullets: who you are, where you are, who it’s for, what makes it special.
## About the business
Explain the business type, main services / products, and positioning in a few short paragraphs.
## Who we serve
- Typical customer profiles (commuters, families, students, fitness enthusiasts, etc.)
- Typical visit / usage scenarios (weekday lunch, after-work training, weekend brunch, etc.)
## Where we are
- Full address + nearby landmarks
- How to get there by walking / public transport / driving
## Opening hours & booking
- Weekday / weekend / holiday hours
- Reservation / booking methods (phone, website form, app, messaging, etc.)
## Products & services
- Core offerings list (name + short description + who it’s best for)
- Optional: indicative price ranges or popular bundles
## FAQ
Q1: [common local question]
A1: [short but informative answer]
Q2: ...
## Tips
- Parking / waiting times / peak hours
- Kid / pet friendliness
- Any other local tips
For service-area pages, adapt the template to focus on coverage area and how on-site / remote service works.
Output a ## Local Page Structures section that:
Use or conceptually apply geo-schema-gen to design structured data for local entities and pages:
@type selections:
LocalBusiness or specific subtypes such as Restaurant, CafeOrCoffeeShop, Store,
MedicalClinic, Dentist, HealthClub, EducationalOrganization, etc.Service for at-home / remote servicesPerson for key practitioners or experts when relevantname, image, url, telephoneaddress (with postal address fields)geo (latitude / longitude, if available)openingHoursSpecificationareaServed / serviceAreaservesCuisine, priceRange, amenityFeaturesameAs linking to main map / listing profiles and strong social profilesOutput a ## Local Structured Data Package section with:
Page URL pattern → Schema types → Key fields to fillAlso align map / listing profiles:
Design a sustainable local reputation engine so search engines and AI models keep receiving fresh, high-quality signals:
Output a ## Local Reputation & Q&A Plan section with:
Focus on how new or improved local content gets discovered and trusted by search engines and AI:
llms.txt and AI index pages:
geo-llms-txt to:
llms.txt exists, propose a minimal starter structureOutput a ## Local AI & Crawler Signaling Plan section with:
URL → Sitemaps / llms.txt / Internal links / External citationsDefine what success means for local GEO in the age of AI, and how to iterate:
Output a ## Measurement & Iteration section that:
Unless the user explicitly requests a different format, structure your answer as:
## Local Business Brief## Local Presence Snapshot## Local Entity & Page Plan## Local Page Structures## Local Structured Data Package## Local Reputation & Q&A Plan## Local AI & Crawler Signaling Plan## Measurement & IterationUse:
If the user only asks for a subset (e.g., “just the store page structure and review scripts”), still keep the headings but clearly mark skipped sections (e.g., “Not in scope for this request”).
These are example user prompts that should trigger this skill (for reference; not user-facing):
You do not need to surface this list directly to the user; it exists only to clarify intent.