agentleFS
kid7stkid7st/agenticseo/.agents/skills/local-seo/SKILL.md

local-seo

Skill2 starsChanged 53 days agoMITView on GitHub

Audit a Google Business Profile, compare it to local competitors, and map Maps visibility around a location. Use when rankings depend on a physical location or service area.

  • Reads credentials

28 other projects use a version of this, 4 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use ecommerce-seo, image-seo and 2 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.
  • MYehia565Skill

    ecommerce-seo

    Applies Google ecommerce SEO guidance: IA/URLs, product data, and shopping-related structured data. Use when building or fixing product/category/store search presence.

    Also in 4 projects that use this

  • arturseo-geoSkill

    image-seo

    Full image SEO pipeline: optimise file size, convert to WebP, upload to WordPress media library, and set all 4 SEO metadata fields (alt text, title, caption, description). Optionally set as featured image on a post. Use when the user wants to upload an image to WordPress, optimise images for a post, or bulk-process a folder of images. Automatically activates when user references an image file and WordPress deployment.

    Also in 4 projects that use this

  • deeployCOSkill

    youtube-seo

    Advanced YouTube SEO analysis and optimization for channels and videos. Routes to specialized sub-skills for audits, single-video deep dives, metadata optimization, channel branding, keyword research, thumbnails, and competitor intel. Models YouTube's modern recommender (session watch time / Reinforce / persona matching) not just keyword match. Use when user says "YouTube SEO", "optimize my video", "rank my YouTube video", "YouTube channel audit", "YouTube keywords", or provides a YouTube URL.

    Also in 3 projects that use this

  • jstanxSkill

    ai-visibility-audit

    Audit how ready a brand is to be cited by answer engines and produce a prioritized fix list — baseline what ChatGPT, Perplexity, Gemini, and Google AI Overviews say today, then score discoverability, interpretability, attribution, authority, and governance. Works for any business, B2B or B2C, product or service. Use when the request is to run an AEO or GEO audit, check AI visibility, find out why a brand is not cited by AI, baseline AI search presence, or assess answer-engine readiness. For competitor share of voice use competitor-ai-analysis; for ongoing tracking use ai-visibility-tracking.

    Also in 3 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. 0 are common, 4 are distinctive, and 10 are very specific to this project.

  • 0

    Common

    Most of the 26 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 10

    Very specific

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

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

    Use this when rankings depend on a physical location or service area.

    line 14
  2. Very specific:

    Use the installed agenticseo command.

    line 16
  3. Very specific:

    Run agenticseo context first and ground the work in it: what the business does and where it operates decide which keywords and radius …

    line 26
  4. Very specific:

    Before paying, check researchLog.

    line 28
  5. Very specific:

    Run agenticseo local serp for the main keyword near the business coordinate.

    line 49
  6. Very specific:

    Run agenticseo local reviews for the user and the strongest competitor.

    line 52
  7. Very specific:

    Run agenticseo local grid for the main keyword.

    line 53
  8. Very specific:

    Add agenticseo local questions and agenticseo local posts when the profile basics are already competitive and the gap is engagement rather …

    line 54
  9. Very specific:

    Always build the profile snapshot table for the whole chain.

    line 59
  10. Very specific:

    If a report template applies (see seo-report), its sections and tone replace this list.

    line 68
  11. Distinctive:

    Q&A and posting: only when the basics are already competitive.

    line 76
  12. Distinctive:

    Do not run a 5×5 grid, or grids for several keywords, without telling the user the cost first: every point is a paid Maps search.

    line 82
  13. Distinctive:

    Do not infer local-pack strength from national organic metrics.

    line 85
  14. Distinctive:

    Never recommend review gating, fake reviews or keyword-stuffed business names.

    line 86

“Common” is measured: kept by at least 6 in 10 of the 26 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
<!-- Adapted from OpenSEO plugins/openseo/skills/local-seo/SKILL.md (https://github.com/every-app/open-seo, MIT, Copyright (c) 2026 Ben Senescu) for the AgenticSEO CLI. -->

Local SEO

Goal

Work out why a business does or does not show up in Google Maps and the local pack near its customers, and what to fix first.

Use this when rankings depend on a physical location or service area. For national organic work, use competitor-analysis or keyword-research.

Use the installed agenticseo command. Local lookups are billed by DataForSEO and need DATAFORSEO_API_KEY; each result states its cost and points to an evidence file. agenticseo local categories is free.

Required inputs

  • The business: its name, or a cid/place_id (most reliable)
  • Its coordinate (latitude,longitude): derive it from an agenticseo local businesses or agenticseo local serp row; only ask the user when derivation is ambiguous
  • One to three keywords customers actually search (for example "emergency plumber", not the brand name)

Project context

  1. Run agenticseo context first and ground the work in it: what the business does and where it operates decide which keywords and radius matter. If there is no project, set one up as seo-project-setup step 1 describes.
  2. This skill needs sections.business_overview. If it is empty, run a minimal inline setup: infer what the business does and its location from the site and confirm it with the user in one question, write it to .agenticseo/context.json, then continue. Never front-load the full interview; suggest seo-project-setup at the end for the rest.
  3. Before paying, check researchLog. If the same research ran within the last 30 days, reuse its evidence and say so instead of buying it again.
  4. On finish, write back what is durable: local competitors that have a website in competitors (entries are keyed by domain, so skip listings without one) and a corrected business_overview. Append { "entryDate": "<today from agenticseo context>", "summary": "Local SEO: <business> near <area>. Verdict: <conclusion>. Evidence: <paths>" } to researchLog. Run agenticseo context to validate.

Deliver as a report

Deliver through the seo-report skill. If that skill is not available, say so and stop before writing the report.

Commands

  • agenticseo local businesses --near LAT,LNG --radius KM [--query TEXT]: nearby listings, filterable with --min-rating, --min-reviews and --claimed/--unclaimed (use --unclaimed to find unclaimed listings when prospecting). One call with the brand name as --query and a wide radius returns category, rating, review count, claimed status, coordinates and cid for every location of a chain, usually enough that per-location profile calls are unnecessary.
  • agenticseo local serp "QUERY" --near LAT,LNG: the Maps (or --type local_finder) result set near a coordinate. The rows carry cid and place_id; collect them once and reuse them everywhere below.
  • agenticseo local profile --cid ID: the full profile for one business (hours, rating breakdown) when the listing row is not enough.
  • agenticseo local reviews --cid ID: reviews with ratings, text and whether the owner replied. Billed when the task is posted, collected for free: a processing result returns a taskId; run agenticseo local reviews --task-id ID after 30–60 seconds, at no extra cost.
  • agenticseo local grid "QUERY" --center LAT,LNG --cid ID: the rank at every point of a grid around a coordinate, with each point's result count and #1 business. --size 3 (the default) is nine searches; only use --size 5 (25 searches) when the service area is genuinely wide.
  • agenticseo local questions --cid ID --near LAT,LNG --radius KM: Q&A on the profile.
  • agenticseo local posts --cid ID: posts published on the profile, with dates; queued like reviews.
  • agenticseo local categories [TEXT]: valid category slugs for --categories in local businesses.

Workflow

  1. Find the business. Given only a name or website, agenticseo local businesses --query NAME centered on the business's city with a wide radius locates the listing and yields its cid and exact coordinate. If it returns several locations, the business is a chain; see multi-location below.
  2. Run agenticseo local serp for the main keyword near the business coordinate. Record the top 3–5 competitors' cid/place_id and the user's own row.
  3. Compare the user's listing against the top two competitors: primary category, additional categories, review count, hours completeness, photo count and claimed status. local businesses rows usually carry all of this; use agenticseo local profile for what they lack.
  4. Sanity-check each listing's website link (url in the rows): it should deep-link to that location's page on the project domain, not a homepage or a stale domain. For broader on-page work, hand off to agenticseo audit start (see seo-audit).
  5. Run agenticseo local reviews for the user and the strongest competitor. Look at review volume, recency, average rating and how many reviews got an owner reply.
  6. Run agenticseo local grid for the main keyword. Use the grid to separate "ranks at the storefront only" from "ranks across the service area", and each point's top result to name who wins where the target does not.
  7. Add agenticseo local questions and agenticseo local posts when the profile basics are already competitive and the gap is engagement rather than setup.
  8. Turn the evidence into a prioritized list. Category and claim problems outrank posting cadence every time.

Multi-location businesses

Always build the profile snapshot table for the whole chain; one agenticseo local businesses call covers it. The per-location deep-dives (reviews, grid, posts, Q&A) are where cost scales:

  • 5 locations or fewer: deep-dive them all.
  • More than 5: present the snapshot table, then ask the user which 1–3 locations to deep-dive. Recommend sensible defaults, for example the weakest profile in the densest market.

Output format

Title: Local SEO: <business name> — <date> (see seo-report).

If a report template applies (see seo-report), its sections and tone replace this list.

Sections in this order:

  1. Snapshot: one or two opening sentences, then a table of category, rating, review count and claimed status. One row per location for a chain.
  2. The one fix: one finding. Category and claim problems outrank posting cadence every time.
  3. Head to head: a table of signal, this business, the best competitor and the gap. Cover categories, reviews (count, recency, owner replies), hours and profile completeness, and the listing's website link.
  4. Maps coverage: what the grid shows, where visibility drops off, and who wins there. A bar chart of ranks by direction reads faster than a paragraph; label every value.
  5. Q&A and posting: only when the basics are already competitive.
  6. What to do next: an ordered list.
  7. How this report was made: opens with the skill link line from seo-report, pointing at https://github.com/kid7st/agenticseo/blob/main/.agents/skills/local-seo/SKILL.md ("AgenticSEO Local SEO skill"), then which commands returned what (with costs and evidence paths), plus a note reading each missing grid rank against that point's result count rather than calling it invisibility.

Guardrails

  • Do not run a 5×5 grid, or grids for several keywords, without telling the user the cost first: every point is a paid Maps search.
  • Match businesses by cid or place_id when you have one. Name matching collides with chains and similarly named businesses.
  • A missing rank at a grid point means the business was not among the results returned there. Read it with that point's result count: a full result set means outranked; a near-empty one means a sparse SERP, not proof of invisibility.
  • Do not infer local-pack strength from national organic metrics.
  • Never recommend review gating, fake reviews or keyword-stuffed business names.
  • A grid centered on the wrong place is worse than no grid: confirm the coordinate matches the storefront before paying for the grid.
  • On exit code 3, ask the user to fix the key; on exit code 4, report the error and any charged cost, and do not retry in a loop.

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.