
CONTENTGECKO CONNECTOR
ContentGecko Connector compatibility with REEID Translate
ContentGecko Connector compatibility with REEID Translate is being reviewed using official plugin documentation. Secure REST API access protected by a shared API key header (`X-ContentGecko-Key`) with the stored key hashed using `hash_hmac()` (with `AUTH_SALT`). No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What ContentGecko Connector does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
ContentGecko Connector is documented in the Security category with 7 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How ContentGecko Connector compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Secure REST API access protected by a shared API key header (`X-ContentGecko-Key`) with the stored key hashed using `hash_hmac()` (with `AUTH_SALT`).
- Optional inbound IP allow-listing via an allow-list filter (`contentgecko_allowed_ips`) to restrict requests by source IP.
- Capability checks inside `wp-admin` for REST operations (described as “tight capability checks inside wp-admin”).
- REST endpoints for publishing/updating content: posts via `/wp-json/contentgecko/v1/posts` and pages via `/wp-json/contentgecko/v1/pages`, with sanitising of content and metadata using WordPress core helpers.
- Remote featured image sideloading using WordPress core upload handlers with MIME restriction, reusing existing attachments when possible.
- Optional debug logging that persists the last 50 REST calls and exposes recent request metadata in the WordPress admin settings screen; logging is disabled by default.
- Multilingual content mapping that links translations and respects the site’s default language when WPML or Polylang are present (described as “Map multilingual content to WPML or Polylang”).
TRANSLATION BOUNDARY
ContentGecko Connector capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
FREQUENTLY ASKED QUESTIONS
ContentGecko Connector and REEID Translate FAQ.
What does ContentGecko Connector do?
ContentGecko Connector has 7 documented features listed in its official documentation. See the Plugin Information section for details.
Does ContentGecko Connector have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from ContentGecko Connector?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate ContentGecko Connector in a multilingual WordPress workflow.
REEID documents ContentGecko Connector functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.