Cludo Studio

11 Jun, 2026 Implementation

Cludo Studio is a hands-on environment for building and previewing search experiences. It lets you spin up a working demo of a search setup quickly, switch between implementation types, and share a link that preserves exactly what you configured. It is especially useful when designing a Rich Inline search, where you want to see how titles, categories, images, and tags will look in real results before going live.

This guide covers what Studio does, how to access it, and how to set up a crawler so your Rich Inline results look their best.

How to access Cludo Studio

You can open Cludo Studio here: https://customer.cludo.com/templates/catalog/studio/dist/

How to use it

Studio is built to help you create clear, realistic demos of the different search implementations. The typical flow is:

1. Set up a crawler and engine

Start by creating or selecting a crawler for the website you want to demo, and make sure the content is indexed correctly so you have relevant, realistic results to show. For Rich Inline and custom templates, some crawler fields are predetermined, so it is worth setting them up before you build the demo. The crawler field setup is covered in the next section.

Connect the crawler to an engine. If you want to use AI Summary or AI mode in the demo, make sure the engine is AI enabled. If you need extra facets, add the extra crawler field names to the engine’s facet list (see the Category and extra facet notes below).

2. Select a template

Choose the implementation type that fits your scenario. You can switch between templates after adding your settings. The only action that clears all settings is returning to the index page or clicking the logo.

  • Rich Inline for out-of-the-box demos.
  • Custom for tailored functionality.
  • Custom Categorized for structured, result-based designs.

Configure the demo to match the needs you are designing for, and highlight the relevant features and value.

4. Share the demo

Send the generated demo link. The link preserves all chosen settings, so what the recipient sees matches exactly what you configured.

Crawler setup for Rich Inline results

Setting up the crawler fields correctly ensures search results are accurate and complete, with the metadata and tags you want to display. Below is how to configure each field. You can verify field mapping with the Test Crawler feature before running a full crawl.

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

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.

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

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.

Related Posts