Skip to main content
Free Passive public check

Broken Internal Link Checker

Crawl a small set of URLs or pasted URLs for broken links.

The scanner uses public signals only, follows strict request limits, and stores private cached results for up to 24 hours.

Last reviewed 2026-06-24 Scanner Technical SEO
Free Scanner Last reviewed 2026-06-24 Technical SEO

Use this when

Use this when you need to crawl a small set of URLs or pasted URLs for broken links.

Best input: Starting page URL. Do not include secrets or customer data.

What Broken Internal Link Checker Does

Crawl a small set of URLs or pasted URLs for broken links. Broken Internal Link Checker is built for technical SEOs, WordPress publishers, developers, and site owners preparing crawl or indexation fixes who need a result they can verify instead of a vague score.

The page keeps the working tool first, then explains how to read the output, what can make the result unreliable, and which follow-up checks matter before production work.

Expected output: prioritized findings with the source signal, confidence, and verification notes.

When to use it

  • Review broken and internal decisions before a launch, migration, update window, or client handoff depends on them.
  • Compare broken internal link check output with browser source, rendered DOM, HTTP headers, XML sitemaps, robots directives, canonical tags, and Search Console when the visible page and the WordPress source may disagree.
  • Create a documented link next step for technical SEOs, WordPress publishers, developers, and site owners preparing crawl or indexation fixes instead of relying on memory or a scattered support thread.
  • Check a staging change that affects broken, internal, link, crawl, small before copying the same decision to production.
  • Give a client or teammate a concrete broken explanation that separates checked facts from follow-up assumptions.

When not to use it

  • Broken Internal Link Checker is not a substitute for authenticated broken inventory in the WordPress dashboard, hosting account, repository, or database.
  • Do not use a internal result to justify production work when the setting owner has not been identified.
  • Do not use it to bypass controls, crawl private link material, or infer secrets from incomplete public signals.
  • Do not treat a broken internal link check review as a final legal, compliance, accessibility, or security certification.
  • Do not paste passwords, API keys, private tokens, customer data, or confidential client notes into the broken input.

How to use this tool

  1. Start with the page, export, setting, log snippet, or inventory that best represents the real broken internal link check problem.
  2. Remove unrelated noise first: use the canonical broken source, current environment, current plugin/theme state, and the cache state you want to evaluate.
  3. Enter Starting page URL and keep the original internal source open so the result can be compared against the owning system.
  4. Run the scan, then read the highest-impact link output before scanning lower-priority notes.
  5. Separate directly observed broken signals from inferred, calculated, generated, or user-supplied details.
  6. Apply one reversible internal follow-up at a time, then repeat the same check so the before-and-after result is comparable.

How to interpret the result

Treat success, warning, and info results as a map of observed signals. A warning means the submitted page exposes a condition worth checking, not that every related WordPress setting is wrong. Info results are useful context for deciding whether to inspect a plugin, theme, CDN, or server layer next.

Practical examples

Pre-launch broken review

Input: A staging URL, export, or current configuration that contains the broken internal link check decision going live.

Output: Broken Internal Link Checker highlights the most relevant internal checks and separates immediate blockers from follow-up notes.

Next action: Fix the broken blocker on staging, verify with recheck the final rendered URL, canonical, robots directives, response status, and sitemap coverage, then document the final production step.

internal support ticket

Input: The reported symptom, URL, export, or snippet attached to a internal maintenance request.

Output: The result turns the request into a reviewable link checklist so the team can see what was checked and why.

Next action: Attach the broken result to the ticket with the original input, owner, and rollback or verification step.

Post-change link verification

Input: The same broken internal link check input used before an update, cache purge, migration, or configuration change.

Output: Differences in the output show whether the intended broken change reached the final rendered page, export, or server response.

Next action: Keep the before-and-after internal notes with the deployment record and investigate unexpected differences before closing the task.

Methodology and logic

Broken Internal Link Checker focuses on the broken internal link check workflow rather than giving a broad, unfocused site score. It asks for Starting page URL, then frames the output around broken, internal, and link signals a WordPress team can actually verify.

The method separates user-supplied broken input, directly visible internal signals, calculated checks, generated output, and assumptions. That separation matters because SEO fixes can remove pages from search, split signals, or create conflicting directives.

Tool-specific review angles

  • For broken, record the broken source, broken owner, and broken verification route before any production change is approved.
  • A reliable internal review names the layer that produced the internal signal: WordPress, plugin, theme, server, CDN, DNS, browser, or external service.
  • When link differs between staging and production, compare the exact URL, cache state, logged-in state, and deployment version before calling it fixed.
  • If generated output references crawl, replace project-specific values and check that the crawl decision still matches the target environment.
  • For client reporting, keep the small input beside the small result so another reviewer can reproduce the same conclusion later.
  • A set warning deserves priority only when it connects to traffic, revenue, indexation, security exposure, maintainability, or user trust.
  • Before closing the task, retest pasted after the relevant cache purge and confirm the browser or server sees the same pasted state.
  • Do not merge a links fix with unrelated cleanup; separate links changes make rollbacks faster and post-deployment notes clearer.
  • For broken workflows, compare the generated recommendation with current WordPress behavior instead of copying the first acceptable-looking answer.
  • If the internal result depends on pasted text, keep a snapshot of that text because later edits can make the original internal conclusion hard to audit.
  • When link touches WooCommerce, forms, redirects, schema, headers, or checkout, test the customer-facing route and the admin-facing route separately.
  • A low-severity crawl note can still matter when the same pattern repeats across templates, archives, products, language versions, or multisite subsites.
  • For small, the safest owner is the system that can both apply the change and verify the final rendered or served result.
  • If set output conflicts with another tool, trust the result with the clearest source, freshest input, and most repeatable verification path.
  • Document pasted assumptions explicitly, especially when the tool cannot see private admin settings, host rules, plugin options, or source code.
  • Use links findings to choose the next narrow check, not to expand the task into unrelated redesign, hosting, plugin, or content work.

Limitations and false positives

  • Broken Internal Link Checker can only evaluate the broken input you provide; hidden admin settings, private logs, and host-level rules still need owner verification.
  • Cached HTML, CDN rewrites, optimization plugins, security plugins, and page-builder output can make submitted internal material differ from what WordPress stores.
  • A missing link signal does not prove the issue is absent; it means the supported checks did not see it in the supplied material.
  • Staging, production, mobile, logged-in, and geographic variants may produce different broken internal link check results for the same workflow.
  • Generated broken rules or recommendations may need host-specific changes for Apache, Nginx, LiteSpeed, managed WordPress, multisite, or headless setups.
  • SEO fixes can remove pages from search, split signals, or create conflicting directives; review the internal result with the person who owns that layer before applying a fix.

Recommended next steps

  1. Save the original broken input, current setting, or current response before making any change.
  2. Handle critical internal blockers first: broken access, wrong status codes, exposed files, invalid markup, failing checkout, or unsafe configuration.
  3. Fix one link layer at a time: WordPress setting, plugin, theme, server, CDN, DNS, or external service.
  4. Purge only the cache layers that affect the tested broken path, then rerun Broken Internal Link Checker with the same input pattern.
  5. Record the internal owner, applied change, verification result, and rollback step in the maintenance note or client ticket.
  6. Update documentation or deployment status only after the final broken internal link check result matches the intended state.

Common mistakes

  • Using Broken Internal Link Checker once and assuming every broken template, product, archive, language version, or checkout path behaves the same way.
  • Changing production before checking whether WordPress, the theme, a plugin, the server, or the CDN owns the internal problem.
  • Comparing a cached link result with an uncached result and calling the difference a fix.
  • Ignoring broken warnings because the page still appears to work visually in one browser.
  • Copying generated internal output without replacing project-specific domains, paths, IDs, prefixes, versions, or policy choices.
  • Updating dateModified, client notes, or launch status before the broken internal link check result has been verified on the final public URL.

Validation checklist

  • Re-run Broken Internal Link Checker with the same broken input after the change and compare the result to the saved baseline.
  • Check browser source, rendered DOM, HTTP headers, XML sitemaps, robots directives, canonical tags, and Search Console for the system that owns the final internal behavior.
  • Test a logged-out browser session and, when relevant, a logged-in WordPress admin or customer session for the link path.
  • Review server logs, browser console output, Search Console, email logs, or payment logs when broken internal link check touches those systems.
  • Confirm mobile, desktop, cached, uncached, www, non-www, HTTP, and HTTPS variants when the broken issue can vary by route.
  • Document the final internal state, who approved it, and exactly how to roll it back.

Related workflow

Broken Internal Link Checker FAQs

What is Broken Internal Link Checker best used for?

Broken Internal Link Checker is best used to turn Starting page URL into a clearer broken internal link check decision. It helps you see what to inspect next, what to verify, and which change should be handled carefully before production.

Does Broken Internal Link Checker make changes to my WordPress site?

No. The page is designed as a broken review and planning tool. It may generate code, rules, or recommendations, but you decide whether to apply them in WordPress, hosting, DNS, CDN, or server configuration.

Can Broken Internal Link Checker be used on a live production site?

Yes, but production use should be read-only unless you have a rollback path. For any generated internal snippet, redirect, schema change, performance change, or security rule, test on staging when possible before deployment.

Why can Broken Internal Link Checker show a different result after caching or CDN changes?

Caching and CDN layers can serve older HTML, rewrite broken asset URLs, compress files, alter headers, or mask WordPress output. Clear the relevant cache layer and retest the same URL before deciding the result changed.

What should I verify after using Broken Internal Link Checker?

Verify the internal result in the system that owns the setting: WordPress admin, WP-CLI, browser devtools, Search Console, hosting controls, server logs, CDN settings, WooCommerce logs, or the source repository depending on the workflow.

Is Broken Internal Link Checker enough for a complete audit?

No single tool is a complete audit. Use it as a focused broken internal link check step, then combine it with related checks, authenticated inventory, current documentation, and manual review before final sign-off.

Maintained and reviewed

This tool page was last reviewed on 2026-06-24 for current WordPress, SEO, performance, security, WooCommerce, and migration workflows. Update the reviewed date only after the tool behavior, guidance, examples, and FAQ answers have been checked again.