off-page-seo

off-page-seo is a skill for Claude Code from huifer/claude-code-seo. It costs 105 tokens per session (4,281 once invoked), scanned A, original, MIT.

An SEO guide focused on signals outside your own website, especially links from other sites and mentions of your brand. It also examines competitors and outlines nine ways to seek or track link opportunities.

In plain words
What is it for?
Use it to review backlink quality and quantity, compare competitor sources, assess potential referring sites, plan outreach methods, and track link-building work.
Why use it?
It helps reveal where a site's reputation comes from, where competitors have an advantage, and which external opportunities may be worth pursuing.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the claude-code-seo plugin — 7 skills, 37 commands, 2 agents shipped together

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.

agentmods
npx agentmods add skills/huifer/claude-code-seo/off-page-seo
Any agent
npx skills add huifer/claude-code-seo --skill off-page-seo
Clone the repo
git clone --depth 1 https://github.com/huifer/claude-code-seo

Made for: Claude Code.

Or install claude-code-seo, the plugin that ships this one along with the rest of its 7 skills, 37 commands, 2 agents.

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 off-page-seo

README.md
[![agentmods](https://agentmods.dev/badge/skills/huifer/claude-code-seo/off-page-seo.svg)](https://agentmods.dev/skills/huifer/claude-code-seo/off-page-seo)
Your own site
<a href="https://agentmods.dev/skills/huifer/claude-code-seo/off-page-seo"><img src="https://agentmods.dev/badge/skills/huifer/claude-code-seo/off-page-seo.svg" alt="Measured on agentmods" height="20"></a>
Per session 105 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,281 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00105 $0.04281
Opus 5 $0.00053 $0.02141
Sonnet 5 $0.00021 $0.00856
Haiku 4.5 $0.00011 $0.00428

Measured 6d ago against content hash b8dbb74aac7c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

off-page-seo 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 6d 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/off-page-seo/SKILL.md · 594 lines

How it starts

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

你是站外 SEO 专家,专注于分析网站的外部权威性和建立高质量的外链策略。

核心职责

当需要进行站外 SEO 分析时,你会:

  1. 分析外链现状 - 评估当前外链质量和数量
  2. 竞争对手外链分析 - 识别竞争对手的外链来源和策略
  3. 提供外链建设策略 - 推荐 9 种有效的外链建设方法
  4. 评估外链机会 - 分析每个潜在外源的价值
  5. 跟踪管理外链 - 提供外链建设活动的跟踪系统

工作流程

步骤 1:外链现状分析

使用工具分析(模拟):

虽然不能直接访问 Ahrefs/Moz,但可以:
- 使用 Google 搜索语法查找外链
- 分析竞争对手的外链来源
- 识别高质量的外链机会

外链质量评估:

评估维度:
- Domain Authority (DA)
- Page Authority (PA)
- 流量(使用 SimilarWeb 估算)
- 相关性
- DoFollow vs NoFollow

外链类型识别:

分类:
- 编辑链接(自然获得)
- 客座博客
- 目录链接
- 论坛签名
- 社交媒体
- 评论链接
- 合作伙伴链接

步骤 2:竞争对手外链分析

识别主要竞争对手:

使用 Google 搜索:
"[主要关键词]"

分析竞争对手外链:

搜索语法:
"competitor name" -site:competitor.com
"competitor name" inurl:blog -site:competitor.com
link:competitor.com(Google 的结果有限)

识别外链差距:

对比:
- 竞争对手有但我们没有的外链
- 高质量的外链来源
- 可以复制的外链策略

步骤 3:9 种外链建设策略

策略 1:客座博客

识别机会:

搜索语法:
"[你的关键词]" "write for us"
"[你的关键词]" "guest post"
inurl:write-for-us "[你的关键词]"
site:medium.com "[你的关键词]"

质量评估:

  • DA > 50
  • 高相关性
  • DoFollow 链接
  • 有真实流量

使用 /guest-blogs 命令获取详细策略。

策略 2:断链建设

寻找断链:

搜索语法:
site:.edu "[你的关键词]" "404"
site:.com "[你的关键词]" "no longer available"
"[你的关键词]" "page not found"

工作流程:

  1. 找到断链页面
  2. 在你的网站找到相关内容
  3. 联系网站管理员
  4. 提供替换内容

使用 /broken-links 命令获取详细指导。

策略 3:摩天大楼技术

实施步骤:

  1. 找到行业内的热门内容
  2. 分析其外链数量和质量
  3. 创建更好的内容
  4. 联系原内容的外链来源

搜索热门内容:

"[你的主题]" popular
"[你的主题]" viral
"[你的主题]" most shared

使用 /skyscraper 命令获取详细指导。

策略 4:HARO (Help a Reporter Out)

使用 HARO 平台:

  • 注册 HARO 账号(helpareporter.com)
  • 订阅相关主题的查询
  • 快速响应记者需求
  • 获得媒体引用

回复要素:

  • 简洁的专家介绍
  • 直接回答问题
  • 提供 credentials
  • 包含联系信息

使用 /haro-opportunities 命令获取详细指导。

策略 5:行业目录提交

识别高质量目录:

质量标准:
- DA > 30
- 相关性强
- 审核严格
- 有真实流量
- DoFollow 链接

搜索行业目录:

"[你的行业]" directory
"[你的行业]" "top companies"
"[你的行业]" "best sites"

使用 /directories 命令获取详细指导。

策略 6:品牌提及监测

搜索未链接的品牌提及:

"your brand" -site:yourbrand.com
"your brand" inurl:blog
"your brand" intext:mentioned

Read the full file on GitHub · 594 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. 6d ago First seen · 594 lines · 105 tokens per session scan A b8dbb74aac7c

Subscribe to this mod's changes

off-page-seo is a skill published in the GitHub repository huifer/claude-code-seo (110 stars, last pushed 8mo ago), licensed MIT. It adds 105 tokens to every session and 4,281 once invoked, about $0.0005 per session on Opus 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-30.

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