WordPress Broken Link Finder
Pricing
$250.00 / 1,000 completed checks
WordPress Broken Link Finder
Finds dead internal links on any WordPress site: reads content via the public REST API, checks every internal link it references, and reports each broken one with the pages that link to it. Charged only when a check completes.
Pricing
$250.00 / 1,000 completed checks
Rating
0.0
(0)
Developer
Chris Arsenault
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
5 days ago
Last modified
Categories
Share
Every dead internal link on a WordPress site, with the pages that point at it — in one call. Broken internal links leak authority, waste crawl budget, and quietly tell visitors the site is unmaintained. Finding them by hand means clicking everything; this Actor reads the site's own public REST API, extracts every internal link its content references, verifies each one, and hands you the fix list.
What you get
A summary row:
{"ok": true,"site": "https://example.com","pages_scanned": 60,"internal_links_found": 62,"links_checked": 60,"broken_count": 1,"broken_pct": 1.7}
Plus one row per broken link:
{"url": "https://example.com/some-deleted-page/","status": 404,"found_on": ["https://example.com/post-that-links-it/"]}
found_on lists up to five referencing pages, so the repair is a targeted edit, not a site-wide hunt.
Input
| Field | Type | Description |
|---|---|---|
url | string | Root URL of the WordPress site |
maxItemsPerType | integer | Cap on posts and pages scanned (each). Default 200 |
maxLinks | integer | Cap on distinct internal links verified. Default 300; the summary reports any skipped over the cap |
How it works, honestly
- Content comes from the public WordPress REST API; link targets are verified with polite HEAD requests (GET fallback), same-host only.
- External links are not checked — this is an internal-integrity tool, by design.
- Links behind login walls will report their real status (401/403), which is usually what you want to know anyway.
- If the target is not a WordPress site, the run says so and you are not charged. Billing is per completed check.
Use cases
- Agencies and consultants: run before the client call;
broken_pctwith a fix list is instant credibility. - Agents doing content maintenance: pipe
found_onstraight into an editing workflow. - Migration verification: run before and after a redesign or domain move; the diff is your regression list.
Built and used daily by 1450 Enterprises — its first production run found a dead page on one of our own sites, which we then fixed.