seo-audit SKILL.md skillA
seo-audit from kulykivska/claude-plugins is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kulykivska/claude-plugins/seo-audit@git:20260922.a4bd47bPins git:20260922.a4bd47b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kulykivska/claude-plugins
- Path
seo/skills/seo-audit/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260922.a4bd47b, committed Sep 22, 2026
- First version recorded
- Jul 11, 2026
- Size
- 1,419 bytes
- Repository stars
- 6
- License
- MIT
Run an SEO audit of a site, section, or single page. Trigger on "check SEO", "seo audit", "why are we not showing up on Google", "optimize this page for search", or after shipping new public pages. Delegates the deep pass to the seo-strategist subagent and turns the result into applied fixes.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# SEO audit ## Steps 1. **Scope**: one page, a section (e.g. /race/*), or the whole site. Identify the repo templates behind the target pages. 2. **Snapshot what a bot sees**: `curl -A "Googlebot" <url>` and check the returned HTML for title/meta/OG/schema BEFORE JS. For an SPA, this is where server-side meta injection either works or doesn't. 3. **Delegate**: spawn the `seo-strategist` subagent with the scope, the fetched evidence, and repo paths. For big scopes spawn one per section in parallel. 4. **Apply**: implement the top fixes it returns (meta/OG/schema/sitemap/ robots changes are code; content gaps become a page list with target queries). Anything touching prediction pages must respect the access gating policy (free teaser visible to bots, paid content locked). 5. **Verify**: re-curl the fixed pages, validate schema (Google Rich Results test via WebFetch), confirm sitemap entries, request re-indexing steps. 6. Track: keep the running SEO roadmap in the project's docs so audits build on each other instead of restarting.
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_fvqixbiqis6re4wy/1f4a6d15ebf187d74832e1c6dbdb355f7b9fb4af59377efe00ca0a3d65e5c87d.json
Then /plugin install seo-audit@markdownregistry-fvqixbiqis6re4wy in Claude Code. It installs git:20260922.a4bd47b, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add kulykivska/claude-plugins/seo-audit@sha256:1f4a6d15ebf187d7The line at the top of this page pins the label git:20260922.a4bd47b, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_fvqixbiqis6re4wy)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in kulykivska/claude-plugins/seo-audit since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of seo-audit from somewhere else? Ask it: where did my seo-audit come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 2 versions of this file, between Jul 11, 2026 and Sep 22, 2026, about one every 72 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260922.a4bd47b latest | 2026-09-22 | a4bd47b | 1,419 B | A | view · diff |
| git:20260711.2d30535 | 2026-07-11 | 2d30535 | 1,470 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/seo-audit/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (1419 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
kulykivska/claude-plugins · 6 stars · license MIT · pushed 2026-11-13 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_fvqixbiqis6re4wy GET https://markdownregistry.com/api/v1/resolve?ref=kulykivska/claude-plugins/seo-audit GET https://markdownregistry.com/api/v1/blob/1f4a6d15ebf187d74832e1c6dbdb355f7b9fb4af59377efe00ca0a3d65e5c87d
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from kulykivska/claude-plugins
Every file in kulykivska/claude-plugins