seo
iannuttall/seo · Agent Skill
Use for SEO audits, rankings, keyword research, indexing, metadata, Search Console, GA4, and AI search visibility. Routes to evidence-backed reports through the local SEO CLI and MCP server.
Jump to install ↓Overview
| Publisher | |
|---|---|
| Repository | iannuttall/seo ↗ |
| Skill folder | seo |
| Stars | 594 |
| Forks | 51 |
| Bundled files | 2 |
| License | Apache-2.0 |
| Last updated | October 23, 2026 |
| Links | Skill source ↗ · Repository ↗ |
Mozgi check
What we found in the skill files. Details come with a subscription.
Installation
A skill is a folder with a SKILL.md file. Pick your agent and run the commands in a terminal (macOS, Linux or Git Bash on Windows) from your project root.
Copy the prompt into Claude, Codex or another assistant: it will review the skill and install it for you.
Install the “seo” skill from mozgi.io (https://mozgi.io/skills/iannuttall-seo/) for me. 1. Download the archive: https://mozgi.io/skills/iannuttall-seo/download If it fails, take the skill folder from the source: https://github.com/iannuttall/seo/tree/main/skills/seo 2. Read SKILL.md and the other files. Check the skill is safe: no hidden commands, no sending data elsewhere, no scripts doing something other than described. If anything looks suspicious, stop and tell me. 3. Put the “seo” folder into your agent's skills folder: .claude/skills/ for Claude Code, .agents/skills/ for Codex, .cursor/skills/ for Cursor, .gemini/skills/ for Gemini CLI. Inside the project if we are in one, otherwise in the home folder (~/.claude/skills/ etc.). 4. Make sure <skills folder>/seo/SKILL.md exists. 5. Briefly tell me what this skill does and offer to try it on my task. If you cannot do a step yourself, tell me what to click or type.
git clone --depth 1 --branch main https://github.com/iannuttall/seo.git /tmp/seo mkdir -p .claude/skills cp -r /tmp/seo/skills/seo .claude/skills/seo
Restart Claude Code — the skill appears in the list; call it manually with /seo. For all projects use ~/.claude/skills.
git clone --depth 1 --branch main https://github.com/iannuttall/seo.git /tmp/seo mkdir -p .agents/skills cp -r /tmp/seo/skills/seo .agents/skills/seo
Codex looks for skills in .agents/skills from the current folder up to the repo root; call one with /skills or $seo. For all projects use ~/.agents/skills.
git clone --depth 1 --branch main https://github.com/iannuttall/seo.git /tmp/seo mkdir -p .cursor/skills cp -r /tmp/seo/skills/seo .cursor/skills/seo
Cursor picks the skill up on start; call it with “/” in Agent chat. Cursor also reads .claude/skills and .agents/skills. For all projects use ~/.cursor/skills.
git clone --depth 1 --branch main https://github.com/iannuttall/seo.git /tmp/seo mkdir -p .gemini/skills cp -r /tmp/seo/skills/seo .gemini/skills/seo
Gemini CLI offers to activate the skill when a task matches — you approve it. For all projects use ~/.gemini/skills.
Read SKILL.md and any companion files before deciding whether to install. Click a file to preview it.
SKILL.md contents
Original author text · read-onlyseo
seo reads Search Console, Google Analytics, Bing Webmaster Tools and Clicky
data, crawls sites, checks live pages, and gets keyword and backlink data from
DataForSEO or Ahrefs.
Use the MCP tools when they are connected (hosted at
https://seoskill.dev/mcp, or local with seo mcp serve). Otherwise use the
CLI: seo, or npx -y seo. Add --json for JSON.
seo crawl --url <url> needs no sign-in and works on any site, local and
staging too. The other commands need the person's data: seo login prints a
link for them to approve, then run it again.
| CLI | MCP tool | Returns |
|---|---|---|
| seo report --site <site> | seo_report | Search Console overview and sections; with no site, last week across the sites in the weekly site audit beta |
| seo page --url <url> | seo_page | One URL: live page, index status, queries |
| seo compare --site <site> --date <date> | seo_compare | Before and after a date, with Google updates |
| seo index --site <site> | seo_index | Google's indexing reasons, labelled, and pages that lost their clicks |
| seo research <action> | seo_research | Keywords, SERP, competitors, backlinks, AI answer citations |
| seo data --site <site> | seo_data | Raw Search Console, Bing, Clicky or Google Analytics rows |
| seo crawl --url <url> | seo_crawl | Technical issues across a site |
| seo internal-links --site <site> or --url <url> | seo_internal_links | Links to add across a site, or to one page |
| seo sites | seo_sites | The properties the person can read |
Each result ends with the command to run next. Start small and ask for more:
a site, then a --section (section), then --detail rows or full.
seo <command> --help shows the options.
Indexing reasons each week
seo index inspects known URLs in a fixed order (lost-click pages, Search
Console pages by clicks, the sitemap, the rest), 100 by default, and labels
each Google reason fix, check, expected or indexed from a live check. In the
CLI or local MCP, --max-urls (max_urls) asks for more, up to today's
quota, and reuses saved inspections up to 7 days old, so paging or `--detail
full costs no quota. Run it once for a baseline and keep the full result (--detail full`).
Run it again each week with the same number and compare by URL and reason: a
new reason, or a URL that moved to fix, is what to report.
seo keeps no history, so you store the results. Once this runs weekly, the
person can turn off Search Console's indexing emails. For one URL from such an
email, run seo page --url <url>.
Frequently asked questions
What does the seo skill do?
Use for SEO audits, rankings, keyword research, indexing, metadata, Search Console, GA4, and AI search visibility. Routes to evidence-backed reports through the local SEO CLI and MCP server.
How do I install seo?
Open the “Installation” block on this page and pick your agent — Claude Code, Codex, Cursor or Gemini CLI — for ready-made commands that copy the skill folder to the right place. Or copy the prompt from the “Via assistant” tab and let the assistant review and install the skill.
Which AI models work with seo?
Skills are plain Markdown instructions (the Agent Skills format), so seo works with any agent that reads SKILL.md: Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and more. The model loads the instructions only when a task matches the skill's description.
Is seo free?
The skill is published openly by iannuttall under the Apache-2.0 license. The skill itself costs nothing — you only pay your AI provider for the tokens you use.
Is it safe to install skills?
A skill is a set of instructions your agent will follow, so read SKILL.md and its companion files before installing. Scripts in the skill folder only run if your agent runs them — keep an eye on what it does and do not grant unnecessary permissions.
How is a skill different from an MCP server or a plugin?
An MCP server or plugin gives the model new tools — code that runs and returns a result. A skill gives it knowledge and process: how to approach a task, which steps to follow and what good output looks like. It needs no server or API key.