Robin

PiedWeb AI Polyglot is the multilingual infrastructure for your WordPress + WooCommerce site — routing, SEO, admin UI, virtualized stock and reviews — without duplicating content. It does not translate text itself: you bring your own translation provider (an LLM, a translation API, or a human translator), and the plugin handles everything else.
It uses a Master/Shadow architecture: you manage content in your primary language, and the plugin creates linked shadow copies for each target locale. Each language gets its own domain (or subdomain), with full SEO support out of the box. WP-CLI commands expose the master content as JSON so you can pipe it into any LLM or translation API and push the result back.
Designed to fit AI-powered translation workflows — but works just as well with human translators or a flat-file editing loop.
<h4>Why PiedWeb AI Polyglot?</h4>
<ul>
<li>No content duplication — shadows are linked copies, not clones. Update the master, shadows follow.</li>
<li>No separate database — everything lives in a single WordPress install. No sync headaches.</li>
<li>No performance penalty — stock, images, and reviews are virtualized at query time, not copied.</li>
<li>No plugin lock-in — all data is stored as standard WordPress post meta. Remove the plugin, your content stays.</li>
<li>AI-ready — WP-CLI commands expose master content as JSON, ready to pipe into any translation API or LLM.</li>
</ul>
<h4>Features</h4>
<ul>
<li>Domain-based routing — one domain per language, detected via <code>HTTP_HOST</code>. Each domain serves only its locale’s content.</li>
<li>Virtualized stock — shadow products read stock from the master in real time. Orders on any domain decrement the same inventory.</li>
<li>Virtualized reviews — reviews submitted on any domain are stored on the master product. Star ratings are aggregated across all locales.</li>
<li>Virtualized images — shadow products inherit the master’s featured image and gallery without duplicating media files.</li>
<li>Hreflang SEO — automatic <code><link rel="alternate" hreflang="..."></code> tags plus sitemap annotations with <code>xhtml:link</code>.</li>
<li>Locale-filtered sitemaps and RSS — each domain’s sitemap and feed only expose its own content.</li>
<li>WooCommerce i18n — shipping labels, checkout legal texts, cart product names, and permalink slugs are all translated per locale.</li>
<li>Human lock — manually edited translations are protected from automated overwrite (unless you <code>--force</code>).</li>
<li>Language suggestion banner — auto-detects the visitor’s browser language and suggests switching locale, with dismiss + localStorage persistence.</li>
<li>Draft link handling — internal links pointing to drafts are auto-hidden for public visitors and re-activate once the target is published. Editors keep working links.</li>
<li>Language switcher — drop-in function for your theme with WooCommerce cart session transfer across domains.</li>
<li>Admin UI — locale filter dropdown, language badge column, shadow warning banner, and translations metabox on masters.</li>
<li>Flat-file export/import — bulk export all translations to TSV + HTML files, edit offline, re-import.</li>
<li>WP-CLI powered — list untranslated content, push translations, manage slugs — all from the command line.</li>
</ul>
<h4>Works without WooCommerce</h4>
All WooCommerce features (stock, reviews, cart, slugs) activate only when WooCommerce is present. On a standard WordPress site, the plugin handles routing, hreflang, admin UI, and translation management with no extra dependencies.
<h4>Full documentation</h4>
For the complete documentation (data model, WP-CLI command reference, hooks, draft link handler, configuration examples), see the <a href="https://github.com/PiedWeb/wp-ai-polyglot" rel="nofollow ugc">README on GitHub</a>.
<h3>Credits</h3>
Brought to you by Robin (<a href="https://en.piedweb.com" rel="nofollow ugc">Pied Web</a>), inspired by <a href="https://pushword.piedweb.com" rel="nofollow ugc">Pushword CMS</a>, sponsored by <a href="https://woodrockclimbing.com" rel="nofollow ugc">Woodrock Climbing</a>.
Country flag SVGs in <code>assets/flags/</code> are from <a href="https://github.com/lipis/flag-icons" rel="nofollow ugc">flag-icons</a> by Panayiotis Lipiridis, licensed under the MIT License.

PiedWeb AI Polyglot

Multilingual infrastructure for WordPress + WooCommerce. One install, one database, zero duplication. Bring your own translator (AI or human).

kisyamalgavisya

labvaxe

LabVaxe is a lightweight, modular platform plugin. It adds a LabVaxe menu in wp-admin where you can enable/disable modules independently. 
After activation, all modules are disabled by default until you enable them in LabVaxe.
Included modules:
<h4>SEO & Head Studio</h4>
A “no-bloat” head manager with global settings + per-page overrides: 
* Document title override (via WordPress title filters). 
* Meta description, canonical, robots meta. 
* Open Graph tags (og:title, og:description, og:image, og:url, og:locale, etc.). 
* Twitter Cards tags (twitter:card, twitter:title, twitter:description, twitter:image, etc.). 
* Identity / web-app tags: favicon links, Apple touch icon, manifest URL, theme-color. 
* Per-post metabox on all public post types (except attachments): 
 – SEO title / description / canonical override 
 – Robots mode override (default / index,follow / noindex,follow / noindex,nofollow) 
 – OG/Twitter overrides 
 – Per-page custom JSON-LD (application/ld+json)
Optional extras: 
* Hreflang output from a simple language map. 
* Tracking toggles (opt-in): 
 – Google Analytics 4 (GA4) 
 – Google Tag Manager (GTM) 
 – Meta Pixel 
* Optional GTM/Meta Pixel noscript body output (with automatic wp_footer fallback when themes do not call wp_body_open).
<h4>Head Cleaner</h4>
Performance-focused cleanup for head output and certain core assets: 
* Disable emoji detection scripts/styles. 
* Disable feed links, REST discovery links, oEmbed discovery links. 
* Disable RSD link, shortlink, wp_generator meta. 
* Optional removal of core rel=canonical output (use with care). 
* Optional removal of the core “skip to content” link (accessibility impact—use only if your theme replaces it). 
* Optional cleanup of inline block CSS handles (may affect block styling—use only with a custom theme). 
* Optional disable of WordPress <code>wp_img_tag_add_auto_sizes</code> behavior (can reduce responsive image optimization quality).
Important: Head Cleaner is intentionally “sharp”. If you disable something your theme/site relies on, you can break UX, styling, embeds, feeds, accessibility, or SEO. Enable only what you understand.
<h3>External Services</h3>
LabVaxe itself stores only plugin settings (wp_options) and per-post metadata (postmeta) that you enter in wp-admin.
However, the “SEO & Head Studio” module can load external services if you explicitly enable them. All tracking options are disabled by default. 
A tracker is output only when: 
* “Enable tracking (global)” is enabled 
* the specific tracker is enabled (GA4/GTM/Meta Pixel) 
* the tracker ID is set
When enabled, the plugin may load scripts/iframes from these services:
<h4>Google Analytics 4 (GA4)</h4>
<ul>
<li>Loaded from:
<ul>
<li>https://www.googletagmanager.com/gtag/js</li>
<li>https://www.google-analytics.com/</li>
</ul>
</li>
<li>What may be sent:
<ul>
<li>page URL, referrer, device/browser info, events you configure, cookies/identifiers set by Google.</li>
</ul>
</li>
<li>Provider policies:
<ul>
<li>Google Privacy Policy: https://policies.google.com/privacy</li>
</ul>
</li>
</ul>
<h4>Google Tag Manager (GTM)</h4>
<ul>
<li>Loaded from:
<ul>
<li>https://www.googletagmanager.com/</li>
<li>https://www.googletagmanager.com/ns.html (optional noscript iframe when enabled)</li>
</ul>
</li>
<li>What may be sent:
<ul>
<li>depends on your GTM container configuration (can include page URL, events, cookies, etc.).</li>
</ul>
</li>
<li>Provider policies:
<ul>
<li>Google Privacy Policy: https://policies.google.com/privacy</li>
</ul>
</li>
</ul>
<h4>Meta Pixel</h4>
<ul>
<li>Loaded from:
<ul>
<li>https://connect.facebook.net/</li>
<li>https://www.facebook.com/</li>
<li>https://www.facebook.com/tr (optional noscript image request)</li>
</ul>
</li>
<li>What may be sent:
<ul>
<li>page URL, referrer, device/browser info, events you configure, cookies/identifiers set by Meta.</li>
</ul>
</li>
<li>Provider policies:
<ul>
<li>Meta Privacy Policy: https://www.facebook.com/privacy/policy/</li>
</ul>
</li>
</ul>
You control whether these services load by toggles in: 
wp-admin → LabVaxe → SEO & Head Studio → Tracking.

LabVaxe

Modular WordPress platform: enable only the modules you need (SEO/Head output, per-post metadata, JSON-LD, hreflang, and head cleanup).

PiedWeb AI Polyglot vs LabVaxe