Synonyms

In general, a search on a word will return the same results as a search on any of its synonyms.
There is one exception to this rule, .

All synonyms are lowercased and de-unicoded during the indexing process.

Example

Consider a situation where “Résumé” and “CV” are set as synonyms.

A search for “cv” would return any documents containing “cv” or “CV”, in addition to any that contain “Résumé”, “resumé”, “resume”, etc. unaffected by case or accent marks.

Use this when you want one word to be synonymous with another, but not the other way around.

However, if you search for iphone, documents containing will be ranked lower in the results due to .

Example

To create a one-way synonym list, this is the JSON syntax that should be .

By associating one or more synonyms with each other, they will be considered the same in both directions.

  1. shoe <=> boot <=> slipper <=> sneakers

When a search is done with one of these words, all synonyms will be considered as the same word and will appear in the search results.

Example

To create a mutual association between four words, this is the JSON syntax that should be .

When a multi-word phrase is considered the synonym of another word or phrase, the exact search query will always take precedence over its synonym(s).

TIP

Multi-word synonyms are limited to a maximum of three words.
For example, although you could make “League of Legends” and “LOL” into synonyms, you could not do the same for “The Lord of the Rings” and “LOTR”.

Example

Suppose you set “San Francisco” and “SF” as synonyms with a 

  1. {
  2.     "sf"
  4.   "sf": [
  5.     "san francisco"
  6.   ]

If you input “SF” as a search query, then results containing “San Francisco” will also be returned. However, they will be considered less relevant than those containing “SF”. The reverse is also true.