The Search Tuning Tab
Decide how your native search page ranks results: how much meaning counts against exact words, which fields matter most, how many words must match. The defaults work for most sites.
Where: Configuration › Search and metadata › Opensolr Search › Search Tuning tab (
/admin/config/search/opensolr/tuning)| Control | Default | What it does |
|---|---|---|
| Lexical Weight | 0.50 | Semantic ↔ Lexical Balance, from 0.10 to 1.00. Lower leans on meaning, higher on the exact words. More |
| Field Weights | Title 0.1, Description 0.03, URI 0.01, Text 0.01, LD Text 0.03 | How much a match in each field counts, from 0.01 to 999.99. More |
| Minimum Match | Balanced | How many of the typed words must match: Flexible, Balanced, Strict, or Custom with your own rule. More |
| Search Mode | Union | How words and meaning combine: Union, KW Required, Meaning Req., Intersection, or Lexical Only (words alone, no meaning search at all). More |
| Vector Candidate Pool (topK) | 500 | How many candidates meaning search looks at, from 10 to 1000. More finds more, a little slower. More |
| Content Quality Boost | Off | Lifts pages with rich titles, descriptions and text over thin ones. More |
| Fresh Bias Weight | 0.5 | How hard the visitor's Fresh switch pushes newer content. More |
Click Save configuration; the next search uses the new values. Reset All to Defaults, at the bottom, puts every control back after a confirmation.
Good to know
- The balance, the search mode and the candidate pool only matter when meaning search runs: on a plan with AI and AI requests left, with Search Mode other than Lexical Only. Otherwise every search uses the words alone.
- Visitors can switch meaning search off for themselves with the AI switch.
- In Embeddable Search UI mode this tab only shows a link: tuning is done in the Control Panel of your index.