ADD CODE TO HEAD
Add Code To Head compatibility with REEID Translate
Add Code To Head compatibility with REEID Translate is being evaluated from available plugin evidence. Adds custom HTML/JavaScript/CSS snippets to the rendered page without editing the site template. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Add Code To Head.
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
Add Code To Head is documented in the Security category with 6 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 Add Code To Head 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 custom HTML/JavaScript/CSS snippets to the rendered page without editing the site template.
- Provides an options screen where users can save head-code content that is later output on public pages.
- Implements capability-based sanitization/normalization for saved head code: users without the `unfiltered_html` capability have saved head code normalized and sanitized before storage (per the CVE-2025-48314 FAQ).
- Capability bypass behavior: users who intentionally grant `unfiltered_html` (e.g., administrators on single-site installs) bypass the sanitization described above by design (per the CVE-2025-48314 FAQ).
- Does not support applying different head-code per specific page(s); the plugin FAQ states you cannot target only certain pages/pages at this time.
- If another theme/plugin adds head content after this plugin runs, the plugin’s inserted codes may not appear at the absolute end of the head (per the FAQ).
CONTENT BOUNDARY
Add Code To Head 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
Add Code To Head and REEID Translate FAQ.
What does Add Code To Head do according to the available plugin evidence?
Add Code To Head has 6 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 Add Code To Head?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Add Code To Head?
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 Add Code To Head in a multilingual WordPress workflow.
REEID documents Add Code To Head 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.