Site search
Search built on your catalog. Typos and product codes handled.
Your developers add it to your website or B2B portal through the REST API. Only products marked Approved show up.
How it works
Built for how people type. Tuned by your team.
From typo to report.
01Forgive
Room for typos.
Typo tolerance is on by default. When a search finds nothing, it retries with corrections and tells your site what changed.
02Teach
Teach it your shoppers’ words.
Add synonyms and correction rules. Pin, boost or hide products for a search, by channel, language or date, and preview first.
03Learn
See what people search for.
Queries and zero-result searches are recorded. Send click and purchase events to see which searches lead to sales.
Also in site search
Tune it without code.
Filters from your attributes
Pick attributes such as size or color, plus category, price range and discount.
Autocomplete
Suggest products, popular searches, categories and spelling fixes as people type.
Only Approved products, updated on change
Drafts stay off your site. The index updates after saves, status changes and deletes.
Prices from Product Pricing
Show prices from the price list, currency and zone you set, with price filters.
A/B tests and relevance checks
Weight fields, boost categories, run A/B tests and score saved test queries. A/B tests need click and purchase events.
API keys with fixed filters
Give each site or portal its own API key, with product results limited to a channel or language.
Good to know
Straight answers.
Still curious? Email the founders
Is AI matching on?
Only if you switch it on. By default, search matches on keywords, so exact product codes return exact matches. Each workspace can add AI matching, which blends keyword results with results that match what the shopper means. It needs an AI embedding model set up first.
Which languages and channels does it cover?
Each workspace searches one channel in your primary language, plus extra languages you add, whose product text then becomes searchable too. Results show names and descriptions in your primary language. Word-form matching is tuned for English, and typo tolerance doesn’t apply to Chinese, Japanese or Korean searches.
Is there a widget or SDK?
Developers add search through the REST API with an API key, and your team builds the search box and results into your own site or portal. Pre-built widgets and SDKs aren’t available.
Do Brand Hub buyer portals use it?
Yes. Brand Hub buyer portals run on the same search engine, and Brand Hub workspaces get portal search without adding Site search. The search settings and API on this page need Site search, an add-on to PIM Hub.
Works with
See search on a catalog like yours.
Tailored to your site or portal.