AI translation for a WordPress site, with the SEO parts handled

Where it fits

The list below is meant to be checked line by line against the site you actually have.

• The site already exists and is not going to be rebuilt for the sake of translation
• Pages were built with Elementor or Gutenberg and the layout has to survive
• Each language needs its own URL, not a cookie or a browser-language redirect
• Search engines need to be told which page is which language
• The site sells with WooCommerce and the products have to stay working products after translation, not copies of the description
• The budget is a per-use AI bill you control, not a per-language subscription

What it translates

Posts, pages and products

Title, content, excerpt, categories and tags in one action.

Builder content

Elementor and Gutenberg are translated as text only — layout and styles are untouched. Custom widgets and repeaters are detected from the builder’s own type system rather than configured one by one.

WooCommerce

Products, product categories, tags, brands and attributes. Price, stock and gallery are carried over, so the translated product is a working product.

Taxonomies

Per-language versions of categories, tags and custom taxonomies, with translated archives.

Interface strings

The theme and plugin strings a visitor actually sees can be captured and translated, and official wordpress.org language packs are pulled automatically where they exist.

Menus

One menu serves every language; items switch to their translation.

The SEO parts

These are the parts that are tedious to do by hand and invisible when they are wrong: per-language URLs under a prefix, hreflang alternates that reference each other, a canonical per language, and a sitemap that lists all of them. They are emitted as a consequence of translating, not as a separate setup step.

What the AI costs, and who holds the key

There are two ways to connect, and the difference decides whether you enter a key at all.

The AI client built into WordPress

WordPress 7.0 ships an AI client. If the site owner has already connected a provider under Settings → Connectors, there is nothing to configure here: the plugin sends only the text to be translated, holds no key of its own, and shares that one connection with every other plugin on the site.

A direct connection

Entirely optional, and it needs your own key. It exists because the connectors WordPress ships cover Anthropic, Google and OpenAI, and a site whose network cannot reach any of those still needs a way to translate. It speaks the OpenAI-compatible chat API, so any service implementing it can be entered by hand.

Either way the AI account is yours. There are no per-translation fees from us, no quota from us, and no account with us of any kind. Text that has already been translated is served from your own database and never leaves the site again.

Keeping terms consistent

A glossary pins how chosen terms are translated — a brand name kept as-is, a term forced to one wording — so repeated runs stay consistent rather than each one picking its own synonym.