About Content Gap Causes
When your administrators and usage analysts notice that there are content gaps (see Identifying Content Gaps), they usually want to find the causes and fix them. In this topic, you will learn the different causes of the content gaps.
Visitor Permissions Are Too Restrictive
When the user permissions are too restrictive, some visitors cannot find what they are searching for on your Coveo search page. You should thus ensure your users have the necessary permissions to access the results they need (see Coveo Cloud V2 Management of Security Identities and Item Permissions and Source Permission Types).
Issues With the Query Terms
Misspelling: if your users spell their query terms too far from what your organization has in its index, they could be unable to find results for their search. The Did You Mean feature suggests to your users another spelling for words in their query (see Misspelled Words).
If you typed
Istnagermm), the partial match will not find it.
The partial match does not learn from user behavior, as Coveo Machine Learning does (see Coveo Machine Learning).
Length: if the visitor writes many terms in the search box, the search engine can have difficulties to find the answer. When you enter a query, the search box adds
ANDbetween each term. By using the
partialMatchquery parameter, the most common words are removed and the returned results matches only the important ones (see Managing Query Pipeline Query Parameters and Query Parameters).
If your query is
How can I have access to my Coveo Cloud on my Android Galaxy smartphone?, the search box will pass the following query to the index:
How AND can AND I AND have AND access AND to AND my AND Coveo AND Cloud AND on AND my AND Android AND Galaxy AND smartphone AND ?.
Invalid syntax: Coveo uses a specific query syntax to perform queries. When the Coveo query syntax is enabled on your search interface, and your visitors are using an invalid syntax in their query, this could result in a content gap (see Coveo Cloud Query Syntax Reference and Querybox Component - enableQuerySyntax).
When a field (e.g.,
InstagramFilter) is not implemented in your Coveo Cloud organization, and you want results to be returned if a user performs a field query (e.g.,
@InstagramFilter=Ludwig), you should disable the Coveo Cloud query syntax.
Filters on the Query Are Too Restrictive
The filters selected by the user could be too restrictive. The user could not be in the right tab (cq) or could have selected too many facets (aq), which restrict considerably the number of results.
In your browser console, you can inspect the constant and advanced query expressions to understand the user path and find a solution (see Inspecting a Query).
Issues With Your Query Pipeline Rules
When a query pipeline rule is impacting the basic query expression (q), the advanced query expression (aq), or the constant query expression (cq), your search page can return no results. You can add conditions to your query pipeline rules, but too many restrictions can create content gaps (see Managing Query Pipeline Rules and Rule Conditions From Tabs).
The keywords entered by the user could not match any content. This means that your organization does not have the content in its index or that the user is searching for something but does not enter the right keywords.
Gamers were trying to find
Flash Player to install games on their computer, so they went on a gaming search page and looked for
game requirements, but no results were returned.
If the cause is not one of the following above, it could be because there are no pages related to the user query. This content can be missing or not interesting for your company or vast majority of users. After analysis, if a lot of people is looking for this information, you can create an article on the subject.