Agent skill

SEO

Audit and improve website discoverability across traditional search, answer engines, and generative search.

Install SEO

skills CLI

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

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

GitHub CLI

$ gh skill install magnus919/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/magnus919/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/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/

Paste into Claude Code

Install the "seo" agent skill from https://github.com/magnus919/agent-skills/tree/main/seo into .claude/skills/seo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo", 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

$skill-installer install https://github.com/magnus919/agent-skills/tree/main/seo

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

skills CLI

$ npx skills add magnus919/agent-skills --skill seo -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install magnus919/agent-skills seo --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/seo .agents/skills/seo && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "seo" agent skill from https://github.com/magnus919/agent-skills/tree/main/seo into .agents/skills/seo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo", 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.

skills CLI

$ npx skills add magnus919/agent-skills --skill seo -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install magnus919/agent-skills seo --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/seo .cursor/skills/seo && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "seo" agent skill from https://github.com/magnus919/agent-skills/tree/main/seo into .cursor/skills/seo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo", 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

$ gemini skills install https://github.com/magnus919/agent-skills.git --path seo

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add magnus919/agent-skills --skill seo -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install magnus919/agent-skills seo --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/seo .gemini/skills/seo && rm -rf skills-src

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

Paste into Gemini CLI

Install the "seo" agent skill from https://github.com/magnus919/agent-skills/tree/main/seo into .gemini/skills/seo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo", 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.

GitHub CLI

$ gh skill install magnus919/agent-skills seo

Installs 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).

skills CLI

$ npx skills add magnus919/agent-skills --skill seo -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

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

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

Paste into GitHub Copilot

Install the "seo" agent skill from https://github.com/magnus919/agent-skills/tree/main/seo into .github/skills/seo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo", 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.

skills CLI

$ npx skills add magnus919/agent-skills --skill seo -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install magnus919/agent-skills seo --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/seo .opencode/skills/seo && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "seo" agent skill from https://github.com/magnus919/agent-skills/tree/main/seo into .opencode/skills/seo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo", 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.

Facts

Skill name: seo
GitHub stars: 115
Token cost: ~1.9k tokens
SKILL.md length: 803 words
Files: 29 (incl. scripts, references, assets)
Skills in repo: 131
Repo updated: Oct 10, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Audit and improve website discoverability across traditional search, answer engines, and generative search.

Works in 7 steps: Scope the surface and outcome. Name the… → Inspect and research. Audit the… → Map intent to canonical content. Use… → …
On-page content
SKILL.md covers Operating model, Terminology and boundaries, Evidence rules and Reference routing, plus 4 more sections
Calls python3

What it does

SEO is an agent skill from magnus919/agent-skills. Audit and improve website discoverability across traditional search, answer engines, and generative search. Use for technical SEO, on-page content, structured data, question and entity architecture, AI citations, crawler controls, agent-readable content, and reproducible visibility measurement. Do not use for only copy-editing, writing, CMS operations, or generic AI marketing claims without a defined search surface and verification plan.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 31 other files, including scripts, reference files and assets (for example `README.md`, `assets/audit-report-template.md` and `evals/evals.json`). Compatibility notes: Requires access to the target site or content for implementation and verification; bundled scripts use Python 3.9+ standard library only.

It sits in Marketing & SEO, covering AI search optimization, Technical SEO and Schema markup. The repository describes itself as: Curated collection of AI agent skills for Hermes and other agent frameworks. The licence is MIT.

When your agent uses it

On-page content
Structured data
Question and entity architecture
Crawler controls

Example prompts

“/seo”

Requirements

Python 3
Compatibility (from SKILL.md): Requires access to the target site or content for implementation and verification; bundled scripts use Python 3.9+ standard library only.

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

Scope the surface and outcome. Name the provider, product or search surface, audience, entity, questions, business outcome, and…
Inspect and research. Audit the public/rendered page and technical delivery. Read current first-party provider guidance and authoritative…
Map intent to canonical content. Use topics and question clusters, but avoid manufacturing near-duplicate pages. Assign one canonical…
Improve people-first content and structure. Put a concise answer near the relevant heading, then supporting evidence, qualifications, and…
Implement only supported controls. Fix crawlability, indexability, metadata, internal links, page experience, textual content…
Measure at the correct boundary. Freeze prompts and versions, capture exact answers and citations, score citation correctness, and use…
Verify and learn. Recheck the rendered/public boundary, validate structured data, inspect search-console or provider evidence, and run…

What it can do on your machine

Read from SKILL.md and the folder at commit 22b4723. 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
Ships 1 file in scripts/, which the agent can run.
Shell commands in SKILL.md call:
- python3
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.
Compatibility
Requires access to the target site or content for implementation and verification; bundled scripts use Python 3.9+ standard library only.
From compatibility in the SKILL.md frontmatter.

Context cost

SEO loads about 1.9k tokens when it runs, and up to ~22k if it reads all its reference files. Until then it costs about 111 tokens; SKILL.md has 803 words of instructions outside code blocks.

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

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); the scripts in this folder are not scanned.

SKILL.md

The full file from magnus919/agent-skills at commit 22b4723, republished under its MIT licence (© magnus919). 803 words, ~1,934 tokens.

Download SKILL.mdSave it as .claude/skills/seo/SKILL.md (or your agent's skills folder). This skill also uses 28 other files; get the full folder from GitHub.

name: seo
description: Audit and improve website discoverability across traditional search, answer engines, and generative search. Use for technical SEO, on-page content, structured data, question and entity architecture, AI citations, crawler controls, agent-readable content, and reproducible visibility measurement. Do not use for only copy-editing, writing, CMS operations, or generic AI marketing claims without a defined search surface and verification plan.
compatibility: Requires access to the target site or content for implementation and verification; bundled scripts use Python 3.9+ standard library only.
license: MIT
metadata.scope: search-answer-generative-engine-optimization
metadata.aliases: SEO, AEO, GEO, LLMO, AI-search optimization

SEO

A full-spectrum search visibility skill. It treats traditional SEO, Answer Engine Optimization (AEO), and Generative Engine Optimization (GEO) as overlapping work across different search and answer surfaces, not as separate collections of ranking hacks.

Operating model

Scope the surface and outcome. Name the provider, product or search surface, audience, entity, questions, business outcome, and exclusions. Define whether success means crawl access, index eligibility, retrieval, mention, citation, citation correctness, share of voice, referral, or conversion.
Inspect and research. Audit the public/rendered page and technical delivery. Read current first-party provider guidance and authoritative subject sources. Treat practitioner claims and vendor studies as hypotheses unless methods and scope support more.
Map intent to canonical content. Use topics and question clusters, but avoid manufacturing near-duplicate pages. Assign one canonical answer location, entity ownership, evidence, freshness owner, and internal links.
Improve people-first content and structure. Put a concise answer near the relevant heading, then supporting evidence, qualifications, and useful detail. Preserve natural prose, distinct point of view, accessibility, and human value.
Implement only supported controls. Fix crawlability, indexability, metadata, internal links, page experience, textual content, structured-data parity, sitemaps, freshness, and provider-specific crawler or preview controls. Optional files such as llms.txt or Markdown representations are provider-scoped proposals, not universal requirements.
Measure at the correct boundary. Freeze prompts and versions, capture exact answers and citations, score citation correctness, and use provider-native reports where available. Separate implementation evidence from observed visibility and causal claims.
Verify and learn. Recheck the rendered/public boundary, validate structured data, inspect search-console or provider evidence, and run bounded one-variable experiments. Do not declare success from HTTP 200, parseable JSON-LD, a single answer, or a third-party score.

Terminology and boundaries

SEO is the umbrella: improving a site's eligibility, discoverability, interpretation, and useful visibility in search systems.
AEO is a stakeholder label for answer-oriented work, including direct answers, snippets, knowledge surfaces, and answer-engine inclusion.
GEO is a stakeholder label for visibility in generated answers, especially being selected, cited, or factually absorbed into a synthesized response. The term originated in the 2024 KDD paper by Aggarwal et al.; it does not establish a universal algorithm.
LLMO and AI-search optimization are overlapping labels. Preserve the target organization's term, then define the measurable outcome and provider scope.
These terms do not guarantee ranking, inclusion, citation, traffic, recommendation, or conversion. A mention is not a citation, a citation is not proof of correctness, and a citation is not a click.

Evidence rules

Use these labels in plans and reports:

Primary documentation: provider, standards body, schema vocabulary, or tool owner describes its own behavior.
Observed: recorded crawl, rendered page, provider dashboard, exact answer, URL, or reproducible local result.
Independent study: disclosed method and dataset, with generalization limits stated.
Vendor-reported: useful for hypothesis generation, not a universal rule.
Inference: reasoned interpretation beyond direct observation.
Unresolved: provider-dependent, stale, contradicted, or not verified.

Reject claims such as “FAQ schema guarantees citations,” “short paragraphs are required by all engines,” “llms.txt is a search standard,” or “allowing a crawler guarantees inclusion.” Record source URL, access date, provider scope, exact support, what it does not prove, confidence, and refresh trigger for every material claim.

Show full SKILL.md (278 more words)Show less

Reference routing

Need	Read
Crawlability, indexability, robots, sitemaps, performance, canonicals, mobile, HTTPS	`references/technical-seo.md`
Titles, descriptions, headings, content quality, links, images	`references/onpage-seo.md`
Schema.org, JSON-LD, rich-result eligibility, visible parity	`references/schema-markup.md` and `references/structured-data.md`
Topics, question clusters, entities, answer blocks, evidence architecture	`references/content-and-entity-architecture.md`
Full answer/generative implementation sequence and completion gate	`references/implementation-playbook.md`
Provider guidance, crawler identities, robots and preview controls	`references/platform-guidance.md` and `references/discovery-and-freshness.md`
`llms.txt`, Markdown delivery, content negotiation, provider support	`references/agent-readable-content.md`
Outcome definitions, confidence, and rejected claims	`references/evidence-boundaries.md`
Prompt sets, citation logs, metrics, experiments, and confounders	`references/measurement-and-experimentation.md`
Ghost metadata and injection	`references/ghost-metadata.md`
Content strategy, topic clusters, keywords, gaps, SERP features	`references/content-strategy-seo.md`
Source URLs, access dates, authority tiers, and refresh notes	`references/source-index.md`

Scripts and templates

Run from the skill directory:

bash

python3 scripts/aeo_audit.py <page.html-or-URL> --json
python3 scripts/build_prompt_matrix.py <topics.json> --output prompt-matrix.json
python3 -m pytest scripts/test_aeo_scripts.py

The scripts are read-only and use the Python standard library. They inspect source HTML; they do not execute JavaScript, call an LLM, publish, submit URLs, or change crawler policy. Templates cover implementation plans, question clusters, citation observations, optional llms.txt, and crawler-policy decisions.

Audit output

Use assets/audit-report-template.md and distinguish:

Observed findings: what the inspected page, response, dashboard, or answer actually shows.
Recommended changes: proposed actions with owner, risk, expected mechanism, and verification.
Provider scope: which engine or search surface the evidence applies to.
Status: implemented, verified, observed, inferred, or unresolved.

When not to use

Do not use this skill alone for only mechanical copy-editing, ordinary article writing, CMS administration, or a generic request to “rank better” without a defined target, evidence boundary, or measurable outcome. Route those to the relevant writing, copy-editing, CMS, or product skill.

Portability

Use the host agent's normal mechanisms to load references, templates, and scripts. Do not assume a particular profile system, orchestrator, memory service, CMS, search console, or provider API.

Files

SKILL.md and 28 other files (scripts, references, assets) in seo of magnus919/agent-skills.

SKILL.md
README.md
assets/audit-report-template.md
evals/evals.json
references/aeo-methodology.md
references/agent-readable-content.md
references/content-and-entity-architecture.md
references/content-strategy-seo.md
references/discovery-and-freshness.md
references/evidence-boundaries.md
references/ghost-metadata.md
references/implementation-playbook.md
references/measurement-and-experimentation.md
references/onpage-seo.md
references/platform-guidance.md
references/schema-markup.md
references/source-index.md
references/structured-data.md
… and 11 more

Open the folder on GitHubat commit 22b4723

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
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
SEO this skillmagnus919/agent-skills	115	—	~1.9k	Automated safety check: Pass	MIT	yesterday
Geo Auditvellum-ai/vellum-assistant	1.4k	—	~2k	Automated safety check: Pass	MIT	yesterday
SEO Visibility Expertcuriositech/some_claude_skills	244	—	~1.6k	Automated safety check: Notes	MIT	1 mo ago
GEO-First SEO Audit Toolzubair-trabzada/geo-seo-claude	11k	—	~2.8k	Automated safety check: Notes	MIT	yesterday
SEO Ops Structural Checklisttigerless-labs/seo-ops	700	—	~3.3k	Automated safety check: Notes	None	1 mo ago
SEOAgriciDaniel/seo-os	137	2 repos	~3.5k	Automated safety check: Pass	MIT	3 mo ago

Similar skills

Geo Audit
vellum-ai/vellum-assistant
Runs a one-command technical GEO audit on any domain. An agent skill from vellum-ai/vellum-assistant.
1.4k GitHub stars~2k tokensUpdated yesterday
Marketing & SEOAuto-check passed
SEO Visibility Expert
curiositech/some_claude_skills
Comprehensive SEO, discoverability, and AI crawler optimization for web projects.
244 GitHub stars~1.6k tokensUpdated 1 mo ago
Marketing & SEOAuto-check: notes
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 Ops Structural Checklist
tigerless-labs/seo-ops
Checks a site against a deterministic set of structural SEO and GEO checks, either running a crawler-eye report against a URL or reviewing code against the same checklist.
700 GitHub stars~3.3k tokensUpdated 1 mo ago
Marketing & SEOAuto-check: notes
SEO
AgriciDaniel/seo-os
Comprehensive SEO analysis for any website or business type.
137 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

Questions about SEO

What does SEO do?

Audit and improve website discoverability across traditional search, answer engines, and generative search. SEO is an agent skill from magnus919/agent-skills. Audit and improve website discoverability across traditional search, answer engines, and generative search.

When should I use SEO?

SEO fits situations like: on-page content; structured data; question and entity architecture; crawler controls.

How do I install SEO in Claude Code?

Run `npx skills add magnus919/agent-skills --skill seo -a claude-code`. Or copy the skill folder (seo in magnus919/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 magnus919/agent-skills --skill seo -a codex`. Or copy the skill folder (seo in magnus919/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 magnus919/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?

Going by SKILL.md and its folder, SEO needs the command-line tools its instructions call (python3). Our summary lists: Python 3. Compatibility (from SKILL.md): Requires access to the target site or content for implementation and verification; bundled scripts use Python 3.9+ standard library 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does SEO use?

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

How many tokens does SEO use?

About 1.9k tokens (SKILL.md is roughly 7.7k 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 20k 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 Audit (vellum-ai/vellum-assistant, 1.4k stars), SEO Visibility Expert (curiositech/some_claude_skills, 244 stars), GEO-First SEO Audit Tool (zubair-trabzada/geo-seo-claude, 11k stars) and SEO Ops Structural Checklist (tigerless-labs/seo-ops, 700 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains SEO?

magnus919 (a GitHub user) maintains it in magnus919/agent-skills, which has 115 GitHub stars. The repository holds 131 skills in this directory. The repository was last updated on October 10, 2026.

Source: magnus919/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.

Install SEO

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Compatibility

Context cost

Safety

SKILL.md

SEO

Operating model

Terminology and boundaries

Evidence rules

Reference routing

Scripts and templates

Audit output

When not to use

Portability

Files

Compare with similar skills

Similar skills

More from magnus919/agent-skills

Related

Questions about SEO