n8n Workflow: Check Broken Links & Images with PowMCP
n8n Workflow: Check Broken Links & Images with PowMCP
Regular price
£36.99
Regular price
£36.99
Sale price
Unit price
/
per
⬇
Instant Digital Download
∞
Unlimited Downloads
★
Lifetime Access in Your Account
Couldn't load pickup availability
🔥
128+ Sold
Popular with n8n builders
⚡
23 people viewing
High interest right now
✅
9 added today
Fast-moving digital product
n8n Workflow: Check Broken Links & Images with PowMCP
Regular price
£36.99
Regular price
£36.99
Sale price
Unit price
/
per
Find and fix broken links and missing images on any public page—automatically
This n8n workflow checks a specified public webpage for broken links and images by calling the PowMCP hosted broken-link checker, then returns a clear human-readable report plus structured evidence of what failed (including timeouts, rate limits, and refused targets).
What this workflow does
- Runs on demand when you manually start the workflow in n8n.
- Sets the target public page URL to check (update the “Set public page URL” node from https://example.com/ to your allowed URL).
- Scans the page via PowMCP by sending the URL to PowMCP’s broken-link-check MCP endpoint.
-
Outputs two results for review:
- A readable report summarizing broken link/image targets.
- Structured evidence showing failure types such as broken targets, timeouts, rate-limit/refused outcomes, and truncation (review these separately).
- Workflow-driven remediation: fix confirmed issues on your site, deploy changes, and rerun to validate.
Use cases
- SaaS teams validating that docs, marketing pages, and changelogs don’t accumulate broken links.
- Automation engineers performing scheduled or ad-hoc link audits before releases.
- Site maintainers troubleshooting missing images and pinpointing which URLs fail.
Technical details
- PowMCP hosted broken-link checker via MCP endpoint.
- Uses n8n nodes including Manual Trigger, Set, Sticky Note, and the n8n built-in MCP Client node (“built-in MCP Client node, version 1.1”).
- No AI model, model API key, or community node is required.
- Requires available PowMCP guest allowance (50 lifetime requests per resolved network identity; shared egress addresses share the allowance). The template stops if allowance is exhausted.
Result: a practical n8n automation workflow for reliable broken link and image checks—ideal for maintaining public-facing pages at scale.
