agentleFS
OneWave-AIOneWave-AI/claude-skills/local-seo-optimizer/SKILL.md

local-seo-optimizer

Skill378 starsChanged 57 days agoMITView on GitHub

Get a local business found on Google -- audit and optimize the Google Business Profile, local pack ranking factors, review velocity, NAP consistency across directories, and location pages. For businesses whose customers search "near me," this outranks everything else in marketing.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    NAP sweep: Search the business name/phone across major directories (Yelp, Apple Maps, Bing Places, Facebook, industry-specific ones, data …

    line 17
  2. Distinctive:

    Never recommend fake reviews, review gating (filtering unhappy customers away from Google), or keyword-stuffed business names -- all are …

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “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 Optimizer

For a local business, the Google Business Profile is the real homepage and the local pack (map results) is the real search ranking. This skill audits the three local ranking pillars -- relevance, distance, prominence -- and produces the fix list. Complements seo-optimizer (content/on-page SEO); this is the maps-and-profile layer.

Workflow

  1. Baseline. Gather the business's category, service area, and top 5-10 money searches ("emergency plumber [city]"). Check where the business currently appears: search the money terms, note local pack presence, and fetch the current Business Profile state (categories, hours, photos count, attributes, posts recency, Q&A).
  2. Profile audit. Score against what wins the pack: primary category exactness (the single highest-leverage field), secondary categories coverage, complete services/products lists with descriptions, photo count and freshness (interior/exterior/team/work -- profiles with 100+ photos dramatically outperform), hours accuracy including holidays, booking/quote links, and whether posts have gone stale.
  3. Review engine. Review count, average, velocity vs. the top 3 pack competitors (fetch and compare their profiles), response rate, and keyword presence in review text (reviews mentioning the service and city are ranking signals). Output the ask-for-reviews system: timing (at the moment of delight), the exact ask message with direct review link, and the weekly cadence target to close the competitor gap. Pair with review-response-writer for the response side.
  4. NAP sweep. Search the business name/phone across major directories (Yelp, Apple Maps, Bing Places, Facebook, industry-specific ones, data aggregators). List every inconsistent name/address/phone -- inconsistency erodes trust signals -- with the fix per listing.
  5. Website local layer. Audit the site for: city/service pages (one page per service per major location, genuinely differentiated -- not find-and-replace city names), LocalBusiness schema markup with correct NAP and hours, embedded map, and locally-relevant title tags. Output the page-by-page fix list, with drafts for the highest-value gaps.

Rules

  • Primary category first, always -- it is worth more than everything else on the profile combined.
  • Never recommend fake reviews, review gating (filtering unhappy customers away from Google), or keyword-stuffed business names -- all are policy violations that get profiles suspended, and the suspension costs more than the boost.
  • Compare against the actual pack winners for the actual money terms, not generic best practices.
  • Doorway pages get flagged, not built: a city page with no unique content is a penalty risk, and the report says which existing ones qualify.
  • Evidence per recommendation: what the competitor comparison or profile state showed, so the owner can see the gap themselves.
  • Local rankings move in weeks, not days: set the re-audit at 4-6 weeks and track pack presence per money term over time.

Quick Commands

  • "Audit [business name, city]" -- full workflow
  • "Why is [competitor] outranking me?" -- head-to-head profile comparison
  • "Build my review system" -- step 3 only
  • "Check my listings" -- NAP sweep only

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.