
Default WordPress search only matches keywords. If the words a visitor types
don’t literally appear in a post, they get “nothing found”, even when your site
has exactly the right page.
SmartMatch Search looks at what the visitor means instead. It puts the best
matching page at the top of the normal search results, marked as the best
match. Visitors can search the way they talk:
It also leaves out results that only share a word with the query: a post
isn’t suggested just because the search term shows up in it somewhere.
The normal search results stay where they are. SmartMatch Search only adds a
suggestion above them. If nothing relevant is found, or the AI is unavailable,
visitors see the normal results as before. When the normal search finds
nothing, the suggestion becomes the result, so visitors don’t hit an empty
page.
It works with your existing search form and theme, both classic and block
themes. You don’t need a new template or shortcode.
Every AI search costs you a small amount at your AI provider, so you want to
spend that on people, not bots. This is why SmartMatch Search works together
with Burst Statistics. Burst already filters bots, crawlers and spam out of
your visits. SmartMatch Search only uses the AI for visits Burst has counted as
human. Bots get the normal search results and cost you nothing.
Logged-in users always get the AI search, even without a Burst visit, for
example when Burst doesn’t track their user role. A logged-in user is never
a bot.
Costs are also limited by:
Searches show up in the Engagement tab of your Burst dashboard. You see what
visitors search for, and where your content doesn’t answer their questions yet.
SmartMatch Search does not connect to any service of its own and sends no data
to Burst or SmartMatch servers. When a search needs an AI answer, the search
term and the candidate posts (post ID, post type, title, URL path and a short
excerpt of public, published content) are sent to the AI provider that you
configured in the WordPress AI plugin. Which provider that is depends entirely
on your configuration there, and its terms of service and privacy policy apply
to those requests. This only happens for validated human visits, within the
daily budget, and only when the answer isn’t already cached. No IP addresses or
visitor identifiers are included in these requests.