Customizing the Rich Inline Template
Once your crawler fields are configured as per Setting up Crawler Fields for the Rich Inline, use these settings to fine-tune behavior beyond the defaults. This is optional, and most implementations can keep the defaults; review only the sections that apply to your site or implementation.
If you wish to skip this, and head straight to the code snippets, see our Rich Inline Template Technical Reference.
Quick configuration guide
Each row links to the matching section of the Rich Inline Template Technical Reference for the actual settings and code.
| Configuration | What it controls | Change it when… | Typical setup |
| Search Bar | Placeholder text, accessibility labels, and search button | You want the search bar to better match your site or brand | Keep defaults |
| Basic Settings | Search Page URL and Search Input Selector | You need to connect Cludo to a specific search page or existing search box | Review |
| Selectors & Multiple Instances | Search results, facets containers, and Instance ID | Your implementation uses custom HTML or more than one Cludo search | Keep defaults |
| Behavior | Focus, scrolling, highlighting, loading, and browse behavior | You want to change how search behaves after a visitor searches or filters | Optional |
| Autocomplete | Autocomplete behavior, Pre-search Suggestions, and Search-as-you-type | You want to fine-tune what visitors see before and while typing | Review if enabled |
| Facets | Facet labels, selection behavior, presets, and value order | You need to customize how visitors interact with facets | Review if using facets |
| Filters | Hidden restrictions on what the search can return | The search experience should only search a specific site, section, or content set | Optional |
| Default Sort Order | How results are ordered | Results should be ordered by something other than relevance, such as date | Keep relevance for most searches |
| Pagination | Numbered pages, endless scroll, and results per page | You want to change how visitors move through larger result sets | Review |
| Tracking | Cludo analytics, Google Analytics, and cookie consent | You need custom analytics or consent behavior | Keep defaults for most sites |
| Voice Search | Microphone-based search | You enabled Voice Search in Cludo Studio | Review if enabled |
| Override Strings | Interface text, labels, messages, and translations | You want to replace Cludo’s default wording | Optional |
| Callbacks | Custom JavaScript at specific search events | A developer needs custom logic during the search experience | Advanced |
| Single Page Application (SPA) | Support for client-side routing | Your website is an SPA or uses navigation without full page reloads | Developer review |
Review for most implementations
Search Bar: review the placeholder text, ARIA labels, and search button. Most sites can keep the defaults unless you want the search bar to better match your site’s language or branding. See Add/update search form.
Basic Settings: confirm the Search Page URL and Search Input Selector. Your Customer ID, Engine ID, and language are already populated from Cludo Studio. See Add script.
Autocomplete: review this section if you’re using Pre-search Suggestions or Search-as-you-type. If you’re using Cludo Studio, these features may already be enabled based off it; use this mainly to fine-tune their behavior. See Autocomplete.
Facets: confirm the facets you want to use and adjust visitor-facing labels or selection behavior if needed. See Facets.
Pagination: choose between Pagination and Endless Scroll, and set how many results load at a time. See Pagination.
Optional settings
| Setting | When to use it |
| Behavior | Change focus, scrolling, highlighting, loading states, or allow visitors to browse results without entering a search term |
| Filters | Permanently restrict a search experience to a specific domain, Category, or field value |
| Default Sort Order | Use date or another field instead of relevance for a specialized search such as News or Events |
| Tracking | Send analytics to a specific Google Analytics property or configure cookie consent behavior |
| Voice Search | Fine-tune Voice Search if it was enabled in Cludo Studio |
| Override Strings | Replace default labels, messages, or accessibility text |
Advanced developer settings
| Setting | What it is | Recommendation |
| Selectors & Multiple Instances | Connects Cludo to custom result/facet containers and separates multiple search instances | Leave defaults unless your implementation uses custom markup |
| Callbacks | Runs custom JavaScript before or after specific search events | Use only for custom developer functionality |
| Single Page Application (SPA) | Supports websites that use client-side routing | Enable only if your site is an SPA |
Good to know
Facets vs. filters: a facet is visible and lets visitors narrow results. A filter works behind the scenes and permanently restricts what the search can return.
Default sort order: relevance should remain the default for most site searches. Date sorting is most useful for experiences such as News or Events.
Callbacks: most implementations will not need callbacks. Use them only when a developer has a specific custom behavior to implement.
Related articles
- Rich Inline Template Overview – what the Rich Inline Template is and when to use it
- Cludo Studio – design and preview your search
- Setting up Crawler Fields for the Rich Inline – set up the crawler fields your results will display
- Rich Inline Template Technical Reference – the full implementation, styling, and configuration reference