內容簡介
IndexLane Redirect & Internal Link Auditor 是一款用於檢查網站內部連結狀態的外掛，能夠發現返回404/410錯誤的連結、301/302重定向的連結，或指向舊的、測試或開發域名的連結。它提供詳細的報告，幫助網站擁有者或開發者進行內容審核。
【主要功能】
• 掃描所有已發佈內容或最新內容的數量限制
• 標記404/410錯誤和301/302重定向連結
• 提供詳細的連結狀態報告和證據
• 支援多種已註冊的公共文章類型
• 匯出CSV報告以供進一步分析
外掛標籤
開發者團隊
② 後台搜尋「IndexLane Redirect & Internal Link Auditor」→ 直接安裝（推薦）
原文外掛簡介
IndexLane Redirect & Internal Link Auditor finds internal content links that return 404/410, redirect through 301/302, or still point to old, staging, or development domains. It also shows how scanned content links to each published item.
It runs from inside WordPress admin, stays read-only, and produces evidence a site owner or developer can review or export. It does not auto-fix content or mutate the database.
Learn more at IndexLane.
Version 0.4 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.
Extract links from post content.
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.
Show the source post/page.
Group broken/error and redirected destinations by occurrence count and distinct affected content count.
Show status, redirect, effective-final-URL, warning, and result evidence for each destination.
Report one content-link coverage row per scanned published item.
Count incoming occurrences, distinct linking items, outgoing occurrences, distinct destinations, anchor variants, self-links, and direct versus redirected incoming links.
Resolve redirects to their final published WordPress content item while retaining redirect evidence.
Filter content with zero or one detected linking source and open every target’s source-and-anchor details.
Export separate target-coverage, destination-impact, and detailed-row CSV reports.
Show live content, link, unique-destination, HTTP-request, and actionable-issue progress.
Pause, continue, cancel, and resume a saved scan after reloading the page.
Provide translation-ready administrator, progress, evidence, JavaScript, and CSV strings through the WordPress.org text domain.
The destination-impact view is derived from the completed occurrence rows. It does not make more HTTP requests. Two links to one destination in the same page count as two occurrences and one affected content item.
The content-link coverage view is also derived from the exact completed scan without additional HTTP requests. “No incoming links detected in scanned content” means only that no links were found in the selected items’ stored post_content; menus, templates, widgets, shortcode output, and rendered page-builder content are outside this evidence.
Destination 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 evidence.
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. 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 CSV exports reuse the exact displayed evidence without scanning again.
The plugin does not create an account, call an IndexLane service, or add frontend tracking.
Limits
Version 0.4 scans links found in the post_content field of selected public post types. It does not crawl menus, widgets, theme templates, page-builder metadata, shortcode output, or rendered frontend pages.
Each AJAX batch makes at most five outbound HTTP requests. A session begins with an explicit allowance of 250 actual requests, including redirect hops. When that allowance is reached, the administrator can grant another 250 requests and continue without losing progress or recording incomplete evidence.
