ONSITE LINK VERDICT

Onsite Link Verdict — Broken Link Checker translation compatibility with REEID Translate — evidence review.

Official plugin evidence describes what Onsite Link Verdict — Broken Link Checker does, but does not yet establish specific visitor-facing content values that REEID should translate.

Visit Onsite Link Verdict — Broken Link Checker ↗

AWAITING VERIFICATION

Translation scope is not yet established.

Plugin capabilities can be documented without treating structure, behavior, configuration or feature availability as translatable content.

AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.

TRANSLATION SCOPE
No specific visitor-facing content values are currently approved for translation scope.

PLUGIN EVIDENCE
Plugin capabilities and distinctive features are documented separately from REEID translation support.

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).

Distinctive features
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).

Dynamic content
Dynamic or runtime content behavior remains limited to what is explicitly documented in the official plugin evidence.

SEO and metadata
SEO and metadata behavior is documented only where it is explicitly established by official plugin information.

URLs and navigation
URL and navigation behavior remains outside translation scope unless explicitly represented by the integration category.

Forms and commerce
Forms and commerce behavior is limited to factual capabilities documented for this plugin.

CONTENT BOUNDARY

Keep plugin capabilities separate from translation scope.

Current evidence documents what Onsite Link Verdict — Broken Link Checker does, but no specific visitor-facing content values have been approved as translation scope.

Structure, configuration, logic, integrations and runtime behavior are not translation claims.

LIMITATIONS & QA

Verification notes

  • This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.

RELATED GUIDES

Continue through the compatibility library.

INTEGRATION EVIDENCE

Explore REEID Translate for multilingual WordPress workflows.

REEID separates factual plugin intelligence from evidence-backed translation scope.

No specific visitor-facing content values are currently approved for this integration.

Shopping Cart
Scroll to Top