TranslatePress vs Weglot for Japanese WordPress: Inside the CMS or Outside It

A WordPress site can get a Japanese version from either direction: a plugin that lives inside WordPress, or an external translation layer connected to WordPress. TranslatePress and Weglot are credible examples of each model. The right choice depends less on the translation itself and more on where the Japanese copy lives, who edits it, and which team can operate the result.

Independent guide. This guide is based on current public documentation, not hands-on testing. Japan Legible has no commercial relationship with TranslatePress or Weglot. All product links are direct, non-affiliate links. Official pages were checked on August 11, 2026, and this guide makes no guarantee of search performance for either tool.

Short answer

TranslatePress keeps translation inside WordPress: the plugin creates translated versions of pages, stores them in the site's own database, and offers a visual translation interface. Weglot works as an external layer: its WordPress integration connects the site to the Weglot translation service, and the multilingual SEO architecture is delivered by Weglot.

For a team that wants WordPress to remain the single source of truth, TranslatePress is the natural fit. For a team that wants a centralized translation workspace or prefers Weglot's documented server-side SEO path, Weglot can fit. Neither choice removes the need for a named Japanese reviewer.

The decision behind the comparison

The real question is where the Japanese version lives.

• Inside WordPress: translated content is part of the site's database, edited in the WordPress context, and managed by the same people and plugins that manage the English site.
• Outside WordPress: translation lives in a vendor account, and WordPress connects to it. Editing, glossary, and team controls are in the vendor's workspace.

Both can produce dedicated Japanese URLs, translate metadata, and add language signals. They differ in ownership: who holds the translations, what happens when a license changes, and how much of the workflow is visible to the WordPress team.

Shared ground

Google's multilingual-site guidance asks for distinct URLs per language, hreflang annotations or sitemaps, language-switch links, and no automatic redirects based on assumed language. Google's localized-versions guidance shows that hreflang can be delivered through HTML link tags, HTTP headers, or XML sitemaps, with reciprocal links between variants.

WordPress adds its own reality. The site already has a content database, a theme, an SEO plugin, and a publishing workflow. A Japanese version should fit that system or deliberately not fit it. That choice, more than any feature checkbox, determines whether the site stays maintainable.

TranslatePress: translation as part of WordPress

The official pricing page presents TranslatePress as a WordPress plugin with three yearly plans. On August 11, 2026, it displayed Personal at €8.25 per month billed annually at €99 per year for one site with 50,000 AI-translated words, Business at €16.59 per month billed annually at €199 per year for three sites with 200,000 words, and Developer at €29.09 per month billed annually at €349 per year for unlimited sites with 500,000 words. Premium plans list the SEO Pack and Multiple Languages add-ons as included, along with URL slug translation.

Two ownership details stand out. TranslatePress states that all translations are stored locally in the site's server database and that they continue to work if a license is not renewed. It also describes a visual translation interface, which matches the idea that Japanese copy is edited in the WordPress context rather than in a separate system. The pricing page also documents a 15-day money-back guarantee.

The SEO Pack documentation adds the technical boundary: it translates URL slugs for posts, pages, custom post types, taxonomies, and terms, plus page titles and descriptions and social titles and descriptions, and it extends popular SEO plugins with multilingual sitemaps. The page names Yoast SEO, SEOPress, All in One SEO Pack, Squirrly SEO, and Slim SEO. In this model, WordPress SEO plugins remain the engine; TranslatePress supplies the translated fields and sitemap coverage.

Weglot: an external layer with a documented SEO path

Weglot's help center states that implementation details vary by integration. Its JavaScript snippet does not offer SEO benefits because translations render client-side and are not crawlable. Subdomain and subdirectory integrations create dedicated URLs, serve translated HTML server-side, add hreflang tags automatically, and translate metadata, titles, image alt text, and structured data. For WordPress, that means the team should confirm which deployment mode the WordPress integration uses before assuming the Japanese URLs are indexable.

The external model changes the operating boundary. Weglot's pricing page plans by translated words and languages: Free at 2,000 words and one language, Starter at about $17 per month for 10,000 words, Business at $32 per month for 50,000 words and three languages, Pro at $87 per month for 200,000 words and five languages, and higher tiers up to five million words. USD figures are estimates based on euro pricing, and annual billing includes two months free.

The same page describes a workspace: glossary rules, team members, translation memory, and professional translation services. That is a centralized editing model. The Japanese workflow lives partly in Weglot, not only in WordPress. The pricing FAQ also describes word limits as fixed per account and states that translations can be discontinued if the account exceeds its limit, unless auto-upgrade is enabled.

The SEO boundary

Both tools claim Google-aligned multilingual SEO, but they implement it at different layers.

TranslatePress works through WordPress: translated slugs, metadata, and sitemaps come from its SEO Pack plus the site's existing SEO plugin. This is a good fit when the WordPress SEO setup is already mature and the team wants one place to manage metadata.

Weglot handles URLs, hreflang, and translated SEO fields through its service, with the specific behavior depending on the integration. The team relies on Weglot to emit the language signals correctly. The help center's integration caveat means the WordPress deployment should be verified in rendered HTML, including hreflang reciprocity and translated metadata.

Neither source guarantees Japanese rankings. Both sources describe prerequisites: crawlable pages and clear language signals. Demand still depends on the pages, the queries, and the content.

The cost boundary

The pricing models are structurally different, and the difference matters for a Japanese launch.

| Dimension | TranslatePress | Weglot | | --- | --- | --- | | Licensing | Yearly WordPress license by site count | Monthly service by words and languages | | Storage | Translations in the site database | Translations in the vendor account | | Word quota | AI-translated words included with the license | Fixed translated-word limit per plan | | Add-ons | SEO Pack and language add-ons included | Glossary, team, memory, and pro translation by plan | | Currency | EUR, billed annually | USD shown as an estimate of euro pricing |

A small one-site WordPress project may be cheaper with TranslatePress. A team that manages several sites or wants one translation workspace may prefer Weglot's per-account pricing. Neither model is usefully cheaper until you count the actual word volume, the number of languages, the review hours, and what happens when the site changes.

The workflow test

Run the same pilot in both models:

1. Create a Japanese homepage, one product page, pricing, a trust page, and a contact path.
2. Inspect rendered HTML for dedicated Japanese URLs, Japanese content, translated metadata, hreflang reciprocity, canonicals, and sitemap entries.
3. Ask a qualified reviewer to reject unacceptable Japanese copy and count the edits.
4. Update a page in English and watch what happens to the Japanese version.
5. Check who can edit, approve, and publish Japanese, and what happens if the license changes.

Who should choose what

Choose TranslatePress when WordPress should remain the system of record, when the team already depends on WordPress SEO plugins, when one site or a small site network is in scope, and when keeping translations in the site's database matters.

Choose Weglot when the team wants a centralized translation workspace, when multiple sites or languages need one workflow, when Weglot's documented subdomain or subdirectory SEO architecture is confirmed for the WordPress deployment, and when the team is comfortable with an external dependency for serving translations.

Choose neither as a substitute for a Japanese editorial owner. The tool can reduce publishing friction. It cannot decide what a Japanese buyer should believe.

Final recommendation

Compare the two models against one real WordPress page, not against the pricing tables. Translate the page, inspect the rendered source, and have a reviewer mark every sentence that needs more than translation. The cost structure will follow the workflow, and the workflow should follow where the team wants the Japanese version to live.

Review TranslatePress's current plans on the official site. Review Weglot's current plans on the official site.