SearchWP plugin review and common issues

A missing or stale index is the most common cause of zero results. Go to SearchWP → Settings → Index tab and check the index status — it should show all content types as fully indexed. If indexing is incomplete or stale, click “Rebuild Index” to reindex all content from scratch. On large sites, indexing may take several minutes or longer. If rebuilding does not fix results: (1) verify the search engine is configured to include the content type being searched; (2) check that the tested search term is actually in the indexed content (SearchWP only returns results for content it has indexed); (3) confirm SearchWP is set as the default search engine in Settings → Advanced.

Go to SearchWP → Settings → [engine name] → Sources. Each indexed source (post title, content, custom fields, etc.) has a weight value — higher weights make that source more influential in ranking. If product SKU matches rank lower than general content matches: increase the weight of the SKU attribute source. If post titles are not ranking high enough: increase the Post Title weight. Changes take effect immediately without reindexing. Common tuning: Post Title weight 20+, Post Content weight 5-10, Custom Fields weight 3-8 depending on their relevance to the search context.

PDF indexing requires: (1) the PDF Indexer extension is included with SearchWP Pro or available as an add-on; (2) your PHP installation has the required libraries for PDF text extraction (typically pdftotext via the exec() function or a PHP PDF library); (3) go to SearchWP → Settings → [engine] → Sources and add “PDF Attachments” as an indexed source with an appropriate weight; (4) rebuild the index to process existing PDFs. If PDFs still do not index, check that PHP exec() is available on your hosting environment — some shared hosts disable it. The SearchWP debug mode shows indexing status per document.

With SearchWP Pro: go to SearchWP → Settings → [engine] → Sources → Add Source → Products (WooCommerce product post type). Add the following sources: Product Title (weight 20), Product Content/Description (weight 10), Product Short Description (weight 8), and Custom Fields — specifically the _sku meta key (weight 15 for strong SKU matching). Rebuild the index. Now a search for a product’s SKU number returns that product as the top result. Add product categories and tags as indexed taxonomy sources for category-based search.

SearchWP Pro logs every search query and whether it returned results. Go to SearchWP → Statistics to view the most-searched terms and their result counts. Searches with zero results (“no results” searches) indicate content gaps — topics users are looking for that do not exist on the site. Export the no-results list to identify which new content to create. High-volume searches with low click-through on results indicate poor relevance for those terms — adjust the weight configuration or add synonyms to improve results for those queries.

Both are excellent WordPress search replacements with different strengths. SearchWP excels at configuration depth — per-source weighting, WooCommerce product attribute search, live Ajax search, and search analytics make it the more complete commercial solution. Relevanssi excels at relevance algorithm quality and is beloved by content-heavy sites (blogs, news sites, documentation) where its TF-IDF based relevance scoring and extensive filtering hooks provide academic-level search quality. SearchWP is the stronger choice for WooCommerce stores and sites needing custom field indexing; Relevanssi is the stronger choice for content-rich sites where search result relevance quality is the primary concern.

Yes — once SearchWP is configured and set as the default engine, all existing WordPress search widgets, search blocks, and theme search forms automatically use SearchWP’s engine instead of the default WordPress search. No theme or template modifications are needed for the basic integration. SearchWP also provides its own search form widget and shortcode for placing custom search forms anywhere on the site.

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.