A source-code audit for on-page search engine optimization, the practices that help search engines understand and rank web pages. It checks files such as HTML, JSX, TSX, and Next.js pages and produces a Markdown report.

Checking page titles, descriptions, headings, images, and other on-page SEO details in website source files.

It finds page-structure and metadata problems that can make a site harder for search engines to interpret. The report pairs findings with suggested fixes.

seo-audit — Skill for Claude Code and Codex by Shiven0504

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add Shiven0504/claude-skills-collection --skill seo-audit

Clone the repo

git clone --depth 1 https://github.com/Shiven0504/claude-skills-collection

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/shiven0504/claude-skills-collection/seo-audit/github.svg)](https://agentmods.dev/skills/shiven0504/claude-skills-collection/seo-audit)

Your own site

<a href="https://agentmods.dev/skills/shiven0504/claude-skills-collection/seo-audit"><img src="https://agentmods.dev/badge/skills/shiven0504/claude-skills-collection/seo-audit/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/shiven0504/claude-skills-collection/seo-audit"><img src="https://agentmods.dev/badge/skills/shiven0504/claude-skills-collection/seo-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 121 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,010 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00121	$0.02010
Opus 5.5	$0.00048	$0.00804
Sonnet 5.5	$0.00024	$0.00402
Haiku 4.5	$0.00012	$0.00201

Measured 2mo ago against content hash d18916cea78d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

seo-audit scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/custom/seo-audit/SKILL.md · 184 lines

How it starts

The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.

On-Page SEO Audit

Analyze source code files for on-page SEO issues and produce a clear, actionable markdown report. The goal is to catch real problems that hurt search rankings — not to nitpick or generate noise.

How to run an audit

Identify the files to audit. If the user points to specific files, use those. If they say "audit my site" or similar, look for page-level files — things like index.html, Next.js pages (app/**/page.tsx, pages/**/*.tsx), or layout files. Use Glob to find them.
Read each file and check against the checklist below.
Produce the report in the format described at the bottom.

What to check

Work through each section for every page file. Not every check applies to every file — use judgment. A shared <Header> component won't have a <title> tag, and that's fine.

Title tag

The <title> element (or metadata.title in Next.js) is the single most important on-page SEO signal.

Check for:

Missing title entirely
Title that's too short (under 20 characters) or too long (over 60 characters) — search engines truncate long titles
Generic/meaningless titles like "Home", "Page", "Untitled", or the framework default
Duplicate titles across pages (if auditing multiple pages)

Why it matters: The title tag is displayed as the clickable headline in search results. A clear, descriptive title with relevant keywords directly affects click-through rate and ranking.

Meta description

The <meta name="description"> tag (or metadata.description in Next.js).

Check for:

Missing entirely — search engines will auto-generate one, but it's usually worse
Too short (under 50 characters) or too long (over 160 characters)
Doesn't summarize the page content or include relevant keywords
Duplicate descriptions across pages

Why it matters: While not a direct ranking factor, the meta description appears as the snippet in search results and heavily influences click-through rate.

Heading structure

Read the full file on GitHub · 184 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 184 lines · 121 tokens per session scan A d18916cea78d

Subscribe to this mod's changes

seo-audit is a skill published in the GitHub repository Shiven0504/claude-skills-collection (6 stars, last pushed 7mo ago), licensed MIT. It adds 121 tokens to every session and 2,010 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Marketing and SEO

seo-audit next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
seo-auditShiven0504/claude-skills-collection	Skill	6	7mo ago	MIT	A	121	Claude Code, Codex
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code