ONSITE LINK VERDICT
Onsite Link Verdict — Broken Link Checker compatibility with REEID Translate
Onsite Link Verdict — Broken Link Checker compatibility with REEID Translate is being evaluated from available plugin evidence. Runs link and image checks on the site’s own server via WordPress cron (not during visitor page loads). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Onsite Link Verdict — Broken Link Checker.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Onsite Link Verdict — Broken Link Checker is documented in the SEO category with 7 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How Onsite Link Verdict — Broken Link Checker compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Runs link and image checks on the site’s own server via WordPress cron (not during visitor page loads).
- Performs link verification using HTTP requests with a `HEAD`-first strategy and falls back to `GET` only when needed; reads at most 2 KB of any response body.
- Imposes hard ceilings per run: checks up to 100 links and uses no more than 45 seconds of wall-clock time (both configurable).
- Deduplicates repeated URLs across multiple posts by fetching the same URL once rather than once per occurrence.
- Classifies results into separate tabs (Broken, Warnings, Unverifiable, Good) and distinguishes “broken” (e.g., `404`/`410` with additional confirmation) from “could not check” responses (e.g., `403`/`503`/rate limits/challenges).
- Checks internal links to the site’s own content and, when a link returns `404`/`410`, looks up the destination in the plugin’s own database to report draft/private/pending status rather than treating it as definitively dead.
- Stores scan results in a table in the plugin’s own database (and does not upload posts/pages/comments to a cloud service).
CONTENT BOUNDARY
Onsite Link Verdict — Broken Link Checker capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
Onsite Link Verdict — Broken Link Checker and REEID Translate FAQ.
What does Onsite Link Verdict — Broken Link Checker do according to the available plugin evidence?
Onsite Link Verdict — Broken Link Checker has 7 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for Onsite Link Verdict — Broken Link Checker?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Onsite Link Verdict — Broken Link Checker?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate Onsite Link Verdict — Broken Link Checker in a multilingual WordPress workflow.
REEID documents Onsite Link Verdict — Broken Link Checker functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.