Marco Almeida | Webdados

Naked Cat Plugins

This plugin aims to provide a way to ensure that any language change in the content of a page is indicated to assistive technologies at the container block level, helping a website comply with WCAG guidelines.
This feature is available on the core block editor only at a text formatting level after code from <a href="https://wordpress.org/plugins/lang-attribute/" rel="ugc">Jb Audras plugin “Lang Attribute for the Block Editor”</a> was merged into core. The objective of this plugin is to provide the same functionality at a container block level (Group – including all its variants, Columns, Cover, and other specific block types) so that the language applies to all child elements, no matter the kind of content inside.
This plugin is heavily inspired by the Jb Audras plugin (including this readme file), and the development started at WordCamp Europe 2025 Contributor Day, by Marco Almeida from <a href="https://profiles.wordpress.org/nakedcatplugins/" rel="nofollow ugc">Naked Cat Plugins</a> / <a href="https://profiles.wordpress.org/webdados/" rel="nofollow ugc">Webdados</a>, and the help from <a href="https://profiles.wordpress.org/welcher/" rel="nofollow ugc">Ryan Welcher</a> on the code side and <a href="https://profiles.wordpress.org/alh0319/" rel="nofollow ugc">Amber Hinds</a> on the accessibility compliance side.
For more context: this plugin helps you to make your website compliant with the Web Content Accessibility Guidelines (WCAG) success criterion 3.1.2: “Language of Parts”. The purpose of this success Criterion is to ensure that user agents can correctly present content written in multiple languages.
Keep in mind that you should only set the lang and dir attributes to a container block if the content you’re going to insert inside it is written in a different language than that set globally on your website.
As per Web Content Accessibility Guidelines:
This makes it possible for user agents and assistive technologies to present content according to the presentation and pronunciation rules for that language. This applies to graphical browsers as well as screen readers, braille displays, and other voice browsers.
Both assistive technologies and conventional user agents can render text more accurately if the language of each passage of text is identified. Screen readers can use the pronunciation rules of the language of the text. Visual browsers can display characters and scripts in appropriate ways.
This is especially important when switching between languages that read from left to right and languages that read from right to left, or when text is rendered in a language that uses a different alphabet. Users with disabilities who know all the languages used in the Web page will be better able to understand the content when each passage is rendered appropriately.
That’s not just good for accessibility. It’s also great for SEO. Search engines like Google can better understand your content when languages are clearly defined. That means improved indexing and potentially better rankings.
Banner photo by <a href="https://unsplash.com/@hannahwrightdesigner?utm_content=creditCopyText&utm_medium=referral&utm_source=unsplash" rel="nofollow ugc">Hannah Wright</a>.
<h3>Supported block types</h3>
<ul>
<li>Group (<code>core/group</code>): Group contents together and set a language for them</li>
<li>Columns (<code>core/columns</code> and <code>core/column</code>): Organize content into a set of columns and set a language for all the columns or a specific column</li>
<li>Cover (<code>core/cover</code>): Set the language to all the contents inside a cover block</li>
<li>Navigation (<code>core/navigation</code>): Create full navigation menus in different languages</li>
<li>Submenu (<code>core/navigation-submenu</code>): Set a different language on a sub-section of your menu (for example, if you have the default language pages on the first level and a sub-menu with pages in another language)</li>
<li>Page List (<code>core/page-list</code>): List all the pages on your website that are written in a different language and created as a child of the main page of that language</li>
<li>Content (<code>core/post-content</code>): Set the post content on a custom template to a different language</li>
</ul>
<h3>Features</h3>
<ul>
<li>Add “lang” and “dir” attributes to Group, Columns, Cover, and other specific WordPress Blocks</li>
<li>Show visual outline around blocks that have a language attribute set – For easy identification of blocks you have already set to a different language during your editing process, only for Administrators and Editors, and if enabled in Settings – Writing</li>
</ul>

Language Attribute for Container Blocks

Add “lang” and “dir” attributes to Group, Columns, Cover, and other specific WordPress Blocks.

edo888

Google Language Translator plugin is now a part of GTranslate family!
GTranslate is a leading website translation services provider since 2008 and powers more than 500.000 multilingual websites worldwide.
Please use <a href="https://wordpress.org/support/plugin/google-language-translator/" rel="ugc">Google Language Translator Support</a> for your questions and support requests! We are multilingual!
Please check our <a href="https://gtranslate.io/?xyz=3167#faq" rel="nofollow ugc">FAQ</a> to get quick answers.
Features
<ul>
<li>Free Google automatic machine translation</li>
<li>Option to hide “Suggest better translation” pop-up</li>
<li>Option to hide Google top frame after translation</li>
<li>Google Analytics integration</li>
<li>Translate the site on the fly</li>
<li>Translate posts and pages</li>
<li>Translate categories and tags</li>
<li>Translate menus and widgets</li>
<li>Translate themes and plugins</li>
<li>Right to left language support</li>
<li>Floating language selector</li>
<li>Language bar with flags in menu</li>
<li>Translate WooCommerce shop</li>
</ul>
Paid Features
<ul>
<li>Multilingual SEO – Enable search engine indexing</li>
<li>Neural machine translations with human level translation quality</li>
<li>Increase traffic and AdSense revenue</li>
<li>Search engine friendly (SEF) URLs</li>
<li>Yoast SEO compatible</li>
<li>WooCommerce compatible</li>
<li>You can have sub-directory (example.com/es/) or sub-domain (es.example.com) URL structure</li>
<li>Translate URLs aka slug translation is possible (example.com/about-us → example.es/sobre-nosotros)</li>
<li>Add hreflang tags for translated alternatives</li>
<li>You can manually correct translations</li>
<li>In context translation interface (make corrections without losing the context)</li>
<li>Translate meta data (meta keywords, meta description)</li>
<li>Translating schema.org microdata for better search engine appearance</li>
<li>Seamless updates (cloud service updated on our side – SaaS, you do not need to worry about backups on your side)</li>
<li>Translate JSON objects (JSON format translation)</li>
<li>Translate AMP pages (Accelerated Mobile Pages translation)</li>
<li>Image localization – Translate media</li>
<li>Translation Proxy (aka Translation Delivery Network)</li>
<li>Centralized Translation Cache – We revise and improve translations over time</li>
<li>Language Hosting (example.fr)</li>
<li>User Dashboard with Analytics</li>
<li>Live Chat Support</li>
</ul>

Translate WordPress – Google Language Translator

When I use the shortcode in two places, the first is loaded but the second is not. (language switcher)

Use the short code in two different places


I never used a different Google Translator but with Google Language Translator there's really no need to. I'm very thankful to have this plugin installed not only for WordPress pages to get translated into the user's preferred language, but I also like to use it to translate text when I'm speaking with someone outside the us. After creating a test page in WordPress, I simply copy and paste the text that needs to be translated, hit the preview button and choose the language and my text instantly gets translated. 


Excellent


This is an outstanding plugin, and I've been using it for a few years now. My site is well-indexed and gets traffic to my language subdomains. However, it needs optimized better:1. The scripts.js doesn't need to be loaded if you're not offering a translation widget or shortcode on the front-end.2. The scripts.js has a toolbar.js code in it that's legacy and takes a hit from pagespeed.3. Hiding the flags div just adds a display:none div with all the flags in it.4. No hreflang tags are loaded in your header and no XML sitemap is generated to redirect for language.I've fixed all of these in my site, but it would be nice if these got corrected in the core code. I'd be glad to offer my code to assist.


Hide Language Switcher is display:none

Translate WordPress with Google Language Translator multilanguage plugin which allows to insert Google Translate widget anywhere on your website.

Language Attribute for Container Blocks vs Translate WordPress – Google Language Translator