agentleFS
oegeyilmaz9oegeyilmaz9/seo-aeo-geo-ultimate/skills/seo-local/SKILL.md

seo-local

Skill6 starsChanged 3 months agoApache-2.0View on GitHub

Use when auditing or planning local search visibility for a storefront, service-area business, practitioner, or multi-location brand across Google Business Profile, Bing Places, NAP/hours/categories, location pages, LocalBusiness data, reviews, duplicates, service areas, and location-aware query evidence; require authorized profile data and never promise map rankings, calls, visits, or revenue.

35 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use seo-maps, seo-sxo and 5 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • timruebenachSkill

    seo-maps

    Maps intelligence for local SEO — geo-grid rank tracking, GBP profile auditing via API, review intelligence across Google/Tripadvisor/Trustpilot, cross-platform NAP verification (Google/Bing/Apple/OSM), competitor radius mapping, and LocalBusiness schema generation from API data. Three-tier capability: free (Overpass + Geoapify), DataForSEO (full intelligence), DataForSEO + Google (maximum coverage). Use when user says "maps", "geo-grid", "rank tracking", "GBP audit", "review velocity", "competitor radius", "maps analysis", "local rank tracking", "Share of Local Voice", or "SoLV".

    Also in 15 projects that use this

  • timruebenachSkill

    seo-sxo

    Search Experience Optimization: reads Google SERPs backwards to detect page-type mismatches, derives user stories from search intent signals, and scores pages from multiple persona perspectives. Identifies why well-optimized pages fail to rank by analyzing what Google rewards for each keyword. Use when user says "SXO", "search experience", "page type mismatch", "SERP analysis", "user story", "persona scoring", "why isn't my page ranking", "intent mismatch", or "wireframe".

    Also in 17 projects that use this

  • indranilbanerjeeSkill

    seo-drift

    Compare two SEO exports (Search Console, two dates): gainers, losers, drift classes. \"what moved after the core update\"

    Also in 16 projects that use this

  • +4 more from timruebenach

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 32 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read markdown-delivery-contract.md for every task.

    line 10
  2. Distinctive:

    Read local-evidence-protocol.md before a formal audit.

    line 17
  3. Distinctive:

    Never fabricate an address, service area, category, review, rating, practitioner relationship, opening status, or profile access.

    line 32

“Common” is measured: kept by at least 6 in 10 of the 32 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Local SEO

Markdown delivery contract

Read markdown-delivery-contract.md for every task. Write a substantive .md document for every material work step and register its direct destination in the work index.md. For public-site work, apply the owner-required Markdown discovery profile across the full eligible inventory; preserve native standards and immutable evidence formats.

Lane outputs: local-review.md; location-facts.md (combine small related steps with stable section links). Publish factual location/service-area Markdown with exact NAP, hours, dates, local audience tasks and public evidence. Preserve locale/location ownership and profile truth; avoid thin location variants or exposing private contact data.

Audit the relationship between real-world business facts, authorized platform profiles, location pages, structured data, reviews, and location-aware query demand.

Read local-evidence-protocol.md before a formal audit.

Procedure

  1. Define business model, eligible locations/practitioners, service areas, markets/locales, official entity names, profile owners, and customer tasks.
  2. Capture authorized Google Business Profile/Bing Places data when available, official business records, representative location pages, LocalBusiness markup, citations, and review-policy evidence.
  3. Reconcile name, address, phone, website, hours, special hours, categories, services, areas served, coordinates, booking/order links, and status across first-party and platform surfaces.
  4. Build or consume a Query Corpus with locale, country/location, device, intent, current/target URL, and source. Separate local intent from a generic keyword and keep demand unavailable when no evidence exists.
  5. Inspect location-page uniqueness, crawlability, internal discovery, canonical/hreflang behavior, accessibility, conversion task completion, and truthful business/entity support.
  6. Identify duplicate, moved, closed, practitioner, department, review, category, or policy risks. Do not merge or suspend profiles without an authorized owner and current platform guidance.
  7. Route structured data to seo-schema, page/content to seo-content, technical/index issues to seo-technical, task flows to seo-agentic, and measurement to seo-performance.
  8. Package formal findings as SEO Findings 1.1.0 with business_profile, web_page, or locale_cluster targets and local, entity, content, technical, or policy categories.

Guardrails

Never fabricate an address, service area, category, review, rating, practitioner relationship, opening status, or profile access. Do not create doorway location pages or promise Local Pack placement.

Formal evidence handoff

Package only supported observations as SEO Findings 1.1.0. Let <suite-root> mean ${CLAUDE_PLUGIN_ROOT} in Claude Code. In Codex, read .seo-suite-runtime.json beside this SKILL.md when present and use its suite_root value; otherwise use the absolute repository checkout, then run python "<suite-root>/scripts/validate_seo_findings.py" validate-findings <bundle>/seo-findings.json --bundle <bundle>. Keep the handoff provisional until this command passes.

Output

Return the location/entity inventory, profile-page-schema parity, query/location map, duplicates and policy risks, prioritized owners, verification, rollback, and evidence gaps—without a local visibility score.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.