seo-audit

seo-audit is a skill for Claude Code, Codex from tranfu-labs/tranfu-skills. It costs 0 tokens per session (1,160 once invoked), scanned A, original, MIT.

A single-page search-engine optimization audit that checks whether a webpage is technically prepared to be found and understood by search engines.

In plain words
What is it for?
Use it to check robots.txt, sitemaps, canonical URLs, language targeting, structured data, page titles, descriptions, headings, links, keywords, and trust signals.
Why use it?
It turns common search-visibility issues into a structured report instead of requiring a developer to inspect each page element manually.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Claude Code.

Good fit Use it to check robots.txt, sitemaps, canonical URLs, language targeting, structured data, page titles, descriptions, headings, links, keywords, and trust signals.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tranfu-labs/tranfu-skills/seo-audit
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 tranfu-labs/tranfu-skills --skill seo-audit
Clone the repo
git clone --depth 1 https://github.com/tranfu-labs/tranfu-skills

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.

agentmods badge for seo-audit

README.md
[![agentmods](https://agentmods.dev/badge/skills/tranfu-labs/tranfu-skills/seo-audit/github.svg)](https://agentmods.dev/skills/tranfu-labs/tranfu-skills/seo-audit)
Your own site
<a href="https://agentmods.dev/skills/tranfu-labs/tranfu-skills/seo-audit"><img src="https://agentmods.dev/badge/skills/tranfu-labs/tranfu-skills/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.

agentmods 80×15 button for seo-audit

Your own site · 80×15
<a href="https://agentmods.dev/skills/tranfu-labs/tranfu-skills/seo-audit"><img src="https://agentmods.dev/badge/skills/tranfu-labs/tranfu-skills/seo-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,160 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01160
Opus 5 $0.00000 $0.00580
Sonnet 5 $0.00000 $0.00232
Haiku 4.5 $0.00000 $0.00116

Measured 12d ago against content hash a7b45eaf885f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, 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 12d 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.

external-skills/seo-audit/SKILL.md · 67 lines

How it starts

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

seo-audit (external thin pointer)

这是一个 external 薄指针 —— 仓库里只存 frontmatter 和推荐者补充内容, 不存 skill body.

首次 tfs install seo-audit 时, install 流程会从 source_url 拉上游 (seo-audit/ 子目录, 含 SKILL.md + Python 脚本 + HTML 报告模板). 上游官方推荐 npx skills add JeffLi1993/seo-audit-skill 一键装.

更新内容请直接看上游 README / SKILL.md, 别在本仓库改 body.

推荐场景

适用:

  • 落地页 / 营销页上线前自查 (TDK / H1 / canonical / 内链 / 关键词)
  • 公司站季度 SEO 体检, 出 HTML 报告给团队过
  • 跟 Cursor / Claude Code 配合, 把报告 finding 喂回让 AI 逐项 fix

不适用: 全站爬虫 / 关键词排名追踪 / 反链分析 (走 Ahrefs / Semrush); 不审 SPA 客户端渲染内容 (需先 SSR).

同类 Skill 对比

由 tranfu-publish 起草, 推荐者签字.

公司库内

  • web-design-guidelines — 审 UI 代码合规 (a11y / focus / forms); 本 skill 区别: 不审代码本身, 而是审"上线后能不能被搜到", 走搜索引擎可见性维度
  • ui-ux-pro-max — 设计参考库 (风格 / 配色 / 字体); 本 skill 区别: 设计前 vs SEO 后, 三者形成"设计 → 代码 → 搜索"全链路闭环

外部世界

  • Lighthouse SEO audit — Chrome 官方 SEO 审计 (5-10 项); 本 skill 区别: 检查项更深 (20+ 含 hreflang / Schema / E-E-A-T 信任页 / 关键词布局等 Lighthouse 不查的)
  • Screaming Frog SEO Spider — 老牌全站爬虫 + GUI; 本 skill 区别: 单页深度审 + LLM 语义判断, 不是全站爬, 适合精审而非批量

本 skill 独特价值

  • Script + LLM 混合架构 — Python 跑确定性检查, LLM 跑语义判断
  • 输出独立 HTML 报告含 Priority Actions 排序, 可直接转交团队
  • 跑 RFC 9309 / JSON-LD / hreflang 等深度解析, 检查覆盖面广

使用技巧

由 tranfu-publish 引导起草.

材料方案

  • 装上游推荐 npx skills add JeffLi1993/seo-audit-skill, 一次铺好两个 tier (basic + full)
  • 准备目标 URL (HTTPS, 可公网访问, 非登录态)
  • Python 3 + 网络 (脚本要 fetch 目标页 + robots.txt + sitemap)

推荐用法

  • 第一次跑: 直接说 "audit this page: https://example.com"
  • 报告产物: reports/<hostname>-audit.html, 自己读完留要的, 丢不要的
  • 二阶段: 把 Priority Actions 段贴回 Claude/Cursor, 让 AI 逐项 fix

已知限制

  • 只审单页, 不是全站爬虫
  • SPA 客户端渲染页可能漏内容 (脚本拉原始 HTML)
  • 部分检查依赖外部 API (full tier 用 CrUX/GSC, basic tier 不依赖)

Read the full file on GitHub · 67 lines

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.

  1. 12d ago First seen · 67 lines · 0 tokens per session scan A a7b45eaf885f

Subscribe to this mod's changes

seo-audit is a skill published in the GitHub repository tranfu-labs/tranfu-skills (2 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,160 tokens. 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens