IndexLane Redirect & Internal Link Auditor

Popis

IndexLane Redirect & Internal Link Auditor finds broken, redirected, old-site, and staging links. It shows where links appear and checks whether your fixes worked against an explicitly saved scan.

It runs from inside WordPress admin, stays read-only, and produces results a site owner or developer can review or download. It does not auto-fix content or change the database.

Learn more at IndexLane.

Version 0.6 can:

• Scan all published content or a numeric limit of the newest content.
• Scan any registered public post type, not only posts, pages, and products.
• Select stored link sources independently.
• Inspect normal post content, classic menus, Navigation entities, synced patterns, block templates, template parts, and assigned block widgets.
• Check same-site link status.
• Flag 404/410 responses.
• Flag 301/302 redirects and redirect chains.
• Flag links to old domains supplied by the administrator.
• Flag common staging and development-domain links.
• Retain each source’s exact identity, surface, edit URL, link text, and contextual or shared/global scope.
• Group broken/error and redirected URLs by times linked and editable sources affected.
• Show status, redirects, final URL, warnings, and outcome for each URL.
• Report one content-link coverage row per scanned published item.
• Count contextual links, navigation/shared links, distinct editable sources, outgoing links, distinct URLs, link-text variants, self-links, and direct versus redirected incoming links.
• Resolve redirects to their final published WordPress content item while retaining redirect results.
• Filter content with zero or one detected editable source and open every target’s exact source details.
• Download separate content-coverage, problem-URL, and link-detail CSV reports.
• Save one explicitly selected completed scan for comparison per administrator.
• Download and upload strict, versioned, site-specific saved-scan JSON.
• Rerun the saved scan’s exact scope as a fix check.
• Classify issue URLs as new, changed, resolved, or still present.
• Compare saved-scan and latest-scan status chains, redirects, final URLs, outcomes, times linked, and affected-source counts.
• Download the exact completed comparison as CSV.
• Delete the saved scan explicitly without changing current scan results.
• Show live stored sources checked, links found, unique URLs, and links needing attention.
• Pause, continue, cancel, and resume a saved scan after reloading the page.
• Provide translation-ready administrator, progress, result, JavaScript, and CSV strings through the WordPress.org text domain.

The problem-URL view is derived from the completed link results. It does not make more HTTP requests. A URL found once in a shared Footer template part is reported against that exact editable source, with a direct edit link.

The content-link coverage view is also derived from the exact completed scan without additional HTTP requests. “No incoming links detected in selected sources” means only that no links were found in the stored adapters chosen for that scan. Shortcode output, arbitrary metadata, proprietary page-builder storage, and rendered frontend output remain outside these results.

Third-party plugins can register reliable stored-source adapters through the indexlane_rila_source_providers filter. The provider supplies bounded snapshot and next-source callbacks plus stable source identity and edit evidence; this plugin does not maintain proprietary storage parsers.

URL grouping normalizes scheme and host case, fragments, and default ports. Paths, query strings, schemes, non-default ports, and trailing slashes remain distinct because they can return different results.

HTTP requests are made only to the current site. Links to old, staging, or development domains are still reported for review.

Data handling

Scans run on demand from WordPress admin through authenticated AJAX batches. Each batch processes at most five stored sources and makes at most five outbound HTTP requests. The active or completed session is stored in a per-user WordPress transient for up to 24 hours after its last activity. Abandoned sessions expire automatically, and completed-session downloads reuse the exact displayed results without scanning again.

An administrator may explicitly save one site-specific scan in their WordPress user options. It remains until it is replaced or deleted. Portable saved-scan JSON is limited to 20 MB and validated against the exact supported format and current site URL before upload.

The plugin does not create an account, call an IndexLane service, or add frontend tracking.

Limits

This is a stored-source scanner, not a rendered-site crawler. It reads only the selected built-in adapters or adapters registered by other plugins. It does not execute shortcodes, scan arbitrary metadata, render templates, inspect unsupported page-builder storage, or crawl frontend pages.

A scan can snapshot at most 100,000 stored sources. Block widgets are included only when their stored block structure is available and the widget is assigned to a widget area.

Each AJAX batch makes at most five outbound HTTP requests. A session begins with an explicit limit of 250 actual requests, including redirect hops. When that limit is reached, the administrator can increase it by 250 and continue without losing progress or recording incomplete results.