Most explanations of site search stop at the search box. The buyers shopping for it have usually moved past that: what they are deciding is whether the search their platform already includes is still enough, and if not, what to replace it with. Their answers are the useful half of this page — who buys it, what pushes them to change, what it costs, and the few who go back.
What is ecommerce site search?
Ecommerce site search is the search box on your own store and the software behind it that decides what it returns. It interprets what a shopper typed, retrieves matching products, ranks them, and gives the shopper ways to narrow the result.
The ranking is the part people underestimate: the tool is not only matching words, it is choosing an order — and deciding what never surfaces at all. Site search is a ranking system with a merchandising surface attached.
Work out what they meant. Misspellings, synonyms, and phrasing your catalogue does not literally contain. Rain jacket has to reach a product called a shell.
Decide what comes first. Every query returns an order, and something has to produce it — relevance scoring, popularity, margin, stock, or a rule someone wrote.
Let the shopper narrow. Size, colour, price, availability. Only as good as the attributes your product data actually carries.
Let a human intervene. Boost, bury, pin or curate results for particular searches — a recurring reason teams want a different tool.
Four jobs behind a mature search experience. These interviews make clear that filtering and merchandising matter alongside interpretation and ranking.
What the interviews add is the part a definition leaves out:
Most stores start on the search their commerce platform includes — Shopify and Salesforce Commerce Cloud are the native searches buyers here most often describe running — so the first decision is usually not do we need this? but is the one we already have still sufficient?
Buyers describe native search in the language of adequacy rather than enthusiasm. One says their setup does what it needs to do. When they do move, the most common reason they now give is AI or semantic search, ahead of merchandising control.
What is the difference between site search and product discovery?
Site search is the query-driven part of product discovery; product discovery also covers browsing, recommendations and merchandising. A shopper using site search types what they want, and the system interprets, ranks and filters the results. Product discovery adds every way a shopper finds products without typing anything.
The two are bought together more often than the definitions suggest. Many vendors span both, so a tool bought for search can end up judged on its recommendations too — buyers here describe combining search with recommendations and merchandising in one tool as a reason to switch.
Against product recommendations
Search answers a shopper who has said what they want; recommendations guess for one who has not. Vendors such as Bloomreach and Nosto sell both, which is why the line blurs in evaluations. The full comparison is site search vs product recommendations.
Against your platform’s built-in search
Native search comes with the commerce platform; a dedicated tool is bought separately to add relevance, merchandising rules or AI the platform does not ship. Buyers do not treat these as different categories so much as two stages of the same one.
Who buys site search software?
Ecommerce teams. About half of the buyers in market for site search in these interviews hold ecommerce or digital titles, against under a third of all the buyers we interview. Marketing titles, the largest group across the corpus, account for only about one in seven here, as do merchandising and product titles.
By company size the cohort is weighted toward mid-sized and large companies, with the very largest under-represented: companies above $10B in revenue make up about one in seven of these buyers, against about one in four across the corpus. The native platforms they are most often weighing are Shopify and Salesforce Commerce Cloud.
What pushes buyers to change site search?
The direction is lopsided. Nearly half of the buyers in market are moving off built-in or home-grown search, nearly a third are replacing one specialist tool with another, and only a handful are going back to native. Across both groups, the reasons line up in this order:
- AI or semantic search
- Merchandising control
- Personalization
- Results that fail shoppers
AI search is now the most common reason given, raised by about four in ten buyers in market — and by buyers replacing a specialist as well as those leaving native.
AI or semantic search
Buyers want natural-language, vector or conversational search that can better interpret what a shopper means, rather than relying only on the words they typed. Interest in it drives evaluations both of replacements for native search and of newer specialist tools — though the interviews do not establish that every AI-first option returns better results.
One buyer replacing a specialist describes the shortlist as very similar to Searchspring in how they're built, and we're looking for something that is more AI-first.
Merchandising control
The ability to boost, bury, pin and write rules for particular searches. Buyers name a specific rule the current tool will not support rather than a general dissatisfaction.
One buyer on Shopify’s own search says it is not really a merchandising tool. Another, on a third-party tool, describes gaining a bit more control over search than Shopify's native search.
Personalization
Results that change with the shopper rather than one ranking for everyone.
One buyer relying only on Shopify's search capabilities is evaluating dedicated vendors for AI relevance, conversion optimization, and personalization of search.
Results that fail shoppers
Misspellings, synonyms and zero-result searches — the plain relevance problem.
One buyer describes the moment the problem became visible: the search functionality is what failed them and that's where the session dropped off.
A few buyers move the other way. One describes re-platforming and concluding we don't really need a third-party search tool; another finds the native Shopify search functionality is better than BloomReach in my opinion at this point, especially considering it's free. It is a handful next to the group going the other way, so it is not a trend — but it is a reason to keep asking what a paid tool does that the built-in one would not.
Which site search tools do buyers rate highest?
Coveo and Bloomreach have the highest observed buyer ratings among the site-search platforms compared here, though Coveo’s figure is rounded because fewer buyers rated it. Algolia is the most-rated platform but sits below several smaller names. These are overall platform ratings, and some buyers also use these products for recommendations, merchandising or other jobs beyond search. The spread is wide — among the widest of any category we can measure this way.
| Tool | Rating | What it means here |
|---|---|---|
| Coveo | around 7.5 | Too few buyers for a decimal. An enterprise option that appears in evaluations where AI relevance at scale is the requirement. |
| Bloomreach | 7.3 | Spans search, merchandising and messaging, so buyers are rating more than the search box. |
| Constructor.io | around 7 | Too few buyers for a decimal. Appears in evaluations by buyers leaving native search specifically for relevance. |
| Algolia | 6.9 | The most-rated site-search tool in our corpus by a wide margin, and it rates below smaller names here. Cost is a recurring complaint in these interviews. |
| Nosto | 6.7 | Sits across search, recommendations and personalization; several buyers run it alongside native search rather than instead of it. |
| Searchspring | 6.3 | A mid-market specialist. Buyers name filters, merchandising and recommendations as where it falls short of what they wanted. |
| Fast Simon | around 5 | Too few buyers for a decimal, and the lowest figure here. |
| Klevu | not rated | Too few buyers rated it to publish a number. |
| Platform-native search | not rated | Too few buyers rate their platform's built-in search as a product for a number to mean anything — which is itself telling about how it is regarded: as part of the platform rather than a tool you chose. |
That is worth holding lightly — the tools serve different sizes of catalogue and different teams — but it does mean the shortlist should not start from adoption alone. Head-to-heads are published for Algolia vs Bloomreach Discovery, Algolia vs Searchspring, Constructor vs Bloomreach Discovery and Searchspring vs Nosto.
What does site search cost, and how do buyers measure it?
Dedicated tools are usually priced on search volume, and most buyers do not say how they will measure the result. Buyers describe pricing in units based on search volume, a price per search, or an annual request quota, so the bill grows with traffic. That is one of the reasons buyers give for replacing a specialist: a buyer on Coveo says the model worked with a small scale. Right now we are getting priced as price per search. Another describes annual quotas their vendor is not flexible about lowering mid-year. Native search is typically bundled with the ecommerce platform rather than bought as a separate search subscription, which makes it attractive to buyers who cannot justify the extra cost of a specialist.
Measurement is thinner. Most buyers in market do not name a success measure at all. Those who do name conversion, zero-result or exit rates on searches, and revenue per search; a few plan a side-by-side test of the shortlisted tools, and one sets cost per search as its return-on-investment criterion.
Want this checked against your own stack?
Start my checkup →Should you upgrade from native site search?
Upgrade when you can name the specific thing you cannot do. That is how the buyers here who moved describe it — a rule they cannot write, a search that returns nothing, an AI capability the platform does not ship — rather than a general sense that search is bad. The questions below are our recommendation rather than a framework buyers describe.
First, name the blocked task, and check whether it is AI relevance, merchandising control, personalization or plain relevance — they lead to different tools. Second, check the product data: a tool can rank and interpret, but it cannot invent an attribute your catalogue does not carry. Third, price it on your own search volume, since that is how most dedicated tools bill. And if you already pay for a specialist, ask what it does that the platform’s own search would not now do — a few buyers here asked and went back.
Where buyers go when they leave a search vendor, and what they wish they had checked, are covered on why ecommerce teams switch site-search vendors and what site-search buyers wish they had known.
Common questions
What is ecommerce site search?
Ecommerce site search is the search box on your own store and the software behind it that decides what comes back. It takes what a shopper typed, works out what they probably meant, and returns a ranked set of products with filters to narrow them. That last part matters more than it sounds: the software is not only matching words, it is choosing an order. Which products appear first, which are filtered out, and which never surface at all are decisions the tool makes on every query.
What does site search software actually do?
Four jobs. It interprets the query, handling misspellings, synonyms and phrasing a catalogue does not literally contain. It ranks the matches, deciding what comes first. It provides filters and facets, so a shopper can narrow by size, colour, price or whatever your catalogue supports. And it gives merchandisers control: rules to boost, bury, pin or curate results for particular searches. In these interviews it is mostly bought by ecommerce teams, and merchandising control is one of the most common reasons they want a different tool.
Is your ecommerce platform's built-in search good enough?
For many stores, for a while. Native search is where most catalogues start, and buyers describe it in terms of adequacy rather than enthusiasm: one says theirs does what it needs to do, another that they are satisfied enough that it is not a hot-button issue. Native search often becomes insufficient gradually rather than failing outright: it keeps working while slowly becoming the reason a team cannot do something it wants to do.
When should you upgrade from native site search to a dedicated tool?
When you can name the specific thing you cannot do. In these interviews the most common reason buyers give for changing site search is AI or semantic search, raised by about four in ten, followed by merchandising control, personalization and results that fail shoppers. Nearly half of buyers in market are moving off built-in or home-grown search, and nearly a third are replacing one specialist tool with another. Where the complaint is vaguer than a named task, check whether the problem is the tool, the merchandising process, or the product data underneath it.
Do companies ever move back to native site search?
A few do, and it is the minority direction by a wide margin. One buyer describes re-platforming and concluding they did not really need a third-party search tool because the native one did just as well; another finds their platform's native search better than their specialist, especially considering it is free. The counter-current is small next to the number of buyers going the other way, so it is a reason to check whether you still need what you are paying for rather than evidence of a trend.
What is the difference between site search and product discovery?
Site search is the query-driven part of product discovery: a shopper types what they want, and the system interprets, ranks and filters the results. Product discovery is broader and also includes category browsing, recommendations, merchandising and the other ways shoppers find products without typing anything. Many vendors span both, which is why buyers often evaluate them together, and why a tool bought for search can end up judged on its recommendations too.
How much does site search software cost?
These interviews do not support a typical price, but they are consistent about the shape. Dedicated tools are usually priced on search volume, whether as units, a price per search or an annual request quota, so the bill grows with traffic, and that pricing is one of the reasons buyers give for replacing a specialist tool. Native search is typically bundled with the commerce platform rather than bought as a separate subscription, which is part of its appeal. The implication, ours rather than a buyer's, is to price a dedicated tool on your own search volume, not on the demo.
Get a checkup on your tech stack
A checkup for your marketing stack, built from hundreds of verified buyer interviews: what matters most to you, a shortlist for your stack, and your next steps.
Start my checkupFree · no password · your answers are anonymized before they inform research like this.