WordPress Broken Link Checker
Scan any WordPress URL to extract page links, test HTTP status codes, and detect 404 broken link errors.
Fixing Broken Links & Preserving WordPress Crawl Budget
- β 1. What is Link Rot & Why It Matters
- β 2. SSRF Protection & Link Audit Protocol
- β 3. Auditing Broken Image Media Assets
- β 4. Zero 404 Latency via Nimbica Static Edge
- β 5. How the Scan Actually Works
- β 6. Worked Example: Reading a Scan Report
- β 7. Practical Use Cases
- β 8. Limitations & Common Mistakes
1. What is Link Rot & Why It Matters
As external websites restructure or delete content, outbound links break. As documented in Google Search Central Crawling Guidelines, dead URLs waste crawler budget.
2. SSRF Protection & Link Audit Protocol
Every extracted URL is validated against loopback and private IP blocks before testing. Audit technical SEO tags in our WordPress SEO Health Checker.
3. Auditing Broken Image Media Assets
Scan image assets in our WordPress Image Optimization Scanner.
4. Zero 404 Latency via Nimbica Static Edge
Nimbica pre-renders WordPress sites into static HTML served from 300+ global edge locations, ensuring all valid pages respond with sub-50ms TTFB.
5. How the Scan Actually Works
Enter any WordPress URL and the tool fetches the raw HTML of that single page, then runs a regular-expression pass to extract every fully-qualified link written as href="https://..." or href="http://...". Duplicate URLs are removed and the list is capped at the first 25 unique matches to keep the scan fast and prevent abuse. Each surviving URL is first checked against SSRF rules β blocking localhost, loopback addresses, and private IP ranges (10.x, 172.16β31.x, 192.168.x, 169.254.x) β then tested with a lightweight HEAD HTTP request carrying a 3-second timeout and a self-identifying NimbicaBot/1.0 user agent.
Any response with a status code of 400 or higher (404 Not Found, 410 Gone, 500 Internal Server Error, etc.) is marked broken. A request that times out or fails to connect is also marked broken with status 0. Because links are checked one page at a time, this is best used as a targeted spot-check on high-traffic pages β your homepage, cornerstone blog posts, and resource/link roundup pages β rather than a full-site crawler.
6. Worked Example: Reading a Scan Report
Suppose you scan a "Best WordPress Plugins 2026" roundup post with 18 outbound links to plugin developer sites. A typical report might read: "3 Broken Links (18 Checked)". Two of the three might show HTTP 404 β meaning the linked plugin page was moved or deleted β while the third shows Timeout (3s), meaning that server simply took too long to respond and could either be genuinely down or just slow.
Interpretation: treat the two confirmed 404s as immediate fixes β replace the URL or remove the link. Treat the timeout as "needs manual verification" β reload it yourself in a browser before editing the post, since a slow-but-working server will pass on a second attempt while a genuinely broken one won't.
7. Practical Use Cases
- Pre-publish content review: Run a scan on any post before hitting publish to catch typo'd affiliate links or dead citation sources.
- Resource page maintenance: "Best tools" and "further reading" pages accumulate link rot fastest since they point almost entirely at third-party domains you don't control.
- Quarterly SEO housekeeping: Spot-check your top 10 highest-traffic pages (from Google Analytics) once a quarter to catch links that broke silently since publication.
- Post-redesign QA: After a theme or content migration, re-scan key landing pages to confirm internal absolute links (e.g. links to
https://yoursite.com/old-slug/) weren't left pointing at pre-migration URLs.
8. Limitations & Common Mistakes
- Relative links are invisible to this scanner: Internal links written as
href="/contact"instead of a full URL are not matched by the extraction pattern. Combine this tool with your XML sitemap and Search Console Coverage report for full internal-link coverage. - One page per scan: This is a single-URL auditor, not a full-site crawler β it will not follow links to a second page and check those recursively.
- HEAD requests can produce false positives: A small number of servers reject HEAD requests outright (returning 405) while serving GET requests normally. Always manually verify a flagged link before removing it from published content.
- 25-link cap on link-heavy pages: A page with 80 outbound links will only have its first 25 unique URLs tested; the rest are silently skipped in that run.
Give search engine crawlers sub-50ms response times with Nimbica
Transform dynamic PHP rendering bottlenecks into ultra-fast static HTML deployed across 300+ global edge locations.
Frequently Asked Questions
Why are broken links (404 errors) harmful to WordPress websites?
Broken links create poor user experience, increase visitor bounce rates, waste search engine crawl budget, and send negative quality signals to Google Search.
How does the WordPress Broken Link Checker enforce security and SSRF protection?
Every extracted URL is validated against strict SSRF rules (blocking localhost, 127.0.0.1, private IP ranges) before an HTTP request is made. Scans are capped at 25 links with a 3-second timeout per link.
Should I fix broken links using 301 redirects or URL updates?
Update broken links directly in page content to point to current valid URLs. Use 301 redirects for broken incoming internal or external landing page URLs.
Why does the scan only check 25 links even on pages with hundreds of URLs?
The 25-link cap and 3-second per-link timeout keep the scan fast and prevent the tool from being abused as a mass HTTP request proxy. For sites with more outbound links, run the scan separately on each key landing page and template.
Does the checker test relative internal links like /contact or only full URLs?
Only fully-qualified links written as href="https://..." or href="http://..." are extracted and tested. Relative internal links (href="/about") are not matched by the current extraction pattern, so this tool is strongest at catching broken outbound and cross-domain links.
Why would a link show as broken here but work fine when I click it in my browser?
The scanner sends a lightweight HEAD request rather than a full GET request. Some servers, WAFs, or CDNs reject or mishandle HEAD requests even though the page loads normally for real visitors β treat a single flagged link as a signal to verify manually, not an automatic confirmation of failure.
What HTTP status codes does the tool count as "broken"?
Any response status of 400 or higher is flagged broken β this covers client errors (404 Not Found, 410 Gone, 403 Forbidden) and server errors (500, 502, 503). Redirects (3xx) and successful responses (2xx) are counted as healthy.
Related Tools in This Cluster
WordPress SEO Health Checker
Audit meta titles, canonical tags, Open Graph declarations, and robots meta directives.
WordPress XML Sitemap Validator
Validate XML sitemap structure, urlset declarations, and HTTP response health.
WordPress Image Optimization Scanner
Scan image assets for missing alt text, WebP/AVIF formats, and dimension attributes.
