WordPress Search Plugins: Relevanssi, Ajax Search Lite, and Ivory Search
Compare Relevanssi for relevance and indexing controls, Ajax Search Lite for results while typing, and Ivory Search for forms with different content scopes. Changing a search box and improving what it finds are separate tasks. Start with actual reader queries and the articles that should appear, then identify missing content, poor ranking, or difficult interaction.
Diagnose the search problem before changing the box
Internal site search helps someone already visiting your website find material. It is different from appearing in Google results: installing an internal search plugin does not establish improved search-engine indexing or rankings.
If an article never appears, investigate content scope and indexing. If it appears too far down, investigate relevance and ordering. If useful results are hard to use, examine placement, keyboard access, and mobile behavior. A product-only search and a whole-blog search also serve different purposes; label the scope clearly.
An index organizes searchable words and their connections to content in advance. A tool using an index may require selecting content and building that index in addition to inserting a form. Review the plugin selection and installation guide, prepare a test environment and a recoverable backup, and identify existing theme or plugin search features.
Compare Relevanssi, Ajax Search Lite, and Ivory Search
| Candidate | Main purpose | Free features to assess | Additional requirements |
|---|---|---|---|
| Relevanssi | Indexing and relevance | Relevance ordering, basic weights, partial matching, query logs | Attachment-content indexing requires Premium; separate database space |
| Ajax Search Lite | Results while typing | Content and field selection, basic filters, form placement | Compare Pro for separately configured search bars, advanced filters, and file-content search |
| Ivory Search | Forms with distinct scopes | Multiple forms, basic inclusions/exclusions, menu placement, AJAX | SKU and variation search, some ordering and exclusions require Premium |
Relevanssi: verify the index before adjusting relevance
Relevanssi generally uses the standard WordPress form and results template to change retrieval behavior. It is not primarily a tool for decorating the search field. Choose post types and fields, save the configuration, and build the index.
Find Indexing in the Relevanssi settings. Older instructions use Settings → Relevanssi; the current official Premium guide follows Relevanssi → Settings. Check the edition and interface in the installation and settings guide. Build the index rebuilds the existing index using saved rules. Index unindexed posts adds missing posts; it does not refresh every previously indexed document.
The separate index consumes database space and takes processing time to build. Check hosting capacity and job limits before adoption; do not repeatedly rebuild simply because there are too few matches. PDF and Office document-content indexing and improved spelling correction are Premium features. Finding an attachment by its title is different from searching sentences inside the file.
Ajax Search Lite: test retrieval as well as live display
AJAX requests data to update part of a page without reloading the whole page. Ajax Search Lite uses this approach to show results while visitors type. A responsive animation does not establish a fast response or relevant results.
Under Ajax Search Lite → General Options → Sources & Basics, select post types and fields such as title, content, excerpt, or custom fields. The official scope guide says password-protected published posts are returned by default. Turn off that display where inappropriate and verify while logged out, rather than assuming default visibility is suitable for restricted material.
Use its block, widget, or documented search shortcode for placement. To try it in a post or page, place [wpdreams_ajaxsearchlite] in a Shortcode block and inspect the result. Compare Pro for multiple independently configured search bars, advanced filters, and attachment-content searching. Do not assume it automatically uses another plugin’s index.
Ivory Search: connect each configured form to its placement
In Ivory Search, create or duplicate a form and review Search, Exclude, Design, AJAX, and Options. A whole-site form and a focused collection form can use different content and exclusion rules. Save the form, then place its shortcode where that specific search should be available.
The official usage guide distinguishes form controls from overall settings. For menu placement, use Ivory Search → Settings → Menu Search and choose the menu and associated form. The menu placement instructions require a menu assigned to a theme menu location; merely creating a menu is not the same as displaying it.
Multiple forms and AJAX are available without buying every advanced option. The official listing marks SKU and variation search and certain detailed ordering/exclusion controls as Premium. Searching image or attachment titles and descriptions should not be treated as equivalent to searching PDF body text.
Test short queries and different languages separately
Relevanssi’s default minimum indexed word length is three characters. A two-character query such as “AI” or the Korean “백업” may behave differently from longer words. Use the search troubleshooting checklist to inspect length, stopwords, punctuation handling, and index completeness. Save changes to indexing rules and rebuild when necessary to apply them to existing content.
Partial matching finds character sequences; it does not establish understanding of meaning or every grammatical form. The official language explanation describes limitations in word segmentation and relevance for Japanese and Chinese text without word-separating spaces. Test Korean spacing and suffixes against actual material too. Successful English retrieval does not verify other language editions.
Build a test list using real articles and expected results. The following examples illustrate the checks; they are not reported measurements of a particular installation.
| Test query | Expected check |
|---|---|
| AI / AI writing | Check short-word indexing and multiword behavior |
| WordPress / 워드프레스 | Test both spellings rather than assuming automatic synonyms |
| A Japanese query used on your site | Relevant Japanese articles and useful ordering |
| Unknown word / empty input | Clear no-results and empty-query behavior |
| A unique phrase in a protected test article | No inappropriate title, snippet, or live-result disclosure while logged out |
Verify results, exposure, and recovery after adoption
- Record the baseline. Pair representative queries with articles that should appear and content that must be excluded. Preserve settings and form positions, and test one tool at a time.
- Configure scope and indexing. Include necessary public content and fields. Do not add every custom field without checking whether it contains sensitive internal data.
- Compare each search route. Admin search, public search, and a theme’s live header search may use different engines. Try the same query in each and open the destinations.
- Use keyboard and mobile controls. Reach the form with Tab and check the relevant arrow-key, Enter, and Esc behavior. Results should remain usable without being clipped or hidden behind menus and ads.
- Verify updates and exclusions. Edit a test article and confirm results and snippets update, then restore it. While logged out, inspect protected titles, excerpts, and file URLs as well as the final destination.
Search exclusion is not an access-control system. A members-only file also needs appropriate restrictions when its direct URL is opened. If query logging is enabled, set access and retention rules with the possibility of readers entering contact or other personal information in mind.
If admin search finds a document but public search does not, check whether that form actually uses the intended engine. For slow responses, compare the same query and device, separating initial and repeated requests, then narrow scope and result count to identify the cause. Do not confuse page caching with search-index updates.
To undo adoption, restore the previous blocks, shortcodes, and menu-form association, deactivate the new plugin, and verify default search. Deletion can remove settings, indexes, or logs, so distinguish it from deactivation and check the official removal instructions and backup first. Prefer a configuration that helps readers find the right explanation over one producing the most matches or the flashiest dropdown.




