Ajax Search Lite plugin review and common issues

Disappearing dropdowns indicate a JavaScript conflict or CSS positioning issue. Check: (1) browser DevTools Console for JavaScript errors during search; (2) the results container may be getting a CSS display:none applied by theme styles — inspect the dropdown element in DevTools when it appears briefly to identify conflicting CSS; (3) an event listener on the document (from another plugin or theme) may be closing the dropdown on mousedown — temporarily disable other plugins to identify the conflict; (4) verify Ajax Search Lite is updated to the latest version — some historical versions had dropdown timing bugs.

In Ajax Search Lite → Settings, find the thumbnail/image settings. Enable thumbnail display and set the thumbnail size. Thumbnails display the WordPress featured image (post thumbnail) for each result. If posts do not have featured images set, results appear without images — this is expected behavior. For posts without featured images, Ajax Search Lite can be configured to show a default fallback image (set the fallback image URL in settings). Ensure the post thumbnail image sizes are registered and generated in WordPress.

In Ajax Search Lite → Settings → Sources tab (or Post Types section), check which content types are currently searched. Uncheck post types that should not appear in results (e.g., if showing only Blog Posts, uncheck Pages; if you have custom post types installed, ensure they are not inadvertently included). Also check the Category Restriction settings to exclude specific categories from results. Note that the free version has limited post type configuration compared to Ajax Search Pro — for more granular control over content sources, Ajax Search Pro or Ivory Search provide better options.

In Ajax Search Lite → Settings → General tab, there should be a “Custom class” or “Additional CSS class” field for the search container. Add your custom class name here (e.g., my-custom-search). This class is added to the outer search form container, allowing targeted CSS rules in your theme’s stylesheet: .my-custom-search .autocomplete-suggestions { background: #fff; } For deeper style customization, use Ajax Search Lite’s built-in color settings (Settings → Visual) to change the primary colors without custom CSS.

In Ajax Search Lite → Settings → Sources → Category Restriction, enable category filtering and select the categories to include in search results. Only posts from the specified categories will appear in the search dropdown. This is useful for a search form positioned within a specific site section — a search bar in a News section could be configured to show only News category posts, while the main header search shows all content.

Yes — Ajax Search Lite’s live search dropdown is a meaningful UX improvement over the default WordPress search for almost any site. The default search requires submitting a form and loading a new page to see results. Ajax Search Lite shows results instantly as you type, with thumbnails and excerpts, in a dropdown. This faster feedback loop reduces search abandonment and helps visitors find content more quickly. For sites where even basic visitor experience matters, the zero-cost upgrade from default search to Ajax Search Lite is worthwhile.

Ajax Search Lite does not natively include WooCommerce products in its search results in the free version. WooCommerce products require the paid Ajax Search Pro version, or dedicated WooCommerce search plugins like FiboSearch (free version available). For stores where product search is the primary use case, FiboSearch is the better free option as it is purpose-built for WooCommerce product discovery.

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.