100 Days of Elasticsearch & Woocommerce guides for WordPress & WooCommerce

Using Synonyms Without Reindexing Products

Synonyms are often introduced as an indexing feature, but WooCommerce agencies can usually add or change customer-facing synonyms without reindexing product documents. The key is to apply the synonym rules in a search-time analyzer rather than the index-time analyzer. Why search-time synonyms avoid product reindexing Elasticsearch stores the analyzed terms produced when a product is indexed. If synonyms are applied during indexing, changing the synonym list changes the terms that should have been stored, so existing products must be reindexed. With search-time synonyms, the product index remains unchanged. Elasticsearch analyzes the shopper’s query, expands or replaces the query terms, and searches the existing terms. This is useful for catalog teams that regularly add vocabulary such as: tv and television mobile phone and smartphone sneakers and

Multi-Word Synonyms in Elasticsearch

WooCommerce shoppers rarely use the exact vocabulary stored in a product catalog. A customer may search for tee shirt when the product title contains t-shirt, or search for trainers when the catalog uses running shoes. Single-word synonym filters can handle simple substitutions, but multi-word alternatives require Elasticsearch’s token graph support. For product search, the preferred approach is to apply a synonym_graph filter in the search analyzer. This preserves the relationships between multiple tokens and allows Elasticsearch to build correct phrase queries and relevance calculations. Why Multi-Word Synonyms Need a Token Graph A multi-word synonym changes the number and position of tokens in a query. For example, the query tee shirt contains two tokens, while the catalog term t-shirt may be represented as one token. A

Synonyms for Brands, Products and Categories

WooCommerce search often fails for reasons that have little to do with relevance scoring. Customers may search for a brand’s abbreviated name, an alternative product name, or a category term that differs from the wording stored in the catalogue. Elasticsearch synonyms can bridge those differences, but only when they are designed around the way the catalogue and shoppers actually use language. Where synonyms fit in a WooCommerce search architecture A synonym is a relationship between two or more terms that should be treated as equivalent, or as related in a specific direction. For example, a store might want hp to match hewlett packard, or trainers to match sneakers. Synonyms are applied by an Elasticsearch analyzer. The analyzer may be used when indexing product fields, when

Stop Words: Should WooCommerce Search Ignore Them?

Stop words are common terms such as the, and, for, with, and of. In a WooCommerce catalog, they can appear frequently in product names, attributes, categories, and descriptions. Whether Elasticsearch should ignore them depends on the type of search, the fields involved, and how customers use product language. What stop-word removal changes Elasticsearch applies analysis when text is indexed and, separately, when a search query is analyzed. A stop filter removes configured terms from the token stream. For example, the phrase shoes for running might become shoes and running. Stop-word removal can reduce index size and prevent common words from affecting relevance. It can also make searches more forgiving when customers include natural-language phrasing. However, it removes information that can be meaningful in a product

Search-Time vs Index-Time Analysis

In WooCommerce search, analysis determines how product text is converted into terms that Elasticsearch can store and match. The two important moments are index time, when a document is written to the index, and search time, when a user query is analyzed before matching. Designing these stages deliberately is essential for product names, descriptions, SKUs, attributes, and multilingual catalogs. What index-time analysis does Index-time analysis processes a field before its terms are placed in the inverted index. A typical analyzer performs character filtering, tokenization, and token filtering. For example, the text Waterproof Running Shoes might be converted into the terms waterproof, running, and shoes. Index-time analysis affects what terms are available for future searches. If a transformation removes or changes information, Elasticsearch cannot recover that

Custom Analyzers for Product Catalogs

Search quality in a WooCommerce catalog depends heavily on how product text is analyzed at index time and query time. The default analyzer is a useful starting point, but agencies often need different behavior for product names, descriptions, brand names, SKUs, and merchandising terms. What an analyzer does An Elasticsearch analyzer converts text into the terms that are stored in the inverted index. An analyzer can contain three stages: Character filters: Modify the original text before tokenization, such as removing HTML markup or replacing selected characters. Tokenizer: Splits the resulting text into tokens. Token filters: Normalize or transform tokens, for example by lowercasing, removing stop words, applying stemming, or generating autocomplete prefixes. For example, the product name Men’s Running-Shoes, Size 10 might be converted into

Lowercase, Stemming and WooCommerce Search

WooCommerce search quality depends heavily on how product text is analyzed before it is indexed and searched. Two small but important analysis steps are lowercasing and stemming. Lowercasing makes matching consistent across capitalization differences, while stemming can match related word forms such as shirt and shirts or running and run. These features are useful for product titles, descriptions, categories, and attributes, but they should be applied deliberately. An analyzer that is too aggressive can produce irrelevant results, especially for brand names, SKUs, model numbers, and technical terms. What lowercasing does The lowercase token filter converts alphabetic tokens to lowercase during analysis. For example: Women's Running Shoes can be indexed as tokens similar to: women's<br>running<br>shoes A search for RUNNING SHOES can then match the same indexed

How Elasticsearch Tokenizes Product Names

Product-name search quality depends heavily on how Elasticsearch turns text into tokens. A shopper may search for “men’s waterproof trail shoes”, while the catalog contains “Men’s Waterproof Trail Shoe – Black/Blue, Size 10”. Elasticsearch does not compare these values as raw strings. It analyzes the product name, creates tokens, and uses those tokens in the inverted index. What tokenization means Tokenization is the process of splitting a character sequence into searchable terms. An analyzer usually performs several stages: Character filters modify the original text before tokenization. A tokenizer identifies token boundaries. Token filters normalize or transform the generated tokens. For example, a product name such as Acme Trail-Shoe 2.0 / Women's might be converted into tokens such as acme, trail, shoe, 2.0, and women's, depending

Elasticsearch Analyzers Explained for WooCommerce

Search quality in a WooCommerce store depends on more than matching product titles against a query. Elasticsearch first converts text into searchable terms, and the rules used for that conversion are defined by analyzers. A well-designed analyzer can make searches tolerant of punctuation, capitalization, accents, plurals, and common product terminology without changing the data stored in WooCommerce. For agencies, analyzers are especially important when implementing product search across multiple stores. A suitable configuration must reflect the catalog’s language, SKU conventions, brand names, attributes, and customer search behavior. It must also be introduced safely because analyzer changes generally require a new index and reindexing. What an analyzer does An analyzer is a processing pipeline used for full-text fields. It normally contains three stages: Character filters modify

Minimum Should Match for Smarter Queries

WooCommerce product search often combines several optional clauses: product title, SKU, categories, attributes, brands, and synonyms. A broad bool query can return products that match only one weak clause, producing results that are technically relevant but not useful to shoppers. Elasticsearch’s minimum_should_match parameter lets you require a sensible number of those optional clauses to match. How minimum_should_match works Use minimum_should_match inside a bool query with a should array. The value determines how many should clauses must match before a document can be returned. { "query": { "bool": { "should": [ { "match": { "name": { "query": "red running shoes", "boost": 4 } } }, { "match": { "short_description": "red running shoes" } }, { "term": { "categories.slug": "running-shoes" } }, { "term": { "attributes.color.keyword": "red"

Disjunction Max for Better Multi-Field Search

Multi-field product search often produces inconsistent results when the same query is sent to every field and the scores are blended without considering which field matched best. A shopper searching for running shoes should usually see a product with those words in its name above a product that only mentions them in a long description. Elasticsearch’s dis_max query is useful for this ranking problem. It selects the highest score from several subqueries and can optionally add a controlled portion of the scores from the other matching queries. This makes the strongest field match the primary ranking signal instead of allowing many weaker matches to overwhelm it. Why Disjunction Max Helps Product Search Consider a WooCommerce product indexed with separate fields for its name, SKU, short

Wildcard Queries: Powerful but Expensive

Wildcard queries are useful when a WooCommerce search requirement includes incomplete terms, variable SKU formats, or unknown characters. They are also one of the easiest ways to make Elasticsearch queries expensive, especially when the pattern begins with * or ?. What a wildcard query does A wildcard query matches terms using pattern characters: * matches zero or more characters. ? matches exactly one character. For example, this query can find product SKUs containing shoe anywhere in the value: { "query": { "wildcard": { "sku.keyword": { "value": "*shoe*", "case_insensitive": true } } } } Wildcard queries operate on terms in the index. They do not analyze the input like a match query. For WooCommerce product data, this usually means querying a keyword field such as sku.keyword,

Prefix Search for Product Discovery

Prefix search matches products whose searchable terms begin with the customer’s input. In a WooCommerce catalog, this is useful for product names, SKUs, brand names, and category labels when shoppers type the beginning of a word such as wire for “Wireless Charging Stand” or nike air for a product family. Prefix search is different from substring search. A prefix query can match wireless when the input is wire, but it should not match a value where “wire” appears only in the middle of a term. That distinction makes prefix search faster and more predictable for autocomplete and product discovery. Choose the right Elasticsearch field For product discovery, the most flexible approach is usually a text field with an analyzer designed for prefixes. A standard analyzed

Handling Typo-Tolerant Product Search

Customers do not always enter product names exactly as they appear in the catalog. A shopper may search for wireles headphones, iphon case, or stainles steel bottle and still expect relevant products. Typo-tolerant search uses Elasticsearch’s fuzzy matching to recover from small spelling errors without requiring a perfect query. How fuzzy matching works Elasticsearch fuzzy matching compares terms using edit distance. An edit can be an insertion, deletion, substitution, or transposition. For example, headphons can match headphones because only a small number of edits are required. The fuzziness option controls the permitted edit distance. A practical starting point is AUTO, which selects a distance based on the length of the term. For more predictable behavior, an agency may use an explicit value such as 1

Fuzzy Search for Misspelled Product Names

Misspelled product names are a common reason shoppers abandon WooCommerce searches. A customer may search for wireles headphones, stainles steel bottle, or runing shoes and still expect the correct products to appear. Elasticsearch can handle these mistakes with fuzzy matching, provided the query is configured carefully and integrated with WooCommerce product rules. How Elasticsearch fuzzy matching works Fuzzy matching uses edit distance to find terms that are within a small number of character changes from the search term. The supported changes include inserting, removing, replacing, or transposing characters. For example, a search for headphons can match headphones. Elasticsearch exposes this behavior through the fuzziness option on queries such as match and multi_match. For product search, AUTO is usually a good starting point because Elasticsearch selects

Phrase Matching for WooCommerce Search

Phrase matching is useful when WooCommerce shoppers enter a sequence of words that should remain together, such as stainless steel bottle, wireless gaming mouse, or men's running shoes. Unlike a broad full-text query, a phrase query checks both the presence and the order of the terms. This can make product search results more predictable without requiring an exact match of the entire product title. Why phrase matching matters in WooCommerce WooCommerce catalogs often contain overlapping terms. A search for wireless gaming mouse should usually prioritize products containing that sequence over products that mention wireless, gaming, and mouse in unrelated parts of the description. A regular match query analyzes the input and generally matches the terms independently. A match_phrase query adds a positional requirement: the analyzed

Boosting Your Most Important Product Fields

Not every product field deserves equal influence in search results. For most WooCommerce catalogs, a match in the product name is a stronger signal than a match in a long description, while an exact SKU match may be more important than either. Elasticsearch lets you express those priorities with field boosts. What a field boost does A field boost changes how strongly a match contributes to a document’s relevance score. In a multi_match query, a boost is added to the field name with the ^ notation: { "query": { "multi_match": { "query": "waterproof hiking boot", "fields": [ "name^5", "sku^8", "short_description^2", "description", "categories.name^3", "attributes.value^2" ], "type": "best_fields" } } } In this example, a match in sku receives the highest preference, followed by the product name.

Why Some WooCommerce Products Rank Higher

When shoppers search a WooCommerce store, products are not returned in a random order. Elasticsearch evaluates several signals, including how closely a product matches the query, which fields contain the match, how often terms occur, and any business rules added by the store. This is why two products that appear equally relevant in the catalog can receive very different positions. For agencies, improving product ranking starts with identifying which signals the search integration actually sends to Elasticsearch. A well-designed index and query can make product discovery more predictable without relying on manual ordering for every category or keyword. Text relevance is usually the first ranking signal Elasticsearch commonly uses the BM25 similarity algorithm for full-text queries. BM25 considers term frequency, the rarity of a term

BM25: The Relevance Algorithm Behind Elasticsearch

BM25 is the default relevance algorithm used by Elasticsearch for most text fields. When a WooCommerce shopper searches for a phrase such as waterproof hiking boots, BM25 helps Elasticsearch decide which product documents should appear first by comparing the query terms with the content of each document. For WooCommerce agencies, understanding BM25 is important because search quality is affected by more than whether a product contains a keyword. Term frequency, document length, term rarity, field configuration, analyzers, and query structure all influence the final _score. What BM25 measures BM25 evaluates three primary signals: Term frequency: how often a searched term appears in a field. Inverse document frequency: how rare the term is across the index. Field-length normalization: whether the matching field is unusually short or

Boosting Product Titles Over Descriptions

In a WooCommerce catalog, the product name usually carries more commercial intent than the long description. A shopper searching for waterproof hiking boots is generally looking for products whose names identify that item, not products that merely mention waterproof materials somewhere in their description. Elasticsearch can express this priority directly by assigning a higher boost to the product title field than to the description field. This improves relevance without removing useful descriptive matches. Why field weighting matters A basic multi-field search treats every matching field according to the query configuration. Without deliberate weighting, a long description can produce a higher score simply because it contains more matching terms than a concise product name. For WooCommerce stores, this can create problems such as: Products with a

Searching Across Multiple Product Fields

Product relevance often depends on information distributed across several fields. A shopper may enter a brand, model number, product type, and descriptive phrase in one query, while the indexed product stores those values in separate fields such as name, sku, brand, categories, and description. For WooCommerce agencies, the important decision is not simply which fields to search. It is how Elasticsearch should combine matches, how strongly each field should influence ranking, and how the query should behave when a term appears in different fields. Typical product fields A WooCommerce product index might expose fields similar to these: name: the product title, usually mapped as analyzed text with a keyword subfield. sku: an exact or partially searchable stock keeping unit. brand: a brand name, often available

Combining Search and Filters in One Query

WooCommerce shoppers often need two things at the same time: relevant text results and precise product constraints. A customer may search for waterproof hiking boots while also selecting a brand, price range, stock status, and product category. Elasticsearch can handle these requirements in one request by combining a scored search clause with non-scoring filters inside a Boolean query. Use must for search and filter for constraints The usual structure is an Elasticsearch bool query. Put the full-text portion in must or should, and put exact restrictions in filter. Filter clauses narrow the result set without changing relevance scores, and Elasticsearch can optimize them efficiently. { "query": { "bool": { "must": [ { "multi_match": { "query": "waterproof hiking boots", "fields": [ "name^4", "short_description^2", "description", "sku" ],

Range Queries for WooCommerce Prices

Price filtering is one of the most common requirements in WooCommerce search: show products between two values, find items below a sale threshold, or build a layered price-navigation experience. Elasticsearch range queries are designed for these operations, but the result depends on how WooCommerce prices are indexed and which price concept the store needs to expose. What a price range query does A range query matches documents whose value falls within a specified interval. Elasticsearch supports four primary operators: gte: greater than or equal to gt: greater than lte: less than or equal to lt: less than For example, the following query finds products with a current price from 50 through 100, including both boundaries: {"query":{"range":{"price":{"gte":50,"lte":100}}}} The field must be mapped as a numeric or

Search Context vs Filter Context

Elasticsearch evaluates clauses in two different ways: query context determines how well a document matches, while filter context determines whether a document matches at all. Choosing the right context is important for WooCommerce product search because product text needs relevance scoring, whereas attributes such as stock status, price range, brand, category, and visibility usually represent strict constraints. Query context: matching by relevance A clause runs in query context when Elasticsearch calculates a relevance score for each matching document. The score helps order results from the strongest match to the weakest match. Query context is appropriate for searchable product content, including a product name, SKU, description, short description, and carefully selected custom fields. For example, a customer searching for waterproof hiking boots expects products matching both

Filtering Products Without Affecting Relevance

Faceted navigation is essential in WooCommerce stores, but product filters should not accidentally change the order of otherwise relevant results. A customer searching for “running shoes” should still see the products most related to that phrase after selecting a size, brand, or price range. Separate relevance from eligibility Elasticsearch uses query context to calculate relevance scores and filter context to decide whether a document is eligible. Full-text clauses such as match and multi_match belong in the scoring portion of the request. Exact constraints such as stock status, product category, brand, price, and attributes belong in a bool.filter array. Clauses in filter context do not contribute to the _score. They narrow the result set while leaving the text relevance calculation to the search query. { "query":

Should You Use Match or Term for WooCommerce?

Choosing between match and term queries affects whether WooCommerce product search behaves like a customer-facing search experience or an exact filtering system. The right choice depends on how the field is mapped and whether the input should be analyzed. The practical difference A match query is designed for analyzed text. Elasticsearch processes the search input with the field’s analyzer, usually converting it into one or more searchable terms. This makes it suitable for product names, descriptions, and other fields where customers may enter natural language. A term query searches for an exact indexed term. Elasticsearch does not analyze the value supplied to a term query. It is therefore appropriate for exact identifiers and filters, such as product IDs, SKUs, stock flags, brand codes, or taxonomy

Boolean Queries for Complex Product Search

Complex WooCommerce product search rarely depends on one condition. A shopper may need products that match a phrase, belong to a specific category, fall within a price range, include selected attributes, and exclude discontinued or hidden items. Elasticsearch combines these requirements through the bool query. How the bool query is structured A bool query combines other queries through four primary clauses: must: the document must match. Scores contribute to relevance. filter: the document must match, but the clause does not affect relevance scoring. Filters are generally the best choice for exact values, ranges, and visibility rules. should: an optional relevance or preference clause, unless the query has no must or filter clauses. must_not: the document must not match. For WooCommerce integrations, put business constraints in

Term Queries for Exact WooCommerce Matches

For WooCommerce search features, an exact match is often different from a relevant text match. A shopper searching for SKU TSHIRT-BLU-M should not receive products whose descriptions merely contain similar words. Elasticsearch’s term query is designed for this type of lookup, provided that the target field is mapped as a keyword or another non-analyzed field. What a term query does A term query looks for the exact indexed term supplied in the query. Elasticsearch does not analyze, stem, tokenize, or otherwise process the value in the same way that it does for a typical match query. {"query":{"term":{"sku.keyword":{"value":"TSHIRT-BLU-M"}}}} This query is appropriate when sku.keyword contains the complete SKU as one indexed value. It will not match a different SKU such as TSHIRT-BLU-L, and it may not

Match Queries for Better WooCommerce Search

WooCommerce product search often starts with a simple keyword query, but a match query provides much better control over how Elasticsearch interprets customer input. It analyzes the search text, converts it into terms using the field’s analyzer, and finds documents that contain matching terms rather than requiring an exact field-value match. Why use a match query for WooCommerce? Product titles, descriptions, SKUs, and attributes are usually indexed as analyzed text. A customer may search for waterproof hiking boots, while the indexed product title contains Men’s Waterproof Boots for Hiking. A match query can analyze both the indexed content and the search input so that relevant products are returned even when the word order differs. By comparison, a term query is intended for exact, un analyzed

Understanding Elasticsearch Relevance Scores

When a shopper searches a WooCommerce catalog, Elasticsearch does more than identify products containing the search terms. It calculates a relevance score for each matching document and uses that score to order the results. Understanding how _score is produced helps agencies diagnose poor search results, tune product queries, and explain ranking behavior to store owners. What the _score value represents The _score is a numeric estimate of how well a document matches a query. A higher score generally means a stronger match, but the number has no universal meaning outside the request that produced it. A score of 8.4 is not automatically better than a score of 4.2 from a different query, index, or shard configuration. For example, a WooCommerce product with the title Waterproof

Building Your First WooCommerce Elasticsearch Query

Your first Elasticsearch query for WooCommerce should answer a specific storefront question, such as: “Which published products match a customer’s search for waterproof hiking boots?” Start with a small, readable query and add filters only when the business requirement is clear. Understand the indexed product document Elasticsearch searches the document that was indexed, not the WooCommerce database directly. The exact field names depend on your indexing pipeline or search extension. A product document might contain fields like name, description, sku, categories, attributes, stock_status, price, status, and visibility. Before writing a query, inspect a document and its mapping: GET wc_products/_mapping GET wc_products/_search { "size": 1, "query": { "match_all": {} } } Replace wc_products with the index used by your environment. The mapping tells you whether a

Text Fields vs Keyword Fields in WooCommerce

In Elasticsearch, choosing between text and keyword fields directly affects how WooCommerce product data is searched, filtered, sorted, and aggregated. The distinction is especially important for agencies building catalog search, layered navigation, reporting, and integrations that synchronize products from WordPress and WooCommerce. What is a text field? A text field is designed for full-text search. Elasticsearch analyzes the value when it indexes the document. Analysis commonly includes tokenization, lowercasing, stemming, stop-word removal, or other language-specific processing. For example, a WooCommerce product title such as Organic Cotton Running Shirt might be indexed as separate terms such as organic, cotton, running, and shirt. A search for cotton shirt can then match the product even though the query does not exactly reproduce the stored title. { "product_name": {

Choosing the Right Elasticsearch Field Types

Field types determine how Elasticsearch indexes WooCommerce data and what operations are available at query time. A product name needs full-text analysis, while a SKU must support exact matching. A price should be numeric, and product attributes may require nested documents when each attribute combination must remain associated with the correct variation. Start with the operation, not the source value The same WooCommerce value can be represented differently depending on how the store searches and filters it. Before defining a mapping, list the required operations: Full-text search: Use text for product names, descriptions, and other prose. Exact matching: Use keyword for SKUs, brand slugs, order statuses, and identifiers. Filtering and aggregations: Use keyword, numeric types, boolean, or date. Sorting: Use a numeric, date, or keyword

Indexing Product Titles, SKUs and Descriptions

Define the product document before indexing A reliable WooCommerce search experience starts with a deliberate Elasticsearch document structure. Do not send the entire wp_posts row or raw post metadata and expect Elasticsearch to infer the right behavior. Build one search document per product, or per variation when customers need to search and filter variations independently. A typical product document can contain separate fields for the values customers search as text and the values they match exactly: { "product_id": 1842, "title": "Organic Cotton Crew Neck T-Shirt", "sku": "TSH-COT-ORG-BLK-M", "description": "A lightweight crew neck T-shirt made from certified organic cotton.", "short_description": "Certified organic cotton T-shirt.", "status": "publish", "stock_status": "instock", "categories": ["T-Shirts", "Organic Clothing"] } Keep the source fields in the document even if you also create a

Mapping WooCommerce Products to Elasticsearch Documents

Why the WooCommerce-to-Elasticsearch mapping matters A WooCommerce product contains much more than a name and price. It may include SKUs, descriptions, taxonomies, attributes, stock state, sale dates, images, custom fields, and multiple variations. Elasticsearch can search and filter this data efficiently, but only when the document structure reflects how customers use the catalogue. For agencies, the mapping should be designed before indexing the first product. A reliable design prevents common problems such as prices being indexed as text, category filters behaving inconsistently, and variation attributes being matched across different variants. Start with a stable product document Each Elasticsearch document should represent one searchable WooCommerce product unless the project specifically requires one document per variation. Include a stable identifier that connects the document to the WooCommerce

Designing an Elasticsearch Index for WooCommerce

Start with the search experience An Elasticsearch index for WooCommerce should be designed around the queries customers and merchandisers need to run, not as a direct copy of the WordPress database. WooCommerce stores products across posts, post metadata, taxonomy tables, lookup tables, and variation records. Elasticsearch performs best when the fields required for search, filtering, sorting, and display are denormalized into a document that can be read without joining those sources at query time. Before creating a mapping, list the required operations: Full-text search across product names, SKUs, descriptions, and attributes Exact filtering by category, brand, stock status, and product attributes Numeric range filtering and sorting by price Sorting by relevance, popularity, rating, or date Variant-aware filtering for size, color, and other options Boosting products

What Happens When You Index a WooCommerce Product?

The indexing workflow WooCommerce does not send a product to Elasticsearch by itself. An integration plugin, a custom WordPress process, or an external synchronization service must convert the WooCommerce product into an Elasticsearch document and write it to an index. A typical workflow looks like this: A product is created or updated in WooCommerce. WordPress fires product-related hooks such as save_post_product or WooCommerce-specific product update actions. The integration loads the product, its variations, taxonomies, attributes, stock data, and metadata. It transforms those values into a search document. The document is indexed using the Elasticsearch API. Search requests query the resulting index rather than the WordPress database. For large catalogs, the initial synchronization is usually performed with the Elasticsearch Bulk API. Incremental updates then keep individual

Elasticsearch vs MySQL for WooCommerce Search

Choosing the Right Search Engine for WooCommerce WooCommerce product search often starts with WordPress and MySQL. That approach is straightforward and works well for small catalogs, but search quality and response times can decline as product counts, variations, attributes, and custom fields increase. Elasticsearch provides a separate search engine designed for fast, relevance-aware retrieval. The right choice depends on catalog size, query complexity, traffic, operational capacity, and how quickly product changes must appear in search results. How WooCommerce Search Works with MySQL In a standard WooCommerce installation, product data is stored across WordPress tables, including wp_posts, wp_postmeta, taxonomy tables, and lookup tables such as wp_wc_product_meta_lookup. A simple product search may use a query similar to: SELECT ID, post_title FROM wp_posts WHERE post_type = 'product' AND

Why Elasticsearch Changes WooCommerce Search

Search Is a Revenue Feature WooCommerce search is often treated as a small theme or template concern. In a catalog with a few dozen products, the default WordPress search may be adequate. For a store with thousands of products, variations, technical specifications, or inconsistent customer terminology, search becomes a core part of the buying journey. Elasticsearch changes that experience by moving product discovery from database text matching to a dedicated search engine. Instead of relying primarily on SQL queries against post titles and content, a WooCommerce integration can index product data and search it using relevance scoring, analyzers, filters, aggregations, and typo tolerance. Why Default WooCommerce Search Struggles WordPress and WooCommerce search commonly depend on database queries that look for matching text in fields such