The Yext Publisher Network includes sites across the globe. Different publishers handle multi-language content differently, so understanding publisher behavior helps you decide which language profiles to create for your entities.

For background on creating and managing multi-language entity profiles, see  Manage Multi-Language Entity Profiles.

Publisher Behavior

Publisher behavior varies by site. The locale behavior is broken into the following categories:

• Supports all locales
• Does not support multi-language profiles
• Support Multi-language profiles
• Hybrid

Supports All Locales

The publisher accepts content in any language and has no preference for a specific language. Yext sends only the primary language profile.

For example, if an entity has five language profiles but the primary is English, only the English content is sent to this publisher.

Example publisher: Google

Does Not Support Multi-Language Profiles

In this case, the publisher only supports specific locales, and they are not set up to support multi language profiles, meaning they will only take one profile. In this case, they will take the profile in the supported language, or they may take a merged profile if content is missing from one supported language, but exists in another supported language. One example of a publisher that falls into this category is Yelp.

The languages these publishers support are often in a ranked order. For example, in the image below the publisher in question prefers content in Germany, then English, then French.

These preferences determine in what order we will pull data from location profiles.

So, our system will pull all the available fields it can for the first locale, if any are missing, it will try to pull those from the second locale in the list. If any fields are still missing, then it tries to pull those fields from the 3rd locale, and so on down the list of locales.

Meaning, if a location has French, Dutch, and German profiles with the description field only filled out in the Dutch and German profiles. If the locale preference looks like: [fr, nl, de], the merged profile would include the Dutch description but every other piece of data would be from the French profile.

Then, all the data in the combined, or merged profile, will be sent to the publisher.

If an entity does not have a profile with a locale in the supported locale list, an Unavailable Reason will display for that entity, and you will need to create a profile with content in the supported language in order to send content to that publisher. You can learn more about unavailable reasons in Unavailable Listings.

Supports Multi-Language Profiles

If a publisher and the locales are set up as multi-language, then each locale is treated as a separate thing. Similar as the example above, the languages these publishers support are often in a ranked order.

However, for these publishers, instead of merging the content the system pulls the profile for each of the support locales. One example of a publisher that falls into this category is Bing.

At the end of this, we have a list of profile data for every corresponding locale profile that the entity has. Ultimately, the system will determine the primary profile according to the preferences, but also include a complete list of all the profiles as “variants” that will be sent as separate items to the publisher.

Hybrid

There could be cases where only some of the locales supported by a publisher are marked as multi-language.

In cases where the publisher is set up in a hybrid approach, the system does a mix of both approaches. For all the locales that are not marked as multi-language, the system pulls the merged or combined profiles. For everything that is marked as multi-language, the system treats them separately, the same way as in the multi-language approach.

In the end there will be a list of separate profiles for each supported language, but one of those profiles would be the merged profile of all the non-multi-lang locales.

When to Create Multi-Language Profiles for Listings

We just reviewed all of the publisher behavior when it comes to multi-language profiles, and multi-language content. However, the most important thing to remember is that because certain publishers prefer certain profiles, you should always attempt to fill out the local profile if you can. Additionally, when thinking about the ‘local profile’ this is not the local profile to the business, but the local profile to the publisher.

Meaning, if you are a business headquartered in the United States, but you also have locations in China, you will want to have Chinese profiles for these locations. That way, customers searching on Chinese publishers can find content about your business in their location language.

Another example would be, if you are in the United States and you serve a lot of Spanish-speaking customers, you may want to create a Spanish language profile for sites like YaSabe which is a bilingual directory in the US that allows users to search in both English and Spanish.

Tourist Publishers

Additionally, Yext also pushes content to Chinese publishers that are used by Chinese tourists. This is because many Chinese tourists use these Chinese-based publishers when they travel, so it is also beneficial to create profiles to provide content for tourists using these publishers when they travel to any locations outside of China.

Additionally, sites like Yandex, a Russian publisher, is also commonly used by users that speak Russian, regardless of where they currently live.

You can find the full list of publishers and their language support on The Yext Knowledge Network page.

Best Practices

• Always put the correct language content in the correct language profile. Never place Russian content in a French profile, or vice versa.
• Create profiles for all languages relevant to your customer base and the publishers you are targeting.
• If you create profiles in multiple languages, focus on populating the fields that will actually be used on the publisher's listing.