I need a translation plugin on my WordPress website.

How do I translate my website?

Q&A with CourseVector

This is a question we hear a lot at CourseVector, especially from municipal clients, service businesses, and organizations that want to be more accessible without accidentally hurting SEO or creating compliance problems.

There are a ton of translation options available for your WordPress website. But which one you choose matters a lot. Let’s walk through what actually matters before you install anything.

The real question isn’t “Do I need a translation plugin?” It’s: Do I need automatic translation… or real multilingual pages? Those are two very different goals.

Option 1: Automatic translation (quick and low effort)

A common tool for this is GTranslate. This plugin produces live, on-the-fly visitor-side translation.

This approach works like this:

• Your site stays in one language
• The plugin dynamically translates the content when a visitor switches languages
• You do not create separate pages for each language

People might choose GTranslate because it’s fast to launch with minimal setup. The cost for this plugin is low and there is no content duplication or separate page management.

The important limitation (especially for SEO)

With most automatic-translation setups:

• Google does not treat each language as its own fully optimized page
• You usually are not ranking in other languages
• Translations are machine-generated and not reviewed

This may not be a problem if you’re a PA municipality that is not trying to rank your website in another language. This option is also good for municipalities, commercial clients, and organizations whose visitors need quick readability, whereby removing language friction allows access to important information as long as SEO is not the main goal for translation.

Option 2: True multilingual content (SEO-ready)

If you actually want:

• separate language versions of pages
• proper indexing by search engines
• full control over translated text

then you are looking at a multilingual system such as OnTheGoSystems’s WPML plugin. We’ve used the WPML tool on several of our clients’ sites.

The WPML plugin creates real translated pages with unique URLs for each page. WPML does offer AI / machine translation now, but this should not be thought of as an “automatic translation”. It automatically generates the translation inside your editor, not for the visitor. This means with WPML the translation is created for you, you review / edit it, and then you publish the page.

Why this matters for SEO

With a full multilingual setup:

• each language version can be indexed
• proper language signals (hreflang, page structure, URLs) are created
• translations can be professionally written instead of machine-generated

This is the only realistic path if your goal is to show up in search results for users who search in another language.

One complaint we receive about this plugin is that our clients don’t understand their pricing. WPML uses credits for translation. Each package comes with credits. There are also pay-as-you-go options. Because you’re translating and then publishing a page, you’re paying for the translation, with your purchased credits, one time. You are not paying to translate a page every time a visitor wishes to see it in the new language. If WPML has already translated a sentence before, it can reuse that translation on other pages. This means you don’t spend credits translating the same text again.

The part most sites overlook: accessibility and accuracy

For our government and compliance-focused clients, this is an important nuance.

Automatic translation does not guarantee accessibility, does not guarantee plain-language accuracy, can misinterpret legal, policy, or public-service content.

If the content involves public notices, legal language, instructions for residents, or emergency information that must be translated machine translation should be treated as a convenience tool and not an authoritative version.

TIP: It’s important to note that WPML and GTranslate do not translate PDFs or other documents at the time of this writing. If you must post documents in another language, the translation responsibility is yours.

This is especially important given your broader accessibility and risk-management goals that we already build into sites. It’s always a good idea to check with your solicitor if you have questions.

A simple decision guide

Here’s how we normally decide with clients:

Use GTranslate-style automatic translation if:

• You only need to help visitors read the site
• You do not need multilingual SEO
• You want fast deployment and minimal maintenance

Use WPML (true multilingual structure) if:

• You want to rank in multiple languages
• You need accurate, reviewed translations
• You need structured language pages for long-term growth

Other Translation Plugins

Visit the plugin sites for more details on how translations work, pricing, and what it means to be “editable”.

Bottom Line for SEO

Installing a translation plugin by itself does not:

• expand your keyword footprint
• improve international visibility
• create language-specific search signals

Only properly structured multilingual pages do.

If SEO matters, the plugin is only the infrastructure. Real SEO work still matters. Things like translation quality, page structure, internal linking, and metadata per language will make or break your translated pages’ indexing power.

Our practical recommendation

If you’re simply trying to make your site easier for non-English visitors to use start with an automatic translation solution.

If your organization wants multilingual reach, discoverability, and long-term search performance plan for a true multilingual build using a structured translation system.

If you’re not sure which path makes sense for your site, we can review your goals and tell you whether a simple translation plugin is enough or whether a multilingual setup is actually worth the investment.