Relevanssi plugin review and common issues

Go to Relevanssi → Searching tab and enable “Keyword indexing debugging” temporarily. Perform the failing search and note the debug output showing which posts were considered and their scores. Common causes of missing results: (1) the post’s content was not indexed — go to Relevanssi → Indexing and check index completeness, then rebuild if necessary; (2) the post type is excluded from search — verify the post type is enabled in Relevanssi → Indexing → Indexed post types; (3) the search term is in a stopword list — check Relevanssi → Stopwords for terms that may have been added incorrectly; (4) the post status is not “publish” — Relevanssi only indexes published posts by default.

Relevanssi highlighting requires the theme to use Relevanssi’s custom excerpt function. Go to Relevanssi → Excerpts and Highlights and enable both “Highlight in Excerpts” and “Highlight in Posts.” If highlighting works in excerpts but not in full post content when users click through to the post: the theme must call the_content() through the Relevanssi content filter, which is standard WordPress behavior — if your theme uses custom content display functions that bypass the_content() filter, highlighting will not apply. For excerpt highlighting, the theme must use get_the_excerpt() or the_excerpt() rather than custom excerpt generation.

The Relevanssi index table grows with site content volume. Reduce index size by: (1) exclude post types you do not want in search results from Relevanssi → Indexing → Indexed post types; (2) add common words (the, and, is, a, etc.) to the stopwords list — Relevanssi → Stopwords — these words add index entries without improving result quality; (3) reduce the maximum number of terms stored per post in the configuration; (4) if certain custom fields are indexed but not needed for search, remove them from the indexed fields list. After changes, rebuild the index to apply exclusions retroactively.

Post pinning requires Relevanssi Premium. Go to the edit screen of the post you want to pin. In the Relevanssi meta box (added to the post editor by Premium), add the keywords for which this post should appear first in results. Enter one keyword per line. When a user searches for any of those keywords, this post appears as the first result regardless of its relevance score. This is useful for ensuring a key landing page or documentation article always appears first for specific important queries.

In Relevanssi → Indexing → Custom Fields, add _sku (the WooCommerce product SKU meta key) to the list of custom fields to index. Assign it a weight value — a higher weight (e.g., 5-10) ensures SKU matches rank highly. Rebuild the index. After indexing, searching for a product’s SKU number returns that product prominently in results. Relevanssi Premium adds full WooCommerce variation indexing — each product variation’s attributes are individually indexed, enabling attribute-specific searches (e.g., searching for a specific color SKU).

Yes — Relevanssi free improves WooCommerce product search relevance for product titles, descriptions, and indexed custom fields. Relevanssi Premium adds indexing of product variation attributes and SKUs, making it a comprehensive WooCommerce search solution. For stores that need live Ajax search dropdown (showing product images and prices as you type), pair Relevanssi with FiboSearch or a dedicated live search plugin — Relevanssi handles relevance ranking while the live search plugin handles the frontend UX.

Yes — Relevanssi works with WPML, Polylang, and TranslatePress for multilingual sites. It indexes content in all languages and respects the active language filter, returning results in the current site language only. For multilingual search, configure each language’s stopwords separately in Relevanssi settings and rebuild the index. The Premium version has tested compatibility with major multilingual plugins. Some configuration adjustments may be needed depending on how your multilingual plugin structures content.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.