link-checker

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Link Checker

链接检查器

Audit and fix broken or insecure links across your Webflow site to improve SEO and user experience.
审计并修复Webflow网站中的无效或不安全链接,以提升SEO效果和用户体验。

Important Note

重要说明

ALWAYS use Webflow MCP tools for all operations:
  • Use Webflow MCP's
    webflow_guide_tool
    to get best practices before starting
  • Use Webflow MCP's
    data_sites_tool
    with action
    list_sites
    to identify available sites
  • Use Webflow MCP's
    data_sites_tool
    with action
    get_site
    to retrieve site details
  • Use Webflow MCP's
    data_pages_tool
    with action
    list_pages
    to get all pages
  • Use Webflow MCP's
    data_pages_tool
    with action
    get_page_content
    to extract links from static pages
  • Use Webflow MCP's
    data_pages_tool
    with action
    update_static_content
    to fix links on static pages (requires Designer)
  • Use Webflow MCP's
    data_cms_tool
    with action
    get_collection_list
    to get all CMS collections
  • Use Webflow MCP's
    data_cms_tool
    with action
    get_collection_details
    to get collection schemas
  • Use Webflow MCP's
    data_cms_tool
    with action
    list_collection_items
    to get CMS items with links
  • Use Webflow MCP's
    data_cms_tool
    with action
    update_collection_items
    to fix links in CMS (draft)
  • Use Webflow MCP's
    data_cms_tool
    with action
    publish_collection_items
    to publish fixed CMS items
  • DO NOT use any other tools or methods for Webflow operations
  • All tool calls must include the required
    context
    parameter (15-25 words, third-person perspective)
  • Designer connection required for static page link fixes
所有操作请务必使用Webflow MCP工具:
  • 开始前使用Webflow MCP的
    webflow_guide_tool
    获取最佳实践
  • 使用Webflow MCP的
    data_sites_tool
    并指定动作
    list_sites
    来识别可用站点
  • 使用Webflow MCP的
    data_sites_tool
    并指定动作
    get_site
    来获取站点详情
  • 使用Webflow MCP的
    data_pages_tool
    并指定动作
    list_pages
    来获取所有页面
  • 使用Webflow MCP的
    data_pages_tool
    并指定动作
    get_page_content
    从静态页面提取链接
  • 使用Webflow MCP的
    data_pages_tool
    并指定动作
    update_static_content
    修复静态页面上的链接(需要Designer权限)
  • 使用Webflow MCP的
    data_cms_tool
    并指定动作
    get_collection_list
    来获取所有CMS集合
  • 使用Webflow MCP的
    data_cms_tool
    并指定动作
    get_collection_details
    来获取集合架构
  • 使用Webflow MCP的
    data_cms_tool
    并指定动作
    list_collection_items
    来获取包含链接的CMS条目
  • 使用Webflow MCP的
    data_cms_tool
    并指定动作
    update_collection_items
    修复CMS中的链接(草稿状态)
  • 使用Webflow MCP的
    data_cms_tool
    并指定动作
    publish_collection_items
    发布已修复的CMS条目
  • 请勿使用任何其他工具或方法进行Webflow操作
  • 所有工具调用必须包含必填的
    context
    参数(15-25个单词,第三人称视角)
  • 修复静态页面链接需要Designer连接

Instructions

操作步骤

Phase 1: Site Selection & Discovery

阶段1:站点选择与发现

  1. Get site information: Use Webflow MCP's
    data_sites_tool
    with action
    list_sites
    to identify target site
  2. Confirm scope: Ask user if they want to check:
    • Static pages only
    • CMS content only
    • Both static pages and CMS content
  3. List pages: Use Webflow MCP's
    data_pages_tool
    with action
    list_pages
    to get all pages
  4. List collections: Use Webflow MCP's
    data_cms_tool
    with action
    get_collection_list
    to get all CMS collections
  1. 获取站点信息:使用Webflow MCP的
    data_sites_tool
    并指定动作
    list_sites
    识别目标站点
  2. 确认范围:询问用户是否需要检查:
    • 仅静态页面
    • 仅CMS内容
    • 静态页面和CMS内容都检查
  3. 列出页面:使用Webflow MCP的
    data_pages_tool
    并指定动作
    list_pages
    获取所有页面
  4. 列出集合:使用Webflow MCP的
    data_cms_tool
    并指定动作
    get_collection_list
    获取所有CMS集合

Phase 2: Link Extraction & Validation

阶段2:链接提取与验证

  1. Extract links from static pages: Use Webflow MCP's
    data_pages_tool
    with action
    get_page_content
    for each page
    • Identify all link elements (Link, Button, TextLink, LinkBlock)
    • Capture: pageId, nodeName, URL, link text
  2. Extract links from CMS: Use Webflow MCP's
    data_cms_tool
    with action
    list_collection_items
    for each collection
    • Identify Link fields and Rich Text fields with links
    • Capture: collectionId, itemId, fieldName, URL
  3. Validate each link: Test URL accessibility
    • Check for 4xx/5xx errors (broken links)
    • Check for HTTP vs HTTPS (insecure links)
    • Test if HTTP has HTTPS equivalent available
    • Flag redirects (3xx status codes)
  4. Categorize results:
    • ✅ Working links (2xx status)
    • ❌ Broken links (4xx/5xx errors)
    • ⚠️ Insecure links (HTTP when HTTPS available)
    • 🔄 Redirects (3xx status)
    • ⚪ Manual review needed (timeouts, DNS errors, etc.)
  1. 从静态页面提取链接:对每个页面使用Webflow MCP的
    data_pages_tool
    并指定动作
    get_page_content
    • 识别所有链接元素(Link、Button、TextLink、LinkBlock)
    • 捕获:pageId、nodeName、URL、链接文本
  2. 从CMS提取链接:对每个集合使用Webflow MCP的
    data_cms_tool
    并指定动作
    list_collection_items
    • 识别Link字段和包含链接的Rich Text字段
    • 捕获:collectionId、itemId、fieldName、URL
  3. 验证每个链接:测试URL的可访问性
    • 检查4xx/5xx错误(无效链接)
    • 检查HTTP与HTTPS(不安全链接)
    • 测试HTTP链接是否有可用的HTTPS替代版本
    • 标记重定向(3xx状态码)
  4. 分类结果
    • ✅ 可用链接(2xx状态)
    • ❌ 无效链接(4xx/5xx错误)
    • ⚠️ 不安全链接(有HTTPS可用但仍使用HTTP)
    • 🔄 重定向链接(3xx状态)
    • ⚪ 需要手动审核(超时、DNS错误等)

Phase 3: Analysis & Reporting

阶段3:分析与报告

  1. Calculate statistics:
    • Total links scanned
    • Links by type (internal vs external)
    • Links by status (working, broken, insecure, redirects)
    • Links by location (static pages vs CMS)
  2. Generate health score: Calculate link health (0-100)
    • Working links: +1 point each
    • Broken links: -5 points each
    • Insecure links: -2 points each
    • Redirects: -1 point each
    • Normalize to 0-100 scale
  3. Identify critical issues: Prioritize fixes
    • 🔴 Critical: Broken links on high-traffic pages
    • ⚠️ Warning: Insecure HTTP links
    • 💡 Suggestion: Optimize redirects
  1. 计算统计数据
    • 扫描的链接总数
    • 链接类型占比(内部vs外部)
    • 链接状态占比(可用、无效、不安全、重定向)
    • 链接位置分布(静态页面vs CMS)
  2. 生成健康评分:计算链接健康度(0-100分)
    • 可用链接:每个加1分
    • 无效链接:每个扣5分
    • 不安全链接:每个扣2分
    • 重定向链接:每个扣1分
    • 归一化到0-100分区间
  3. 识别关键问题:优先处理修复任务
    • 🔴 紧急:高流量页面上的无效链接
    • ⚠️ 警告:不安全的HTTP链接
    • 💡 建议:优化重定向链接

Phase 4: Suggestion Generation & Approval

阶段4:生成修复建议与确认

  1. Generate fix suggestions: For each problematic link, suggest fix
    • Broken links: Remove link or update to correct URL
    • Insecure links: Upgrade HTTP to HTTPS
    • Redirects: Update to final destination URL
  2. Show preview with validation:
    [1] ✓ Fix insecure link
        Page: About Us
        Element: Button "Learn More"
        Current: http://example.com
        Suggested: https://example.com
        ✅ HTTPS version verified working
    
    [2] ⚠️ Fix broken link
        Page: Blog Post "Getting Started"
        Element: Text link
        Current: https://oldsite.com/page
        Suggested: [REMOVE LINK or provide correct URL]
        ❌ URL returns 404 - manual review needed
  3. Implement granular approval: Ask user which fixes to apply
    • Type numbers to skip (e.g., "2,4")
    • Type "all" to proceed with all automatic fixes
    • Type "none" to cancel
    • Flag manual review items separately
  1. 生成修复建议:为每个有问题的链接提供修复方案
    • 无效链接:移除链接或更新为正确的URL
    • 不安全链接:将HTTP升级为HTTPS
    • 重定向链接:更新为最终目标URL
  2. 显示带验证的预览
    [1] ✓ 修复不安全链接
        页面:关于我们
        元素:按钮“了解更多”
        当前:http://example.com
        建议:https://example.com
        ✅ HTTPS版本已验证可用
    
    [2] ⚠️ 修复无效链接
        页面:博客文章“入门指南”
        元素:文本链接
        当前:https://oldsite.com/page
        建议:[移除链接或提供正确URL]
        ❌ URL返回404 - 需要手动审核
  3. 精细化确认:询问用户要应用哪些修复
    • 输入数字跳过(例如:“2,4”)
    • 输入“all”应用所有自动修复
    • 输入“none”取消操作
    • 单独标记需要手动审核的条目

Phase 5: Execution & Confirmation

阶段5:执行与确认

  1. Apply fixes to static pages: Use Webflow MCP's
    pages_update_static_content
    • Requires Designer connection
    • Update link URLs in nodes
    • Process in batches of 20 links
  2. Apply fixes to CMS content: Use Webflow MCP's
    data_cms_tool
    with action
    update_collection_items
    • Update Link fields directly
    • Update links in Rich Text fields
    • Process in batches of 50 items
  3. Publish changes (if requested): Use Webflow MCP's
    data_cms_tool
    with action
    publish_collection_items
  4. Show progress: Display progress indicators for large operations
  5. Generate final report:
    • Links scanned: X
    • Links fixed: Y
    • Links requiring manual review: Z
    • Health score improvement: Before → After
  1. 修复静态页面链接:使用Webflow MCP的
    pages_update_static_content
    • 需要Designer连接
    • 更新节点中的链接URL
    • 按每批20个链接处理
  2. 修复CMS内容链接:使用Webflow MCP的
    data_cms_tool
    并指定动作
    update_collection_items
    • 直接更新Link字段
    • 更新Rich Text字段中的链接
    • 按每批50个条目处理
  3. 发布更改(如果用户要求):使用Webflow MCP的
    data_cms_tool
    并指定动作
    publish_collection_items
  4. 显示进度:为大型操作显示进度指示器
  5. 生成最终报告
    • 扫描的链接数:X
    • 修复的链接数:Y
    • 需要手动审核的链接数:Z
    • 健康评分提升:修复前 → 修复后

Phase 6: Verification & Recommendations

阶段6:验证与建议

  1. Verify fixes: Re-check fixed links to confirm success
  2. Report failures: Clearly identify any fixes that failed
  3. Provide recommendations:
    • Schedule regular link checks (monthly/quarterly)
    • Set up monitoring for critical external links
    • Consider using 301 redirects for changed URLs
  4. Export report (optional): Offer to export findings
  1. 验证修复结果:重新检查已修复的链接以确认成功
  2. 报告失败情况:明确标识任何修复失败的链接
  3. 提供建议
    • 定期安排链接检查(每月/每季度)
    • 为关键外部链接设置监控
    • 考虑为更改的URL设置301重定向
  4. 导出报告(可选):提供导出结果的选项

Examples

示例

Example 1: Complete Site Audit

示例1:完整站点审计

User prompt:
Run a complete link check on my site and fix any issues
Step 1: Site Selection
🔍 Link Checker: Site Selection

Available sites:
1. Company Website
2. Blog Site
3. Portfolio

Which site would you like to audit? (1/2/3)
Step 2: Scope Confirmation
📋 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)
Step 3: Extraction & Validation
🔄 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%)
Step 4: Analysis Report
📊 Link Health Report: Company Website

Overall Health Score: 76/100 ⚠️
用户提示:
对我的站点进行完整的链接检查并修复所有问题
步骤1:站点选择
🔍 链接检查器:站点选择

可用站点:
1. 公司官网
2. 博客站点
3. 作品集

您要审计哪个站点?(1/2/3)
步骤2:范围确认
📋 链接检查器范围

您需要检查哪些内容?
1. 仅静态页面(速度更快)
2. 仅CMS内容
3. 静态页面和CMS内容都检查(全面审计)

推荐:选择选项3进行完整审计

您的选择?(1/2/3)
步骤3:提取与验证
🔄 正在扫描链接...

进度:████████████████████ 100%

发现247个链接:
├── 静态页面:89个链接(15个页面)
├── CMS内容:158个链接(3个集合)
│   ├── 博客文章:142个链接
│   ├── 团队成员:12个链接
│   └── 产品:4个链接

正在验证链接...

进度:████████████████████ 100% (247/247 已检查)

✅ 可用:215个链接(87%)
❌ 无效:8个链接(3%)
⚠️ 不安全:18个链接(7%)
🔄 重定向:6个链接(2%)
步骤4:分析报告
📊 链接健康报告:公司官网

整体健康评分:76/100 ⚠️

Issues Found:

发现的问题:

🔴 Critical: Broken Links (8)

🔴 紧急:无效链接(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...
├── [1] 页面:“关于我们” │ └── 链接指向:https://partner-site.com/old-page │ 状态:404 未找到 │ 影响:高(首页) │ ├── [2] CMS:博客文章“产品发布” │ └── 链接指向:https://press-release.com/announcement │ 状态:404 未找到 │ 影响:中 │ ├── [3-8] 另外6个无效链接...

⚠️ Warning: Insecure Links (18)

⚠️ 警告:不安全链接(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...
├── [9] 页面:“联系我们” │ └── 链接:http://social-media.com/company │ 修复方案:https://social-media.com/company │ ✅ HTTPS版本已验证可用 │ ├── [10] CMS:博客文章“入门指南” │ └── 链接:http://tutorial-site.com │ 修复方案:https://tutorial-site.com │ ✅ HTTPS版本已验证可用 │ ├── [11-26] 另外16个不安全链接...

💡 Suggestion: Redirects (6)

💡 建议:重定向链接(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

**Step 5: Fix Preview**
🔧 Proposed Fixes (26 total)
├── [27] 页面:“服务” │ └── 链接:https://example.com/old-url │ 重定向到:https://example.com/new-url │ 建议:更新为最终目标URL │ ├── [28-32] 另外5个重定向链接...

💡 建议:
  1. 立即修复8个无效链接(影响SEO)
  2. 将18个HTTP链接升级为HTTPS(安全问题)
  3. 将6个重定向链接更新为最终URL(性能优化)
预计修复时间:约5分钟

**步骤5:修复预览**
🔧 建议修复方案(共26个)

Automatic Fixes Available (24):

可自动修复(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
[1] ✓ 升级为HTTPS 页面:联系我们 元素:按钮“关注我们” 当前:http://social-media.com/company 新链接:https://social-media.com/company ✅ HTTPS版本已验证可用
[2] ✓ 升级为HTTPS CMS:博客文章 > “入门指南” > 内容字段 当前:http://tutorial-site.com 新链接:https://tutorial-site.com ✅ HTTPS版本已验证可用
[3] ✓ 更新重定向链接 页面:服务 元素:文本链接“了解更多” 当前:https://example.com/old-url 新链接:https://example.com/new-url ✅ 最终目标URL已验证
[4-24] ... 另外21个自动修复方案

Manual Review Required (2):

需要手动审核(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

**Step 6: After User Approves "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)
undefined
[25] ⚠️ 无效链接 - 需要修正 页面:关于我们 元素:按钮“访问合作伙伴站点” 当前:https://partner-site.com/old-page 问题:404 未找到 操作:提供正确URL或移除链接
[26] ⚠️ 无效链接 - 需要修正 CMS:博客文章 > “产品发布” > 内容字段 当前:https://press-release.com/announcement 问题:404 未找到 操作:更新为正确URL或移除

您要应用哪些修复?
  • 输入“all”应用所有24个自动修复
  • 输入数字跳过(例如:“3,5,7”)
  • 输入“none”取消操作

**步骤6:用户确认“all”后**
✅ 正在应用修复...
进度:████████████████████ 100%
静态页面:
  • 在5个页面上更新了8个链接
  • ✅ 联系我们页面:修复3个链接
  • ✅ 服务页面:修复2个链接
  • ✅ 关于我们页面:修复1个链接
  • ✅ 博客页面:修复2个链接
CMS内容:
  • 在12个条目中更新了16个链接
  • ✅ 博客文章:修复14个链接
  • ✅ 团队成员:修复2个链接

🎉 链接修复完成!
摘要:
  • 扫描的链接数:247
  • 修复的链接数:24 ✅
  • 需要手动审核的链接数:2 ⚠️
  • 修复失败:0 ❌
健康评分:76 → 95(提升19分)✨

⚠️ 需要手动审核的条目:
[1] 关于我们页面 - 无效的合作伙伴链接 当前:https://partner-site.com/old-page 操作:手动更新或移除
[2] 博客文章“产品发布” - 无效的新闻稿链接 当前:https://press-release.com/announcement 操作:手动更新或移除

💡 后续步骤:
  1. 修复2个需要手动审核的条目
  2. 1个月后重新运行链接检查器
  3. 为关键外部链接设置监控
  4. 考虑为任何URL更改设置301重定向
您要导出此报告吗?(是/否)
undefined

Example 2: CMS-Only Link Check

示例2:仅CMS链接检查

User prompt:
Check all links in my blog posts
Step 1: Collection Selection
🔍 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...
Step 2: Link Extraction
🔄 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
Step 3: Issue Report
📊 Blog Posts Link Health: 91/100 ✅
用户提示:
检查我博客文章中的所有链接
步骤1:集合选择
🔍 链接检查器:CMS集合

发现3个集合:
1. 博客文章(47个条目)
2. 团队成员(8个条目)
3. 分类(6个条目)

您要求检查博客文章。正在检查“博客文章”集合...
步骤2:链接提取
🔄 正在从博客文章中提取链接...

进度:████████████████████ 100% (47/47 条目)

在博客文章中发现142个链接:
├── Link字段:23个链接
├── Rich Text内容:119个链接
└── 唯一URL总数:87个(55个URL多次出现)

正在验证链接...

进度:████████████████████ 100% (87/87 唯一URL已检查)

结果:
✅ 可用:79个链接(91%)
❌ 无效:3个链接(3%)
⚠️ 不安全:5个链接(6%)
🔄 重定向:0个链接
步骤3:问题报告
📊 博客文章链接健康度:91/100 ✅

Issues Found:

发现的问题:

🔴 Broken Links (3):

🔴 无效链接(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
[1] 文章:“Webflow入门指南” 字段:content(Rich Text) 链接:https://old-docs.example.com/guide 状态:404 未找到 出现位置:3篇文章
[2] 文章:“2024最佳实践” 字段:external-link(Link) 链接:https://expired-resource.com 状态:410 已删除
[3] 文章:“教程系列第3部分” 字段:content(Rich Text) 链接:https://video-host.com/deleted-video 状态:404 未找到

⚠️ Insecure Links (5):

⚠️ 不安全链接(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
undefined
[4] 文章:“案例研究:A公司” 字段:content(Rich Text) 链接:http://company-a-site.com 修复方案:https://company-a-site.com ✅ HTTPS版本可用且已验证
[5-8] 另外4个不安全链接...

🔧 建议修复方案:
[1] ⚠️ 移除无效链接(需要手动审核) 受影响的文章:3篇(入门指南、教程1、教程2) 链接:https://old-docs.example.com/guide 建议:如果有新文档URL请更新
[2] ⚠️ 移除无效链接(需要手动审核) 文章:“2024最佳实践” 链接:https://expired-resource.com 建议:移除或替换为替代链接
[3] ⚠️ 移除无效链接(需要手动审核) 文章:“教程系列第3部分” 链接:https://video-host.com/deleted-video 建议:更新为新的视频URL
[4] ✓ 升级为HTTPS 文章:“案例研究:A公司” 当前:http://company-a-site.com 新链接:https://company-a-site.com ✅ HTTPS版本已验证可用
[5-8] ... 另外4个HTTPS升级方案

您要应用哪些修复?
  • 输入“4-8”仅应用HTTPS升级
  • 输入“all”应用所有自动修复
  • 输入“none”取消操作
undefined

Example 3: Static Pages Only (Quick Check)

示例3:仅静态页面(快速检查)

User prompt:
Quick check on my static pages for broken links
Response:
🔍 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.
用户提示:
快速检查我的静态页面中的无效链接
响应:
🔍 快速链接检查:静态页面

正在扫描15个静态页面...

进度:████████████████████ 100%

在15个页面中发现89个链接

验证结果:
✅ 所有链接都可用!(89/89)

健康评分:100/100 ✨

您的静态页面没有无效或不安全的链接。

💡 提示:运行包含CMS内容的完整审计以获得全面覆盖。

Example 4: Fixing Specific Issues

示例4:修复特定问题

User prompt:
I have some broken links on my About page. Can you fix them?
Response:
🔍 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
用户提示:
我的关于页面上有一些无效链接,你能修复它们吗?
响应:
🔍 正在检查“关于我们”页面的链接...

在关于我们页面上发现12个链接

验证结果:
✅ 可用:9个链接
❌ 无效:2个链接
⚠️ 不安全:1个链接

---

发现的问题:

[1] ❌ 无效:合作伙伴站点链接
    元素:按钮“访问合作伙伴”
    链接:https://partner-old-site.com
    状态:404 未找到
    修复:需要手动审核

[2] ❌ 无效:团队成员资料
    元素:文本链接“认识Sarah”
    链接:/team/sarah-old-profile
    状态:404 未找到
    修复:更新为/team/sarah-johnson?

[3] ⚠️ 不安全:社交媒体链接
    元素:链接“关注我们”
    链接:http://social.com/company
    修复:https://social.com/company
    ✅ HTTPS版本已验证

---

您要应用哪些修复?
- 输入“3”仅修复不安全链接
- 输入“2,3”修复条目2和3
- 输入“all”应用所有自动修复
- 输入“none”取消操作

注意:条目[1]需要提供正确的URL进行手动修正

Guidelines

指南

Phase 1: Discovery Best Practices

阶段1:发现最佳实践

Site Selection:
  • Use
    sites_list
    to get available sites
  • Never assume site ID
  • Confirm site name with user
Scope Definition:
  • Ask if checking static pages, CMS, or both
  • Estimate time based on scope:
    • Static pages only: 1-3 minutes
    • CMS only: 2-5 minutes (depends on item count)
    • Full site: 5-10 minutes
Collection Selection:
  • List all collections with item counts
  • If user specifies collection, focus on that
  • If "all CMS", check all collections
站点选择:
  • 使用
    sites_list
    获取可用站点
  • 切勿假设站点ID
  • 与用户确认站点名称
范围定义:
  • 询问用户是检查静态页面、CMS还是两者都检查
  • 根据范围估算时间:
    • 仅静态页面:1-3分钟
    • 仅CMS:2-5分钟(取决于条目数量)
    • 完整站点:5-10分钟
集合选择:
  • 列出所有集合及其条目数量
  • 如果用户指定集合,则专注于该集合
  • 如果是“所有CMS”,则检查所有集合

Phase 2: Link Extraction Best Practices

阶段2:链接提取最佳实践

Static Page Link Extraction:
  • Use
    pages_get_content
    to get page nodes
  • Look for these node types:
    • Link (a tag)
    • Button (with link)
    • TextLink
    • LinkBlock
  • Extract href/url property
  • Capture link text for reporting
  • Track nodeId for fixing later
CMS Link Extraction:
  • Use
    collections_get
    to identify Link and Rich Text fields
  • Use
    collections_items_list_items
    to get all items
  • For Link fields: Extract URL directly
  • For Rich Text fields: Parse HTML to extract <a> tags
  • Track: collectionId, itemId, fieldName for fixing
Link Validation:
  • Test each unique URL (avoid duplicate tests)
  • Use HEAD request first (faster than GET)
  • Fallback to GET if HEAD fails
  • Handle timeouts (10 second max)
  • For HTTP links: Test HTTPS equivalent
  • Record status code and final URL (after redirects)
Categorization Rules:
✅ 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
静态页面链接提取:
  • 使用
    pages_get_content
    获取页面节点
  • 查找以下节点类型:
    • Link(a标签)
    • Button(带链接)
    • TextLink
    • LinkBlock
  • 提取href/url属性
  • 捕获链接文本用于报告
  • 记录nodeId以便后续修复
CMS链接提取:
  • 使用
    collections_get
    识别Link和Rich Text字段
  • 使用
    collections_items_list_items
    获取所有条目
  • 对于Link字段:直接提取URL
  • 对于Rich Text字段:解析HTML以提取<a>标签
  • 记录:collectionId、itemId、fieldName以便后续修复
链接验证:
  • 测试每个唯一URL(避免重复测试)
  • 优先使用HEAD请求(比GET更快)
  • 如果HEAD失败则回退到GET
  • 处理超时(最多10秒)
  • 对于HTTP链接:测试其HTTPS替代版本
  • 记录状态码和最终URL(重定向后)
分类规则:
✅ 可用(2xx):
- 200 OK
- 201 Created
- 204 No Content

❌ 无效(4xx/5xx):
- 400 Bad Request
- 401 Unauthorized
- 403 Forbidden
- 404 Not Found
- 410 Gone
- 500 Internal Server Error
- 502 Bad Gateway
- 503 Service Unavailable

⚠️ 不安全(HTTP):
- URL以http://开头
- 存在可用的HTTPS替代版本且返回2xx
- 标记为“升级为HTTPS”

🔄 重定向(3xx):
- 301 Moved Permanently
- 302 Found
- 307 Temporary Redirect
- 308 Permanent Redirect

⚪ 需要手动审核:
- 超时错误
- DNS解析失败
- 连接被拒绝
- SSL证书错误

Phase 3: Analysis Best Practices

阶段3:分析最佳实践

Health Score Calculation:
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
Issue Prioritization:
🔴 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
Statistics to Report:
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
健康评分计算:
公式:
1. 基础分 = 100
2. 可用链接:不扣分
3. 无效链接:每个扣5分
4. 不安全链接:每个扣2分
5. 重定向链接:每个扣1分
6. 最低分:0
7. 最高分:100

示例:
- 总链接数:200
- 可用:180个(不扣分)
- 无效:5个(扣25分)
- 不安全:10个(扣20分)
- 重定向:5个(扣5分)
- 得分:100 − 25 − 20 − 5 = 50/100
问题优先级:
🔴 紧急(立即修复):
- 首页上的无效链接
- 高流量页面上的无效链接
- 导航中的无效链接
- 重要外部引用的404错误

⚠️ 警告(尽快修复):
- 不安全的HTTP链接(安全风险)
- 博客文章中的无效链接
- 页脚中的无效链接
- 410 Gone错误

💡 建议(优化):
- 301重定向(更新为最终目标URL)
- 302重定向(可能会变化,需监控)
- 响应缓慢的外部链接
需要报告的统计数据:
基础数据:
- 扫描的链接总数
- 可用链接数量及占比
- 无效链接数量及占比
- 不安全链接数量及占比
- 重定向链接数量及占比

详细数据:
- 链接位置分布(静态vs CMS)
- 链接类型分布(内部vs外部)
- 最常见的问题
- 问题最多的页面/条目
- 无效链接最多的外部域名

Phase 4: Suggestion Generation Best Practices

阶段4:生成建议最佳实践

Automatic Fix Criteria:
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)
Preview Format:
[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]
Granular Approval:
  • Number each fix starting from 1
  • Show all automatic fixes first
  • Show manual review items separately
  • Allow user to select specific fixes
  • Options: "all", "none", or specific numbers
  • Example: "1,3,5-10" applies fixes 1, 3, and 5 through 10
自动修复标准:
可自动修复:
✅ HTTP → HTTPS(如果HTTPS版本已验证可用)
✅ 重定向链接 → 最终目标URL(如果最终URL已验证)
✅ 相对URL → 绝对URL(针对外部站点)

需要手动审核:
⚠️ 无效链接(404、410、5xx)- 需要正确的URL
⚠️ 没有HTTPS替代版本的HTTP链接
⚠️ 超时或连接错误
⚠️ SSL证书错误
⚠️ 需要认证(401、403)
预览格式:
[X] ✓ 可自动修复
    位置:[页面名称或CMS条目]
    元素:[元素类型 + 文本]
    当前:[当前URL]
    新链接:[建议URL]
    ✅ 验证:[状态]

[Y] ⚠️ 需要手动审核
    位置:[页面名称或CMS条目]
    元素:[元素类型 + 文本]
    当前:[当前URL]
    问题:[错误描述]
    建议:[操作方案]
精细化确认:
  • 从1开始为每个修复方案编号
  • 先显示所有自动修复方案
  • 单独显示需要手动审核的条目
  • 允许用户选择特定的修复方案
  • 选项:“all”、“none”或具体编号
  • 示例:“1,3,5-10”表示应用修复方案1、3以及5到10

Phase 5: Execution Best Practices

阶段5:执行最佳实践

Static Page Updates:
Requirements:
- Designer connection required
- Use pages_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 Updates:
For Link Fields:
- Direct update: fieldData[fieldName] = "new-url"
- Use collections_items_update_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
Publishing:
Ask user:
"Would you like to publish the changes immediately?"
- Yes: Use collections_items_publish_items
- No: Leave as drafts

For static pages:
- Changes are immediate (Designer updates live)
- Warn user that static page changes are live
静态页面更新:
要求:
- 需要Designer连接
- 使用pages_update_static_content
- 更新nodes数组中的新URL
- 按每页20个链接分批处理
- 每批处理后验证更新结果

错误处理:
- 如果未连接Designer:报告并跳过静态页面
- 如果更新失败:标记该链接并继续处理其他链接
- 单独报告部分成功的情况
CMS更新:
对于Link字段:
- 直接更新:fieldData[fieldName] = "new-url"
- 使用collections_items_update_items
- 选项:更新为实时版本或草稿版本

对于Rich Text字段:
- 解析HTML内容
- 查找并替换<a>标签
- 保留其他HTML格式
- 使用新HTML更新fieldData[fieldName]

分批处理:
- 每批处理50个条目
- 为大型集合显示进度
- 优雅处理API速率限制
发布:
询问用户:
“您要立即发布更改吗?”
- 是:使用collections_items_publish_items
- 否:保留为草稿

对于静态页面:
- 更改会立即生效(Designer更新实时版本)
- 提醒用户静态页面的更改是实时的

Phase 6: Verification Best Practices

阶段6:验证最佳实践

Re-validation:
  • Re-check all fixed links
  • Confirm status changed (404 → 200, HTTP → HTTPS)
  • Report any fixes that didn't work
  • Calculate new health score
Failure Reporting:
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
Success Reporting:
✅ 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 ⚠️
Recommendations:
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
重新验证:
  • 重新检查所有已修复的链接
  • 确认状态已更改(404 → 200,HTTP → HTTPS)
  • 报告任何修复无效的链接
  • 计算新的健康评分
失败报告:
如果有修复失败:
❌ 修复失败的链接(X个):

[1] 更新失败
    位置:联系我们页面
    原因:Designer连接丢失
    操作:重新连接Designer并重试

[2] URL仍然无效
    位置:博客文章“指南”
    原因:HTTPS版本返回404
    操作:需要手动修正
成功报告:
✅ 摘要:

修复前:
- 健康评分:76/100
- 无效链接:8个
- 不安全链接:18个
- 重定向链接:6个

修复后:
- 健康评分:95/100(+19)
- 无效链接:2个(修复6个,2个需要手动审核)
- 不安全链接:0个(修复18个)
- 重定向链接:0个(修复6个)

更改:
- 静态页面:在5个页面上更新了8个链接
- CMS内容:在12个条目中更新了16个链接
- 总修复数:24 ✅
- 手动审核:2 ⚠️
建议:
始终提供:
1. 下次检查的时间安排(每月/每季度)
2. 关键链接的监控建议
3. 避免无效链接的最佳实践
4. 适用的URL重定向策略

示例:
💡 建议:

1. **定期安排检查**
   - 活跃站点每月运行一次链接检查器
   - 静态站点每季度运行一次
   - 设置日历提醒

2. **监控关键外部链接**
   - 主要合作伙伴:company-a.com、partner-site.com
   - 文档:docs.example.com
   - 社交媒体资料

3. **设置URL重定向**
   - 如果更改URL,创建301重定向
   - 上线前测试重定向
   - 保持重定向映射更新

4. **最佳实践**
   - 添加前测试外部链接
   - 内部链接使用相对URL
   - 避免深度链接到外部页面
   - 重大重新设计后验证链接

Phase 7: Export Options

阶段7:导出选项

Report Formats:
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
Export Example (Markdown):
markdown
undefined
报告格式:
提供导出结果的选项:

1. **Markdown** - 易读的报告格式
   - 包含所有统计数据
   - 列出所有发现的问题
   - 显示已应用的修复
   - 添加建议
   - 适合文档记录

2. **CSV** - 电子表格格式
   - 列:位置、元素、URL、状态、问题、已应用的修复
   - 易于筛选和分析
   - 适合团队共享

3. **JSON** - 机器可读数据
   - 完整的原始数据
   - 适合集成
   - 用于历史跟踪存档
导出示例(Markdown):
markdown
undefined

Link Audit Report: Company Website

链接审计报告:公司官网

Date: January 10, 2026
日期:2026年1月10日

Summary

摘要

  • Total links scanned: 247
  • Health score: 95/100
  • Links fixed: 24
  • Manual review needed: 2
  • 扫描的链接总数:247
  • 健康评分:95/100
  • 修复的链接数:24
  • 需要手动审核的链接数:2

Issues Found

发现的问题

Broken Links (8)

无效链接(8个)

  1. About Us > Button "Visit Partner"
...
  1. 关于我们 > 按钮“访问合作伙伴”
...

Recommendations

建议

  1. Schedule monthly link checks
  2. Monitor key external links
  3. Set up 301 redirects for URL changes
undefined
  1. 每月安排链接检查
  2. 监控关键外部链接
  3. 为URL更改设置301重定向
undefined

Phase 8: Performance Optimization

阶段8:性能优化

Batch Processing:
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
Caching Validation Results:
- 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 vs Sequential:
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)
分批处理:
对于大型站点:
- 按每批10个页面处理
- 按每批50个CMS条目处理
- 显示进度:“正在处理第1批,共5批...”
- 超时保护:每批超过30秒则跳过
缓存验证结果:
- 按唯一URL缓存验证结果
- 如果同一URL出现10次,仅验证一次
- 报告:“正在检查87个唯一URL(共247个链接)”
- 显著减少验证时间
并行与串行:
并行(更快):
- 链接验证(同时测试多个URL)
- 页面内容提取(同时获取多个页面)

串行(必须):
- 链接更新(一次一个以避免冲突)
- 发布(一次一批)

Phase 9: Error Handling

阶段9:错误处理

Common Errors:
1. Designer Not Connected:
❌ 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. Rate Limits:
⚠️ Warning: Rate limit reached

Pausing for 60 seconds...

Progress will resume automatically.
Current: 50/200 links validated
3. Timeout Errors:
⚠️ Link validation timeout

Link: https://very-slow-site.com
Timeout: 10 seconds exceeded

Marked for manual review.
Continuing with remaining links...
4. SSL Certificate Errors:
⚠️ SSL Certificate Error

Link: https://expired-cert-site.com
Issue: Certificate expired

Cannot verify HTTPS. Marked for manual review.
常见错误:
1. 未连接Designer:
❌ 错误:无法更新静态页面

原因:未连接Designer MCP应用

解决方案:
1. 打开Webflow Designer
2. 打开目标站点
3. 连接Designer MCP应用
4. 重试静态页面修复

注意:无需Designer即可进行CMS修复
2. 速率限制:
⚠️ 警告:达到速率限制

将暂停60秒...

进度将自动恢复。
当前:50/200 个链接已验证
3. 超时错误:
⚠️ 链接验证超时

链接:https://very-slow-site.com
超时:超过10秒

标记为需要手动审核。
继续处理剩余链接...
4. SSL证书错误:
⚠️ SSL证书错误

链接:https://expired-cert-site.com
问题:证书已过期

无法验证HTTPS。标记为需要手动审核。

Phase 10: Edge Cases

阶段10:边缘情况

Case 1: No Issues Found
🎉 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.
Case 2: All Links Broken
❌ 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)
Case 3: Mixed HTTP/HTTPS Site
⚠️ 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)
Case 4: Redirect Chains
⚠️ 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)
情况1:未发现问题
🎉 优秀!未发现任何问题

所有247个链接都正常可用!

健康评分:100/100 ✨

您的站点:
✅ 没有无效链接
✅ 没有不安全的HTTP链接
✅ 没有不必要的重定向

💡 建议:
每月运行此检查以保持链接健康度。
情况2:所有链接都无效
❌ 紧急:多个无效链接

在所有页面中发现89个无效链接。

这表明可能存在站点级问题:
- 域名迁移未配置?
- 外部服务中断?
- 相对URL路径问题?

🔍 建议操作:
1. 检查外部服务是否中断
2. 验证域名和SSL配置
3. 手动测试几个链接
4. 如有需要联系Webflow支持

仍要继续修复单个链接吗?(是/否)
情况3:混合HTTP/HTTPS站点
⚠️ 混合内容警告

您的站点使用HTTPS但包含18个HTTP链接。

这会导致:
- 浏览器中的安全警告
- SEO惩罚
- 访客信任问题

🔧 建议:
将所有18个HTTP链接升级为HTTPS(全部可自动修复)

要进行升级吗?(是/否)
情况4:重定向链
⚠️ 检测到重定向链

链接:https://example.com/old
  → 301 到:https://example.com/temp
  → 301 到:https://example.com/final

建议:直接更新为最终URL
- 提升页面加载速度
- 减少重定向开销
- 对SEO更友好

修复方案:更新为https://example.com/final

要应用此修复吗?(是/否)

Production Checklist

生产环境检查清单

Before considering link checker implementation complete:
在确认链接检查器实现完成前,请检查以下内容:

✅ Discovery

✅ 发现阶段

  • Sites listed with all details
  • Scope confirmed (static/CMS/both)
  • All pages retrieved
  • All collections identified
  • User understands time estimate
  • 列出所有站点及详细信息
  • 确认范围(静态/CMS/两者都有)
  • 获取所有页面
  • 识别所有集合
  • 用户了解时间估算

✅ Link Extraction

✅ 链接提取阶段

  • Static page links extracted correctly
  • CMS link fields identified
  • Rich Text links parsed correctly
  • All link elements captured (nodeId, URL, text)
  • Duplicate URLs consolidated for validation
  • 正确提取静态页面链接
  • 识别CMS Link字段
  • 正确解析Rich Text链接
  • 捕获所有链接元素(nodeId、URL、文本)
  • 合并重复URL以进行验证

✅ Validation

✅ 验证阶段

  • Each unique URL validated
  • Status codes captured correctly
  • HTTP/HTTPS checking works
  • Redirects detected and final URLs captured
  • Timeout handling implemented
  • Error categorization accurate
  • 验证每个唯一URL
  • 正确捕获状态码
  • HTTP/HTTPS检查正常工作
  • 检测重定向并捕获最终URL
  • 实现超时处理
  • 错误分类准确

✅ Analysis

✅ 分析阶段

  • Health score calculated correctly
  • Issues prioritized (Critical/Warning/Suggestion)
  • Statistics complete and accurate
  • Internal vs external links separated
  • Location tracking (page/CMS) accurate
  • 正确计算健康评分
  • 问题优先级划分正确(紧急/警告/建议)
  • 统计数据完整准确
  • 区分内部和外部链接
  • 位置跟踪(页面/CMS)准确

✅ Suggestion Generation

✅ 建议生成阶段

  • Automatic fixes identified correctly
  • Manual review items flagged
  • HTTPS upgrades verified before suggesting
  • Redirect final destinations verified
  • Preview format clear and detailed
  • Validation status shown for each fix
  • 正确识别可自动修复的链接
  • 标记需要手动审核的条目
  • 建议HTTPS升级前先验证
  • 验证重定向的最终目标URL
  • 预览格式清晰详细
  • 显示每个修复的验证状态

✅ Approval System

✅ 确认系统

  • Granular approval implemented
  • User can select specific fixes
  • "all"/"none"/numbers format works
  • Manual review items separated
  • Clear instructions provided
  • 实现精细化确认
  • 用户可以选择特定修复方案
  • “all”/“none”/编号格式正常工作
  • 手动审核条目单独显示
  • 提供清晰的说明

✅ Execution

✅ 执行阶段

  • Static page updates work (Designer connected)
  • CMS Link field updates work
  • CMS Rich Text link updates work
  • Batch processing implemented
  • Progress indicators shown
  • Error handling graceful
  • 静态页面更新正常工作(已连接Designer)
  • CMS Link字段更新正常工作
  • CMS Rich Text链接更新正常工作
  • 实现分批处理
  • 显示进度指示器
  • 错误处理优雅

✅ Verification

✅ 验证阶段

  • Fixed links re-validated
  • New health score calculated
  • Failures reported clearly
  • Partial successes vs full failures separated
  • Before/after comparison shown
  • 重新验证已修复的链接
  • 计算新的健康评分
  • 清晰报告失败情况
  • 区分部分成功和完全失败
  • 显示修复前后的对比

✅ Reporting

✅ 报告阶段

  • Final summary complete
  • Statistics accurate
  • Recommendations provided
  • Export options offered
  • Next steps clear
  • 最终摘要完整
  • 统计数据准确
  • 提供建议
  • 提供导出选项
  • 后续步骤清晰

✅ Error Handling

✅ 错误处理

  • Designer disconnected handled
  • Timeout errors handled
  • Rate limits handled
  • SSL errors handled
  • [ [ ] Partial failures reported separately
  • 处理未连接Designer的情况
  • 处理超时错误
  • 处理速率限制
  • 处理SSL错误
  • 单独报告部分失败情况

✅ Performance

✅ 性能

  • Batch processing for scale
  • URL deduplication for validation
  • Progress indicators for long operations
  • Timeout protection implemented
  • Efficient API usage
  • 为大规模场景实现分批处理
  • 验证时去重URL
  • 为长时间操作显示进度指示器
  • 实现超时保护
  • 高效使用API

✅ User Experience

✅ 用户体验

  • Clear feedback at each step
  • Progress indicators shown
  • Warnings shown before changes
  • Success confirmation clear
  • Recommendations actionable
  • 每个步骤都有清晰反馈
  • 显示进度指示器
  • 更改前显示警告
  • 成功确认清晰
  • 建议可执行