Search takeover

The search takeover replaces Shopify's native search with the same index that powers collections — and teaches it to read vehicles out of ordinary language.

Four behaviours#

Keyword search

typo-tolerant relevance across title, vendor, SKU, product type and your spec fields.

Autocomplete

suggestions as the shopper types, with product thumbnails, prices and fitment chips.

SKU redirect

a query that exactly matches one SKU goes straight to that product page instead of a one-result list.

Vehicle detection

"f150 6 inch lift kit" resolves the F-150, sets it as the active vehicle, and searches the rest.

That last one is the difference people notice. Shoppers type their vehicle into search boxes whether or not the box was designed for it; detecting it turns a zero-result query into the right result.

Placement#

Two parts, and you usually want both:

1. The results template — add the WySync search block to your /search template in place of the theme's results section.
2. The autocomplete embed — the app embed that attaches to your theme's existing search inputs, including the one inside a header drawer or dialog.

Settings#

• Placeholder copy
• Number of suggestions, and whether to show collections and pages alongside products
• Whether detected vehicles set the active vehicle automatically or offer a confirm chip
• Empty-state copy and the rescue behaviour

Zero results#

A query that matches nothing falls through a rescue ladder rather than dead-ending: relax the fitment filter, then relax filters, then offer popular products for the active vehicle. The shopper always sees something buyable, and the query is still recorded as zero-result in analytics so you can act on it.

What gets measured#

Search and autocomplete are counted separately — per-keystroke suggestions would otherwise swamp real search volume. Queries are scrubbed of anything that looks like an email address or phone number before they are stored, and nothing customer-identifying is ever recorded.