Universally Documentation

Step-by-step guides, multilingual SEO tips, and best practices to help you translate and scale your WordPress website.

Supported platforms

Universally works with WordPress through a dedicated plugin, with Astro through a native integration, with seven website builders and any other site through one script tag, and with every other stack through a translation API that only needs your pages as HTML.

WordPress

WordPress is the primary supported platform. The Universally plugin handles everything automatically: language detection, translation, caching, URL routing, and the language switcher. Install the plugin, connect your API key, and you’re done. See Install on WordPress.

This works with standard WordPress themes, page builders (Elementor, Divi, Beaver Builder), WooCommerce, and most popular plugins. If your content renders as HTML on the page, Universally can translate it.

Astro

Astro has a native integration, in Beta. You install one package and keep one page tree, and every language is served under its own URL prefix, such as /fr/about. See Astro integration.

Website builders

Each of these connects with one script tag in the site-wide head, and pages are translated in the visitor's browser. See JavaScript serving mode for what that covers.

Any website

Any other site you can add a script tag to uses the Any Website project type. You add the same one line, then pick JavaScript mode, which translates in the browser at the same addresses, or Subdomain mode, which serves each language on its own subdomain. See Install on any website.

Any stack via the API

When you would rather translate on your own server, the translation API takes HTML and returns it translated, whatever built the page. It works with:

  • Static site generators: Next.js, Gatsby, Hugo, Jekyll
  • Headless CMS setups: Contentful, Strapi, Sanity, Prismic, WordPress headless
  • Single-page applications: React, Vue, Angular (via server-side middleware)
  • Custom-built sites: any framework or language, as long as you can make an HTTP request

The API integration requires developer involvement, since you need to add the translation call into your server or build pipeline.

Shopify, BigCommerce and Wix

These three have no native integration yet. They appear in the dashboard's project screen marked Coming Soon, which is also the honest status: they are planned, with no date to quote.

Until one lands, these sites connect the same way any custom stack does: through the API, wherever you can reach your own HTML output at the server level. That is a build rather than an install. If one of them matters to you, ask support where it stands.

Was this helpful?