When website visitors submit a search expression, the index is scanned instead of the raw data and the results are returned. Index Flexibility You have full control over the content of every search index. Additionally, the search functionality can be limited for visitors, according to assigned permissions. This ensures that data from secured website sections are not displayed to unauthorized users in search results. Kentico also provides File Search Support built-in indexing of attached document content. Visitors to your website can see results before submitting the search.
|Published (Last):||9 July 2010|
|PDF File Size:||1.17 Mb|
|ePub File Size:||1.26 Mb|
|Price:||Free* [*Free Regsitration Required]|
If you are familiar with Search Engine Optimization, your first guess is most likely that they originate from the meta page title and description. While that is where Google and Bing get the title and summary text from, Smart Search in Kentico works a little different. Unlike Google and Bing, Smart Search gives you a good bit of control over how it indexes the content on your website.
Specifically, there are four pieces of data you control for each result: the title, the summary or content, an image and a date. Each document or page within a Kentico site is of a specific type. These types are naturally called Page Types. The most common Page Type is the Page menu item which serves as a general content page.
Other Page Types are used to create structured content such as blog posts, news articles, FAQs, events, and more. When it comes to Smart Search, each Page Type gives you the ability to configure various aspects of how those types of documents are treated in regards to search. You can control aspects such as which fields are included in the search index and how they can be searched, but what we are concerned with in this case is how these documents appear in the search results.
You can find a list of all Page Types in the system by navigating to the Page Types module. To see the search settings for a given type, you must click to edit that Page Type and then go to the Search Fields tab. This tab has two main sections with three set of functions. The first is simply the top most setting which indicates whether or not search is enabled.
This setting determines if these types of documents should be searchable at all. Next, are the four fields below this setting. These control how your documents will display in the search results, and we will talk about them in a minute. Lastly is the grid section at the bottom. These are the settings that determine which fields are included in the index and how they can be searched, however, we will talk about that in a separate blog post.
The four fields that control which results are output are the Title field, Content field, Image field, and Date field. The information required for these fields is pretty obvious except that Content might be a bit misleading.
You may think that the Content field requires the content for what is being searched, but in fact, it is the field that determines the summary text for the search result. Each of these fields is "asking" which field from the Page Type it should get the content to use for Title, Content, Image, and Date values of a search result.
Depending on how your development team has built the layout of your search results, you may or may not be using the Image and Date values at all. Also, not all Page Types will have an Image or Date field as those may be irrelevant base on the type of data the Page Type represents. If you notice that documents appearing in the search results are missing the summary or displaying an incorrect date, the most common cause is that these values are not set correctly.
You will need to go into these settings for those Page Types and ensure they get updated as necessary. Most of the common issues we encounter around these fields occur when a custom page type is created, but the search settings are never updated.
When you create a custom Page Type, Kentico sets default values for each of these settings based on the underlying document settings that are common to all page types. In most cases, these are not what you want. For example, the default for the content field is DocumentContent, which "looks for" any content in an editable area on the Page tab. In this case, you will need to change the content field from DocumentContent to the field name for defined field that contains the content that should be used as a summary.
Similarly, the default for the date field is DocumentCreated but in most cases, this is not optimal because you use workflow or post-date your content because it will be published sometime in the future. This is another case where you need to change the date field from DocumentCreated to the field that contains the correct date that you would like to use.
I hope you find this tip valuable and can use it to optimize user experience through search on your site! Share This!
Kentico Custom Search Index Tips
Kentico makes it easy to generate search indexes and implement a keyword based search out of the box. In this blog post, I will share some vital tips on creating a custom faceted search index in Kentico. For example, lets pretend we want to create a faceted search for kites. Kites can come in different colors and shapes. I have multiple kites that can be a variety of colors and I would like to be able to allow users to search for kites that are multiple different colors and of a specific shape.
Setting up search on your website
The smart search is based on Lucene. Net version 3. NET platform. The smart search uses indexes to store information about the website content. When a user sends a search request, the system searches through the appropriate indexes, which results in significantly better performance compared to linear SQL query search. To set up the smart search functionality on your website, you need to perform the following steps: Enable smart search indexing in the system.
Viewed times -1 [UPDATE] With the help of Kentico, I have determined the cause of the problem to be that the site could not be accessed within the web server itself. Once I corrected that, the page crawler could index the content. The Smart Search page crawler indexing for our production site is not working. However, it is working exactly as we expect on our development site. Smart Search is configured exactly the same in both sites. The content and all Kentico settings are exactly the same in both sites.