关于 link-checker
用于检查和修复 Webflow 网站失效或不安全链接的审计技能，面向维护网站内容的团队。它覆盖静态页面与 CMS 内容，并在应用修复前提供建议和确认步骤。
主要功能
- 01扫描静态页面和 CMS 链接
- 02识别失效、HTTP 和重定向链接
- 03按状态和位置汇总检查结果
- 04提出链接修复建议
- 05经确认后更新页面或 CMS 内容
适用场景
- 01检查网站中的失效链接
- 02将可用的 HTTP 链接升级为 HTTPS
- 03审查博客文章中的链接
- 04修复静态页面或 CMS 链接
MCP 相关
通过 Webflow MCP 提取静态页面和 CMS 中的链接，并更新链接内容；静态页面修复需要连接 Designer，CMS 修改与发布使用相应的 CMS 工具。
安装
复制下面的命令，在终端中运行。
$
npx skills add https:/安装后在 Claude Code 中输入/link-checker确认已加载。
详细介绍
链接检查器
检查并修复 Webflow 网站中失效或不安全的链接，以改善 SEO 和用户体验。
重要提示
所有操作都必须使用 Webflow MCP 工具：
- 开始前，使用 Webflow MCP 的
webflow_guide_tool获取最佳实践 - 使用 Webflow MCP 的
data_sites_tool，并将 action 设为list_sites，确定可用的网站 - 使用 Webflow MCP 的
data_sites_tool，并将 action 设为get_site，获取网站详情 - 使用 Webflow MCP 的
data_pages_tool，并将 action 设为list_pages，获取所有页面 - 使用 Webflow MCP 的
data_pages_tool，并将 action 设为get_page_content，从静态页面中提取链接 - 使用 Webflow MCP 的
data_pages_tool，并将 action 设为update_static_content，修复静态页面中的链接（需要 Designer） - 使用 Webflow MCP 的
data_cms_tool，并将 action 设为get_collection_list，获取所有 CMS 集合 - 使用 Webflow MCP 的
data_cms_tool，并将 action 设为get_collection_details，获取集合架构 - 使用 Webflow MCP 的
data_cms_tool，并将 action 设为list_collection_items，获取包含链接的 CMS 项目 - 使用 Webflow MCP 的
data_cms_tool，并将 action 设为update_collection_items，修复 CMS 中的链接（草稿） - 使用 Webflow MCP 的
data_cms_tool，并将 action 设为publish_collection_items，发布已修复的 CMS 项目 - 不得使用任何其他工具或方法执行 Webflow 操作
- 所有工具调用都必须包含必需的
context参数（15–25 个单词，使用第三人称视角） - 修复静态页面链接需要连接 Designer
操作说明
阶段 1：选择网站并发现内容
- 获取网站信息：使用 Webflow MCP 的
data_sites_tool，并将 action 设为list_sites，确定目标网站 - 确认范围：询问用户希望检查以下哪些内容：
- 仅静态页面
- 仅 CMS 内容
- 静态页面和 CMS 内容
- 列出页面：使用 Webflow MCP 的
data_pages_tool，并将 action 设为list_pages，获取所有页面 - 列出集合：使用 Webflow MCP 的
data_cms_tool，并将 action 设为get_collection_list，获取所有 CMS 集合
阶段 2：提取并验证链接
- 提取静态页面中的链接：对每个页面使用 Webflow MCP 的
data_pages_tool，并将 action 设为get_page_content- 找出所有链接元素（Link、Button、TextLink、LinkBlock）
- 记录：pageId、nodeName、URL、链接文本
- 提取 CMS 中的链接：对每个集合使用 Webflow MCP 的
data_cms_tool，并将 action 设为list_collection_items- 找出 Link 字段以及包含链接的 Rich Text 字段
- 记录：collectionId、itemId、fieldName、URL
- 验证每个链接：测试 URL 是否可访问
- 检查是否存在 4xx/5xx 错误（失效链接）
- 检查 HTTP 与 HTTPS（不安全链接）
- 测试 HTTP 是否有对应的 HTTPS 版本
- 标记重定向（3xx 状态码）
- 对结果进行分类：
- ✅ 可用链接（2xx 状态）
- ❌ 失效链接（4xx/5xx 错误）
- ⚠️ 不安全链接（有 HTTPS 版本时仍使用 HTTP）
- 🔄 重定向（3xx 状态）
- ⚪ 需要人工检查（超时、DNS 错误等）
阶段 3：分析与报告
- 计算统计数据：
- 扫描的链接总数
- 按类型统计的链接（内部链接与外部链接）
- 按状态统计的链接（可用、失效、不安全、重定向）
- 按位置统计的链接（静态页面与 CMS）
- 生成健康评分：计算链接健康度（0–100）
- 可用链接：每个加 1 分
- 失效链接：每个减 5 分
- 不安全链接：每个减 2 分
- 重定向：每个减 1 分
- 归一化至 0–100 分
- 找出关键问题：确定修复优先级
- 🔴 严重：高流量页面上的失效链接
- ⚠️ 警告：不安全的 HTTP 链接
- 💡 建议：优化重定向
阶段 4：生成建议并审批
- 生成修复建议：针对每个有问题的链接，建议修复方式
- 链接失效：移除链接或更新为正确的 URL
- 链接不安全：将 HTTP 升级为 HTTPS
- 重定向：更新为最终目标 URL
- 显示带验证结果的预览：
[1] ✓ 修复不安全链接 页面：关于我们 元素：按钮“了解更多” 当前：https://example.com 建议：https://example.com ✅ 已验证 HTTPS 版本可正常访问 [2] ⚠️ 修复失效链接 页面：博客文章“入门指南” 元素：文本链接 当前：https://oldsite.com/page 建议：[移除链接或提供正确的 URL] ❌ URL 返回 404 - 需要人工审核 - 实施精细化审批：询问用户要应用哪些修复
- 输入编号以跳过（例如，“2,4”）
- 输入“all”以应用所有自动修复
- 输入“none”以取消
- 单独标记需要人工审核的项目
阶段 5：执行并确认
- 修复静态页面：使用 Webflow MCP 的
data_pages_tool，并指定操作update_static_content- 需要连接 Designer
- 更新节点中的链接 URL
- 每批处理 20 个链接
- 修复 CMS 内容：使用 Webflow MCP 的
data_cms_tool，并指定操作update_collection_items- 直接更新链接字段
- 更新富文本字段中的链接
- 每批处理 50 个项目
- 发布更改（如有请求）：使用 Webflow MCP 的
data_cms_tool，并指定操作publish_collection_items - 显示进度：对于大型操作，显示进度指示器
- 生成最终报告：
- 已扫描链接：X
- 已修复链接：Y
- 需要人工审核的链接：Z
- 健康评分提升：修复前 → 修复后
阶段 6：验证并提出建议
- 验证修复：重新检查已修复的链接，确认修复成功
- 报告失败项：明确指出任何修复失败的项目
- 提出建议：
- 定期安排链接检查（每月/每季度）
- 为关键外部链接设置监控
- 对已更改的 URL 考虑使用 301 重定向
- 导出报告（可选）：提供导出检查结果的选项
示例
示例 1：完整站点审计
用户提示：
Run a complete link check on my site and fix any issues
步骤 1：选择站点
🔍 Link Checker: Site Selection
Available sites:
1. Company Website
2. Blog Site
3. Portfolio
Which site would you like to audit? (1/2/3)
步骤 2：确认范围
📋 Link Checker Scope
What would you like to check?
1. Static pages only (faster)
2. CMS content only
3. Both static pages and CMS content (comprehensive)
Recommendation: Option 3 for complete audit
Your choice? (1/2/3)
步骤 3：提取并验证
🔄 Scanning Links...
Progress: ████████████████████ 100%
Found 247 links:
├── Static pages: 89 links (15 pages)
├── CMS content: 158 links (3 collections)
│ ├── Blog Posts: 142 links
│ ├── Team Members: 12 links
│ └── Products: 4 links
Validating links...
Progress: ████████████████████ 100% (247/247 checked)
✅ Working: 215 links (87%)
❌ Broken: 8 links (3%)
⚠️ Insecure: 18 links (7%)
🔄 Redirects: 6 links (2%)
步骤 4：分析报告
📊 Link Health Report: Company Website
Overall Health Score: 76/100 ⚠️
## Issues Found:
### 🔴 Critical: Broken Links (8)
├── [1] Page: "About Us"
│ └── Link to: https://partner-site.com/old-page
│ Status: 404 Not Found
│ Impact: High (homepage)
│
├── [2] CMS: Blog Post "Product Launch"
│ └── Link to: https://press-release.com/announcement
│ Status: 404 Not Found
│ Impact: Medium
│
├── [3-8] 6 more broken links...
### ⚠️ Warning: Insecure Links (18)
├── [9] Page: "Contact"
│ └── Link: http://social-media.com/company
│ Fix: https://social-media.com/company
│ ✅ HTTPS verified working
│
├── [10] CMS: Blog Post "Getting Started"
│ └── Link: http://tutorial-site.com
│ Fix: https://tutorial-site.com
│ ✅ HTTPS verified working
│
├── [11-26] 16 more insecure links...
### 💡 Suggestion: Redirects (6)
├── [27] Page: "Services"
│ └── Link: https://example.com/old-url
│ Redirects to: https://example.com/new-url
│ Suggestion: Update to final destination
│
├── [28-32] 5 more redirects...
---
💡 Recommendations:
1. Fix 8 broken links immediately (SEO impact)
2. Upgrade 18 HTTP links to HTTPS (security)
3. Update 6 redirects to final URLs (performance)
Estimated time to fix: ~5 minutes
步骤 5：修复预览
🔧 Proposed Fixes (26 total)
### Automatic Fixes Available (24):
[1] ✓ Upgrade to HTTPS
Page: Contact
Element: Button "Follow Us"
Current: http://social-media.com/company
New: https://social-media.com/company
✅ HTTPS verified working
[2] ✓ Upgrade to HTTPS
CMS: Blog Posts > "Getting Started" > content field
Current: http://tutorial-site.com
New: https://tutorial-site.com
✅ HTTPS verified working
[3] ✓ Update redirect
Page: Services
Element: Text link "Learn more"
Current: https://example.com/old-url
New: https://example.com/new-url
✅ Final destination verified
[4-24] ... 21 more automatic fixes
### Manual Review Required (2):
[25] ⚠️ Broken link - needs correction
Page: About Us
Element: Button "View Partner Site"
Current: https://partner-site.com/old-page
Issue: 404 Not Found
Action needed: Provide correct URL or remove link
[26] ⚠️ Broken link - needs correction
CMS: Blog Posts > "Product Launch" > content field
Current: https://press-release.com/announcement
Issue: 404 Not Found
Action needed: Update with correct URL or remove
---
Which fixes would you like to apply?
- Type "all" to apply all 24 automatic fixes
- Type numbers to skip (e.g., "3,5,7")
- Type "none" to cancel
步骤 6：用户批准“all”后
✅ Applying Fixes...
Progress: ████████████████████ 100%
Static Pages:
- Updated 8 links on 5 pages
- ✅ Contact page: 3 links fixed
- ✅ Services page: 2 links fixed
- ✅ About page: 1 link fixed
- ✅ Blog page: 2 links fixed
CMS Content:
- Updated 16 links in 12 items
- ✅ Blog Posts: 14 links fixed
- ✅ Team Members: 2 links fixed
---
🎉 Link Fixes Complete!
Summary:
- Links scanned: 247
- Links fixed: 24 ✅
- Manual review needed: 2 ⚠️
- Failed: 0 ❌
Health Score: 76 → 95 (+19) ✨
---
⚠️ Manual Review Items:
[1] About Us page - broken partner link
Current: https://partner-site.com/old-page
Action: Update or remove manually
[2] Blog post "Product Launch" - broken press release
Current: https://press-release.com/announcement
Action: Update or remove manually
---
💡 Next Steps:
1. Fix the 2 manual review items
2. Re-run link checker in 1 month
3. Set up monitoring for critical external links
4. Consider 301 redirects for any URL changes
Would you like to export this report? (yes/no)
示例 2：仅检查 CMS 链接
用户提示：
Check all links in my blog posts
步骤 1：选择集合
🔍 Link Checker: CMS Collections
Found 3 collections:
1. Blog Posts (47 items)
2. Team Members (8 items)
3. Categories (6 items)
You requested blog posts. Checking "Blog Posts" collection...
步骤 2：提取链接
🔄 Extracting Links from Blog Posts...
Progress: ████████████████████ 100% (47/47 items)
Found 142 links in Blog Posts:
├── Link fields: 23 links
├── Rich Text content: 119 links
└── Total unique URLs: 87 (55 appear multiple times)
Validating links...
Progress: ████████████████████ 100% (87/87 unique URLs checked)
Results:
✅ Working: 79 links (91%)
❌ Broken: 3 links (3%)
⚠️ Insecure: 5 links (6%)
🔄 Redirects: 0 links
步骤 3：问题报告
📊 Blog Posts Link Health: 91/100 ✅
## Issues Found:
### 🔴 Broken Links (3):
[1] Post: "Getting Started with Webflow"
Field: content (Rich Text)
Link: https://old-docs.example.com/guide
Status: 404 Not Found
Appears in: 3 posts
[2] Post: "Best Practices 2024"
Field: external-link (Link)
Link: https://expired-resource.com
Status: 410 Gone
[3] Post: "Tutorial Series Part 3"
Field: content (Rich Text)
Link: https://video-host.com/deleted-video
Status: 404 Not Found
### ⚠️ Insecure Links (5):
[4] Post: "Case Study: Company A"
Field: content (Rich Text)
Link: http://company-a-site.com
Fix: https://company-a-site.com
✅ HTTPS available and working
[5-8] 4 more insecure links...
---
🔧 Proposed Fixes:
[1] ⚠️ Remove broken link (manual review)
Posts affected: 3 (Getting Started, Tutorial 1, Tutorial 2)
Link: https://old-docs.example.com/guide
Suggestion: Update to new docs URL if available
[2] ⚠️ Remove broken link (manual review)
Post: "Best Practices 2024"
Link: https://expired-resource.com
Suggestion: Remove or replace with alternative
[3] ⚠️ Remove broken link (manual review)
Post: "Tutorial Series Part 3"
Link: https://video-host.com/deleted-video
Suggestion: Update with new video URL
[4] ✓ Upgrade to HTTPS
Post: "Case Study: Company A"
Current: http://company-a-site.com
New: https://company-a-site.com
✅ HTTPS verified working
[5-8] ... 4 more HTTPS upgrades
---
Which fixes would you like to apply?
- Type "4-8" to apply only HTTPS upgrades
- Type "all" for all automatic fixes
- Type "none" to cancel
示例 3：仅检查静态页面（快速检查）
用户提示：
Quick check on my static pages for broken links
响应：
🔍 Quick Link Check: Static Pages
Scanning 15 static pages...
Progress: ████████████████████ 100%
Found 89 links across 15 pages
Validation Results:
✅ All links working! (89/89)
Health Score: 100/100 ✨
Your static pages have no broken or insecure links.
💡 Tip: Run a full audit including CMS content for comprehensive coverage.
示例 4：修复特定问题
用户提示：
I have some broken links on my About page. Can you fix them?
响应：
🔍 Checking Links on "About" Page...
Found 12 links on About page
Validation Results:
✅ Working: 9 links
❌ Broken: 2 links
⚠️ Insecure: 1 link
---
Issues Found:
[1] ❌ Broken: Partner site link
Element: Button "Visit Partner"
Link: https://partner-old-site.com
Status: 404 Not Found
Fix: Manual review needed
[2] ❌ Broken: Team member profile
Element: Text link "Meet Sarah"
Link: /team/sarah-old-profile
Status: 404 Not Found
Fix: Update to /team/sarah-johnson?
[3] ⚠️ Insecure: Social media link
Element: Link "Follow us"
Link: http://social.com/company
Fix: https://social.com/company
✅ HTTPS verified
---
Which fixes would you like to apply?
- Type "3" to only fix the insecure link
- Type "2,3" to fix items 2 and 3
- Type "all" for automatic fixes
- Type "none" to cancel
Note: Item [1] requires manual correction with correct URL
指南
阶段 1：发现阶段的最佳实践
站点选择：
- 使用
data_sites_tool并指定操作list_sites，获取可用站点 - 切勿假设站点 ID
- 与用户确认站点名称
范围定义：
- 询问检查静态页面、CMS，还是两者都检查
- 根据范围估算耗时：
- 仅静态页面：1-3 分钟
- 仅 CMS：2-5 分钟（取决于项目数量）
- 整个站点：5-10 分钟
集合选择：
- 列出所有集合及其项目数量
- 如果用户指定了集合，则重点检查该集合
- 如果用户要求检查“所有 CMS”，则检查所有集合
阶段 2：链接提取最佳实践
静态页面链接提取：
- 使用
data_pages_tool，并将 action 设为get_page_content，获取页面节点 - 查找以下节点类型：
- Link（a 标签）
- Button（带链接）
- TextLink
- LinkBlock
- 提取 href/url 属性
- 记录链接文本以便报告
- 跟踪 nodeId，以便后续修复
CMS 链接提取：
- 使用
data_cms_tool，并将 action 设为get_collection_details，识别 Link 和 Rich Text 字段 - 使用
data_cms_tool，并将 action 设为list_collection_items，获取所有条目 - 对于 Link 字段：直接提取 URL
- 对于 Rich Text 字段：解析 HTML 以提取 标签
- 跟踪 collectionId、itemId、fieldName，以便修复
链接验证：
- 测试每个唯一 URL（避免重复测试）
- 优先使用 HEAD 请求（速度更快）
- 如果 HEAD 失败，则回退到 GET
- 处理超时（最长 10 秒）
- 对于 HTTP 链接：测试对应的 HTTPS 链接
- 记录状态码和最终 URL（重定向后）
分类规则：
✅ Working (2xx):
- 200 OK
- 201 Created
- 204 No Content
❌ Broken (4xx/5xx):
- 400 Bad Request
- 401 Unauthorized
- 403 Forbidden
- 404 Not Found
- 410 Gone
- 500 Internal Server Error
- 502 Bad Gateway
- 503 Service Unavailable
⚠️ Insecure (HTTP):
- URL starts with http://
- HTTPS equivalent exists and returns 2xx
- Mark as "upgrade to HTTPS"
🔄 Redirects (3xx):
- 301 Moved Permanently
- 302 Found
- 307 Temporary Redirect
- 308 Permanent Redirect
⚪ Manual Review:
- Timeout errors
- DNS resolution failures
- Connection refused
- SSL certificate errors
阶段 3：分析最佳实践
健康评分计算：
Formula:
1. Base score = 100
2. Working links: No change
3. Broken links: -5 points each
4. Insecure links: -2 points each
5. Redirects: -1 point each
6. Minimum score: 0
7. Maximum score: 100
Example:
- Total links: 200
- Working: 180 (no penalty)
- Broken: 5 (−25 points)
- Insecure: 10 (−20 points)
- Redirects: 5 (−5 points)
- Score: 100 − 25 − 20 − 5 = 50/100
问题优先级排序：
🔴 Critical (fix immediately):
- Broken links on homepage
- Broken links on high-traffic pages
- Broken links in navigation
- 404 errors on important external references
⚠️ Warning (fix soon):
- Insecure HTTP links (security risk)
- Broken links on blog posts
- Broken links in footer
- 410 Gone errors
💡 Suggestion (optimize):
- 301 redirects (update to final destination)
- 302 redirects (may change, monitor)
- External links with slow response times
需报告的统计数据：
Essential:
- Total links scanned
- Working links count & percentage
- Broken links count & percentage
- Insecure links count & percentage
- Redirect links count & percentage
Detailed:
- Links by location (static vs CMS)
- Links by type (internal vs external)
- Most common issues
- Pages/items with most issues
- External domains with most broken links
阶段 4：建议生成最佳实践
自动修复标准：
Can auto-fix:
✅ HTTP → HTTPS (if HTTPS verified working)
✅ Redirects → Final destination (if final URL verified)
✅ Relative URLs → Absolute URLs (for external sites)
Needs manual review:
⚠️ Broken links (404, 410, 5xx) - requires correct URL
⚠️ HTTP with no HTTPS equivalent
⚠️ Timeouts or connection errors
⚠️ SSL certificate errors
⚠️ Authentication required (401, 403)
预览格式：
[X] ✓ Auto-fix available
Location: [Page name or CMS item]
Element: [Element type + text]
Current: [Current URL]
New: [Proposed URL]
✅ Verification: [Status]
[Y] ⚠️ Manual review needed
Location: [Page name or CMS item]
Element: [Element type + text]
Current: [Current URL]
Issue: [Error description]
Suggestion: [What to do]
细粒度审批：
- 从 1 开始为每项修复编号
- 首先显示所有自动修复
- 单独显示需要人工审核的项目
- 允许用户选择特定修复项
- 选项："all"、"none" 或指定编号
- 示例："1,3,5-10" 会应用修复项 1、3 和 5 到 10
阶段 5：执行最佳实践
静态页面更新：
Requirements:
- Designer connection required
- Use data_pages_tool with action update_static_content
- Update nodes array with new URLs
- Process in batches of 20 links per page
- Verify updates after each batch
Error Handling:
- If Designer not connected: Report and skip static pages
- If update fails: Mark link and continue with others
- Report partial successes separately
CMS 更新：
For Link Fields:
- Direct update: fieldData[fieldName] = "new-url"
- Use data_cms_tool with action update_collection_items
- Option: update live or draft
For Rich Text Fields:
- Parse HTML content
- Find and replace <a> tags
- Preserve other HTML formatting
- Update fieldData[fieldName] with new HTML
Batch Processing:
- Process 50 items per batch
- Show progress for large collections
- Handle API rate limits gracefully
发布：
Ask user:
"Would you like to publish the changes immediately?"
- Yes: Use data_cms_tool with action publish_collection_items
- No: Leave as drafts
For static pages:
- Changes are immediate (Designer updates live)
- Warn user that static page changes are live
阶段 6：验证最佳实践
重新验证：
- 重新检查所有已修复的链接
- 确认状态已更改（404 → 200，HTTP → HTTPS）
- 报告任何未生效的修复
- 计算新的健康评分
失败报告：
If any fixes failed:
❌ Fixes that failed (X):
[1] Failed to update
Location: Contact page
Reason: Designer connection lost
Action: Reconnect Designer and retry
[2] URL still broken
Location: Blog post "Guide"
Reason: HTTPS version returned 404
Action: Manual correction needed
成功报告：
✅ Summary:
Before:
- Health Score: 76/100
- Broken links: 8
- Insecure links: 18
- Redirects: 6
After:
- Health Score: 95/100 (+19)
- Broken links: 2 (6 fixed, 2 need manual review)
- Insecure links: 0 (18 fixed)
- Redirects: 0 (6 fixed)
Changes:
- Static pages: 8 links updated on 5 pages
- CMS content: 16 links updated in 12 items
- Total fixes: 24 ✅
- Manual review: 2 ⚠️
建议：
Always provide:
1. Schedule for next check (monthly/quarterly)
2. Monitoring suggestions for critical links
3. Best practices for avoiding broken links
4. URL redirect strategies if applicable
Example:
💡 Recommendations:
1. **Schedule regular checks**
- Run link checker monthly for active sites
- Run quarterly for static sites
- Set calendar reminder
2. **Monitor critical external links**
- Key partners: company-a.com, partner-site.com
- Documentation: docs.example.com
- Social media profiles
3. **Set up URL redirects**
- If changing URLs, create 301 redirects
- Test redirects before going live
- Keep redirect map updated
4. **Best practices**
- Test external links before adding
- Use relative URLs for internal links
- Avoid deep linking to external pages
- Verify links after major redesigns
阶段 7：导出选项
报告格式：
Offer to export findings:
1. **Markdown** - Human-readable report
- Include all statistics
- List all issues found
- Show fixes applied
- Add recommendations
- Great for documentation
2. **CSV** - Spreadsheet format
- Columns: Location, Element, URL, Status, Issue, Fix Applied
- Easy to filter and analyze
- Good for sharing with team
3. **JSON** - Machine-readable data
- Complete raw data
- Useful for integrations
- Archive for historical tracking
导出示例（Markdown）：
# Link Audit Report: Company Website
Date: January 10, 2026
## Summary
- Total links scanned: 247
- Health score: 95/100
- Links fixed: 24
- Manual review needed: 2
## Issues Found
### Broken Links (8)
1. About Us > Button "Visit Partner"
- URL: https://partner-old-site.com
- Status: 404 Not Found
- Fix: Manual review needed
...
## Recommendations
1. Schedule monthly link checks
2. Monitor key external links
3. Set up 301 redirects for URL changes
阶段 8：性能优化
批处理：
For large sites:
- Process pages in batches of 10
- Process CMS items in batches of 50
- Show progress: "Processing batch 1 of 5..."
- Timeout protection: Skip after 30s per batch
验证结果缓存：
- Cache validation results by unique URL
- If same URL appears 10 times, validate once
- Report: "Checking 87 unique URLs (out of 247 total links)"
- Reduces validation time significantly
并行与顺序处理：
Parallel (faster):
- Link validation (test multiple URLs simultaneously)
- Page content extraction (fetch multiple pages)
Sequential (required):
- Link updates (one at a time to avoid conflicts)
- Publishing (one batch at a time)
阶段 9：错误处理
常见错误：
1. Designer 未连接：
❌ Error: Cannot update static pages
Reason: Designer MCP app not connected
Solution:
1. Open Webflow Designer
2. Open the target site
3. Connect Designer MCP app
4. Retry static page fixes
Note: CMS fixes can proceed without Designer
2. 速率限制：
⚠️ Warning: Rate limit reached
Pausing for 60 seconds...
Progress will resume automatically.
Current: 50/200 links validated
3. 超时错误：
⚠️ Link validation timeout
Link: https://very-slow-site.com
Timeout: 10 seconds exceeded
Marked for manual review.
Continuing with remaining links...
4. SSL 证书错误：
⚠️ SSL Certificate Error
Link: https://expired-cert-site.com
Issue: Certificate expired
Cannot verify HTTPS. Marked for manual review.
阶段 10：边缘情况
情况 1：未发现问题
🎉 Excellent! No Issues Found
All 247 links are working correctly!
Health Score: 100/100 ✨
Your site has:
✅ No broken links
✅ No insecure HTTP links
✅ No unnecessary redirects
💡 Recommendation:
Run this check monthly to maintain link health.
情况 2：所有链接均已失效
❌ Critical: Multiple Broken Links
Found 89 broken links across all pages.
This suggests a possible site-wide issue:
- Domain migration not configured?
- External service outage?
- Relative URL path issues?
🔍 Recommended Action:
1. Check if external services are down
2. Verify domain and SSL configuration
3. Test a few links manually
4. Contact Webflow support if needed
Shall I still proceed with individual link fixes? (yes/no)
情况 3：混合使用 HTTP/HTTPS 的网站
⚠️ Mixed Content Warning
Your site uses HTTPS but has 18 HTTP links.
This creates:
- Security warnings in browsers
- SEO penalties
- Trust issues for visitors
🔧 Recommendation:
Upgrade all HTTP links to HTTPS (all 18 can be auto-fixed)
Proceed with upgrade? (yes/no)
情况 4：重定向链
⚠️ Redirect Chain Detected
Link: https://example.com/old
→ 301 to: https://example.com/temp
→ 301 to: https://example.com/final
Recommendation: Update directly to final URL
- Improves page load speed
- Reduces redirect overhead
- Better for SEO
Fix: Update to https://example.com/final
Apply fix? (yes/no)
生产环境检查清单
在确认链接检查器实现完成之前：
✅ 发现
- 已列出网站及所有详情
- 已确认范围（静态/CMS/两者）
- 已获取所有页面
- 已识别所有集合
- 用户了解预计耗时
✅ 链接提取
- 已正确提取静态页面链接
- 已识别 CMS 链接字段
- 已正确解析 Rich Text 链接
- 已捕获所有链接元素（nodeId、URL、文本）
- 已合并重复 URL，以便验证
✅ 验证
- 已验证每个唯一 URL
- 已正确捕获状态码
- HTTP/HTTPS 检查有效
- 已检测到重定向并捕获最终 URL
- 已实现超时处理
- 错误分类准确
✅ 分析
- 已正确计算健康评分
- 已按优先级排列问题（严重/警告/建议）
- 统计数据完整准确
- 已区分内部链接和外部链接
- 页面/CMS 位置跟踪准确
✅ 建议生成
- 已正确识别自动修复项
- 已标记需要人工审核的项目
- 建议升级到 HTTPS 前已完成验证
- 建议采用的重定向最终目标已完成验证
- 预览格式清晰详尽
- 已显示每项修复的验证状态
✅ 审批系统
- 已实现细粒度审批
- 用户可以选择具体的修复项
- 支持「all」/「none」/数字格式
- 单独列出需人工审核的项目
- 提供清晰的说明
✅ 执行
- 静态页面更新正常（已连接 Designer）
- CMS Link 字段更新正常
- CMS Rich Text 链接更新正常
- 已实现批量处理
- 显示进度指示器
- 错误处理完善
✅ 验证
- 重新验证已修复的链接
- 计算新的健康评分
- 清晰报告失败情况
- 分别列出部分成功和完全失败的情况
- 显示前后对比
✅ 报告
- 完成最终摘要
- 统计数据准确
- 提供建议
- 提供导出选项
- 清晰说明后续步骤
✅ 错误处理
- 妥善处理 Designer 断开连接的情况
- 妥善处理超时错误
- 妥善处理速率限制
- 妥善处理 SSL 错误
- 单独报告部分失败的情况
✅ 性能
- 支持大规模批量处理
- 验证时对 URL 去重
- 长时间操作显示进度指示器
- 已实现超时保护
- 高效使用 API
✅ 用户体验
- 每个步骤都提供清晰的反馈
- 显示进度指示器
- 更改前显示警告
- 清晰确认操作成功
- 建议具有可操作性
评论
支持 Markdown