Weglot plugin review and common issues

Weglot uses JavaScript to capture and replace text on the page. Untranslated sections may be loaded after Weglot’s script runs (dynamic AJAX content) or may be excluded by Weglot’s translation rules. Go to Weglot Dashboard → Translation → Exclusion Rules to check if the affected content is excluded. For dynamically loaded content, ensure Weglot’s JavaScript loads before your page builder or plugin JavaScript — adjust script loading order in your caching or performance plugin settings. Some content types require additional configuration in Weglot’s Dashboard → Advanced → Custom Translated Element.

The language flash occurs because Weglot’s JavaScript loads and then replaces text after the initial page render. Reduce flash by: (1) enabling Weglot’s Server-Side Translation option (available in some plans) which pre-translates the HTML response — eliminating client-side replacement entirely; (2) loading Weglot’s script in the document head rather than the footer for faster execution; (3) using a caching plugin to serve pre-cached translated pages — once a translated page is cached, it serves the translated HTML directly without client-side processing.

Weglot translates text content but does not change WooCommerce currency settings by language. Currency display is controlled by WooCommerce’s currency settings and any currency switcher plugin you use (e.g., WooCommerce Currency Switcher). Configure currency behavior separately from Weglot — for example, use a WooCommerce currency plugin to set a default currency per language based on URL or geolocation. Weglot’s role is text translation; currency handling is a WooCommerce-layer configuration.

Go to Weglot Dashboard → Translation → select a language. The translation editor shows all translated strings with their originals. Search for the string to edit, click it, and update the translation. Changes apply immediately without plugin updates or WordPress cache clearing (translations are served from Weglot’s CDN). For a visual editing experience on the actual page, use Weglot’s Visual Editor (accessible from the dashboard) which works similarly to TranslatePress — click on page elements and edit translations in context.

Yes. In Weglot Dashboard → Translation → Exclusion Rules, add URLs or URL patterns to exclude from translation. You can exclude specific pages (e.g., /terms-of-service/), URL prefixes (/wp-admin/), or URL patterns using wildcards. Excluded pages display in the original language regardless of the visitor’s language selection. This is useful for pages with content that should not be translated (legal documents in a specific jurisdiction, country-specific landing pages, etc.).

Weglot offers faster setup, automatic translation, and zero server performance impact. WPML offers more control over translations, one-time purchase with annual renewal (cheaper long-term for content-heavy sites), and data stored on your own server. For a small business site with under 50,000 words needing quick multilingual deployment, Weglot’s convenience justifies the monthly cost. For large content-heavy sites, agencies managing multiple client sites, or teams concerned about data ownership, WPML or Polylang Pro provide better long-term value.

If you cancel your Weglot subscription, translated content is no longer served — your site reverts to displaying only the original language. Translations are stored on Weglot’s servers, and without an active subscription, they are not accessible to visitors. You can export translations from the Weglot dashboard before cancelling. If migrating away from Weglot, the Weglot dashboard provides migration tools to export translations to WPML or Polylang format.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.