Ajax Search Pro plugin review and common issues

The results overlay z-index competes with your theme’s header, navigation, and other positioned elements. Go to Ajax Search Pro → Settings → Visual tab → Results → z-index. Increase the z-index value (try 99999) until the results appear above all other elements. If the theme’s header has a higher z-index than this value, inspect the header’s CSS z-index in DevTools and set Ajax Search Pro’s z-index higher. For sticky headers with very high z-index values, you may need to set 999999 or use position:relative on the results container.

Go to Ajax Search Pro → Settings → Sources tab. Ensure “Products” (WooCommerce product post type) is added as a search source. Configure product-specific display settings in the Results → WooCommerce section: enable product image display, price display, and add-to-cart button. Also verify the product status filter includes “publish” status. If products are still missing from results, check if WooCommerce products are set as “private” or have restricted visibility settings that exclude them from standard WordPress queries.

Ajax Search Pro has mobile-specific configuration options. Go to Settings → General → Mobile Settings. Configure the mobile breakpoint width (px), and whether to use fullscreen mode on mobile (recommended for better UX on small screens). In fullscreen mode, the search overlay takes the full viewport when activated — this avoids overflow and clipping issues. Also check the search bar’s CSS width settings for mobile breakpoints — a fixed pixel width may overflow on small devices. Use percentage-based widths for mobile-responsive behavior.

Go to Ajax Search Pro → Themes tab. Select a preset theme from the visual theme selector — each preset shows a preview. Click “Apply Theme” to apply the selected design as a starting point. After applying, go to the Visual tab to customize individual color elements: search bar background, border, text color, button color, results overlay background, result item hover color, and highlight color for matched text. All changes preview in real time in the backend. Save to apply to the frontend search form.

Go to Ajax Search Pro → Settings → General → Statistics. Enable “Google Analytics event tracking” and select the GA event format (GA4 or Universal Analytics). The plugin sends a custom event to Google Analytics each time a search is performed, with the search term as the event label. In your GA4 property, you can then view search events in Events report to see what users are searching for on your site. This provides the search analytics functionality without a separate analytics configuration.

Ajax Search Lite is a free, feature-limited version of Ajax Search Pro designed for basic live search on posts and pages. It provides real-time results but with minimal visual customization, limited content type support (no WooCommerce, BuddyPress, or user search), and no theme editor. Ajax Search Pro provides the full visual theme editor, all content type coverage, advanced layout options, Google Analytics integration, and priority support. For sites where the search bar appearance needs to match a designed aesthetic, Pro is necessary. For sites needing only basic live search functionality, Lite is adequate.

Ajax Search Pro searches the WordPress media library as a content source (finding attachments by title, description, and caption), but does not extract and index text content from within PDF files. For searching within PDF document text, SearchWP Pro (with its PDF indexer extension) or Relevanssi Premium are the appropriate solutions. Ajax Search Pro can then be used as the visual search interface layer while a plugin like SearchWP handles the backend content indexing.

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.