Skip to main contentSkip to footer

Different translation plugins use different methods for storing the translations, and these methods have varying compatibility with how Relevanssi works with the posts.

Best compatibility

  • Polylang. Relevanssi has good built-in support for Polylang. This is the best translation tool that causes the least trouble.
  • WPML. Good built-in support, almost as good as Polylang. WPML is more prone to causing weird edge case problems.
  • MultilingualPress. Uses separate multisite sites for each language. This works well with Relevanssi, making language filtering automatic. With Relevanssi Premium, you can do multisite searching to include posts in different languages.

Not compatible

  • TranslatePress. The translated strings are stored in a separate database, and are invisible for Relevanssi. It is possible to make Relevanssi index the translated strings, but then Relevanssi has no way to index different languages separately. You can’t restrict the search to a specific language; all languages are mixed together.
  • GTranslate. The translations are not stored locally at your site, so Relevanssi can’t access them.

Your account

Not logged in. Log in to see your license details.

Search

Popular Resources

Indexing image alt texts
Relevanssi by default ignores image alt texts (and other tag attributes). That’s often the right thing to do because alt…
Sorting search results

If you want something else than the default relevancy ranking, you can use orderby and order parameters for the search query. Orderby accepts $post variable attributes and order can be asc (ascending) or desc (descending). The most relevant attributes here are most likely post_date and comment_count. If you want to…

Related Posts:

Comment Section:

Leave a Reply

Your email address will not be published. Required fields are marked *

Fill out this field
Fill out this field
Please enter a valid email address.
You need to agree with the terms to proceed