GeoDirectory Multilingual 2.3.11

GeoDirectory Multilingual makes your WPML-powered directory speak every language. It translates listings, categories, tags, custom fields and GeoDirectory options, and works with all three WPML versions on WordPress.

VERSION:
2.3.11
UPDATED:
2026-11-20
DEVELOPER:
AyeCode Ltd
LICENSE:
GPLv2 or greater
AUTO UPDATE:
Yes

Description

Who This Is Built For

GeoDirectory Multilingual translates the content of a GeoDirectory site that runs on WPML: listings, categories, tags, custom fields and the plugin’s own options. This GPL-licensed add-on exists for one job, which is to let a business directory, city guide or regional portal serve each visitor in their own language without maintaining separate sites. It works with all three WPML tiers, from the basic blog edition to the CMS and Agency editions.

Think of a tourism board listing restaurants, hotels and tour operators for visitors who arrive speaking German, French or Spanish. Or a relocation directory that needs every service provider described in the languages expats actually read. Or a chamber of commerce in a country with several official languages, where a listing that exists in only one of them is a listing half the audience never finds.

It also suits agencies. If you build directory sites for clients and the brief says “multilingual,” this GeoDirectory Multilingual WordPress plugin gives you a defined path for the work instead of a pile of custom code. The people who benefit most are those who already chose GeoDirectory for the directory and WPML for translation, and who now need the two to cooperate properly.

What Does GeoDirectory Multilingual Actually Do?

GeoDirectory stores its content in its own structures: custom post types for places, dedicated taxonomies, extra fields attached to each listing, and a long list of settings. WPML knows how to translate standard WordPress content, but it does not automatically understand how a directory organizes everything. This plugin is the bridge. It tells WPML which GeoDirectory elements are translatable and makes sure the translated versions stay connected to their originals.

In practice, you create a listing in your default language, then translate it through WPML like any other content. The translated listing keeps its place in the directory. Its categories and tags appear in the visitor’s language, and its custom fields, such as opening hours labels, price ranges or a “services offered” field, can carry translated values as well.

The plugin also covers GeoDirectory options. Those are the labels, texts and settings that shape the directory interface itself. Translating the listings while leaving the surrounding interface in one language produces a half-finished experience, so this part matters more than it first appears. String translation and media translation depend on the matching WPML add-ons being active, which means the plugin builds on the WPML tools you already use instead of replacing them.

How does it work with the different WPML editions?

The basic WPML edition covers fundamental translation needs. The two premium editions, Multilingual CMS and Multilingual Agency, add advanced translation features, and the WPML add-ons that come with them are supported. If you start on the basic edition and later move up, the directory translation setup does not need to be rebuilt.

Key Capabilities

  • Listing translation: every GeoDirectory listing can be translated and linked to its original, so each language version has its own title, description and content.
  • Category and tag translation: listing taxonomies appear in the visitor’s language, which keeps browsing and filtering understandable.
  • Custom field translation: fields you add to listings, including text-based ones that vary by business type, can be translated alongside the listing.
  • GeoDirectory options translation: interface texts and settings can be translated so the whole directory reads consistently.
  • String translation support: when WPML String Translation is active, translatable strings are handled through it.
  • Media translation support: when WPML Media Translation is active, images and other media can be translated per language.
  • Support for all WPML editions: works with the basic, CMS and Agency versions of WPML.

Why taxonomies and custom fields matter

Directories live and die by navigation. A visitor looking for a dentist wants to click “Zahnärzte,” not hunt for an English label they may not recognize. Categories and tags are the primary route into your content, so leaving them untranslated undermines the translated listings sitting behind them.

Custom fields deserve the same attention. A hotel directory might use fields for amenities, check-in times and house rules. A restaurant directory might have cuisine type and dietary notes. These fields often hold the details a visitor uses to make a decision. Translating them means the useful part of the listing reaches the reader, not just the headline.

Getting Results

The practical outcome is a directory that behaves like one site in several languages. A visitor switches language and stays inside the same directory structure, seeing translated listings, translated categories and translated interface text. Site owners work from the familiar WPML translation workflow instead of learning a separate system just for directory content.

A sensible rollout starts with the interface and taxonomies, since they affect every page. Next, translate the listings that get the most traffic, then work through the rest. Because translations are tied to originals, you can expand into additional languages later without restructuring what you have already built.

For multi-region directories, this approach also supports clearer local presentation. A listing in a bilingual city can be shown in both languages, each version written for its readers, rather than one awkward text trying to serve everyone. Directory owners who accept submissions from business owners can translate those submissions through the same process, keeping quality under editorial control.

The plugin’s documentation covers setup details for those who want step-by-step guidance on configuring the translation of specific GeoDirectory elements.

Frequently Asked Questions

Does GeoDirectory Multilingual translate listings automatically?

It makes GeoDirectory content available for translation through WPML. The translation itself happens in your normal WPML workflow, whether you write the text yourself, assign it to translators or use the translation tools your WPML edition offers. The plugin’s role is to ensure listings and related data are recognized and correctly linked.

Can I translate custom fields I created myself?

Yes. The plugin supports translating GeoDirectory listing custom fields, so fields you added for your own directory can carry translated values in each language. This is useful when different listing types rely on different fields, such as amenities for hotels or cuisine for restaurants. Text shown as field labels can be handled through WPML String Translation when that add-on is active.

Do I need a premium WPML edition to use it?

No. The plugin works with the basic WPML edition as well as the Multilingual CMS and Multilingual Agency editions. The premium editions offer advanced translation features and add-ons, such as string and media translation, which are useful for larger or more complex directories. A smaller directory with basic needs can still run multilingual on the entry-level edition.

Category: