ristorehemagi

<p>ContentGecko Connector exposes a secure REST API that the ContentGecko platform can use to synchronise posts, pages, product data, and translations with WordPress and WooCommerce. Access is protected by a shared API key, optional IP allow-listing, and tight capability checks inside wp-admin. The plugin stores minimal data, leans on WordPress core APIs, and keeps logging opt-in so your site remains lightweight.</p>
<p>Key features:</p>
<ul>
<li>Publish or update posts and pages through <code>/wp-json/contentgecko/v1</code> while sanitising content and metadata through WordPress core helpers.</li>
<li>Map multilingual content to WPML or Polylang, automatically linking translations and respecting the site’s default language.</li>
<li>Provide product, category, and catalog feeds when WooCommerce is active (gracefully failing when it is not).</li>
<li>Sideload remote featured images using WordPress core upload handlers (mime restricted) and reuse existing attachments when possible.</li>
<li>Optional debug log that persists the last 50 REST calls and mirrors high-level telemetry inside the wp-admin settings screen.</li>
</ul>
<p>The admin settings page lives under <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> ContentGecko Connector</strong> where administrators can generate API keys, toggle logging, view recent requests, and confirm the <code>/health</code> endpoint matches the WordPress environment.</p>
<h3>Short Description</h3>
<p>ContentGecko Connector exposes a secure REST API that the allows ContentGecko to automatically write and publish content for your webstore.</p>


ContentGecko Connector


Does exactly what it's supposed to - nothing more, nothing less. ContentGecko is a great way to automate SEO for a Woocommerce store.


Great plugin, no issues

ContentGecko Connector syncs ContentGecko posts, products, and translations with WordPress securely.

David Matthew

<p>Guillotheme chops the front-end (i.e. the head) right off your theme by restricting access to the front-end (specifically, the WordPress-generated front-end permalinks). These are unnecessary in the case of a headless or decoupled set-up, and could potentially confuse non-technical users or other content editors when WordPress is being used headlessly (i.e. purely for its CMS capabilities).</p>
<h3>Features</h3>
<ul>
<li>Designed to complement a headless setup.</li>
<li>Activate the plugin to automatically prevent access to WordPress-generated front-end permalinks.</li>
<li>For logged-in users, redirect back to the source page if the front-end is accessed (e.g. a post preview link within the editor will redirect back to the editor).</li>
<li>Non-logged in users are redirected to the login page.</li>
<li>Optionally use your own custom url for the redirect destination for both logged-in and logged-out users.</li>
</ul>
<h3>Development</h3>
<ul>
<li>Namespaced and object-oriented code.</li>
<li>Adheres to <a href="https://github.com/WordPress/WordPress-Coding-Standards" rel="nofollow ugc">WordPress Coding Standards</a>.</li>
</ul>


Guillotheme

Guillotheme chops the front-end (i.e. the head) right off your theme by restricting access to the front-end (specifically, the WordPress-generated fro …

ContentGecko Connector vs Guillotheme