john201502

<p>VelaLang lets WordPress sites become multilingual without creating duplicate pages.</p>
<p>This free version is focused on one primary language and one secondary language. It keeps the primary language in the normal WordPress title and editor, then stores the secondary language as extra fields on the same page or post. Visitors see the primary language at the normal URL and the secondary language at a clean prefixed URL.</p>
<p>Example:</p>
<ul>
<li>/pricing/ shows the primary language.</li>
<li>/zh/pricing/ shows the secondary language from the same WordPress page.</li>
</ul>
<p>Core ideas:</p>
<ul>
<li>No duplicate pages.</li>
<li>One menu, two labels.</li>
<li>One Elementor Free widget, two text values.</li>
<li>No page linking.</li>
<li>No string scanning.</li>
<li>No complex translation database.</li>
<li>A small support surface by design.</li>
</ul>
<h3>Features</h3>
<ul>
<li>Choose common primary and secondary languages from presets.</li>
<li>Configure custom primary and secondary language names, codes, and locales.</li>
<li>Configure a secondary URL prefix such as /zh/, /ja/, /fr/, or /es/.</li>
<li>Warn about permalink and URL prefix conflicts before they become routing problems.</li>
<li>Add secondary title, excerpt, and content fields to posts and pages.</li>
<li>Highlight secondary-language fields clearly in Classic Editor, Block Editor, Elementor Free widgets, menus, widgets, and settings.</li>
<li>Show translation completion status in the post and page lists.</li>
<li>Add quick links to view the secondary-language version from post and page lists and editors.</li>
<li>Add admin bar shortcuts for switching between primary and secondary versions while reviewing content.</li>
<li>Translate the site title and tagline for the secondary language.</li>
<li>Show secondary content at the prefixed URL.</li>
<li>Add secondary labels to WordPress menu items.</li>
<li>Automatically rewrite internal menu links for the secondary language.</li>
<li>Automatically rewrite internal content links for the secondary language.</li>
<li>Set the secondary language html lang/dir attributes on secondary URLs.</li>
<li>Add secondary fields to common Elementor Free widgets, including text, links, images, maps, video URLs, icon lists, tabs, accordions, toggles, ratings, counters, progress bars, testimonials, social icons, and audio basics.</li>
<li>Add secondary title fields to classic WordPress widgets, plus secondary content fields for Text and Custom HTML widgets.</li>
<li>Output hreflang and x-default tags.</li>
<li>Add a language switcher with [velalang_switcher].</li>
<li>Choose a default switcher style: language names, language codes, dropdown, or globe button.</li>
<li>Place the switcher manually, as the last menu item, or as a fixed floating switcher.</li>
<li>Choose text, flags, or flags with text for the switcher.</li>
<li>Choose the floating switcher position.</li>
<li>Adjust floating switcher offsets and choose a preset floating style.</li>
<li>Includes a translation template and Simplified Chinese translation files.</li>
<li>Keeps settings and translated content when deleting the plugin unless cleanup is enabled.</li>
<li>Optionally redirect first-time homepage visitors based on browser language.</li>
</ul>
<h3>Supported Editors</h3>
<p>VelaLang intentionally keeps a small support surface.</p>
<p>Supported in this version:</p>
<ul>
<li>Classic Editor.</li>
<li>WordPress Block Editor, using the VelaLang secondary-language panel in the editor’s meta boxes area.</li>
<li>Elementor Free common widgets, including Heading, Text Editor, Text Path, Video, Button, Image, Image Carousel, Google Maps, Icon, Icon List, Icon Box, Image Box, Alert, Testimonial, Counter, Progress Bar, Star Rating, Social Icons, SoundCloud, Audio, Tabs, Accordion, and Toggle.</li>
<li>Classic WordPress widgets: secondary widget titles, plus secondary widget content for Text and Custom HTML widgets.</li>
</ul>
<p>Not supported in this version:</p>
<ul>
<li>Divi.</li>
<li>Bricks.</li>
<li>Beaver Builder.</li>
<li>WPBakery.</li>
<li>Oxygen.</li>
<li>More than two languages.</li>
<li>Elementor Pro widgets, Theme Builder, forms, loops, and advanced dynamic content.</li>
<li>Deep media-library attachment translation.</li>
<li>WooCommerce translation.</li>
</ul>
<h3>Language Switcher</h3>
<p>Use the VelaLang shortcode:</p>
<ul>
<li>[velalang_switcher]</li>
</ul>
<p>The default style can be selected in VelaLang in the WordPress admin menu.</p>
<p>Shortcode examples:</p>
<ul>
<li>[velalang_switcher style=”names”]</li>
<li>[velalang_switcher style=”codes”]</li>
<li>[velalang_switcher style=”dropdown”]</li>
<li>[velalang_switcher style=”globe”]</li>
<li>[velalang_switcher icon=”yes”]</li>
</ul>


VelaLang

Make your WordPress site multilingual without duplicating pages.

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).

VelaLang vs LabVaxe