FiboSearch plugin review and common issues

FiboSearch automatically replaces the default WooCommerce search widget. Check: (1) FiboSearch is active in WordPress → Plugins; (2) the search bar on your site uses the standard WooCommerce search form (role=”search” with input name=”s”) — custom search bars may not be detected; (3) check browser DevTools Console for JavaScript errors preventing FiboSearch initialization; (4) in FiboSearch → Settings → Search Trigger, verify the CSS selector configured matches your theme’s search input element; (5) clear all caches after plugin activation — cached pages may not load FiboSearch’s JavaScript.

FiboSearch builds its own search index for performance. If a product is missing from results: (1) go to FiboSearch → Settings → Indexing → Re-index Products to rebuild the index from current WooCommerce product data; (2) verify the product is “Published” — draft, pending, and out-of-stock products may be excluded from search based on FiboSearch settings; (3) check FiboSearch → Settings → Exclude to verify the product is not specifically excluded; (4) for variable products, ensure the parent product or a specific variation has the searched text in its title or description.

FiboSearch includes performance optimization settings: (1) increase the search debounce delay in FiboSearch → Settings → Performance — the default triggers a search after a short pause, but increasing it reduces API calls on fast typists; (2) reduce the number of results displayed in the dropdown; (3) enable FiboSearch’s caching to cache common search queries; (4) ensure your hosting server has adequate resources — live search AJAX calls hit the server for each query; (5) upgrading to FiboSearch Pro provides an optimized indexing structure specifically designed for large catalogs.

In FiboSearch → Settings → Fields, enable “SKU” as a displayed field in the search results dropdown. Also enable “Search by SKU” in the Search In settings so that entering a SKU number finds the matching product. With both settings enabled, B2B customers can type a product code and see the matching product with its SKU, name, and price immediately in the live dropdown — a critical workflow for B2B and trade stores where buyers order by product code.

FiboSearch provides CSS customization options in Settings → Appearance. Basic color settings (background, text, highlight, border colors) can be adjusted through the settings panel without CSS knowledge. For deeper styling, FiboSearch outputs specific CSS classes on the dropdown container and result items — add custom CSS in Appearance → Customize → Additional CSS or your theme’s custom CSS field targeting the FiboSearch-specific class names. The FiboSearch documentation lists all CSS classes for the dropdown, result items, thumbnail, price, and SKU elements.

FiboSearch and SearchWP serve complementary roles. FiboSearch specializes in the live search dropdown UX — the instant product results popup as you type. SearchWP specializes in improving the relevance of the full search results page. Many professional WooCommerce stores use both: FiboSearch for the live search experience (quick product discovery), SearchWP for the search results page (better relevance ranking). FiboSearch alone is sufficient for stores where most customers find what they need from the live dropdown without needing to visit the search results page.

Yes — FiboSearch indexes WooCommerce variable products and can search within product variations. Configuring variation search allows customers to find products by searching for a specific color, size, or other variation attribute. In FiboSearch → Settings → Fields, enable variation attribute search. The search dropdown shows the parent variable product when variation attributes match, allowing the customer to click through to the product page to select their specific variation.

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.