Configuring Cludo Studio for Rich Inline

Setting up the crawler fields correctly ensures your Rich Inline search results in Cludo Studio are accurate and complete, with the metadata and tags you want to display. This guide walks through configuring each field. You can verify field mapping with the Test Crawler feature before running a full crawl.

For a general overview of Cludo Studio, how to access it, and what else to set up in MyCludo first, see Cludo Studio.

Title

Field name Title. The main title shown in the search result. This field already exists and uses the automatic value by default. Keep it descriptive so it reflects the content accurately.

Description

Field name Description. A summary or excerpt shown below the title. This field already exists and uses the automatic value by default. It should give the user a clear idea of the page content.

Meta Description

Field name MetaDescription. The page meta description, used for SEO and an enhanced search display. We suggest extracting it from the meta tag (description) or Open Graph (og:description). Optional, but recommended for better clarity and context in results.

Category

Before you configure this field: plan out your categories first. Once your crawler has indexed your content, ask your Customer Success Manager or Cludo Support for a URL export, then look for natural groupings by URL folder path (for example /admissions/ or /news/) and check how many pages fall into each. Choose category names that reflect how visitors are likely to search, not internal taxonomy terms.

URL patterns are the easiest source to map from, but they don’t work for every page type. News and event pages, for example, often use a flat URL like /news/2026/08/27/article-name that doesn’t expose a category. In those cases, check whether the category is available in the page’s metadata, JSON-LD, or CMS taxonomy instead.

See Understanding Facets and Filters in Cludo for how Category relates to other filtering options.

Field name Category. The category assigned to the page, displayed as a tag above the title and usable for filtering and facets. This field exists and is set to automatic by default, but automatic does not work well for category. We suggest mapping it from a few URL parameters, such as /news/ or other sections from the site’s main navigation. A working Category is required for Custom Categorized to work.

Image

Field name Image. The main image for the page, displayed alongside the result to make it more visual. This field exists and you can try the automatic value first. If automatic does not work, it will require an XPath. The image URL must be correct and publicly accessible, otherwise it may not render in results. If you would like help setting up the XPath, reach out to us.

Date

Field name Date. The date associated with the content. There is an automatic value, and if it does not work it will require an XPath. Make sure the value is recognized as a date string (the indexed field becomes Date_date). If the date is not formatted correctly, it will not be translatable, filterable, or usable in date facets, and the raw string will be shown as is. Reach out to us if you would like help configuring this.

Breadcrumb

Field name Breadcrumb. The hierarchical navigation path for the page (for example “Home > Products > Laptops”). Breadcrumbs often follow a consistent pattern, so an XPath such as //*[contains(@class, "breadcrumb")]//a works in many cases. If this field is missing, the crawler uses the page link instead. You can also derive a sub-category, division, or department from URL patterns, in which case neither the link nor the actual breadcrumb is shown.

Badge

Field name Badge. A tag included in Rich Inline, displayed above the title next to the category tag. It can be the same as Category or something else entirely. You can map it from specific URL patterns, metadata, or an XPath. In Rich Inline, no badge is shown if it has not been set up.

Tags

Field name Tag. Additional labels for the page, mapped from URL patterns, metadata, or an XPath, and displayed above the title next to the category tag. Tags are available for Custom and Custom Categorized implementations only, not for Rich Inline.

Extra facet or category

Setting up an Extra Facet takes two steps, and both are required before it appears in your search:

1. Create and populate the custom field in your crawler (Configuration › Crawlers › select your crawler › Edit › Content › Add custom field).
2. Register that field as a facet on your search engine by emailing support@cludo.com with your Customer ID, the Engine ID, and the exact custom field name you want registered as a facet.

Start the recrawl before requesting the engine facet, since the field needs to already be in the crawled index before support can register it.

You can add any additional facet for the customer. Name it however you like, using CamelCase with no spaces, for example ExtraCategory. Map it from URL patterns, a meta tag, or a second breadcrumb (for example (//*[contains(@class, "breadcrumb")])[2]//a). When you use a field as a facet, it must be added to the engine facets. Contact you account manager or Cludo Support to add the engine facet.