WP ANTI-CLICKJACK
WP Anti-Clickjack compatibility with REEID Translate
WP Anti-Clickjack compatibility with REEID Translate is being evaluated from available plugin evidence. Adds the `X-Frame-Options: SAMEORIGIN` HTTP response header to help prevent clickjacking via iframe embedding. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for WP Anti-Clickjack.
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
WP Anti-Clickjack is documented in the Security category with 5 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 WP Anti-Clickjack 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
- Adds the `X-Frame-Options: SAMEORIGIN` HTTP response header to help prevent clickjacking via iframe embedding.
- Includes a modified OWASP “legacy browser frame breaking” script intended to prevent other sites from framing the site, including in browsers that don’t support `X-Frame-Options`.
- Provides a WordPress filter `wp_anti_clickjack` that can disable the clickjacking JavaScript behavior (example: `add_filter('wp_anti_clickjack', '__return_false');`).
- Provides a WordPress filter `wp_anti_clickjack_x_frame_options_header` that can disable the `X-Frame-Options` header behavior (example: `add_filter('wp_anti_clickjack_x_frame_options_header', '__return_false');`).
- Claims compatibility with common WordPress page builders/editors (e.g., Elementor, Divi, WPBakery, Bricks, Breakdance, Oxygen) as part of its stated feature set.
CONTENT BOUNDARY
WP Anti-Clickjack 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
WP Anti-Clickjack and REEID Translate FAQ.
What does WP Anti-Clickjack do according to the available plugin evidence?
WP Anti-Clickjack has 5 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 WP Anti-Clickjack?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for WP Anti-Clickjack?
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 WP Anti-Clickjack in a multilingual WordPress workflow.
REEID documents WP Anti-Clickjack 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.