Skip to main content

The algorithms of our site search feature

In this article, we explain to you the algorithms being used by our Search feature.

Thomas Ta avatar
Written by Thomas Ta
Updated today

📖 Site search matches customer keywords to your product catalog. With Boost AI Search & Discovery, your store uses an advanced relevance algorithm that delivers smarter, more accurate results—well beyond a basic search bar.


How our site search features work

Boost matches your customers’ queries to your store data and ranks results by relevance.

Searchable content

  • Products: title, product type, vendor, tags, options, SKU, barcode, and description (off by default).

    • Typo tolerance applies to: title, product type, vendor.

  • Collections, articles, and pages: title only by default. Indexing full content requires additional setup.

Variant images & color

⚠️ Variant image selection recognizes only common color terms (e.g., black, blue, red, white, gray). If you use a custom color name (e.g., “neon”), search results still show the product, but the first product image (from Shopify) is used instead of a color‑matched variant.

Search intelligence

  • Synonyms and a Suggestion Dictionary refine and normalize queries to improve relevance.


Customize search fields

Tune speed and relevance by choosing which fields to search—and in what order.

  • Enable/disable fields you don’t want the engine to scan.

  • Reorder fields to set priority; higher‑priority fields influence ranking first.

  • Optionally enable the product description field if it’s important to your shoppers.

To customize your searchable attributes:

  1. From the app’s admin, go to Search > Standard search.

  2. Go to the Relevance settings tab.

  3. Toggle ON/OFF the searchable attributes and adjust their priority level individually.

  4. Click Save settings.

💡 To enable the Metafields search field, follow this article.


Feel free to reach out to our dedicated support team via chat if you have any questions or require additional assistance.

Did this answer your question?