Most posts comparing WordPress search plugins are written by whoever sells one of them, which makes them useless at the only moment that matters: when you are trying to work out which problem you actually have. We sell one too. So here is the version that tells you when not to buy ours.
The short answer is that "our search is bad" describes at least four different failures, and they have different fixes at wildly different prices. Diagnosing which one you have takes about fifteen minutes and will save you from paying for the wrong thing.
First, find out which failure you have
Take the ten questions your support team or your sales team answers most often. Real questions, in the words customers actually use. Search each one on your own site. Then count how many returned something genuinely useful in the top five results.
Now look at how the failures failed, because that is the diagnostic:
- The right pages came back, in a useless order. Your answer was on page three under a 2019 blog post. This is a ranking problem.
- Nothing came back at all, but the page exists. Often the content lives in a custom field, a PDF, a product attribute, or a custom post type that search never indexed. This is a coverage problem.
- Hundreds of results came back, none of them relevant. WordPress split your question into words and matched any of them. This is what core search does to a question.
- The page exists and says the same thing in different words. A visitor searches "how do I cancel", your page says "ending your subscription", and the two never meet. This is a vocabulary problem.
Those four have genuinely different answers.
What core WordPress search actually does
It is worth knowing the mechanism, because it explains three of the four failures above. Core search takes your query, splits it on spaces, and matches those terms against post title, content, and excerpt. It does not weight a title match above a body match in any meaningful way, and it orders results by date.
So a question like "how do I get a refund" is treated as a bag of common words. Every page containing "how", "do", "get" or "a" is a match. You do not get zero results. You get hundreds, newest first, and the refund policy is somewhere in there.
This is not a bug. Core WordPress search was built for blogs with a few hundred posts, and it is fine at that size. It stops being fine somewhere north of a thousand documents.
Relevanssi: fixes ranking, and the free version is genuinely good
Relevanssi replaces core search with a real relevance engine. It builds its own index, weights matches by where they appear, handles partial matches and fuzzy matching, and orders results by relevance rather than date.
If your diagnosis was ranking, install the free version today. It is one of the best free plugins in the directory and it will probably solve your problem for nothing. Premium runs about €120 a year for unlimited sites and adds PDF indexing and "did you mean" suggestions.
What it does not do is understand meaning. It is a lexical engine, a very good one. If your visitors use different words than your content, Relevanssi will rank the wrong pages very accurately.
SearchWP: fixes coverage, especially structured content
SearchWP is the answer when your content is not where search is looking. It indexes custom fields, taxonomies, custom post types, WooCommerce product data, and document contents, and lets you assign weights per attribute so a SKU match can outrank a body-text mention.
If your diagnosis was coverage, and particularly if you run WooCommerce or a site built on ACF, this is very likely your tool. It starts at $99 a year for a single site and runs to $399 for agency use.
Like Relevanssi, it is lexical. It will find your content in more places. It will not bridge a wording gap.
FacetWP: not a search engine
Worth naming because it gets bundled into these comparisons. FacetWP does filtering and faceted navigation, which is a different job. It helps a visitor narrow a result set they can already see. It does not decide what goes into that set or in what order.
Plenty of sites run FacetWP over stock WordPress relevance and assume search is handled. It is not. The filters are doing real work on top of a ranking layer that was never fixed.
Hosted search: Algolia and friends
Hosted search services bring speed, typo tolerance, and instant-results interfaces. For large catalogs where response time is the felt problem, they are excellent, and the developer experience is good.
Two things to know. Pricing is usage-based, so cost scales with traffic and can be hard to predict on a content site with spiky traffic. And synonyms are a configuration surface you own: you can absolutely make "cancel" match "ending your subscription", by maintaining that mapping yourself, forever, for every phrasing your visitors invent.
Where semantic search actually earns its price
This is our category, so read it with that in mind.
Semantic search matches on meaning rather than characters. It represents your content and the query in the same conceptual space, so "how do I cancel my subscription" retrieves the page about ending your plan without anyone having written a synonym rule connecting them.
That solves exactly one of the four failures: vocabulary. It happens to be the failure that lexical tools cannot solve by design, and the one that gets worse as your content grows, because a larger library means more ways to say the same thing.
It is also the most expensive option here. WPRAG starts at $49 a month, which is several times the annual cost of Relevanssi Premium. That is a real gap and we are not going to pretend otherwise. It buys you managed infrastructure, no synonym maintenance, and answer summaries generated from your own content. Whether that is worth it depends entirely on whether vocabulary is your actual failure.
When not to buy WPRAG
Genuinely, do not buy this if:
- Your site has under a thousand documents. Below that, visitors find things by browsing, and core search plus Relevanssi is plenty. You will not feel the difference.
- Your diagnosis was ranking. Install Relevanssi free. If it fixes it, you are done, and you spent nothing.
- Your diagnosis was coverage. SearchWP is purpose-built for this and costs a fraction as much.
- Your problem is speed. A hosted lexical service will be faster and cheaper than semantic retrieval.
Buy semantic search when you have a large body of content, your visitors phrase things differently than your writers do, and you have already watched a lexical tool fail to close that gap. That is a narrower set of sites than our marketing would ideally like. It is also the set where the difference is dramatic rather than marginal.
Run the test
Ten real questions. Your own site. Count the useful results in the top five. Note how each failure failed.
Whatever that tells you, it is a better basis for a decision than any comparison table, including this one. If the answer turns out to be Relevanssi, that is a good outcome and it cost you nothing.