Your Site, Now in Other Languages: Introducing the Google Translate Widget

Internationalization is very important to us, and we’re striving to make sites across WordPress.com accessible to all, such as your international followers and multilingual readers.

Today, we’re thrilled to introduce the Google Translate Widget, which allows you and your site visitors to instantly translate your content into 103 languages currently supported by Google Translate.

Languages currently supported by Google Translate.

Languages currently supported by Google Translate.

How it works

To enable automatic translation on your site, add the Google Translate Widget in your Customizer by going to My Site(s) → Customize → Widgets. Once enabled, your site visitors will be able to access a dropdown menu in your sidebar or footer and automatically translate the content into 100+ languages.

A blog post in English.

A blog post in English.

The blog post above, automatically translated into French with the Google Translate Widget.

The blog post above, automatically translated into French with the Google Translate Widget.

Additionally, you can also send readers to a specific language version of your site by adding a language translation code — such as “?lang=de” for German — to any page URL.

You’ll find the steps to activate the widget and use language translation codes in our Google Translate Widget support doc.

Available for Jetpack

The Google Translate Widget is also included in version 4.4 of Jetpack so you can enable automatic translation on your WordPress site, too. Install the latest version of Jetpack on Jetpack.com.

We’re excited to offer this tool to all of our users — and make it easier for you to reach and connect with a wider audience around the world.

Filed under: International, Localization, Widgets, WordPress.com

Altre ricette simili a questa:

VAI ALLA RICETTA


Nessun commento...

Inserisci un Commento

Devi effettuare il Login per inserire un commento.

[an error occurred while processing this directive]
[an error occurred while processing this directive]