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

Geoffrey

To improve your SEO and the accessibility of your content, you must declare changes of language within your content. 
You must also declare translations of your pages to Google to avoid duplicate content.
TinyMCE: For the people still in this old editor, buttons are available to add <code>lang</code> and <code>hreflang</code> attributes on your content, therefore to improve accessibility when screen readers are reading words from different languages than your main page language.
Gutenberg: For Gutenberg users, WordPress already provide the “Language” menu. When selecting a text you can add a specific language. This plugin will enhance this behaviour with its own command, and by remembering the last language code you used. 
This plugin also comes with a hreflang option that you can put on links to tell users “this link lead to a French website” for example.
Example of cases you need this plugin:
<ul>
<li>You translated a blog post in your language from another blog, (hreflang alternate links)</li>
<li>You publish the same article in 2 languages on 2 different websites, (hreflang alternate links)</li>
<li>You use in your content a jargon from another language. (<code>lang</code> attribute)</li>
<li>You link from your post other posts in another language. (<code>hreflang</code> attribute)</li>
<li>Your Menus have some items not translated (<code>lang</code> attributes) or lead to page in another language (<code>hreflang</code>), you can edit those attributes in the Menus admin-menu. (WordPress 5.4 compatibility) If you have a FSE (Full Site Editing) theme, I don’t know how this will work for you, but you can use the Gutenberg commands this plugin put at your disposal.</li>
</ul>
<h3>Features available</h3>
<ul>
<li>Custom <code>hreflang</code> alternate links for posts (page, and custom posts)</li>
<li>Attributes <code>hreflang</code> and <code>lang</code> available and visible in the editor</li>
<li>Attributes <code>hreflang</code> and <code>lang</code> available on your main Menus items. (WordPress 5.4 compatibility)</li>
</ul>
<h3>Known bugs</h3>
In old version of Gutenberg, the <code>hreflang</code> attribute on links is applied, but never save it in database. That is because <code>hreflang</code> is cleaned from WordPress posts. Indeed, it was not well recognized by the WordPress post sanitizing function.
You can donate to support
<ul>
<li><a href="https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=P39NJPCWVXGDY&lc=FR&item_name=Juiz%20Lang%20Attributes2d%20WP%20Plugin&item_number=%23wp%2djla&currency_code=EUR&bn=PP%2dDonationsBF%3abtn_donate_SM%2egif%3aNonHosted" rel="nofollow ugc">Donate what you want with Paypal</a></li>
</ul>
Please, use the support forum to tell me bugs encountered, and be patient
<h3>Other plugins</h3>
<a href="https://wordpress.org/plugins/juiz-social-post-sharer/" rel="ugc">Juiz Social Post Sharer</a>: if you need social buttons. 
<a href="https://fr.wordpress.org/plugins/juiz-outdated-post-message/" rel="nofollow ugc">Juiz Outdated Post Message</a>: if you want to put a warning on old post on your blog. 
<a href="https://wordpress.org/plugins/embed-can-i-use/" rel="ugc">Embed Can I Use</a>: if you talk about support of HTML 5, CSS3 or JS API, you need to embed Can I Use support tables. 
<a href="https://wordpress.org/plugins/social-integration-for-bluesky/" rel="ugc">Social integration for BlueSky</a>: Add a Profile Banner, a list of your recent BlueSky Posts, or an auto syndication on BlueSky with this plugin.

Juiz Lang Attribute

Add a custom HREFLANG meta box on your post to manually edit the link between your post and a translation (which could be outside your domain).

LabVaxe vs Juiz Lang Attribute