TranslateGuard for WooCommerce

WooCommerce product translation checks for Polylang. Find missing translations, stale content, and catalog inconsistencies before customers encounter them. Use it for a multilingual product audit after catalog updates or before reviewing a translated storefront. Scans inspect catalog consistency; they do not translate products or judge linguistic quality. Polylang is required for scanning. Check your multilingual catalog Run a scan from WooCommerce → TranslateGuard, review the findings, and open affected products to investigate. Filter issues and export a CSV to organize follow-up work. TranslateGuard requires Polylang for scanning. Polylang for WooCommerce is optional; some synchronization checks are limited without it. Scans do not modify products or translations. Video overview https://www.youtube.com/watch?v=WgSE0PUycBs Documentation: https://cobaltbranchlabs.com/plugins/translateguard-for-woocommerce Contact: hello@cobaltbranchlabs.com Features

• Manual, resumable batched product scans
• Ten multilingual checks (relationships, missing translations, content, taxonomies, images, commercial fields, attributes, variations, freshness, and more)
• Issue list with search, sort, filters, detail view, dismiss/reopen, and CSV export
• Scan history with progress and cancel
• Settings for checks, batch size, languages, retention, and uninstall cleanup
• Diagnostics report download
• Daily retention cleanup for aged scan/issue records
• Dedicated capability: manage_translateguard

Privacy Scans run on your WordPress site. Product data is not sent to TranslateGuard or third parties. Findings are stored in your database. Administrators control retention and deletion. There is no telemetry. Requirements

• WordPress 6.5+
• PHP 8.1+
• WooCommerce 8.5+
• Polylang (for scanning)

Polylang for WooCommerce is optional. Some WooCommerce-specific sync expectations soft-degrade when it is not installed.

1.0.9

• Removed an unintended deployment helper from the release package.
• Added release-package validation to prevent deployment helpers from being distributed.

1.0.8

• Fixed deactivation cleanup so pending TranslateGuard scan batches are cancelled regardless of their scan arguments.
• Expanded Action Scheduler lifecycle regression coverage.
• Confirmed compatibility with WordPress 7.1.2.

1.0.7

• Restricted commercial-field checks to explicitly approved, no-argument product getters.
• Improved scheduled scan cleanup during plugin deactivation.
• Added versioned capability installation and authorized capability repair.
• Corrected per-site data deletion behavior on WordPress multisite.
• Improved CSV compatibility with PHP 8.4 and standards-compliant escaping.
• Expanded WordPress 7.1 and WooCommerce 11.1 compatibility coverage.

1.0.6

• Restore Plugin URI to the Cobalt Branch Labs product page.
• Exclude developer README from the WordPress.org package.

1.0.5

• Declare WooCommerce 11.1 compatibility (WC tested up to: 11.1).

1.0.4

• Use prepared SQL for legacy post meta key migration (Plugin Check compliance).
• Set plugin author to Cobalt Branch Labs in the plugin header.

1.0.3

• Declare WordPress 7.1 compatibility (Tested up to: 7.1).
• Improve issues list table row headers for WordPress 7.1 screen-reader accessibility.

1.0.2

• Rename scan/issue CPT identifiers to translateguard_scan / translateguard_issue.
• Migrate legacy tg_* post types and meta keys on upgrade.

1.0.1

• Limit admin dependency notices to TranslateGuard screens (Guideline 11).
• Keep optional Polylang for WooCommerce guidance on plugin UI only.

1.0.0

• First stable release for WordPress.org.
• Polylang-backed multilingual product QA for WooCommerce.
• Batched scans with lock/cancel, ten checks, admin UI, CSV export, and retention cleanup.