Hreflang Manager – Hreflang Implementation for International SEO vs LabVaxe

The Hreflang Manager plugin provides you an easy and reliable method to implement hreflang in WordPress. For more information on the technical use of hreflang, please consider reading the official Google documentation. Pro Version The Pro version of this plugin is available on our website with additional features, including the synchronization of hreflang data across all sites in a network, an integrated Hreflang Checker for detecting implementation issues, a Locale Selector to display available alternate versions, support for adding hreflang information in XML sitemaps, up to 100 alternate versions per connection, tools for importing hreflang data from spreadsheets, and more. Features Supports the hreflang implementation of different websites or the sub-sites of a WordPress network Supports all the languages defined with ISO 639-1 Supports all the scripts defined with ISO 15924 Supports all the countries defined with ISO 3166-1 alpha-2 A maximum of 10 alternative versions of the page per connection Includes a tag inspector to verify the correct implementation in the front-end Allows configuring hreflang from the post editor or from a centralized menu Ability to select the default languages, scripts, and countries Automatically deletes the hreflang data of the deleted posts Getting Started To begin working with the plugin, you may find the following Knowledge Base article helpful: How to Manually Add Hreflang Data Once your configuration is complete, you can confirm that your hreflang implementation works as expected with the following guide: Verifying and Debugging Your Hreflang Implementation For more advanced configuration, examples, and troubleshooting, visit the Plugin Knowledge Base.

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: SEO & Head Studio 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). Head Cleaner 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 wp_img_tag_add_auto_sizes 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. External Services 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: Google Analytics 4 (GA4) Loaded from: https://www.googletagmanager.com/gtag/js https://www.google-analytics.com/ What may be sent: page URL, referrer, device/browser info, events you configure, cookies/identifiers set by Google. Provider policies: Google Privacy Policy: https://policies.google.com/privacy Google Tag Manager (GTM) Loaded from: https://www.googletagmanager.com/ https://www.googletagmanager.com/ns.html (optional noscript iframe when enabled) What may be sent: depends on your GTM container configuration (can include page URL, events, cookies, etc.). Provider policies: Google Privacy Policy: https://policies.google.com/privacy Meta Pixel Loaded from: https://connect.facebook.net/ https://www.facebook.com/ https://www.facebook.com/tr (optional noscript image request) What may be sent: page URL, referrer, device/browser info, events you configure, cookies/identifiers set by Meta. Provider policies: Meta Privacy Policy: https://www.facebook.com/privacy/policy/ You control whether these services load by toggles in: wp-admin → LabVaxe → SEO & Head Studio → Tracking.