INTELLECTSIGHT BROKEN LINK CHECKER
IntellectSight Broken Link Checker compatibility with REEID Translate
IntellectSight Broken Link Checker compatibility with REEID Translate is being reviewed using official plugin documentation. Scans posts, pages, and custom post types for broken links () and missing images (). No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What IntellectSight Broken Link Checker does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
IntellectSight Broken Link Checker is documented in the Navigation category with 6 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How IntellectSight Broken Link Checker compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Scans posts, pages, and custom post types for broken links () and missing images ().
- Performs internal link checks directly against the database to identify links to drafts, private posts, or trashed content without external requests.
- Provides one-click remediation actions including editing URLs globally, unlinking text, updating redirect targets, and marking false positives as 'Not Broken'.
- Categorizes problematic links into states such as Broken, Needs Confirmation (re-tested after failure), Redirects, and Blocked (sites refusing automated checks).
- Operates entirely on the local server with no external API dependencies, using background batches that limit execution time to prevent performance impact.
- Includes administrative tools such as CSV export, URL/domain exclusion lists, optional rel='nofollow' injection, and WP-CLI commands for scanning and reporting.
TRANSLATION BOUNDARY
IntellectSight Broken Link Checker capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility. No specific content shown to visitors is confirmed for translation in this category.
FREQUENTLY ASKED QUESTIONS
IntellectSight Broken Link Checker and REEID Translate FAQ.
What does IntellectSight Broken Link Checker do?
IntellectSight Broken Link Checker has 6 documented features listed in its official documentation. See the Plugin Information section for details.
Does IntellectSight Broken Link Checker have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from IntellectSight Broken Link Checker?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate IntellectSight Broken Link Checker in a multilingual WordPress workflow.
REEID documents IntellectSight Broken Link Checker functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.