Link Checker
Audit and fix broken or insecure links across your Webflow site to improve SEO and user experience.
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
- 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)
- No Designer connection is required — both static page and CMS link fixes go through
data_ tools
Instructions
Phase 1: Site Selection & Discovery
- Get site information: Use Webflow MCP's
data_sites_tool with action list_sites to identify target site
- Confirm scope: Ask user if they want to check:
- Static pages only
- CMS content only
- Both static pages and CMS content
- List pages: Use Webflow MCP's
data_pages_tool with action list_pages to get all pages
- List collections: Use Webflow MCP's
data_cms_tool with action get_collection_list to get all CMS collections
- 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
- 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
- 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)
- 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.)
Phase 3: Analysis & Reporting
- 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)
- 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
- Identify critical issues: Prioritize fixes
- 🔴 Critical: Broken links on high-traffic pages
- ⚠️ Warning: Insecure HTTP links
- 💡 Suggestion: Optimize redirects
Phase 4: Suggestion Generation & Approval
- 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
- Show preview with validation:
- 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
Phase 5: Execution & Confirmation
- Apply fixes to static pages: Use Webflow MCP's
data_pages_tool with action update_static_content
- Update link URLs in nodes
- Process in batches of 20 links
- 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
- Publish changes (if requested): Use Webflow MCP's
data_cms_tool with action publish_collection_items
- Show progress: Display progress indicators for large operations
- Generate final report:
- Links scanned: X
- Links fixed: Y
- Links requiring manual review: Z
- Health score improvement: Before → After
Phase 6: Verification & Recommendations
- Verify fixes: Re-check fixed links to confirm success
- Report failures: Clearly identify any fixes that failed
- Provide recommendations:
- Schedule regular link checks (monthly/quarterly)
- Set up monitoring for critical external links
- Consider using 301 redirects for changed URLs
- Export report (optional): Offer to export findings
Examples
Example 1: Complete Site Audit
User prompt:
Step 1: Site Selection
Step 2: Scope Confirmation
Step 3: Extraction & Validation
Step 4: Analysis Report
Step 5: Fix Preview
Step 6: After User Approves "all"
Example 2: CMS-Only Link Check
User prompt:
Step 1: Collection Selection
Step 2: Link Extraction
Step 3: Issue Report
Example 3: Static Pages Only (Quick Check)
User prompt:
Response:
Example 4: Fixing Specific Issues
User prompt:
Response:
Guidelines
Phase 1: Discovery Best Practices
Site Selection:
- Use
data_sites_tool with action list_sites 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
Static Page Link Extraction:
- Use
data_pages_tool with action get_page_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
data_cms_tool with action get_collection_details to identify Link and Rich Text fields
- Use
data_cms_tool with action list_collection_items to get all items
- For Link fields: Extract URL directly
- For Rich Text fields: Parse HTML to extract tags [blocked]
- Track: collectionId, itemId, fieldName for fixing
[blocked]
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:
Phase 3: Analysis Best Practices
Health Score Calculation:
Issue Prioritization:
Statistics to Report:
Phase 4: Suggestion Generation Best Practices
Automatic Fix Criteria:
Preview Format:
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
Phase 5: Execution Best Practices
Static Page Updates:
CMS Updates:
Publishing:
Phase 6: Verification Best Practices
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:
Success Reporting:
Recommendations:
Phase 7: Export Options
Report Formats:
Export Example (Markdown):
Batch Processing:
Caching Validation Results:
Parallel vs Sequential:
Phase 9: Error Handling
Common Errors:
1. Designer Not Connected:
2. Rate Limits:
3. Timeout Errors:
4. SSL Certificate Errors:
Phase 10: Edge Cases
Case 1: No Issues Found
Case 2: All Links Broken
Case 3: Mixed HTTP/HTTPS Site
Case 4: Redirect Chains
Production Checklist
Before considering link checker implementation complete:
✅ Discovery
✅ Validation
✅ Analysis
✅ Suggestion Generation
✅ Approval System
✅ Execution
✅ Verification
✅ Reporting
✅ Error Handling
✅ User Experience