Test your shop search with the words customers use, then fix the first failed match. Start with five products and fifteen searches. You’ll learn more from that small test than from installing another search plugin and hoping for the best.
You call it a “modular mobile workstation”. Your customer types “workbench on wheels”. Search returns nothing. The product is sitting in your warehouse, apparently waiting for someone to guess its official title.
This guide is about the search box inside your shop. It gives you a way to find the gap, choose the right fix and check that the result actually helps someone buy.
In this guide
Run the fifteen-search test
Choose five products that matter commercially: a regular seller, a product with a technical name, one with variations, an accessory and a recently added item. Use products you intend customers to find today.
For each product, write down its URL and three searches:
- The exact name or distinctive model: something copied from the product title. This is your control test.
- The customer’s description: words from an actual enquiry, call or existing search report. Without those, write a plausible phrase and mark it as a test idea.
- One awkward but relevant query: a SKU, common misspelling, alternative spelling or variant-specific phrase. Choose the one that matters for that product.
For a fictional workbench, that could be “Workshop Pro 1200”, “workbench on wheels” and “WP-1200”. For a bag, try its model name, “laptop backpack” and “15 inch backpack”—provided it actually fits that size.
Run the searches while logged out, using the search box a buyer sees. Check both the suggestions that appear as you type and the full results after pressing Enter. Record whether the intended product appears, where it appears and whether the link opens the correct page.
Repeat the important failures in the mobile header. A desktop search that works doesn’t rescue a mobile menu that hides the field or sends the same query somewhere else.
Read the failure before changing anything
| What you observe | What to check next |
|---|---|
| Even the exact name finds nothing | Publication status, catalogue visibility, search scope and any search index. Start here before rewriting copy. |
| The exact name works; everyday wording fails | Whether the wording occurs in a field your search reads. Then check synonyms or word matching. |
| The name works; the SKU fails | Whether this search includes SKU fields, including variation SKUs. An admin search result doesn’t prove the storefront supports it. |
| Typing suggestions work; pressing Enter fails | Whether the dropdown and results page use the same search system and product scope. |
| The right product is buried under accessories | Result relevance, title matching and weighting. More results are not automatically better results. |
| Desktop works; mobile fails | The mobile search control, submission destination and active filters. |
These are diagnostic routes. Confirm the cause with one failing query and its intended product before making a catalogue-wide change.
Check product visibility and search scope
Open the missing item under Products → All Products. Confirm it is published and inspect its Catalog visibility setting. WooCommerce distinguishes products visible in both the shop and search, the shop only, search only, or neither. A direct product link can work even when the product is excluded from search. WooCommerce documents these visibility states.
If the item is meant to be searchable, correct an accidental exclusion. Keep deliberate restrictions intact. Also check stock-related hiding and any active category or price filter in the customer’s search journey.
Next, establish what powers the search box. Ask your developer or check the block, theme feature or plugin that supplies it. A general site search, a product-only search and an extension’s live dropdown can behave differently.
WordPress’s standard text-search routine searches titles, excerpts and content by default. That doesn’t mean every product field is included. Your theme or search extension can change the behaviour, so don’t assume a SKU, attribute or tag becomes searchable just because you entered it in WooCommerce. WordPress: default search fields.
If your installed search tool maintains an index, check its status and follow that tool’s documented refresh process. After a bulk import, confirm the newly added product is included. Buying another extension is a rather expensive way to avoid checking the one already installed.
Fix the language gap without turning titles into keyword soup
If the exact-name test works, compare the failed customer phrase with the product’s visible name and description.
Use accurate everyday language where it helps a buyer. For example:
Before: Workshop Pro 1200 modular mobile workstation.
After: Workshop Pro 1200 workbench on wheels, with drawers for tools and small parts.
Keep the model name. Add the useful description. Check that wheels, drawers and intended use are true of the actual item.
Put one natural explanation in a field your search includes, save it and rerun the failed query. If it still fails, investigate the search configuration instead of repeating the phrase six more times.
For genuine equivalents such as “trolley” and “cart”, use a synonym feature if your search system provides one. Keep mappings narrow. “Laptop bag” and “backpack” overlap, but they are not interchangeable across an entire range. Search should find suitable alternatives, not confidently introduce the wrong product.
Don’t add misspellings to polished product titles. Common typos belong in search matching rules. Don’t promise that every size or material matches a variation unless the selected product really offers it.
Know when better search earns its keep
A search upgrade is justified when your test exposes a capability customers need and the current setup cannot supply it. Write the requirement in plain English:
- “A customer can paste a variation SKU and reach its parent product with that option clearly identifiable.”
- “Our common customer term finds the same relevant range as our catalogue term.”
- “The full results remain consistent with the typing suggestions.”
- “We can inspect searches that returned no products.”
Then test candidate tools against the same queries. Check whether the required feature is in the edition you would actually use. A feature list for the most expensive plan is not a promise about the free one.
Our recommendation: fix visibility and useful product wording first. Upgrade when you can name the remaining failure and demonstrate that the new tool fixes it.
Rick’s pick: FiboSearch, used on Storak
For a small WooCommerce shop that needs live suggestions and product-code search, start with FiboSearch’s free version. It is Rick Edwards’s preferred search plugin, and he uses it on his own shop, Storak.dk. He finds it effective, likes the customisation options and how well it integrates with WordPress themes. Another big reason: customers can search by product SKU.
That matters when a returning buyer already has the code from an earlier order. They should be able to paste it into search and find the item. Making them remember your carefully crafted product title is asking rather a lot.
The free version searches product titles, descriptions and product SKUs, and can show images and prices as people type. A free edition is available at publication, 13 September 2026. Variation SKU search, typo tolerance and synonyms are Pro features. Choose the edition against the searches your customers need. FiboSearch’s official plugin listing and feature breakdown.
A real example: finding a tool trolley
On Storak, we typed værktøjsvogn—Danish for “tool trolley”—into the header search. The live suggestions included Værktøjsvogn med lås – 400L – 600kg and STRONG mobil værktøjsvogn / tool carrier, with product images and prices. That gives the buyer useful clues before opening either page.
Try the same exercise with a product in your own shop: its everyday name first, then its actual SKU. Record both results in the worksheet below. This turns “the search looks nicer” into a concrete check that customers can reach the right product.
Set it up and check the result
- Install and activate FiboSearch – Ajax Search for WooCommerce, then open WooCommerce → FiboSearch.
- Add its search bar using the supported theme integration, a FiboSearch block or the
[fibosearch]shortcode. Use it where shoppers already expect search. - Enable product SKU searching and show images and prices in suggestions. Adjust colours, labels and the suggestion limit to fit your shop.
- Copy a product’s actual SKU from its WooCommerce product record. Paste it into the storefront search while logged out. Check the suggestion and the result after pressing Enter.
- Repeat on your phone. The field, suggestions and destination all need to work with a thumb and an on-screen keyboard.
Keep your fifteen test searches and rerun them after setup. A better-looking dropdown earns its place when it helps people find what you sell.
Copy the test sheet
Use one entry per query. Keep the original result so you can tell whether the change helped.
Date and device: Search box used: [header / mobile menu / category] Intended product URL: Query typed: Query source: [customer enquiry / report / test idea] Typing suggestions: [correct product / wrong products / none] Full results: [correct product and position / wrong products / none] Active filters: Suspected cause: One change made: Retest result: Owner and next action:
Give a developer the failing query, the expected URL and what happens in both search states. “Search is rubbish” is understandable feedback. It is less useful as a repair brief.
Give an empty result a useful next step
Sometimes you genuinely don’t sell what someone wants. The empty-results page should still help them move on.
Keep the query visible and editable. Offer a link to relevant categories and a clear route to ask for help. If filters caused the empty result, make resetting them easy. Avoid silently replacing a precise search with a wall of unrelated bestsellers.
No products found for “[search term]”. Try a shorter product name or check the model number. You can also browse our categories or ask us for help finding the right item.
Add a “search by product code” instruction only after your SKU test passes.
Finish today by fixing one important failed query and rerunning all fifteen. Keep that list for the next import, theme update or search change. A working search box should understand the customer well enough to get them to the right shelf.