SEO Audit skill
Diagnose crawlability, indexing and on-page problems with traceable evidence.
Community · Corey Haines| Author | Corey Haines |
|---|---|
| Licence | MIT |
| Source | coreyhaines31/marketingskills · SKILL.md on GitHub |
| Project website | marketing-skills.com |
| Works in | Claude Code · Codex, Gemini CLI, Cursor, Copilot |
| Read from the source on |
seo-audit: Diagnose crawlability, indexing and on-page problems with traceable evidence.
It prioritizes discovery and technical foundations before content recommendations, with references for international SEO and traffic-drop diagnosis.
From the skill's SKILL.md: # SEO Audit
What it does
- Scope an audit, inspect evidence and rank actionable fixes.
What you get
- Evidence-led findings and a prioritized remediation plan.
When to use it
- Audit a site, migration or reported search decline.
When not to use it
- Declaring missing structured data from an incomplete text fetch alone.
What it needs
- Agent plus relevant page exports, rendered browser/crawl access or authorized Search Console data.
Files in the skill
| File or folder | What it is for |
|---|---|
SKILL.md | Entry instructions and task-specific workflow. |
Licence as found in the repository on 2026-11-16: MIT.
Example prompts
Type one of these after installing; naming the skill makes sure it is used.
- Audit these rendered page exports.
- Prioritize the indexing failures.
- Check reciprocal hreflang on these URLs.
How to install seo-audit
Prepare the workflow
Keep references with the skill and configure only the tools needed for the audit. Account data and crawl access are separate; no live audit is executed by this catalogue.
A skill is a folder with a SKILL.md file. You install it once; the agent reads its short description at the start of each session and loads the full instructions only when a request matches. Pick the place you use:
Claude Code: copy the folder into your skills folder
Put the skill's folder in ~/.claude/skills/ to use it in every project on this computer, or in .claude/skills/ inside a repository to share it with everyone who works there (commit it).
git clone --depth 1 https://github.com/coreyhaines31/marketingskills.git
mkdir -p ~/.claude/skills
cp -R marketingskills/skills/seo-audit ~/.claude/skills/Claude Code notices new or changed skills in these folders during the session. If the skills folder did not exist when the session started, run /reload-skills once. Then type /seo-audit or just describe the task.
On Windows, run the commands in Git Bash or WSL, or copy the folder into the same place with File Explorer.
Codex, Gemini CLI, Cursor and GitHub Copilot
These agents read the same SKILL.md folders. The one folder all four accept inside a project is .agents/skills/, so this copies the skill there:
git clone --depth 1 https://github.com/coreyhaines31/marketingskills.git
mkdir -p .agents/skills
cp -R marketingskills/skills/seo-audit .agents/skills/| Agent | Project folder | Your user folder | Notes |
|---|---|---|---|
| OpenAI Codex | .agents/skills/ | ~/.agents/skills/ | Type $ or run /skills to pick a skill; Codex also chooses one when your task matches. |
| Gemini CLI | .agents/skills/.gemini/skills/ | ~/.agents/skills/~/.gemini/skills/ | Or install from Git with gemini skills install <git URL> --path <folder> --consent. Google replaced Gemini CLI with Antigravity CLI for free-tier and Google One users on 18 June 2026; Antigravity uses .agents/skills/ in a project and ~/.gemini/config/skills/ for you. |
| Cursor | .agents/skills/.cursor/skills/ | ~/.agents/skills/~/.cursor/skills/ | Type / in Agent chat to pick a skill. Cursor also reads Claude Code's .claude/skills/ folders. |
| GitHub Copilot | .github/skills/.agents/skills/.claude/skills/ | ~/.copilot/skills/~/.agents/skills/ | Works in Copilot CLI, the cloud agent, and agent mode in VS Code, Visual Studio and JetBrains (IDE support depends on the version). Or run gh skill install OWNER/REPOSITORY SKILL (public preview, GitHub CLI 2.90.0 or later). |
Sources for these steps
Checked against each vendor's documentation on 2026-11-14:
Findings need evidence
Record the affected URL, observed behavior and practical impact. Distinguish confirmed failures from checks that could not be performed.
International relationships
Canonical and language annotations require actual URL and response checks. Avoid turning one broken pair into a claim that every locale relationship is invalid.
Questions about seo-audit
Does this website execute the skill?
No. This is a source-based installation guide. Your agent runs the skill in its own configured environment.
Are full cloud workflows verified here?
No. Generic cloud upload and API execution steps are omitted; source-specific local requirements and host capabilities still apply.
Can a text fetch prove JSON-LD is absent?
No. A fetch may strip scripts or miss client-generated data. Inspect rendered output or an appropriate export before making that finding.
Does it need Search Console for every task?
No. Supplied page evidence can support a scoped review, while indexing and traffic claims require the appropriate real data.
More AI skills
Related skills
Schema Markup skill
Community · Corey HainesImplement and validate JSON-LD that matches visible page content.Programmatic SEO skill
Community · Corey HainesPlan data-driven page sets with unique value, clean URLs and internal links.AI SEO skill
Community · Corey HainesPlan AI-search visibility work while separating citations, recommendations and evidence.Site Architecture skill
Community · Corey HainesDesign page hierarchy, navigation, URL maps and useful internal linking.Free Tools skill
Community · Corey HainesEvaluate free-tool ideas against user value, business fit and maintenance cost.Content Strategy skill
Community · Corey HainesPlan evidence-backed topics, clusters and distribution around the audience’s needs.