WooCommerce product search with Advanced Woo Search

Choose the search behaviour your shop needs

Advanced Woo Search by KramaKit adds AJAX product search to WooCommerce, so shoppers can see matching products as they type. Before installing it, write down three searches your customers need to make. For a parts shop, that could be a component name, its exact SKU and a material. For clothing, try a product name, a colour and a size.

That small list gives you a way to judge the finished setup. A result appearing in the dropdown is only half the job: opening it should take the shopper to the product they expected.

The official WordPress plugin listing separates the free and Pro features. These are the differences that matter for this guide:

Variable products also work with the free edition. The distinction is whether a search returns the parent product or displays each matching variation separately.

Set up your WooCommerce product search form

Use a staging copy of your shop for the first setup, with a recent backup available. This gives you somewhere to check the header, mobile menu and product links before changing the search your customers use.

1. In Plugins > Add New, search for Advanced Woo Search, then install and activate it.
2. Open Adv. Woo Search > General and run Reindex table. Wait for the initial index to finish.
3. Under Adv. Woo Search > Search Form, enable AJAX Search and save your settings.
4. Add the form using the plugin’s block, widget or [aws_search_form] shortcode. For a Pro form instance, use its supplied shortcode.
5. Open the page as a logged-out visitor and search for a published product by name.

KramaKit’s WooCommerce AJAX search guide explains these placement options. Its Seamless Integration setting can replace compatible theme search forms; check your actual header and mobile search rather than assuming every form has changed.

Make SKU searches useful for returning customers

A customer reordering a part may know its stock code but not its product name. Enable SKU in the plugin’s Search in settings, then try a complete code copied from a published product. KramaKit’s search sources documentation explains the available fields and their weighting controls.

For example, suppose a blue mug has the SKU MUG-BLU-350. Search for that full code and confirm the blue mug appears. Then try the product name. If unrelated descriptions dominate the results, review the enabled sources and give the title or SKU more weight before testing again.

Keep a separate test for a variation SKU. As the variable products documentation explains, a matching variation SKU can return the parent product. That is different from a separate result for the exact colour and size. Check the page a shopper lands on so your team knows what to expect.

Search colours, sizes and other attributes with Pro

Attribute searches need Advanced Woo Search Pro. They also depend on your product data: writing “cotton” in a description does not make it a material attribute. Check where you store the value before changing the search settings.

For global attributes, open Adv. Woo Search > Performance and find Data to index. Enable Attributes and select the fields you need using the adjacent settings control. Rebuild the index, then enable those attributes under Search Results > Search in.

Attributes added directly to individual products need the Custom product attributes selection too. KramaKit’s attribute search troubleshooting guide shows both settings and explains how result filters can hide a match.

Test one value at a time first. Search for a colour that belongs to a known product, then a size. Only after those work should you try combined phrases such as “blue large”. Record the expected results so you can spot a change when you adjust the search configuration.

Decide how to display product variations

A clothing shop with many colours and sizes needs a deliberate choice here. One result for the parent keeps the list shorter. Individual variation results can take the customer closer to a specific combination, but fill the dropdown with more entries.

Pro supports parent products, variations, or both. KramaKit’s product variations guide also describes links that open the parent page with the matching variation attributes selected.

Try this with a product containing several similar variations. Check the result title, image and price, then follow the link. Confirm the selected options match the result and that the item can be added to the basket. Repeat with an unavailable variation to check that the search respects the visibility and stock behaviour you intended.

Test the whole search journey before publishing

Keep your original sample searches and add a deliberately unmatched term. Run the same checks on desktop and a real phone, both logged in and logged out.

• Exact matches: a product name, a simple product SKU and a variation SKU each return the expected destination.
• Pro features: selected attribute values work and variations appear in the format you chose.
• Empty results: a nonsense term leaves the shopper with a clear message and a usable search field.
• Navigation: the dropdown remains usable in the mobile header and results can be reached with a keyboard.
• Product changes: after saving an edit, repeat the relevant search and check the result reflects it.

Save the search settings and your expected results alongside your shop’s update notes. After a theme, WooCommerce or search plugin update, repeat this small set of checks before signing off the release.

If a search does not behave as expected

Start with the product’s publication and visibility settings, the selected search fields and the index. For an attribute problem, check indexing and searching separately. If the form works on a simple test page but fails in the header, record that difference before changing anything else.

For Advanced Woo Search setup questions, use KramaKit’s support first. Send the plugin version, the exact search term, the expected product and a screenshot of the result. For a suspected conflict, reproduce it on staging rather than disabling extensions on a live shop.

If the issue spans your theme or other extensions, BugShield’s WooCommerce troubleshooting and bug fixes service can help investigate the wider problem. Once it is resolved, rerun the same searches to confirm the fix.