Working with stemming and tuning search relevance

Stemming is on by default for every Salesforce search. Users do not configure it; the platform handles it automatically. The configuration work around stemming is mostly indirect: improve search relevance by configuring synonyms, aliases, and search settings that work alongside stemming, and audit search behavior when stemming produces unexpected results. The four-step routine covers: confirm stemming is working as expected for your locale, configure synonyms and aliases for terms stemming alone misses, audit search behavior with sample queries, and tune search settings if specific fields need different treatment.

1. 1
   Confirm stemming is working for your locale

   In Salesforce, run a search for a known word and confirm it matches records containing morphological variants. A search for running should match records containing run, runs, runner. A search for invoices should match records containing invoice. If the matching does not work, confirm the org locale and language settings are correct (Setup, Company Information). Confirm the records are indexed in the right language by checking the Language field on a sample record. Misconfigured locale or language metadata is the most common reason stemming behaves unexpectedly. Test in a sandbox with a small set of records before rolling out search-driven features that depend on stemming.

2. 2
   Configure synonyms for terms stemming alone misses

   From Setup, search Synonym Groups. Create a synonym group for each business term that stemming cannot connect. Common examples: car and automobile and vehicle; laptop and notebook; laptop and PC. Add the equivalent terms inside the group. Save and activate the group. Test by searching for one term and confirming results include records containing the other. Synonym groups are global to the org; consider permission sets if certain synonyms should apply only to specific user groups (a Sales team synonyms may differ from a Service team). Document the synonym groups in the search runbook so future admins understand the rationale for each.

3. 3
   Audit search behavior with sample queries

   Build a sample query set that represents what your users actually search for. Include exact words, variant forms (plurals, verb tenses), proper nouns, product codes, and common misspellings. Run each query in production and confirm the results match expectations. Where results are wrong (too few matches, too many false positives), identify the linguistic pattern that caused the issue. Patterns that map to stemming get addressed through synonyms or aliases. Patterns that map to indexing problems get addressed through re-indexing or field configuration. Schedule the audit quarterly so search quality stays high as the underlying record set grows.

4. 4
   Tune search settings for specific fields

   From Setup, configure which fields are searchable on each object. Some fields should always be matched literally (record IDs, product SKUs, customer account numbers) and should not be exposed to stemming; configure them as Text fields with the exact-match behavior. Other fields benefit from stemming (Description, Notes, Subject, Long Text Area); keep them as searchable text fields with default stemming behavior. For each searchable field, decide whether the field should participate in global search, in record-type-specific search, or in both. Document the field-level search configuration in the search runbook for audit and for future admins to understand the search behavior.