sserghei

<p>WeLocale translates your website into 50+ languages with one connection. No code changes, no<br />
developer, live in minutes. Add your App Key and the WeLocale widget translates your site in<br />
place, with a built-in language switcher and SEO hreflang tags (on paid plans).</p>
<ul>
<li>One connection, no code changes</li>
<li>50+ languages, AI-powered translations</li>
<li>Built-in language switcher</li>
<li>SEO hreflang tags (Pro and Scale plans)</li>
<li>Words are stored permanently and never reset monthly</li>
</ul>
<p>You manage languages, translations, the switcher, and SEO in your WeLocale dashboard. This plugin<br />
only connects your site using your App Key; translations are stored in your WeLocale account, not<br />
in WordPress. The widget always loads its latest version from welocale.net, so improvements arrive<br />
without updating this plugin.</p>
<h3>External service</h3>
<p>This plugin connects your site to WeLocale (https://welocale.net), a third-party website-translation<br />
service, and requires a WeLocale account. When enabled, it loads the WeLocale widget script<br />
(https://welocale.net/widget/latest/loader.js) on your public pages using your App Key. The widget<br />
reads the visible text of your pages to translate it.</p>
<ul>
<li>Terms of Service: https://welocale.net/terms</li>
<li>Privacy Policy: https://welocale.net/privacy</li>
</ul>


WeLocale

Translate your WordPress site into 50+ languages with one connection. AI-powered, no code changes.

kisyamalgavisya

labvaxe

<p>LabVaxe is a lightweight, modular platform plugin. It adds a LabVaxe menu in wp-admin where you can enable/disable modules independently.<br />
After activation, all modules are disabled by default until you enable them in LabVaxe.</p>
<p>Included modules:</p>
<h4>SEO & Head Studio</h4>
<p>A “no-bloat” head manager with global settings + per-page overrides:<br />
* Document title override (via WordPress title filters).<br />
* Meta description, canonical, robots meta.<br />
* Open Graph tags (og:title, og:description, og:image, og:url, og:locale, etc.).<br />
* Twitter Cards tags (twitter:card, twitter:title, twitter:description, twitter:image, etc.).<br />
* Identity / web-app tags: favicon links, Apple touch icon, manifest URL, theme-color.<br />
* Per-post metabox on all public post types (except attachments):<br />
  – SEO title / description / canonical override<br />
  – Robots mode override (default / index,follow / noindex,follow / noindex,nofollow)<br />
  – OG/Twitter overrides<br />
  – Per-page custom JSON-LD (application/ld+json)</p>
<p>Optional extras:<br />
* Hreflang output from a simple language map.<br />
* Tracking toggles (opt-in):<br />
  – Google Analytics 4 (GA4)<br />
  – Google Tag Manager (GTM)<br />
  – Meta Pixel<br />
* Optional GTM/Meta Pixel noscript body output (with automatic wp_footer fallback when themes do not call wp_body_open).</p>
<h4>Head Cleaner</h4>
<p>Performance-focused cleanup for head output and certain core assets:<br />
* Disable emoji detection scripts/styles.<br />
* Disable feed links, REST discovery links, oEmbed discovery links.<br />
* Disable RSD link, shortlink, wp_generator meta.<br />
* Optional removal of core rel=canonical output (use with care).<br />
* Optional removal of the core “skip to content” link (accessibility impact—use only if your theme replaces it).<br />
* Optional cleanup of inline block CSS handles (may affect block styling—use only with a custom theme).<br />
* Optional disable of WordPress <code>wp_img_tag_add_auto_sizes</code> behavior (can reduce responsive image optimization quality).</p>
<p>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.</p>
<h3>External Services</h3>
<p>LabVaxe itself stores only plugin settings (wp_options) and per-post metadata (postmeta) that you enter in wp-admin.</p>
<p>However, the “SEO & Head Studio” module can load external services if you explicitly enable them. All tracking options are disabled by default.<br />
A tracker is output only when:<br />
* “Enable tracking (global)” is enabled<br />
* the specific tracker is enabled (GA4/GTM/Meta Pixel)<br />
* the tracker ID is set</p>
<p>When enabled, the plugin may load scripts/iframes from these services:</p>
<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>
<p>You control whether these services load by toggles in:<br />
wp-admin <span aria-hidden="true" class="wp-exclude-emoji">→</span> LabVaxe <span aria-hidden="true" class="wp-exclude-emoji">→</span> SEO & Head Studio <span aria-hidden="true" class="wp-exclude-emoji">→</span> Tracking.</p>


LabVaxe

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

WeLocale vs LabVaxe