FLOW SEO Framework
AgriciDaniel/claude-seo
Brings the FLOW framework's stage-specific SEO prompts into the agent, from keyword discovery through backlinks, on-page work and conversion to local SEO, loaded on demand.
When the user wants to research keywords for a local business, find local search opportunities, build a keyword map for location pages, or understand local search intent.
$ npx skills add garrettjsmith/localseoskills --skill local-keyword-research -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install garrettjsmith/localseoskills local-keyword-research --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/garrettjsmith/localseoskills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/local-keyword-research .claude/skills/local-keyword-research && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "local-keyword-research" agent skill from https://github.com/garrettjsmith/localseoskills/tree/main/skills/local-keyword-research into .claude/skills/local-keyword-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "local-keyword-research", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/garrettjsmith/localseoskills/tree/main/skills/local-keyword-researchType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add garrettjsmith/localseoskills --skill local-keyword-research -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install garrettjsmith/localseoskills local-keyword-research --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/garrettjsmith/localseoskills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/local-keyword-research .agents/skills/local-keyword-research && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "local-keyword-research" agent skill from https://github.com/garrettjsmith/localseoskills/tree/main/skills/local-keyword-research into .agents/skills/local-keyword-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "local-keyword-research", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add garrettjsmith/localseoskills --skill local-keyword-research -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install garrettjsmith/localseoskills local-keyword-research --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/garrettjsmith/localseoskills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/local-keyword-research .cursor/skills/local-keyword-research && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "local-keyword-research" agent skill from https://github.com/garrettjsmith/localseoskills/tree/main/skills/local-keyword-research into .cursor/skills/local-keyword-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "local-keyword-research", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/garrettjsmith/localseoskills.git --path skills/local-keyword-research--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add garrettjsmith/localseoskills --skill local-keyword-research -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install garrettjsmith/localseoskills local-keyword-research --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/garrettjsmith/localseoskills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/local-keyword-research .gemini/skills/local-keyword-research && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "local-keyword-research" agent skill from https://github.com/garrettjsmith/localseoskills/tree/main/skills/local-keyword-research into .gemini/skills/local-keyword-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "local-keyword-research", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install garrettjsmith/localseoskills local-keyword-researchInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add garrettjsmith/localseoskills --skill local-keyword-research -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/garrettjsmith/localseoskills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/local-keyword-research .github/skills/local-keyword-research && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "local-keyword-research" agent skill from https://github.com/garrettjsmith/localseoskills/tree/main/skills/local-keyword-research into .github/skills/local-keyword-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "local-keyword-research", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add garrettjsmith/localseoskills --skill local-keyword-research -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install garrettjsmith/localseoskills local-keyword-research --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/garrettjsmith/localseoskills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/local-keyword-research .opencode/skills/local-keyword-research && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "local-keyword-research" agent skill from https://github.com/garrettjsmith/localseoskills/tree/main/skills/local-keyword-research into .opencode/skills/local-keyword-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "local-keyword-research", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
local-keyword-researchWhen the user wants to research keywords for a local business, find local search opportunities, build a keyword map for location pages, or understand local search intent.
Local Keyword Research is an agent skill from garrettjsmith/localseoskills. When the user wants to research keywords for a local business, find local search opportunities, build a keyword map for location pages, or understand local search intent. Also use when the user mentions "local keywords," "keyword research," "service area keywords," "near me keywords," "local search volume," "keyword map," "city keywords," "geo-modified keywords," "implicit local intent," or "local keyword strategy." For content creation from keywords, see local-landing-pages. For competitor keyword analysis, see…
Its SKILL.md is about 4.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Marketing & SEO, covering Keyword research and Local SEO. The repository describes itself as: Open-source Claude SEO tool for local search visibility — skills, tool integrations, and automation templates that turn Claude into a Local SEO expert. The licence is MIT.
12 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 405ce20. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Local Keyword Research loads about 4.7k tokens when it runs. Until then it costs about 142 tokens; SKILL.md has 2,389 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from garrettjsmith/localseoskills at commit 405ce20, republished under its MIT licence (© garrettjsmith). 2,389 words, ~4,693 tokens.
.claude/skills/local-keyword-research/SKILL.md (or your agent's skills folder).Default data tool: LocalSEOData (
localseodata-tool). Usekeyword_opportunitiesfor business-specific keyword ideas,keyword_suggestionsfor seed keyword expansion,search_volumefor volume data,keyword_trendsfor seasonality,keywords_for_sitefor current rankings. For advanced gap analysis, use Semrush.
You are an expert in keyword research for local businesses. Your goal is to build comprehensive keyword strategies that capture local search demand across services, locations, and intent types — driving both map pack and organic local rankings.
Local keyword research isn't just "regular keyword research + city names." It has unique dynamics:
The primary services the business offers, without location modifiers.
Examples:
plumberemergency plumbingdrain cleaningwater heater repairsewer line replacementThese carry implicit local intent — Google shows local results without a city name.
Service + specific location.
Formats:
[service] [city] — plumber buffalo[service] in [city] — plumber in buffalo[service] [city] [state] — plumber buffalo ny[service] [neighborhood] — plumber elmwood village[service] [county] — plumber erie county[service] [zip] — plumber 14075 (less common but real)Location-less queries with explicit local intent.
plumber near meemergency plumber near mebest plumber near me24 hour plumber near meImportant: "Near me" queries are determined by the searcher's device location, not by your content. You can't "optimize for near me" with on-page content — you optimize by having strong GBP presence, reviews, and proximity.
What the customer is experiencing, not what the business calls its service.
pipe burst (they don't search "pipe repair")furnace not turning on (not "furnace repair")tooth pain (not "endodontics")water in basement (not "basement waterproofing")These often have high urgency and conversion rates.
Modifiers that signal specific intent.
Urgency: emergency, 24 hour, same day, immediate Cost: cheap, affordable, cost, pricing, free estimate Quality: best, top rated, licensed, certified, experienced Comparison: vs, alternative, reviews, near [competitor]
Long-tail queries from People Also Ask and autocomplete.
how much does a plumber cost in buffalodo I need a permit for a water heater in nyhow long does drain cleaning takeGood for content/FAQ but rarely drive direct conversions.
Many businesses offer proprietary or branded services that patients/customers search by name.
Healthcare examples: Discseel, Intracept, CoolSculpting, Invisalign, LASIK, Botox Home services examples: Rinnai (tankless water heaters), Mitsubishi (mini-splits), Generac (generators) Legal examples: specific legal programs or certifications by name
Why these matter:
Searchers filtering by whether they can use/afford the service.
Healthcare: "[service] that accepts Medicaid," "[service] that takes Blue Cross," "workers comp pain management," "[specialty] accepting new patients" Legal: "free consultation personal injury," "contingency fee lawyer," "pro bono attorney" Home services: "licensed plumber," "insured roofing contractor," "financing available HVAC" General: "[service] that takes [payment method]"
These keywords have very high conversion intent — the searcher has already decided they need the service, they're checking if they can access it.
Businesses near national borders or in multilingual markets have a keyword category most competitors miss entirely.
Examples:
Check: Does the business serve customers who search in another language? If yes, those keywords deserve their own category and potentially their own landing pages.
How people search when they're talking to an AI assistant (ChatGPT, Gemini, Perplexity, Google AI Mode/Overviews) instead of typing into a search box. This isn't a modifier on the other categories — it's a different query shape.
How they differ from typed keywords:
How to find them:
A note on volume: AI query demand is emerging and hard to size — tooling is thin, and for hyperlocal terms measured demand is often near zero even where typed-search demand exists. Treat these as an intent category to cover, not a volume play. Don't ignore a natural-language query because a tool reports no volume; the demand signal for AI is directional at best today.
This category identifies the queries. For how to earn citation in AI answers once you know them, see ai-local-search.
Before touching any tool, gather:
Ask the business: "When someone calls you, what do they say they need?" That language is your keyword seed.
For each seed keyword, pull:
Tool options:
When you search for the client's primary keywords, the SERP results contain competitor intelligence:
This step is often skipped but it's free and produces the highest-quality keyword additions because it's based on actual search behavior, not tool estimates.
For local businesses, the keyword universe is a matrix:
Services × Locations × Modifiers = Keyword Universe
Example:
10 services × 25 cities × 3 modifiers = 750 keyword combinationsDon't create a page for every combination. Use the matrix to:
Every keyword gets an intent tag:
| Intent | Example | Content Type |
|---|---|---|
| Emergency/urgent | "emergency plumber now" | GBP, dedicated emergency page |
| Transactional | "plumber buffalo ny" | Service + city landing page |
| Commercial investigation | "best plumber buffalo reviews" | Review/comparison content |
| Informational | "how to unclog drain" | Blog/FAQ content |
| Navigational | "[business name]" | Homepage, GBP |
Priority order for local businesses: Emergency > Transactional > Commercial > Informational
Each keyword (or keyword cluster) maps to a specific page:
| Keyword Cluster | Target Page | Page Type |
|---|---|---|
| plumber buffalo ny, plumber in buffalo, buffalo plumber | /plumber-buffalo-ny/ | Service + city |
| emergency plumber, 24 hour plumber, pipe burst | /emergency-plumbing/ | Service (urgent) |
| drain cleaning [cities] | /drain-cleaning/ | Service page |
| how much does plumbing cost | /blog/plumbing-cost-guide/ | Blog/FAQ |
Rules:
Know this going in: Keyword tools significantly undercount local search volume.
What to do about it:
| Market Size | Service Keyword Volume | Geo-Modified Volume |
|---|---|---|
| Major metro (NYC, LA) | 5,000-50,000/mo | 500-5,000/mo |
| Mid-size city (Buffalo, Tampa) | 1,000-10,000/mo | 100-1,000/mo |
| Small city / suburb | 100-1,000/mo | 10-100/mo |
| Rural / small town | 10-100/mo | 0-10/mo |
Not all keywords produce the same SERP. Check what actually appears:
| SERP Feature | What It Means |
|---|---|
| Local pack (3-pack) | Implicit local intent — GBP optimization critical |
| LSAs at top | Pay-per-lead opportunity, high commercial intent |
| Ads in map pack | Local search ads opportunity |
| AI Overview / AI Mode | Query is answered by synthesis and citation, not ten blue links — the target shifts from ranking a page to being a cited source (see ai-local-search) |
| People Also Ask | FAQ content opportunity |
| Organic only (no local pack) | Informational intent, blog/guide content |
Run SERP checks for your top 20 keywords to understand what you're competing for. A keyword that triggers a local pack requires different optimization than one that shows only organic results.
Sometimes the best opportunities are keywords with decent volume but weak competition:
For businesses with multiple locations, the research scales differently:
The final deliverable is a keyword map document:
| Keyword | Volume | KD | Intent | Target Page | Status | Priority |
|---|---|---|---|---|---|---|
| plumber buffalo ny | 720 | 35 | Transactional | /plumber-buffalo-ny/ | Exists | High |
| emergency plumber | 480 | 42 | Emergency | /emergency-plumbing/ | Needs creation | High |
| drain cleaning buffalo | 210 | 28 | Transactional | /drain-cleaning-buffalo/ | Exists | Medium |
| how much does plumber cost | 590 | 22 | Informational | /blog/plumbing-costs/ | Needs creation | Medium |
| water heater repair near me | 880 | 38 | Transactional | /water-heater-repair/ | Needs update | High |
Status options: Exists (optimized), Exists (needs update), Needs creation, Low priority
| What You Found | Next Action | Skill |
|---|---|---|
| Keywords identified, need pages for them | Create location and service pages targeting the keyword map | local-landing-pages |
| Found keyword gaps vs. competitors | Deep-dive competitive analysis on those gaps | local-competitor-analysis |
| Keywords have high CPC, worth running ads | Build PPC campaigns targeting high-value keywords | local-ppc-ads |
| Keywords trigger LSA results | Ensure LSA profile is set up for those service categories | lsa-ads |
| Keywords trigger AI Overviews | Optimize content for AI citation | ai-local-search |
| Need to know current rankings for these keywords | Run geogrid scans per keyword | geogrid-analysis |
| Keywords done, need full audit context | Feed keyword map into the audit framework | local-seo-audit |
Default next step: Keyword research without page creation is wasted effort. Map keywords → pages → publish → scan rankings.
This skill requires data from external tools. See docs/tool-routing to pick based on what's connected.
© garrettjsmith, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/local-keyword-research of garrettjsmith/localseoskills.
Open the folder on GitHubat commit 405ce20
Local Keyword Research next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Local Keyword Research this skillgarrettjsmith/localseoskills | 121 | — | ~4.7k | Automated safety check: Pass | MIT | |
| FLOW SEO FrameworkAgriciDaniel/claude-seo | 19k | 2 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Page Play Builderaaron-he-zhu/aaron-marketing-skills | 2.9k | — | ~3.6k | Automated safety check: Pass | Apache-2.0 | |
| SEONexus-JPF/note-companion | 870 | — | ~2.2k | Automated safety check: Pass | MIT | |
| SEO Keyword ClusteringAgriciDaniel/claude-seo | 19k | 2 repos | ~3.3k | Automated safety check: Pass | MIT | |
| Evaluate Skillevery-app/open-seo | 23k | — | ~1.8k | Automated safety check: Notes | MIT |
AgriciDaniel/claude-seo
Brings the FLOW framework's stage-specific SEO prompts into the agent, from keyword discovery through backlinks, on-page work and conversion to local SEO, loaded on demand.
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "build programmatic SEO pages", "generate pages at scale", "rank on a high-authority third-party site", "borrow domain authority", "build a vs /…
Nexus-JPF/note-companion
Use and read this skill immediately if the user request is in any way related to SEO or a site's organic search or AI search presence.
AgriciDaniel/claude-seo
Clusters keywords by how much their search results overlap and designs a hub-and-spoke content plan with an internal link matrix and an interactive cluster map.
every-app/open-seo
Test a candidate OpenSEO skill end to end by running fresh, isolated Codex sessions against the local backend and scoring the reports they save.
AgriciDaniel/claude-seo
Builds research-backed SEO content briefs with competitor scoring, per-section word counts and page-type templates, for new pages or improving existing ones.
garrettjsmith/localseoskills
When the user wants to programmatically manage Google Business Profiles at scale via API, automate GBP updates, build GBP management tools, or integrate GBP data into their systems.
garrettjsmith/localseoskills
When the user wants to create, schedule, or optimize Google Business Profile posts.
garrettjsmith/localseoskills
Generate complete semantic content briefs for local SEO content — location pages, service pages, blog posts, FAQ content, and pillar pages.
garrettjsmith/localseoskills
Manages persistent work state (briefs) for local SEO engagements.
garrettjsmith/localseoskills
Build a complete local content strategy from keyword research output.
garrettjsmith/localseoskills
When the user wants to run a geogrid scan, check existing scan reports, track ranking trends over time, monitor GBP changes via Falcon Guard, or analyze reviews.
Categories
When the user wants to research keywords for a local business, find local search opportunities, build a keyword map for location pages, or understand local search intent. Local Keyword Research is an agent skill from garrettjsmith/localseoskills. When the user wants to research keywords for a local business, find local search opportunities, build a keyword map for location pages, or understand local search intent.
Local Keyword Research fits situations like: wants to research keywords for a local business; find local search opportunities; build a keyword map for location pages; understand local search intent.
Run `npx skills add garrettjsmith/localseoskills --skill local-keyword-research -a claude-code`. Or copy the skill folder (skills/local-keyword-research in garrettjsmith/localseoskills) into .claude/skills/local-keyword-research in your project. Claude Code loads it when a task matches its description.
Run `npx skills add garrettjsmith/localseoskills --skill local-keyword-research -a codex`. Or copy the skill folder (skills/local-keyword-research in garrettjsmith/localseoskills) into .agents/skills/local-keyword-research in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add garrettjsmith/localseoskills --skill local-keyword-research -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/local-keyword-research, .gemini/skills/local-keyword-research, .github/skills/local-keyword-research and .opencode/skills/local-keyword-research in your project.
SKILL.md names no scripts, command-line tools or credentials: Local Keyword Research is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Local Keyword Research is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.7k tokens (SKILL.md is roughly 19k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Local Keyword Research: FLOW SEO Framework (AgriciDaniel/claude-seo, 19k stars), Page Play Builder (aaron-he-zhu/aaron-marketing-skills, 2.9k stars), SEO (Nexus-JPF/note-companion, 870 stars) and SEO Keyword Clustering (AgriciDaniel/claude-seo, 19k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
garrettjsmith (a GitHub user) maintains it in garrettjsmith/localseoskills, which has 121 GitHub stars. The repository holds 38 skills in this directory. The repository was last updated on August 15, 2026.
Source: garrettjsmith/localseoskills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.