- Also known as the Underperforming Query Rewriting feature
- Uses signals data to identify underperforming queries
- Suggests improved queries that could produce better conversion rates
- Suggested by the Head/Tail Analysis Spark job operating on your signals data
- Created manually using the Rules Editor or underlying API
Job-generated query improvements are always assigned an initial status of “Pending”, never “Auto”. Query improvements must be explicitly approved and published in order to be copied to the
COLLECTION_NAME_query_rewrite collection.
LucidAcademyLucidworks offers free training to help you get started.The Course for Query Analytics focuses on how Fusion provides query analytics to detect and improve underperforming queries:
Reviewing auto-generated query improvements
Query improvements that are automatically generated by the Head/Tail Analysis job are assigned the following status value:- Auto
All results will be automatically deployed to the
_query_rewritecollection.
No action is required on these results, but you can edit them if you wish.
Adding new query improvements
You can manually add query improvements in addition to any generated by the Head/Tail Analysis job.How to add a query improvement
- Navigate to Relevance > Rules > Rewrite.
- Select the Head/Tail tab. The application displays the Underperforming Query Rewriting screen.
-
At the bottom of the rules list, click the
icon.
A new query improvement appears at the top of the list:
- Enter the underperforming query.
- Enter one or more query improvements.
It is not necessary to set a confidence value.
- Select the query improvement’s status, depending on whether you want to deploy it the next time you publish your changes (“Approved”) or save it for further review (“Pending”).
- Click the check mark to save the new query improvement.
Publishing your changes
How to publish updated query improvements
- In the Underperforming Query Rewriting screen, click the PUBLISH button.
Fusion prompts you to confirm that you want to publish your changes. - Click PUBLISH.
You can un-publish a query rewrite by changing its status to “denied”, then clicking PUBLISH.
Use Query Rewrites in the Rules Editor
Use Query Rewrites in the Rules Editor
This article describes how to use the Rewrites screen in the Rules Editor.
Query rewrite rule types
- Head/Tail. Replace underperforming queries with queries that produce higher click-through rates. Query improvements always require review before they are published. Schedule the Head/Tail Analysis job to get AI-generated query improvements based on your signals collection.
Manually created Head/Tail rewrites must provide an “Improved Query” in a format appropriate to the type of request the rewrite will be applied to. For Legacy requests, this means a valid Solr query fit for use as theqparameter. For DSL requests this means a JSON string representing the main DSL query.
For more information, see: - Misspelling. Fusion replaces misspelled query terms with their spelling corrections for better search results. Schedule the Token and Phrase Spell Correction job to get AI-generated spelling corrections based on your signals collection. For more information, see Misspelling Detection.
- Phrase. Known phrases are boosted when they appear in new queries. Schedule the Phrase Extraction job to get AI-generated phrases based on your signals collection. For more information, see Phrase Detection.
- Synonym. Synonyms are used to expand queries so that they include all known synonyms of the query terms. To retrieve AI-generated synonyms based on your signals collection, schedule the Synonym Detection job.
- Remove Words - Remove particular phrases from queries. Unlike other rewrites, these should be entered manually and are not generated by a job. For more information, see Remove Words.
Facets
Facet menu
Faceting rules by confidence is not available for Head/Tail rewrites.
Search
Enter a term in the search bar to quickly facet your query rewrite rules.Rules
Begin by selecting one of the query rewrite rule types you will create.Create a rule
- Click +Add.
- In the new table row, complete the required fields, and additional fields as needed.
- Click the checkmark to save, or close to cancel the changes.
Edit a rule
- Hold the pointer over the rule to edit.
- Click the pencil icon.
- Enter desired changes and click the checkmark to save, or close to cancel the changes.
Approve/deny rules
- Hold the pointer over a rule.
- Select the checkbox that displays for that rule.
- To modify multiple rules, hold the pointer over each rule and select its corresponding checkbox.
- Click Approve or Deny as needed.
Publish a rule
- Hold the pointer over a rule.
- Select the checkbox that displays for that rule.
- To publish multiple rules, hold the pointer over each rule and select its corresponding checkbox.
- Click Publish Selected to publish the selected rules.
Publish an individual rule
- Hold the pointer over a rule.
- Click the
button. - To confirm, click Publish.
Delete rules
Delete a single rule
- Hold the pointer over a rule.
- Click the trash can.
- To confirm, click Delete.
Delete multiple rules
- Hold the pointer over a rule.
- Select the checkbox that displays for that rule.
- To delete multiple rules, hold the pointer over each rule and select its corresponding checkbox.
- Click Delete.
- To confirm, click Delete again.
Sort rules
- Hold the pointer over column titles. A
icon displays for some titles to indicate the rules list can be sorted by that column. - Click the title column to sort the rules.
The column that is currently sorting the rules list is indicated by an or 
icon.
or icon.Export rules
To export the rules list, click Export. This generates a.csv file that contains your rules.Columns
Customize columns
To customize columns:- Hold the pointer over the row of column titles.
-
Click the
button.
- In the Customize Columns to Display screen, select the checkboxes for the columns you want to display. Clear the checkboxes for columns you do not want to display.
- Click Save. To exit without saving your changes, click Cancel.
Query rewrite jobs post-processing cleanup
To perform more extensive cleanup of query rewrites, complete the procedures in Query Rewrite Jobs Post-processing Cleanup.Query Rewrite Jobs Post-processing Cleanup
Query Rewrite Jobs Post-processing Cleanup
The Synonym Detection job uses the output of the Misspelling Detection job and Phrase Extraction job. Therefore, post processing must occur in the order specified in this topic for the Synonym detection job cleanup, Phrase extraction job cleanup, and Misspelling detection job cleanup procedures. The Head-Tail Analysis job cleanup can occur in any order.
Synonym detection job cleanup
Use this job to remove low confidence synonyms.Prerequisites
Complete this:- AFTER the Misspelling Detection and Phrase Extraction jobs have successfully completed.
- BEFORE removing low confidence synonym suggestions generated in the post processing phrase extraction cleanup and misspelling detection cleanup procedures detailed later in this topic.
Remove low confidence synonym suggestions
Use either a Synonym cleanup method 1 - API call or the Synonym cleanup method 2 - Fusion Admin UI to remove low confidence synonym suggestions.Synonym cleanup method 1 - API call
-
Open the
delete_lowConf_synonyms.jsonfile.REQUEST ENTITY specifies the threshold for low confidence synonyms. Edit the upper range from 0.0005 to increase or decrease the threshold based on your data. -
Enter
<your query_rewrite_staging collection name/update>in the uri field. An example URI value for an app calledDC_Largewould beDC_Large_query_rewrite_staging/update. -
Change the
idfield if applicable. -
Specify the upper confidence level in the entity field.
The entity field specifies the threshold for low confidence synonyms. Edit the upper range to increase or decrease the threshold based on your data.
Synonym cleanup method 2 - Fusion Admin UI
- Log in to Fusion and select Collections > Jobs.
- Select Add+ > Custom and Other Jobs > REST Call.
- Enter delete-low-confidence-synonyms in the ID field.
-
Enter
<your query_rewrite_staging collection name/update>in the ENDPOINT URI field. An example URI value for an app calledDC_Largewould beDC_Large_query_rewrite_staging/update. - Enter POST in the CALL METHOD field.
- In the QUERY PARAMETERS section, select + to add a property.
- Enter wt in the Property Name field.
- Enter json in the Property Value field.
- In the REQUEST PROTOCOL HEADERS section, select + to add a property.
-
Enter the following as a REQUEST ENTITY (AS STRING)
<root><delete><query>type:synonym AND confidence: [0 TO 0.0005]</query></delete><commit/></root>REQUEST ENTITY specifies the threshold for low confidence synonyms. Edit the upper range from 0.0005 to increase or decrease the threshold based on your data.
Delete all synonym suggestions
To delete all of the synonym suggestions, enter the following in the REQUEST ENTITY section:<root><delete><query>type:synonym</query></delete><commit/></root>This entry may be helpful when tuning the synonym detection job and testing different configuration parameters.
Phrase extraction job cleanup
Use this job to remove low confidence phrase suggestions.Prerequisites
Complete this:- AFTER you complete Synonym detection job cleanup
Remove low confidence phrase suggestions
Use either a Phrase cleanup method 1 - API call or the Phrase cleanup method 2 - Fusion Admin UI to remove low confidence phrase suggestions.Phrase cleanup method 1 - API call
-
Open the
delete_lowConf_phrases.jsonfile. -
Enter
<your query_rewrite_staging collection name/update>in the uri field. An example URI value for an app calledDC_Largewould beDC_Large_query_rewrite_staging/update. - Change the id field if applicable.
-
Specify the upper confidence level in the entity field.
The entity field specifies the threshold for low confidence phrases. Edit the upper range to increase or decrease the threshold based on your data.
Phrase cleanup method 2 - Fusion Admin UI
- Log in to Fusion and select Collections > Jobs.
- Select Add+ > Custom and Other Jobs > REST Call.
- Enter remove-low-confidence-phrases in the ID field.
-
Enter
<your query_rewrite_staging collection name/update>in the ENDPOINT URI field. An example URI value for an app calledDC_Largewould beDC_Large_query_rewrite_staging/update. - Enter POST in the CALL METHOD field.
- In the QUERY PARAMETERS section, select + to add a property.
- Enter wt in the Property Name field.
- Enter json in the Property Value field.
- In the REQUEST PROTOCOL HEADERS section, select + to add a property.
-
Enter the following as a REQUEST ENTITY (AS STRING)
<root><delete><query>type:phrase AND confidence: [0 TO <insert value>]</query></delete><commit/></root>REQUEST ENTITY specifies the threshold for low confidence phrases. Edit the upper range to increase or decrease the threshold based on your data.
Delete all phrase suggestions
To delete all of the phrase suggestions, enter the following in the REQUEST ENTITY section:<root><delete><query>type:phrase</query></delete><commit/></root>This entry may be helpful when tuning the phrase extraction job and testing different configuration parameters.
Misspelling detection job cleanup
Use this job to remove low confidence spellings (also referred to as misspellings).Prerequisites
Complete this:- AFTER you complete Synonym detection job cleanup and Phrase extraction job cleanup
Remove misspelling suggestions
Use either a Misspelling cleanup method 1 - API call or the Misspelling cleanup method 2 - Fusion Admin UI to remove misspelling suggestions.Misspelling cleanup method 1 - API call
-
Open the
delete_lowConf_misspellings.jsonfile. -
Enter
<your query_rewrite_staging collection name/update>in the uri field. An example URI value for an app calledDC_Largewould beDC_Large_query_rewrite_staging/update. - Change the id field if applicable.
-
Specify the upper confidence level in the entity field.
The entity field specifies the threshold for low confidence spellings. Edit the upper range to increase or decrease the threshold based on your data.
Misspelling cleanup method 2 - Fusion Admin UI
- Log in to Fusion and select Collections > Jobs.
- Select Add+ > Custom and Other Jobs > REST Call.
- Enter remove-low-confidence-spellings in the ID field.
-
Enter
<your query_rewrite_staging collection name/update>in the ENDPOINT URI field. An example URI value for an app calledDC_Largewould beDC_Large_query_rewrite_staging/update. - Enter POST in the CALL METHOD field.
- In the QUERY PARAMETERS section, select + to add a property.
- Enter wt in the Property Name field.
- Enter json in the Property Value field.
- In the REQUEST PROTOCOL HEADERS section, select + to add a property.
-
Enter the following as a REQUEST ENTITY (AS STRING)
<root><delete><query>type:spell AND confidence: [0 TO 0.5]</query></delete><commit/></root>REQUEST ENTITY specifies the threshold for low confidence spellings. Edit the upper range from 0.5 to increase or decrease the threshold based on your data.
Delete all misspelling suggestions
To delete all of the misspelling suggestions, enter the following in the REQUEST ENTITY section:<root><delete><query>type:spell</query></delete><commit/></root>This entry may be helpful when tuning the misspelling detection job and testing different configuration parameters.
Head-tail analysis job cleanup
The head-tail analysis job puts tail queries into one of multiple reason categories. For example, a tail query that includes a number might be assigned to the ‘numbers’ reason category. If the output in a particular category is not useful, you can remove it from the results. The examples in this section remove the numbers category.Prerequisites
The head-tail analysis job cleanup does not have to occur in a specific order.Remove head-tail analysis query suggestions
Use either a Head-tail analysis cleanup method 1 - API call or the Head-tail analysis cleanup method 2 - Fusion Admin UI to remove query category suggestions.Head-tail analysis cleanup method 1 - API call
- Open the
delete_lowConf_headTail.jsonfile. - Enter
<your query_rewrite_staging collection name/update>in the uri field. An example URI value for an app calledDC_Largewould beDC_Large_query_rewrite_staging/update. - Change the id field if applicable.
Head-tail analysis cleanup method 2 - Fusion Admin UI
- Log in to Fusion and select Collections > Jobs.
- Select Add+ > Custom and Other Jobs > REST Call.
- Enter remove-low-confidence-head-tail in the ID field.
- Enter
<your query_rewrite_staging collection name/update>in the ENDPOINT URI field. An example URI value for an app calledDC_Largewould beDC_Large_query_rewrite_staging/update. - Enter POST in the CALL METHOD field.
- In the QUERY PARAMETERS section, select + to add a property.
- Enter wt in the Property Name field.
- Enter json in the Property Value field.
- In the REQUEST PROTOCOL HEADERS section, select + to add a property.
- Enter the following as a REQUEST ENTITY (AS STRING)
Delete all head-tail suggestions
To delete all of the head-tail suggestions, enter the following in the REQUEST ENTITY section:<root><delete><query>type:tail</query></delete><commit/></root>This entry may be helpful when tuning the head-tail job and testing different configuration parameters.