PrestaShop Search: Easy Guide to Aliases, Indexing, and Weights

A weak PrestaShop search box wastes traffic: shoppers type a product name, see empty or odd results, and leave. Most of the fix lives in Shop Parameters → Search – aliases for typos, a complete index, fuzzy matching, and field weights. This guide walks through those settings in the order that usually improves findability first.

Open your Back Office and go to Shop Parameters → Search. You land on Search parameters (indexing, options, weights) plus tabs for Aliases and Tags. The same screen exists from PrestaShop 1.7 onward, including 8 and 9 – labels may shift slightly, but the ideas below still apply.

Index the catalog before you tune PrestaShop search

Search only returns products that sit in the search index. On the Search page, compare indexed products with the size of your catalog. If they disagree:

• Add missing products to the index – faster; only new or never-indexed items.
• Re-build the entire index – slower but thorough after bulk edits, imports, or weird result gaps.

Turn Indexing on so saves and updates refresh the index automatically. If you prefer not to index on every product save (large catalogs, slow hosts), leave auto-indexing off and schedule the cron URL PrestaShop shows on that same block. After a CSV import or mass update, check the counters again before you blame aliases or weights.

Aliases: map typos to the real term

Aliases tell PrestaShop search what shoppers meant. If people type sneker, point that alias at sneaker so the right products still appear.

Do not invent aliases from scratch. Open Stats → Shop search (or the Shop search stats tab in your version) and note frequent queries with zero or weak results. Add those misspellings on the Aliases tab: alias word(s) → result word. Several aliases can share one result. Save and retest the storefront search bar in a private window.

Search options: length, blacklist, and fuzzy matching

These toggles change how a PrestaShop search query is matched against the index:

• Search within word – matches inside a word (e.g. lou finds blouse), not only from the start.
• Search exact end match – requires the end of the word to match (e.g. book can match notebook but not bookcase).
• Fuzzy search – tolerates small spelling mistakes (e.g. ummingbird → hummingbird). Available from PrestaShop 1.7.7 onward.
• Maximum approximate words (fuzzy) – how many query words go through fuzzy logic (default often 4). Raising it costs more CPU on large catalogs.
• Maximum word length – characters considered for fuzzy work; docs often suggest around 15 for speed.
• Minimum word length – words shorter than this stay out of the index (helps skip a, of, and similar noise).
• Blacklisted words – pipe-separated list (|) of terms that must never match. PrestaShop ships a default list of common short words.

Start conservative: enable fuzzy if misspellings are common, keep max word length near the documented default, and only widen “within word” if short partial queries matter for your catalog. Official option descriptions live in the PrestaShop 9 search parameters docs.

Weights: decide which fields rank higher

Weights tell PrestaShop search how much each field counts when scoring results. A field with weight 8 counts four times as much as one with weight 2. Defaults usually favor the product name (often around 6) over tags (around 4) and descriptions (around 1) – so a name hit outranks a buried mention in the long description.

You can weight short description, category, tags, attributes, and related fields. On a small catalog the change can look subtle; on a large one, raising name/reference and lowering noisy description weight often cleans the first page of results. Save, then search for a known SKU and a vague keyword to confirm the order feels right.

Performance, tags, and when native search is not enough

Fuzzy matching, long max word length, and “search within word” all cost more on big indexes. If PrestaShop search feels slow after you open those options, tighten fuzzy limits or move heavy reindex work to cron off-peak hours.

Product tags still feed the index (and have their own weight). Manage them on the Tags tab or on each product. For heavier tag workflows you can use a dedicated module such as Ultimate Product Tags – tags help discovery, but they do not replace a healthy index or sensible aliases.

If native PrestaShop search still struggles on a very large catalog, look at a dedicated engine. Our companion note on using Sphinx search in PrestaShop covers that path. Pair better on-site search with crawl hygiene too – a clear PrestaShop sitemap helps Google find products even when shoppers use the site search bar first.

Quick checklist

1. Confirm indexed product count matches (or nearly matches) the catalog; rebuild or add missing items if not.
2. Enable auto-indexing or set the cron URL your host supports.
3. Pull frequent typos from Shop search stats and add aliases.
4. Tune fuzzy / within-word / lengths only as needed; watch server load.
5. Adjust weights so name and reference beat weak description matches.
6. Retest 5 to 10 real queries from Stats after each change.