Search Settings

How do I adjust how "fuzzy" the search is?

To adjust how precisely your search results should match the search terms entered by your site visitors, go to Search Settings -> General.

You can control the relevance of your search suggestions (also known as autocomplete or search-as-you-type results) with Search Suggestion Fuzziness and the relevance of your search results (triggered by Enter/search button) with the Search Fuzziness.

There're different fuzziness levels that you can play around with and compare the outcome in the Search Preview.

SS360 search fuzziness
  • Extremely strict:

    • All searched keywords should be present in the results (AND logic between the terms) and results should be a 100% match.

  • Strict:

    • All searched keywords should be present in the results (AND logic between the terms) but the matching percentage is a bit more forgiving (>=90%).

    • If a product's article number matches the query exactly, it will be the only product shown in the results. For example, if there are two products with article numbers "A123" and "A123-4" and the search query is "A123", only the first product will be found.

  • Default:

    • Either one of the searched keywords should be present in the results (OR logic between the terms) but it has to be a >=90% match.

    • With article number search we'll look both for full and partial matches here. For example, if there are two products with article numbers "A123" and "A123-4" and the query is "A123", both products will be found. Also, "A1234" or "123-4" will bring up the respective products.

    • Queries such as "iphone8" will be broken into "iphone 8" if nothing is found for the original query.

    • If we don't find any results after breaking up the search query, we'll try fuzzier matches.

  • More results:

    • Also uses the OR Boolean logic between the query terms but the matching conditions are more lenient (>=50%).

    • Article number search rules are the same as with the Default level.

  • Even more results:

    • OR logic between the query terms and even more lenient matches (>=40%).

    • Article numbers work the same way as with the Default level.

  • Get most results:

    • All results at least slightly related to the search query should be shown.

The optimal level differs from site to site as it is related to the type of your site content (product descriptions? blog articles? research papers?) and depends on what your users search for the most (product numbers and SKUs? long-tail search phrases?), The Popular Results table in your Dashboard can provide insight into your search data.

Regardless of the fuzziness level, the best-matching results are always shown at the top, so it's more about how many results should be returned even if they don't fully match the search query.

Please note that the difference between the levels is often unnoticeable for single-word terms e.g., "mittens", "payment", but becomes apparent when you test multiple-word queries e.g., "women ski mittens" or "monthly or yearly payment".

Tip: if you want search suggestions to look for matches within the entire content of your pages and documents, and not only in the titles, make sure to have the "Suggestions only on titles" setting unchecked.

To choose the best fuzziness level for your site, we recommend searching your site from the search box and adjusting the fuzziness in Search Preview to compare.

All control panel queries are NOT tracked and NOT counted towards your search limit quotas. Also, caching is disabled so there is no delay in reflecting your changes.

How do I change which search result snippet is shown?

You can control where the text shown in the search results is coming from in Search Settings -> General.

search snippet source

You can choose from:

  • Content around the search query (default).

  • First sentences of the indexed content.

  • A specific area of the website that you determine via XPath.

  • No snippet at all (titles and URLs will still be shown).

If you want to use Meta Descriptions in your snippets, select the option "Use content behind search snippet XPath" and save. By default, we already tell the crawler to index meta descriptions with the following XPath: //meta[@name="description"]/@content

If you set a different Search Snippet XPath, you need to run a full re-index. When you add or update your meta descriptions, you also need to manually re-index your site or wait until the crawler picks up the changes on the next scheduled re-crawl.

How do I change what search suggestions are shown?

Once your website content is properly indexed, you can change the behavior and the precision of your search suggestions without initiating a re-index. Just go to Search Settings -> General where you can:

  • Choose the degree of Search Suggestion Fuzziness, i.e. whether you want your suggestions to strictly match the search query or you'd like to allow more flexibility. More information on fuzziness levels.

  • Restrict suggestions to only derive from page titles.

    tweak search suggestions
  • Restrict your suggestions to a specific result group. You can add data-ss360-include-suggest or data-ss360-exclude-suggest attributes to your search box HTML markup.

    For example, you have a result group named 'Products' and you want the autocomplete to only suggest products, nothing else. You could then add the following to your search input code:

    <input type="search" data-ss360-include-suggest="['Products']">

    Or, to ignore the Uncategorized results or the 'Other' group, you would use:

    <input type="search" data-ss360-exclude-suggest="['Other']">

    If the same restrictions should apply to full search results as well, use the data-ss360-include or data-ss360-exclude attributes instead. More information on result groups.

When is the setting Suggestions only on titles useful?

For example, you have a series of products called "Travelr." When your customers type travel in your search box, you may only want to prompt them with the "Travelr" product pages and ignore all the other pages that mention, let's say, travel budgeting.

Tip: By default, the first h1 header on your page (//h1) is taken as a title that comes up in search suggestions and results. However, you can point our crawler to any part of a page by adjusting the Title XPath under Data Structuing -> Content Extraction. Here's how to work with XPaths. When editing the XPaths, remember to run a re-index for the changes to take effect.

You can enable the Suggest popular searches feature under Result Manager -> Query Suggestions (available for paid plans). All search queries are anonymously tracked and counted and the data is updated every 3 days.

The tracking works even while the feature is disabled so once you turn it on, you can test popular suggestions immediately, unless there is not enough search data (e.g. for new accounts). See it in action by typing, e.g. curry on our demo site.

Popular searches are shown when they fully or partially match the query that is typed into your search box. They appear on top of your regular suggested results.

Here are the defaults that you can change by adjusting the following parameters in your configuration code:

var ss360Config = {
        suggestions: {
            maxQuerySuggestions: 3,
            minChars: 3,
            num: 6

Tip: check how many suggestions you already show (default max: 6, can be modified with the suggestions.num parameter) and how many popular searches you want to add (default max: 3) and make sure the total number of entries (default: 9) fits above the screen breakpoint.

Can I boost certain pages?

Imagine that more than one page is relevant to a certain query but you'd like one of them to always be ranked a bit higher. There are a few ways to boost and give higher search rankings to a specific type of your search results while decreasing the importance of the others. These options are available under Search Settings -> General.

how to boost results with Site Search 360

Using numeric data points for boosting

For example, let's assume that your users give "likes" to your articles or products. You can create a "Popularity" data point and boost the pages that have more upvotes. To do so:

  1. Create a data point and tell the crawler where to find the information about the number of likes on the page. You can source this information from a meta tag or even a hidden HTML element on your pages. Use XPaths to point the crawler to the right element:

  2. You will see the following options for every numeric data point you create:

    1. Unique - check it to only extract one value per page, recommended for boosting.

    2. Boosting - check it to be able to use the data point for boosting.

      creating a data point for boosting
  3. Now, go to Search Settings -> General and set Page boosting to "Use numeric data point" with the corresponding data point name.

    use a numeric data point for boosting

You can also use data points to implement sorting options and show them in a dropdown above your search results. For every option, you can set the order to descending (i.e. sort by good rating first, price: high to low, newest articles first) or ascending (i.e. sort by bad reviews first, price: low to high, oldest publications).

Using URL patterns for boosting

This essentially works in "levels". Even though you can set anything between 1 and 100, it is advisable to use levels of 10 (20, 30 etc.)

Example: you can boost your /products/ by 90, /category/ by 30, and /blog/ by 10: the higher the boosting score is, the more priority is given to the respective results.

How exactly does it work? Let's say you are boosting /blog/ by 10 and /products/ by 30. You type in a search query and you see that matching results under /products/ come up above /blog/ results, even if a blog post is a very good match to your query (e.g. has the exact same title).

So boosting happens more or less independently of how well the query matches, although the query relevance does still play a role, especially for smaller boosting levels such as 1, 2 etc.

set up url boosting levels

You can also downrank or "penalize" certain results by setting the value to anything between 0 and 1. If, for example, your PDFs files come up higher than any other type of search result and this is not the desired behavior, try 0.3-0.5 as boost value and \.pdf as URL pattern to lower default PDF ranking.

Learning each document's importance automatically.

By default, this setting respects the <priority> tag value if it's set in your sitemap. With our AI Ranking Engine [beta feature], we use machine learning algorithms to optimize your search result ranking over time by automatically promoting most popular results to the top.

PDF Settings

Under Search Setting -> PDF settings you can configure what title, content, and thumbnails should be displayed for your PDF search results.

PDF settings

PDF crawling is available in all paid plans with a default maximum size of one PDF document - 15 MB (can be increased if needed).

If the crawler finds the "pdf-data-title" attribute, it overrides whatever is set in the PDF title strategies setting. e.g.:

<a href="link/to/pdf/file.pdf" pdf-data-title="The title of the PDF">read more</a>

You can add your custom HTML content anywhere in the search results for any query you like. For example, if you want your users to see a banner promotion when they search for food, you would follow this process:

  1. Go to Result Manager -> Result Mappings.

  2. Type the query for which you would like to add your custom content.

  3. Decide whether the query must match exactly, contain the term, be part of a phrase, or match a regular expression.

  4. Choose the Custom Results tab and press "Add new custom result".

  5. Edit the newly created custom search result by adding title, image URL, result link, and result content (Snippet) or by writing any custom HTML you want the user to see.

  6. Drag and drop your custom result to the desired position and pin it there.

  7. Save your mapping. You can edit or delete that mapping later. You can use the Search Preview in your control panel to immediately test the mapping.

If you have an XML file with your Google Custom Search promotions, you won't have to rebuild them for Site Search 360. Use the import function at the bottom of the Result Mappings section.

Please refer to this detailed post on Result Mappings for more information.

How do I prevent logging and tracking for certain users?

You might have your own team using your website's search often and don't want these searches to skew your logs. You can simply set a cookie in your browser for those users which prevents logging of their queries.

When you're on your site, press ctrl+shift+e and the tracking will be disabled for this specific browser. Alternatively you can set a ss360-tracking=0 cookie to prevent the tracking.

To do so, open your browser console (F12 in Chrome and Firefox) and write document.cookie = "ss360-tracking=0; expires=Sun, 14 Jun 2022 10:28:31 GMT; path=/";.

You can of course change path and expiration date according to your needs.

You can also add IPs as "IPs that should not be logged" under Search Settings -> IP Settings if the cookie approach does not work for you. We support wildcard notation so you can use an asterisk (*) to add IP ranges e.g., 46.229.168.* or 46.229.*.* or 46.*.*.*

Note: when you test your search by using the search bar in Search Preview, these test queries are not logged either.

What search operators can I use with Site Search 360?

Search operators are special characters that you can add to your query in order to refine the search results. We currently support these 2 most frequently used operators (based on our research analyzing 10 mln queries):

  1. Quotes to search by phrase: put your query in quotes (" ") for an exact match. Example: "bill gates". In this case no pages or documents that mention something like "you have to pay this bill to open the gates" would come up.

  2. Negation to exclude a term. Put a minus (-) right before the word that you want to remove from search results. Example: bill -gates. In this case all pages or documents mentioning bill and NOT mentioning gates would be found.