seo-audit
Use when reviewing a page or site for organic search, or diagnosing why something isn't ranking: crawl and index signals, on-page elements, content quality, and how to order the fixes.
Install / Use
npx skills add fcakyon/claude-codex-settings --skill seo-auditInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
MarketingSupported Platforms
Our assessment of seo-audit
seo-audit scores 80/100 on our quality scale, 590th of 639 Marketing skills we index.
Its SKILL.md is 3.6 KB long, split into 5 sections and no code examples: a solid amount of guidance for an agent.
With 1,153 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so seo-audit is actively maintained.
- It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.
Automated pattern scan on 2026-11-22. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
seo-audit compared with similar skills
All 4 of these similar skills score higher than seo-audit; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| seo-audit (this skill)by fcakyon | 80 | 1.2k | 59d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 2mo ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 2mo ago | SKILL.md |
| prospectingby coreyhaines31 | 100 | 60.1k | 11d ago | SKILL.md |
| ad-creativeby coreyhaines31 | 100 | 60.1k | 11d ago | SKILL.md |
Frequently asked questions
- How do I install seo-audit?
- Run
npx skills add fcakyon/claude-codex-settings --skill seo-audit. The install tabs above show the steps for each supported agent. - Which AI agents does seo-audit work with?
- It is written for Zed, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is seo-audit safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is seo-audit still maintained?
- The repository was last updated about 2 months ago, so seo-audit is actively maintained.
Skill content
View source on GitHubname: seo-audit description: "Use when reviewing a page or site for organic search, or diagnosing why something isn't ranking: crawl and index signals, on-page elements, content quality, and how to order the fixes." license: MIT
SEO audit
Audit in priority order, because the layers depend on each other. A page that can't be indexed doesn't benefit from a better title.
- Can it be found and indexed? Robots rules, canonical tags, noindex, redirect chains.
- Is the foundation sound? HTTPS, mobile rendering, speed, URL structure.
- Is the page optimized? Title, meta description, headings, keyword alignment, internal links, images.
- Does it deserve to rank? Depth, first-hand experience, sourcing, whether it beats what already ranks.
- Does it have credibility? Who links to it, who cites it.
Work down the list and stop where the evidence stops. Most asks are answered at layers 3 and 4.
What a fetch can and can't tell you
web_fetch returns the server's HTML as text. Everything you report as observed has to come from that, from a source you read, or from the caller.
Readable from a fetch: title tag, meta description, heading order and text, body copy, visible links and their anchor text, canonical tag, robots meta, hreflang in the HTML head, server-rendered JSON-LD, robots.txt and sitemap.xml when you fetch them directly.
Not readable, so not yours to assert: anything JavaScript injects after load, Core Web Vitals and any speed measurement, whether Google has actually indexed a URL, rank position, search volume, traffic, backlink counts, and whole-site facts like orphan pages or crawl budget that need a crawl you can't run.
The trap worth naming: CMS SEO plugins commonly inject JSON-LD client side, so a fetch shows no schema on a page that has plenty. Never conclude "no schema" from a fetch. Report that the server HTML carried none, and send them to the Rich Results Test at https://search.google.com/test/rich-results, which renders JavaScript.
For a check you can't run, name the check and the tool rather than skipping it silently. Search Console covers index coverage and queries; PageSpeed Insights covers Core Web Vitals; a crawler like Screaming Frog covers site-wide structure.
Diagnosing a page that isn't ranking
Work outward from the page before reaching for site-wide theories.
- Does the page target one query, and do the title, H1, URL, and opening paragraph agree on which one? Disagreement here explains more ranking problems than anything technical.
- Is another page on the site competing for the same query? Two mediocre pages on one keyword lose to one good one, and the fix is usually to merge them and redirect.
- Is the intent right? A product page will not rank for a question query however well optimized it is.
- Is it thinner than what ranks? Compare against the pages currently ranking rather than against a word count.
- Did something change? A migration, a redesign, or a template change dated near the drop is the first thing to check, and a drop that starts on a single date usually has a single cause.
References
references/audit-checklist.md: the per-area checks, each marked with whether a fetch can verify it.references/international-seo.md: hreflang, canonical interaction, and locale URL structure for multi-language sites, with the errors that silently void a whole cluster.
Reporting
Give each finding the problem, why it matters for search, the evidence, the fix, and its rank against the others. Open with the few things worth doing first, and close with what you couldn't check and what it would take. Group by layer, not by page, so someone can fix a class of problem once.
Related Skills
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
prospecting
60.1kWhen the user wants to find and qualify prospects for outbound, or asks who to target first, which signal to prioritize, or where to spot buyers with the problem: buying signals, enrichment, verification, account research.
ad-creative
60.1kWhen the user wants to write or judge ad creative, or asks which ad, hook, or angle to run or kill: headlines, primary text, and variations for Google, Meta, LinkedIn, and TikTok, fresh angles when creative fatigues. Test hypotheses name the metric, comparison, and expected direction.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
