Search
Set up Search after importing and checking your data. First identify how your theme opens Search on desktop and mobile, then choose the experience that fits it.
Inspect Search #
A theme can have separate desktop inputs, mobile icons, hidden panels, and homepage search fields. Inspect each before choosing triggers.
- Open the webshop on desktop and mobile. Find every input or control that opens Search.
- Use developer tools to inspect stable selectors and confirm which input receives typed text.
- Test the native dropdown, mobile panel, Enter key, and form submission. Note which behaviours need replacing or retaining.
- Check another page type; a homepage search field may differ from the header input.
Fodmagasinet’s example triggers are .search-bar #search-overlay-input and #frontpage_search_container. Check whether those selectors exist and have the same role on your webshop. A trigger container is not necessarily the text input itself.
Choose Experience #
Use Omnisearch for a combined search experience, or keep a separate dropdown and search page where that better fits your theme.
| Experience | When to use it |
|---|---|
| Full-screen Omnisearch | A search overlay covering the viewport with its own interface. |
| Partial Omnisearch | Results below the native header, preserving its search field, logo, and basket. |
| Instant Search | A dropdown linked to an existing input, usually alongside a separate results page. |
| Search Page | A dedicated results page with filtering and sorting. |
Create Omnisearch #
- Go to Search > Designs > New Design and choose an Omnisearch template.
- Name and save the Design, then adapt its product cards using the card-data checks. Product-page links support products that need variant choices.
- Go to Search > Elements > New Element, name the Element, and choose Omni-search as its type.
- Select the Design, save in In preview, and open its insert settings.
- Configure the verified trigger selector using injection, or copy the generated embedded code into your theme once.
- Choose Full Overlay or Partial Overlay and test all intended triggers.
For Partial Overlay, set the Header selector to the native header wrapper and Search input selector to the real text input. Configure the overlay width and height to fit the layout. See Omnisearch for these options.
Fodmagasinet’s Partial setup uses the native header and input rather than a cloned header or basket. Its selectors, header structure, breakpoints, colours, and spacing are examples to inspect, not requirements for other themes.
Separate Search #
For a dropdown, create an Instant Search Design and a Live-search Element. In the insert settings, target the verified input and choose the dropdown position.
For a results page, create a Search Page Design and Element, then insert it in the theme’s results-page template. Pass the current query using the generated embed code and direct the native form to that page.
Use the Instant Search and Search Page guides for the shared configuration. Replace native results only within their results container; preserve surrounding navigation and page layout.
Native Behaviour #
Resolve overlapping handlers before enabling Search for visitors. Hiding a native dropdown alone may leave its keyboard or form handlers active.
During Preview testing, type real characters and check whether both native and Clerk.io results appear. Inspect the mobile icon and panel separately; opening the wrong panel can hide the input or change navigation history.
If native handlers compete, have the theme developer adjust only the relevant input, panel, or form. Scope any temporary replacement to the intended Search state so the normal page remains usable when it closes.
Test keydown, keyup, and form submit paths. Enter must either open the selected Clerk.io result or perform the intended search. Do not globally cancel Enter or remove all keyboard listeners: arrow-key result selection must continue to work.
Close and Escape must restore the underlying page, focus, and scrolling without navigating Back or leaving a blank page. Repeat open/close, navigate to a result, and test Back/Forward on desktop and mobile.
Facets #
Choose filters from attributes that actually exist on imported products. A template’s vendor, brand, or category field may not match your feed.
Inspect several records, select the available attributes in the Search configuration, and give them localized labels. Confirm each facet changes results correctly, including products missing an optional attribute.
For sorting, compare the imported values with the displayed card prices. A visual lowest-variant-price label does not correct an incorrect parent price used for sorting.
See Search best practices for choosing useful filters and result layouts.
Content Results #
Import articles and other pages before enabling them in Search. Follow Import Pages to fetch them through the sitemap as part of your AI Integration.
Then check both the Element’s page-result settings and the Design’s page-results section. Imported articles can remain hidden if the Design omits that section or its layout hides the column.
Search for a distinctive article title and verify its link and content. Check this separately from product matching and page-based recommendations.
Style Safely #
Keep Search CSS within its component so it cannot change recommendation sliders elsewhere on the page.
For example, give your custom Search card wrapper a dedicated class and scope every rule to it:
.ideal-clerk-search .ideal-clerk-card {
display: flex;
flex-direction: column;
}
Do not apply Search layout rules to global .clerk-slider, button, or .active selectors. Recheck homepage and product sliders after opening and closing Search, including their arrows, widths, and overflow.
Finish with the setup checklist. See the Search conflicts FAQ if native controls still interfere.