Ecommerce localization for the whole catalogue

Add one line of code to your store, or point your domain at Proxylang, and choose your languages. Product pages, collections, filters, reviews and blog content are all translated automatically, along with the meta titles and descriptions search engines read. Nothing is installed in your store’s admin and no product feed has to be exported.

They are translated the first time somebody opens them in a given language, and cached from then on. There is no import step and nothing to re-run after a catalogue update, which is what makes this workable for stores that add or retire products weekly.

Yes, as long as the reviews render as text on the page — including reviews written after you set Proxylang up. Reviews are usually the biggest single body of text in a store and the least likely to be translated by hand, so this is often where a shopper in a new market first sees your store as a real one.

Not from the translation layer. Numbers in your pages are preserved exactly as your store produces them. Currency display is a store setting or a payment-provider feature, and once it is switched on, Proxylang translates the resulting page as normal.

It is good when each language is a real page at its own URL, and worthless when the translation only happens in the shopper’s browser, because search engines then index one language and nothing else. From the Start plan, Proxylang gives each language its own indexable URL, hreflang tags, and its own sitemap entries, so your product and collection pages can rank in each market’s search results.

Yes, and with any other platform, because Proxylang reads the rendered page rather than your database. There are setup walkthroughs for the common platforms if you want the platform-specific steps rather than the general ones.