Agent skill

SEO

by mblode in mblode/agent-skills

Audits and fixes technical SEO, researches search demand, creates content briefs, and measures SEO, AEO and GEO performance.

MITAuto-check passedMarketing & SEO

Install SEO

skills CLI
$ npx skills add mblode/agent-skills --skill seo -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mblode/agent-skills seo --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mblode/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/seo .claude/skills/seo && rm -rf skills-src

Use ~/.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/

Facts

Skill name
seo
GitHub stars
143
Token cost
~2.1k tokens
SKILL.md length
1,009 words
Files
10 (incl. references)
Skills in repo
28
Repo updated
First seen
Licence
MIT

At a glance

Audits and fixes technical SEO, researches search demand, creates content briefs, and measures SEO, AEO and GEO performance.

  • Asked to audit SEO
  • SKILL.md covers Route the task, Establish the evidence boundary, Working sequence and References, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Improve AI visibility

What it does

SEO is an agent skill from mblode/agent-skills. Audits and fixes technical SEO, researches search demand, creates content briefs, and measures SEO, AEO and GEO performance. Use when asked to "audit SEO", "fix indexing", "improve AI visibility", "do AEO or GEO", "check keyword volume", "write an SEO brief", or "why did organic traffic drop". For Mintlify Agent Score, AFDocs, or Is Agentic reports use agent-ready. For writing the article use ghostwriter; for visual redesign use ui-design.

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including reference files (for example `evals/evals.json`, `references/answer-engines.md` and `references/audit.md`).

It sits in Marketing & SEO, covering AI search optimization, UI design and SEO audit. The repository describes itself as: Nobody ships AI slop on purpose. These skills make sure you don’t. The licence is MIT.

When your agent uses it

  • Asked to audit SEO
  • Improve AI visibility
  • Check keyword volume
  • Write an SEO brief

Example prompts

  • “audit SEO”
  • “fix indexing”
  • “improve AI visibility”
  • “/seo”

What it can do on your machine

Read from SKILL.md and the folder at commit cef4cfa. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    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.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

SEO loads about 2.1k tokens when it runs, and up to ~14k if it reads all its reference files. Until then it costs about 112 tokens; SKILL.md has 1,009 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~112
When it runs · the whole SKILL.md, loaded when a task matches
~2.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~14k

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.

Safety

Auto-check passed

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.

SKILL.md

The full file from mblode/agent-skills at commit cef4cfa, republished under its MIT licence (© mblode). 1,009 words, ~2,110 tokens.

Download SKILL.mdSave it as .claude/skills/seo/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.
name
seo
description
Audits and fixes technical SEO, researches search demand, creates content briefs, and measures SEO, AEO and GEO performance. Use when asked to "audit SEO", "fix indexing", "improve AI visibility", "do AEO or GEO", "check keyword volume", "write an SEO brief", or "why did organic traffic drop". For Mintlify Agent Score, AFDocs, or Is Agentic reports use agent-ready. For writing the article use ghostwriter; for visual redesign use ui-design.

SEO

  • IS: one entry point for search visibility: evidence-led audits, implementation, demand research, writer briefs, and performance measurement across search engines and AI search (AEO for AI answers inside search, GEO for standalone assistants; see references/answer-engines.md).
  • IS NOT: writing the article or standalone marketing copy (ghostwriter), visual redesign (ui-design), tenant infrastructure (multi-tenant-architecture), or implementing AFDocs / Is Agentic / Is It Agent Ready scorecards (agent-ready). Fix SEO copy and markup when they are part of the requested implementation.

Route the task

RequestLoadDeliverable
Audit a site, diagnose indexing, review a migrationreferences/audit.md and references/validation-evidence.mdPrioritized findings with URLs, observed evidence, impact, and correction
Fix or implement SEOAudit references, then applicable implementation references belowCode changes, scoped checks, and served-page evidence for the changed behavior
Research demand, choose a target, brief a pagereferences/research-protocol.md; references/brief-template.md for a briefSourced demand table and decision, or a durable writer brief
Explain traffic movement, measure AI visibility, monitor SEOreferences/monitoring.mdProperty-scoped diagnosis or configured monitoring with explicit data gaps

For a combined request, reuse one property and URL inventory across modes. An audit request produces findings; a request to fix them proceeds through implementation and verification within the user's authorized scope. A research-only request does not require crawling every URL or changing code.

Establish the evidence boundary

Identify the exact public host, URL-prefix or domain property, production environment, project/subpath, audience, and business outcome. On a shared domain, filter each project's path separately. In analytics, verify hostname, path, conversion event and attribution window before interpreting a number.

Discover connected tools and existing project bindings first. Prefer the established reporting source, then an available equivalent, then a signed-in browser. No vendor is required. Ownership verification, API consent and a successful scoped query are separate states. An export for a neighboring property is not a fallback.

Use No data with its reason for inaccessible, missing, unsupported or unmeasured metrics; distinguish these from a measured zero. Label historical exports by their actual dates. Do useful public checks while an authenticated metric is unavailable.

Working sequence

For substantial mixed work, track only the applicable steps:

  • Confirm property, scope, baseline and intended outcome.
  • Inspect live evidence and map affected route patterns or research questions.
  • Prioritize blocking defects and high-value opportunities; separate observations from hypotheses.
  • Implement authorized corrections or deliver the requested research/brief.
  • Recheck the changed behavior, identify the tested environment, and report remaining gaps.

Prioritize crawl/index defects before cosmetic metadata changes. Page titles, headings and content structure follow the page's purpose and reader intent. Descriptive non-brand terms help category discovery; brand-led portfolio and product pages can be appropriate. Neither a fixed title character count nor question-shaped headings are ranking requirements.

For AI visibility, the owner builds crawl access, content and extractable structure; independent reviews, comparisons and coverage are earned, and they supply most of what answers say about a brand. Fix the owned layers first, then say where the remaining leverage sits instead of padding the site. Original evidence, useful comparisons and honest product limitations earn their place ahead of manufactured keyword permutations. Research likely reader questions; do not present invented query fan-outs as engine telemetry or create a page for every variation.

References

FileRead when
references/audit.mdCrawling, diagnosing or prioritizing a site audit; canonicals, redirects, exclusions and programmatic pages; hreflang; CDN, response headers or preview environments affecting discovery
references/nextjs-implementation.mdImplementing App Router metadata, sitemaps, rendering, status codes, Markdown twins, or schema; verify APIs against the installed Next.js docs
references/answer-engines.mdSEO, AEO and GEO terms, AI visibility, crawler policies, owned versus earned coverage, Markdown alternatives or llms.txt
references/validation-evidence.mdVerifying findings, a built page or a deployed correction
references/research-protocol.mdKeyword/prompt metrics, opportunity selection and question maps
references/brief-template.mdProducing a writer brief
references/monitoring.mdSearch/AI performance, attribution, anomalies or recurring work
references/sources.mdA claim depends on current engine behavior, supported reports, or vendor research
Show full SKILL.md (377 more words)Show less

Delivery

Findings go in chat unless a file is requested. Writer briefs go to the requested project destination; retain prior dated briefs when producing a new revision. Keep scratch crawls and exports out of the repository. No em dashes in authored reports or briefs.

Report what changed, why, exact verification evidence, and what remains unmeasured. A successful local build, ready deployment, public URL probe, Google index record and measured conversion are different evidence. Name the strongest state actually verified.

Sending recaps to others, scheduling recurring work, spending on tools and production deployment follow the user's authorization and host rules. Reuse an existing matching monitor rather than creating another owner or schedule.

Gotchas

  • A sitemap can parse while listing /studio that intentionally returns 404. Check its URLs, not just XML validity.
  • A canvas gated on mounted state can leave the homepage and category hubs with only navigation in initial HTML. Inspect those hubs as well as deep pages; use client alone does not imply missing server-rendered content.
  • lastModified: new Date() or a build timestamp describes generation, not necessarily a significant page update. Use content dates or omit the field.
  • A canonical tag on each URL does not resolve two copies that both self-canonicalize. Compare content and choose the preferred URL.
  • Two consistent JSON-LD scripts are not an error. Verify entity identity, eligible properties and visible supporting content instead of script count.
  • DNS verification needs no invented meta token. Confirm scoped data access separately.
  • A crawler user-agent probe does not authenticate a bot IP or establish index inclusion. Treat CDN logs and engine inspection as separate evidence.
  • Prompt demand, measured citations, mentions, AI impressions and referral sessions are different quantities. Preserve engine, source, match type, scope and window.
  • One prompt run, or one score averaged across engines, is not a visibility measurement. Repeat each prompt, report per engine, and keep recall separate from citations.
  • Schema, llms.txt and fixed answer-block lengths are not measured citation levers. Keep them for their real consumers; do not sell them as AI visibility.
  • A vendor Search Console connector may under-report. Reconcile property, filters and aggregation against native Search Console before diagnosing a drop.

Maintenance only: evals/evals.json holds behavioral scenarios and routing prompts. It is loaded when changing the skill, not during ordinary SEO work.

© mblode, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 9 other files (references) in skills/seo of mblode/agent-skills.

  • SKILL.md
  • evals/evals.json
  • references/answer-engines.md
  • references/audit.md
  • references/brief-template.md
  • references/monitoring.md
  • references/nextjs-implementation.md
  • references/research-protocol.md
  • references/sources.md
  • references/validation-evidence.md

Open the folder on GitHubat commit cef4cfa

Compare with similar skills

SEO 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.

SEO compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
SEO this skillmblode/agent-skills143—~2.1kAutomated safety check: PassMIT
GEO-First SEO Audit Toolzubair-trabzada/geo-seo-claude11k—~2.8kAutomated safety check: NotesMIT
SEOBhanunamikaze/Agentic-SEO-Skill955—~4.9kAutomated safety check: NotesMIT
SEOAgriciDaniel/seo-os1342 repos~3.5kAutomated safety check: PassMIT
SEO and GEO Auditdageno-agents/seo-geo-audit176—~2kAutomated safety check: PassMIT
SEO Coachakseolabs-seo/seo-coach146—~2.8kAutomated safety check: PassNone

Similar skills

  • GEO-First SEO Audit Tool

    zubair-trabzada/geo-seo-claude

    Audits a website for AI search visibility across ChatGPT, Claude, Perplexity and Google AI Overviews while checking traditional SEO, schema and E-E-A-T content quality.

    11k GitHub stars~2.8k tokensUpdated yesterday
    Marketing & SEOAuto-check: notes
  • SEO

    Bhanunamikaze/Agentic-SEO-Skill

    Deterministic LLM-first SEO audits for websites, blog posts, and GitHub repositories.

    955 GitHub stars~4.9k tokensUpdated 2 mo ago
    Marketing & SEOAuto-check: notes
  • SEO

    AgriciDaniel/seo-os

    Comprehensive SEO analysis for any website or business type.

    134 GitHub starsUsed in 2 repos~3.5k tokens
    Marketing & SEOAuto-check passed
  • SEO and GEO Audit

    dageno-agents/seo-geo-audit

    Runs one prioritized audit that combines technical SEO, content quality, trust signals, entity clarity and AI search readiness for a page, site or domain.

    176 GitHub stars~2k tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed
  • SEO Coach

    akseolabs-seo/seo-coach

    Beginner-first SEO coaching for people who want to learn by doing one safe, verifiable step at a time.

    146 GitHub stars~2.8k tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed
  • Universal SEO Analysis

    AgriciDaniel/claude-seo

    Hub for site-wide SEO work: audits, technical checks, schema, content quality, local, hreflang and AI-search readiness, run through slash commands.

    18k GitHub stars~4.9k tokensUpdated 3 days ago
    Marketing & SEOAuto-check passed

More from mblode/agent-skills

All 28 skills in this repo
  • Agent Ready

    mblode/agent-skills

    Implements agent-readiness on public sites and docs from Mintlify Agent Score, AFDocs, Is Agentic, Is It Agent Ready, or url-discovery-bench reports, or from server logs of agents 404ing on guessed…

    143 GitHub stars~2.1k tokensUpdated 2 days ago
    Auto-check passed
  • Agent Skills Creator

    mblode/agent-skills

    Creates and improves portable Agent Skills with a validator, routing scenarios, and evidence-based keep, cut, merge, or retire decisions.

    143 GitHub stars~2.8k tokensUpdated 2 days ago
    Auto-check passed
  • Chat History

    mblode/agent-skills

    Recovers decisions, previous fixes, research, and what followed a prompt from past AI conversations, with source evidence.

    143 GitHub stars~1.5k tokensUpdated 2 days ago
    Auto-check passed
  • CI Speedup

    mblode/agent-skills

    Cuts the wait from push to green by measuring a pipeline's critical path from run timestamps, then splitting, sharding, trimming setup and sharing test module state, with a before/after ledger.

    143 GitHub stars~2.4k tokensUpdated 2 days ago
    Auto-check passed
  • PR Babysitter

    mblode/agent-skills

    Monitors or repairs an open GitHub PR: CI failures, conflicts, review threads, and merge readiness, reporting state changes.

    143 GitHub stars~3.4k tokensUpdated 2 days ago
    Auto-check passed
  • App Verification

    mblode/agent-skills

    Builds and maintains a repo's own verification harness (verify CLI, doctor, worktree isolation, feature map, seed data) and a reproduce-first bug handoff.

    143 GitHub starsUsed in 1 repo~2.3k tokens
    Auto-check passed

Categories

Questions about SEO

What does SEO do?

Audits and fixes technical SEO, researches search demand, creates content briefs, and measures SEO, AEO and GEO performance. SEO is an agent skill from mblode/agent-skills. Audits and fixes technical SEO, researches search demand, creates content briefs, and measures SEO, AEO and GEO performance.

When should I use SEO?

SEO fits situations like: asked to audit SEO; improve AI visibility; check keyword volume; write an SEO brief.

How do I install SEO in Claude Code?

Run `npx skills add mblode/agent-skills --skill seo -a claude-code`. Or copy the skill folder (skills/seo in mblode/agent-skills) into .claude/skills/seo in your project. Claude Code loads it when a task matches its description.

How do I install SEO in Codex?

Run `npx skills add mblode/agent-skills --skill seo -a codex`. Or copy the skill folder (skills/seo in mblode/agent-skills) into .agents/skills/seo in your project. Codex loads it when a task matches its description.

Can I use SEO in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mblode/agent-skills --skill seo -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/seo, .gemini/skills/seo, .github/skills/seo and .opencode/skills/seo in your project.

What does SEO need to run?

SKILL.md names no scripts, command-line tools or credentials: SEO is instructions for the agent only.

Does SEO access the network?

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.

Is SEO safe to install?

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.

What licence does SEO use?

SEO is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does SEO use?

About 2.1k tokens (SKILL.md is roughly 8.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 12k tokens, read only when the agent opens those files.

What are the alternatives to SEO?

Skills that share tags, products or a category with SEO: GEO-First SEO Audit Tool (zubair-trabzada/geo-seo-claude, 11k stars), SEO (Bhanunamikaze/Agentic-SEO-Skill, 955 stars), SEO (AgriciDaniel/seo-os, 134 stars) and SEO and GEO Audit (dageno-agents/seo-geo-audit, 176 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains SEO?

mblode (a GitHub user) maintains it in mblode/agent-skills, which has 143 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on October 6, 2026.

Source: mblode/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.