WP Plugin · Translation

Queryra + Weglot

Works (complementary stack)

Weglot translates your WooCommerce store content and UI. Queryra interprets multilingual search queries natively. Together they form a clean stack for multilingual stores — no special integration needed on either side.

Tested with

Weglot 4.x

Queryra plugin

v1.1.11+

Setup time

10 minutes

What works

  • Weglot translates UI, posts, products, meta tags, slugs, and emails (its specialty)
  • Queryra handles all search queries with multilingual semantic interpretation
  • Visitor types a query in any language — French, German, Polish, mixed — Queryra returns the same matching products
  • No language-specific synonym lists required, ever
  • Weglot's URL prefix structure (/fr/, /de/, /es/) works seamlessly
  • Compatible with Weglot Free, Starter, Business, Pro, and Advanced tiers

Why this works without integration

Translation and search are different problems. Weglot is a translation system — it maps text from one language to another. Queryra is a search system — it interprets what a visitor is looking for and finds matching products.

On a Weglot site, content is translated for visitors at render time. When a visitor on /fr/ searches, Queryra receives the raw query and runs it through its multilingual parser:

'veste imperméable'      (FR)        → semantic = waterproof jacket → 3 results
'wasserdichte Jacke'     (DE)        → semantic = waterproof jacket → 3 results
'kurtka wodoodporna'     (PL)        → semantic = waterproof jacket → 3 results
'jacket for rain'        (EN)        → semantic = waterproof jacket → 3 results
'wasserdichte jacket'    (DE+EN mix) → semantic = waterproof jacket → 3 results

Every query resolves to the same vector embedding regardless of language. Weglot doesn't need to translate the query; Queryra already understands it.

Recommended setup

  1. 1

    Install Weglot and pick your languages

    Standard Weglot setup: install plugin, paste API key from weglot.com, choose target languages. Free tier covers 1 language and 10,000 words — enough to test the full stack.

  2. 2

    Turn OFF Weglot's Translate Search toggle

    Go to Settings → Weglot → WordPress Settings and uncheck Translate Search. This toggle was designed for sites using default WordPress ?s= search. With Queryra in place, search uses its own endpoint, so Weglot's translate-search has nothing to intercept. Turning it off makes the responsibility split explicit: Weglot for content, Queryra for queries.

  3. 3

    Install Queryra and sync your records

    From your Queryra dashboard, click Sync Records. Queryra indexes your default-language content (Weglot stores translations on its servers, not in wp_posts). Multilingual queries are handled by the parser, not by per-language records.

  4. 4

    Test from the front-end

    Open your site, switch to a non-default language, run a search in that language. Results should appear naturally. If the search box submission lands on the default-language page after submit, that's a Weglot URL-rewriting quirk worth raising with their support — Queryra-side everything is working correctly.

Stack at a glance

PluginRoleSettings
WeglotUI, content, meta tags, slugs, emailsTranslate Search: OFF
QueryraAll search queries (semantic, multilingual)Default settings

Want a deeper read on Weglot for WooCommerce?

Our blog post covers Weglot's pricing tiers, what it translates in WooCommerce specifically (variable products, attributes, currency), and how AI search fits into a multilingual stack.

Read: Weglot for Multilingual WooCommerce

Running into issues? See the troubleshooting guide, the general FAQ, or email contact@queryra.com.

Try Queryra freeSee TranslatePress integration

Last updated: May 4, 2026 · Last tested with Weglot 4.x and Queryra plugin 1.1.11.