ADD CODE TO HEAD
Add Code To Head | REEID Translate Compatibility
REEID can process supported visitor-facing security, login and account text while Add Code To Head remains responsible for authentication, protection rules and enforcement.
AWAITING VERIFICATION
Translate messages. Preserve security controls.
Human-readable frontend text stays separate from authentication rules, blocking policies, firewall behaviour and other security configuration.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
CONTENT BOUNDARY
Translatable content remains separate from plugin-specific functional configuration.
SECURITY LOGIC
Authentication, firewall, blocking and protection rules remain controlled by the security plugin.
PRACTICAL WORKFLOW
Translation workflow
01 · Configure security normally
Maintain authentication and protection settings through Add Code To Head.
02 · Identify visitor-facing messages
Locate supported login, account, warning or security-related text exposed to visitors.
03 · Translate supported messages
Process multilingual text without changing security rules or enforcement.
04 · Test protected user flows
Review translated messages alongside login, account and protection behaviour.
SUPPORTED CONTENT
Translation scope
Visitor-facing text
Replace this draft item with the exact content coverage.
Interface content
Document supported labels, titles or interface strings where applicable.
Product-specific content
Add confirmed product-specific support before publication.
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).
Distinctive features
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).
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
Translate human-readable security text, not security policy.
REEID handles supported visitor-facing text while Add Code To Head retains control of authentication, blocking rules, firewall settings and protection logic.
Security configuration must remain functional data and should never be translated as ordinary content.
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.
Does REEID Translate work with Add Code To Head?
REEID Translate Pro processes the supported visitor-facing fields documented for this integration while Add Code To Head retains control of its own functionality.
Does REEID alter Add Code To Head security rules?
No. Authentication, blocking and security policy remain completely under Add Code To Head control.
Can login and account messages be multilingual?
Supported visitor-facing messages can be translated when they are exposed through supported content paths.
RELATED GUIDES
Continue through the compatibility library.
SECURITY INTEGRATION
Translate supported Add Code To Head user-facing text without changing security policy.
Keep multilingual messaging separate from authentication and protection logic.
Supported content and limitations are defined by the integration record.