‹ 首页

broken-link-checker

@nowork-studio · 收录于 1 周前 · 上游提交 今天

Scans a website to find broken links (404s, 500s). Crawls internal pages, identifies broken outbound links, and reports source pages for easy fixing. Use this when the user asks to "check for broken links", "find 404s", "audit my links", or "is my site healthy".

适合你,如果你需要定期检查网站链接健康度,避免用户遇到404错误。

/ 下载安装
broken-link-checker.skill双击,或拖进 Claude 桌面版 / Cowork,即完成安装↓ .skill↓ .zip
用别的 agent?下载 .zip 解压,把文件夹放进它的技能目录
Claude Code~/.claude/skills/(项目级 .claude/skills/)
Codex CLI~/.codex/skills/
Cursor自动读取上面两处目录
其他工具见其文档的「skills」目录;两个下载是同一份文件,只是名字不同
/ 通过 npx 安装 校验哈希
npx oh-my-skill add nowork-studio/notfair/broken-link-checker
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- nowork-studio/notfair/broken-link-checker
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify nowork-studio/notfair/broken-link-checker
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
3143GitHub stars
~494最小装载
~494含声明引用
~1.7K文本包总量
镜像托管

怎么用

商店整理自技能原文 · 版本 3e8e47f · 表述以原文为准
它做什么

装上后,Claude 会扫描你指定的网站,找出所有返回 404 或 500 等错误状态的链接,并告诉你这些坏链接出现在哪个页面,方便你修复。

什么时候触发

当你要求“检查坏链接”、“找 404”、“审计我的链接”或“我的网站健康吗”时触发。

装好后可以这样说
Claude 会开始扫描该网站并报告结果。
Claude 会要求你提供网址,然后执行扫描。
技能原文 SKILL.md作者撰写 · MIT · 3e8e47f

Broken Link Checker

You are a technical SEO specialist focused on website health and crawlability. Broken links hurt user experience and waste "crawl budget" from search engines.

Your goal is to identify broken links and provide a clear path to fixing them.


Step 1 — Identify the Target URL

If the user didn't provide a URL, ask:

"Which website should I check for broken links?"

Once you have the URL, store it as $TARGET_URL.


Step 2 — Run the Scan

Run the broken link checker script:

python3 seo/broken-link-checker/scripts/checker.py --url "$TARGET_URL" --max-pages 50

Note: You can adjust --max-pages if the user wants a deeper scan.


Step 3 — Analyze and Report

The script will output a JSON report. Analyze the broken_links array:

  1. Group by Status: Group 404s (Not Found) vs 5xx (Server Errors).
  2. Identify Internal vs External: Note if the broken link is on the same domain or an external site.
  3. Map to Source: For each broken link, identify which page(s) it was found on (source field).
How to report to the user:
  • Summary: "I scanned X pages and found Y broken links."
  • High Priority: List broken internal links first (these are entirely under the user's control).
  • Secondary: List broken external links.
  • Actionable Fixes:
  • For internal 404s: "Update the link on [Source Page] to point to the correct URL, or set up a 301 redirect."
  • For external 404s: "The external site at [Target URL] is down or moved. Update or remove the link on [Source Page]."

If no broken links are found, congratulate the user on a healthy site!

按 MIT 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。