100 Days of Vespa.ai & Woocommerce guides for WordPress & WooCommerce

Inventory as a Search Signal

WooCommerce search should not treat inventory as a simple availability check. Stock status, quantity, replenishment timing, and fulfillment location can all influence which products deserve visibility for a particular query. For an agency building product search with Vespa.ai, inventory is a ranking signal that should work alongside text relevance, merchandising rules, price, popularity, and customer intent. The goal is not always to hide unavailable products. It is to present the most useful result for the shopper and the business context. Model inventory as searchable product data A WooCommerce product feed should expose inventory fields in a form that Vespa can index and rank efficiently. Typical fields include: Stock state: in stock, low stock, backorder, or out of stock. Available quantity: the quantity currently available for

Price as a Ranking Signal in WooCommerce Search with Vespa

Price can improve WooCommerce search ranking, but it should rarely replace textual or behavioral relevance. A low-priced product is not automatically the best result for a query, and ranking every product by price can reduce conversion when shoppers are looking for premium, branded, or specification-heavy products. In Vespa, price is most useful as a structured ranking feature. The search application can combine price with lexical relevance, category matching, stock status, popularity, margin, and query intent to produce a ranking that reflects the commercial goals of the store. When price should influence ranking Price is a useful signal when the query or shopping context expresses a budget, a preference for value, or a need to compare similar products. Examples include: cheap running shoes laptop under 800

Adding Product Availability to Ranking

Separate eligibility from ranking Product availability should influence search results, but it should not be treated as a substitute for an eligibility rule. In a WooCommerce storefront, an unavailable product may need to be excluded entirely from search, while a product with limited stock, a delayed fulfillment date, or an active backorder policy can remain eligible and receive a lower ranking score. A practical search pipeline uses two decisions: Eligibility: Can this product be shown or purchased in the current channel, region, and customer context? Ranking: Among eligible products, how strongly should availability influence the order? Keeping these decisions separate prevents a highly relevant but unavailable product from outranking products that customers can actually buy. Define a normalized availability model WooCommerce exposes several inventory-related concepts,

Ranking Products by Sales and Conversion Signals

Product ranking should reflect more than a product’s catalog relevance. For a WooCommerce store, recent sales, product views, add-to-cart activity, and completed orders provide useful evidence about what shoppers are likely to buy. Vespa can combine those signals with text relevance, category filters, price, inventory, and business rules in one ranking expression. Choose signals that represent shopper intent Start by defining the events that will be exported from WooCommerce and the time windows that matter to the business. Typical product-level signals include: Orders: completed orders containing the product, preferably split into seven-day, thirty-day, and lifetime totals. Units sold: useful when one order can contain multiple units. Product views: a denominator for estimating demand and conversion. Add-to-cart events: a stronger intent signal than a view. Conversion

Ranking WooCommerce Products by Popularity

Popularity ranking is one of the most useful merchandising features for a WooCommerce store. Instead of sorting products alphabetically or by price, you can rank matching products by sales activity, recent demand, or a blended popularity score calculated in Vespa. A practical implementation keeps product content in Vespa and continuously updates popularity attributes from WooCommerce order data. Search queries can then use a dedicated ranking profile without changing the product documents or application code that renders the results. Define what “popular” means WooCommerce provides several signals that can contribute to popularity: Total quantity sold Quantity sold during the last 7, 30, or 90 days Revenue during a selected period Number of orders containing the product Add-to-cart or product-view events Inventory availability and product status For

Combining Text Relevance and Business Signals

WooCommerce product search usually has two competing goals: match what the shopper typed and present products that are commercially useful. Text relevance identifies products that satisfy the query, while business signals such as sales velocity, margin, inventory, rating, and conversion rate help decide the order among relevant products. Vespa is well suited to this problem because text matching and business logic can be expressed in the same ranking pipeline. The important design principle is to let relevance establish a minimum level of usefulness before business signals influence the final order. Separate matching from ordering A product can have excellent sales numbers and still be a poor result for a specific query. For example, a popular blue running shoe should not rank first for a query

Ranking Products with BM25

For WooCommerce product search, BM25 is a strong lexical baseline when customers search with meaningful words such as waterproof hiking jacket, USB-C dock, or organic cotton sheets. Vespa provides BM25 as a rank feature, allowing an agency to combine text relevance with product availability, price, stock status, sales performance, and other business signals. What BM25 contributes to product search BM25 scores how well a query matches a document. It considers term frequency, the rarity of each term across the index, and the length of the matched field. A rare term such as a specific model number can contribute more than a common term such as product. BM25 also limits the benefit of repeating the same term, which makes it more robust than a simple raw

Understanding BM25 in Vespa

BM25 is a lexical relevance algorithm that scores how well a document matches the terms in a query. In a WooCommerce search application, it can make product titles, descriptions, attributes, and other indexed fields contribute according to term frequency, document frequency, and field length. Vespa exposes BM25 as a rank feature. This lets an agency define exactly which product fields participate in BM25 scoring and combine the result with business signals such as inventory, margin, popularity, or product quality. What BM25 measures BM25 primarily considers three factors: Term frequency: a term appearing in a document can increase its score, but repeated occurrences have diminishing returns. Inverse document frequency: rare terms contribute more than common terms. A distinctive product model or brand name is therefore more

Boosting Product Fields in WooCommerce Search

WooCommerce search quality depends heavily on how product data is represented and weighted. A product title, SKU, brand, category, attributes, and long description do not have equal commercial value, so treating every field as an undifferentiated text blob usually produces weak results. Vespa lets an agency model these fields separately, match queries across the appropriate field set, and apply field-specific relevance weights. Separate searchable product fields Start by mapping WooCommerce data into fields with clear search behavior. Product names and brands should normally contribute strongly to relevance. Descriptions and long-form specifications are useful for recall but should not overpower an exact product or SKU match. SKUs, GTINs, and other identifiers often need exact or near-exact matching rather than ordinary linguistic relevance. A simplified Vespa document

Search Across Product Titles, Attributes and Descriptions with Vespa.ai

Why product search needs more than a title field WooCommerce catalogs often contain the information a shopper needs in several places. A product title may contain the model name, the description may contain technical specifications, and WooCommerce attributes may contain values such as blue, XL, or stainless steel. If an agency indexes only the product title, searches for attribute values and descriptive phrases will produce incomplete results. Vespa.ai can search these sources together while still keeping structured attribute values available for filtering, faceting, and ranking. Use separate fields for separate jobs A practical product document normally contains both searchable text fields and structured fields. Text fields are suitable for relevance matching. Structured fields are better for exact filters and facets. schema product { document product

Prefix Search for Product Discovery

Prefix search matches products whose indexed terms begin with the characters entered by a shopper. A query such as cam can return camera bags, camping equipment, and replacement camera batteries before the shopper has entered a complete word. For WooCommerce stores, this is especially useful in autocomplete, search-as-you-type interfaces, category filters, and merchandising tools. Why prefix search matters in WooCommerce Default WooCommerce search is often insufficient for large catalogs. It may depend on MySQL queries, exact terms, or third-party plugins that become slow as product, variation, attribute, and taxonomy counts grow. A Vespa-backed discovery service can provide low-latency matching while combining prefix relevance with product metadata, inventory status, popularity, price, and merchandising rules. Prefix search is different from substring search. A prefix query for wire

Autocomplete for WooCommerce with Vespa

Autocomplete is a small WooCommerce feature with a large effect on product discovery. Shoppers expect useful suggestions after entering only a few characters, while agencies need those suggestions to be fast, relevant, localized, and safe to operate at scale. Vespa is a good fit when autocomplete must combine prefix matching with product metadata such as popularity, brand, category, stock status, or commercial priority. Choose the right autocomplete model There are two common designs: Product autocomplete: return matching products with an image, price, stock state, and product URL. Query suggestions: return phrases such as “wireless keyboard” or “running shoes” that can be submitted as a normal store search. A WooCommerce implementation can use both. Product autocomplete is usually generated from the product catalog, while query suggestions

Fuzzy Product Search with Vespa

WooCommerce shoppers do not always search with the exact product name. They may type iphnoe case, omit part numbers, or use a brand spelling that differs from the catalog. Vespa can handle these near matches with its fuzzy query operator while retaining structured filters such as stock status, price, category, and product visibility. For a WooCommerce agency, the practical pattern is to keep WooCommerce as the source of product and order data, replicate searchable product fields into Vespa, and send catalog search requests to Vespa. Fuzzy matching is then applied only to fields where spelling variation is useful, rather than indiscriminately across the entire document. When fuzzy search is appropriate Fuzzy search compares terms within a configurable edit distance. An edit is an insertion, deletion,

Phrase Matching for Better WooCommerce Search

Phrase matching helps WooCommerce search distinguish between products whose words are present individually and products whose names contain the customer’s intended wording. A search for wireless charging stand should usually rank “Wireless Charging Stand for iPhone” above a product that mentions “wireless accessories” and “desktop phone stand” in separate parts of its description. For agencies, phrase matching is most useful when product catalogs contain repeated attributes, long descriptions, variations, and similar SKUs. It can improve relevance without forcing every query to behave like an exact product-name lookup. What phrase matching does A phrase query requires the query terms to occur next to one another and in the same order within the matched text field. This is different from a normal multi-term query, where each term

Full-Text Product Search with Vespa

WooCommerce search often begins with a database query over product titles, SKUs, descriptions, and taxonomy terms. That approach can work for a small catalog, but it becomes harder to tune when an agency is managing large catalogs, multilingual content, frequent inventory updates, and merchandising requirements. Vespa provides a dedicated search layer that can index WooCommerce product content and rank matching documents in real time. This implementation focuses on full-text product search: matching a shopper’s words against indexed product fields and returning the most relevant products. Filtering, personalization, semantic retrieval, and recommendations can be added later without replacing the product-search foundation. Choose the WooCommerce fields to index Start by defining which fields contain searchable language and which fields are primarily used for filtering or display. A

Exact Matching for SKUs and Product Codes

SKU and product-code searches are different from ordinary catalog searches. A customer searching for VESPA-GTS-300-RED usually expects one precise product or variation, not products whose descriptions happen to contain parts of that code. In WooCommerce, exact matching is especially important because SKUs often contain hyphens, slashes, numbers, and variant suffixes. Model SKUs as exact-search fields Index the WooCommerce SKU as a dedicated Vespa field instead of relying on a general product title or description field. Product variations should receive their own documents when each variation has a distinct SKU and purchasable inventory. field sku type string { indexing: attribute | summary match: exact } field product_code type string { indexing: attribute | summary match: exact } The match: exact setting makes the field suitable for

Filtering WooCommerce Products with YQL

WooCommerce stores often need more than a simple product search box. Customers may search for “running shoes” and then narrow the result set by price, stock status, brand, category, or product attributes. Vespa Query Language, usually called YQL, provides a structured way to express those constraints when WooCommerce product data has been indexed in Vespa. For an agency, the important distinction is that YQL is not SQL and it does not query the WooCommerce database directly. It queries the Vespa document model. The product fields that can be filtered must therefore be represented in the Vespa schema and populated by the WooCommerce synchronization process. Represent WooCommerce filter fields in Vespa A product document might contain fields such as: product_id: the WooCommerce product ID. title: the

Building a Product Search Query with Vespa

A WooCommerce product search query should combine the shopper’s text with the filters and ranking signals needed by the storefront. Vespa’s Query API provides the query execution layer, while YQL defines which product documents are eligible and which operators are used to match them. Start with a product document model The exact field names depend on the Vespa schema, but a product search collection commonly contains fields such as: title and description for lexical matching. sku and product_id for exact identification. categories, brand, and attributes for filtering and faceting. price for numeric range filters. stock_status and visibility for catalog eligibility. embedding for semantic matching. Fields used in filters and ranking should generally be declared as attributes. Text fields that participate in full-text search need appropriate

Querying WooCommerce Products with YQL

When WooCommerce products are imported into Vespa, YQL becomes the query layer used to search, filter, sort, and group the catalog. For an agency, this provides a consistent way to power product search, category landing pages, faceted navigation, and custom merchandising experiences without querying WordPress for every request. The exact field names depend on the Vespa schema used by your integration. The examples below assume a document type named product with fields such as product_id, title, description, categories, price, stock_status, on_sale, and published. A basic WooCommerce product query A YQL request selects documents from a document source and applies a Boolean condition: select * from product where true Using true is useful when testing the schema or retrieving a complete result set. In a production

Bulk Feeding a Large WooCommerce Catalog

Large WooCommerce catalogs should not be loaded into Vespa with one request per product and no coordination. That approach is slow, difficult to resume, and likely to trigger rate limits on the WooCommerce side. A reliable import treats catalog loading as a controlled data pipeline with checkpoints, bounded concurrency, idempotent document IDs, and a clear recovery strategy. Define the document model before importing Start by deciding which WooCommerce fields belong in the Vespa document. Search usually needs the product name, SKU, descriptions, categories, attributes, stock status, price, visibility, images, and variation data. Do not copy the entire WooCommerce response into every searchable field without a plan. Keep source data that may be useful for debugging or reprocessing, but map it deliberately to the Vespa schema.

Deleting Products from a Vespa Index

Product deletion is part of keeping a WooCommerce-powered Vespa index trustworthy. If a product is permanently removed from WooCommerce but remains searchable, customers can see stale prices, broken product links, or items that can no longer be purchased. In Vespa, deleting a product means sending a document removal operation to the Document API. This is different from updating the document with an empty title, setting its availability to false, or excluding it at query time. A removal operation deletes the document from the content cluster and prevents it from being returned as a normal indexed product. Delete a product with the Vespa Document API The Document API uses an HTTP DELETE request. The general endpoint format is: DELETE /document/v1/{namespace}/{document-type}/docid/{document-id} For example, an index that stores

Real-Time Product Updates with Vespa

WooCommerce catalogs change constantly: prices are adjusted, stock is reserved, products are unpublished, and merchandising teams update attributes throughout the day. A batch export to search can leave shoppers seeing stale inventory or outdated offers. Vespa can receive product document updates as those changes occur, allowing search and recommendation applications to reflect the catalog without waiting for a full reindex. What real-time updates mean in a WooCommerce integration In this architecture, WooCommerce remains the system of record. Vespa stores the searchable product representation used by applications such as product search, category discovery, autocomplete, and recommendations. When a product changes, an integration publishes the affected fields to Vespa through its document API. A typical update flow is: A product is created or changed in WooCommerce. WooCommerce

Keeping a Vespa Product Index in Sync with WooCommerce

A Vespa product index is only useful when it reflects the current WooCommerce catalog. Price changes, stock updates, product edits, variations, unpublished products, and deletions must all reach Vespa reliably. For an agency managing several stores, synchronization should be treated as an integration with clear ownership, idempotency, retry handling, and reconciliation rather than as a one-time import. Choose the document model first The most important design decision is what a Vespa document represents. A common approach is one document per WooCommerce product, with variations stored as nested data or flattened fields. This works well when customers search for products and the parent product is the result. For stores where customers search by SKU, variation-level price, availability, or attributes, create one Vespa document per variation. Use

Feeding WooCommerce Products into Vespa

Vespa can provide fast keyword, filtering, ranking, and semantic retrieval for a WooCommerce catalog, but it needs a deliberate feed design. The integration should turn each WooCommerce product into a stable Vespa document, keep the document schema aligned with the search experience, and update Vespa whenever catalog data changes. Choose the Vespa document model A practical starting point is one Vespa document per searchable WooCommerce product. Use the WooCommerce product ID as the stable identifier rather than the product name or slug. This keeps updates and deletes deterministic even when a product is renamed. For variable products, agencies usually choose one of two models: Parent-product documents: Store the variable product as one document with aggregated attributes such as available sizes, colors, and price range. Variation

Indexing Product SKUs and Exact Identifiers

Product SKUs, GTINs, MPNs, barcodes, and supplier codes are not ordinary product-search text. Store managers and customers usually expect an identifier lookup to return the product whose identifier matches the input, not products that happen to contain similar words. In Vespa, the cleanest design is to model identifier retrieval separately from descriptive search and make the matching behavior explicit. Separate identifiers from descriptive content A WooCommerce product document may contain several identifier fields. A simple product could use the SKU from _sku, while a variable product may expose a parent SKU, variation SKU, GTIN, or manufacturer part number. Do not combine these values into the product title or a general full-text field. Keeping them separate lets the query decide whether an identifier match should be

Handling WooCommerce Variations in Vespa

WooCommerce variable products require more than a simple product-level search document. A parent product such as a T-shirt may have dozens of variations, each with its own SKU, price, stock state, image, and attribute combination. For agencies building search with Vespa, the central design decision is whether to index the parent product, each variation, or both. Choose a variation indexing model For most WooCommerce catalogs, indexing one Vespa document per variation is the most reliable starting point. Each document represents a purchasable SKU and carries a reference to its parent product. Variation document: Stores the variation ID, parent product ID, SKU, price, stock state, attributes, and searchable text. Parent product: Stores the product title, description, categories, brand, and shared merchandising content. Relationship: The variation contains

Indexing WooCommerce Brands and Product Taxonomies

WooCommerce products are rarely organized by one flat label. A product can belong to a hierarchy of categories, have one or more brands, and expose attributes such as color, size, material, or compatibility. A Vespa index should preserve that structure instead of reducing every taxonomy value to a single string. This matters for search, filtering, navigation, autocomplete, and analytics. If taxonomy data is modeled correctly, an agency can support queries such as “black hiking boots from Acme,” category landing pages, brand pages, and faceted navigation without maintaining a separate search-specific taxonomy system. Identify the WooCommerce taxonomies before indexing WooCommerce stores product categories and tags as WordPress taxonomies. Categories are hierarchical, while tags are normally flat. Product attributes are represented through taxonomies as well, commonly with

Indexing WooCommerce Categories in Vespa

WooCommerce categories carry more than display metadata. They provide a stable way to filter products, build landing pages, generate facets, and preserve the structure of a store’s catalog. In Vespa, the most useful design is usually to store category membership directly on product documents and optionally index categories as their own documents when category pages need search, ranking, or independent metadata. Choose the category representation There are two common models for WooCommerce category data: Embedded category membership: each product contains its category IDs, slugs, names, and ancestor IDs. This is the best model for category filters and product search. Category documents: each WooCommerce category becomes a Vespa document. This is useful when category pages need descriptions, images, SEO fields, product counts, or search. These models

Product Titles, Descriptions and Attributes in Vespa

Model the Product Data Before You Rank It WooCommerce product data usually arrives as a combination of post fields, taxonomy terms, custom attributes, and variation records. Vespa works best when those values are mapped deliberately into a document schema rather than copied into one large text field. A practical product document might contain: product_id as the stable WooCommerce product identifier. title for the customer-facing product name. description for the long description and relevant short-description content. brand, category, and attribute_* fields for filtering and structured matching. price, stock_status, and visibility for commerce constraints. popularity, sales signals, or business rules used during ranking. Keep identifiers and filterable values separate from prose. A title such as “Red Cotton T-Shirt” is useful for full-text search, while the color and

Choosing the Right WooCommerce Fields for Vespa

Start with a search contract A WooCommerce product object contains far more information than most search experiences need. Before creating a Vespa schema, define which fields support each user-facing capability: Search: product names, descriptions, SKUs, brands, and relevant attributes. Filtering: categories, stock status, price, rating, brand, size, colour, and other faceted values. Ranking: popularity, sales volume, rating, recency, margin, and inventory signals. Display: the product title, URL, image, prices, availability, and selected merchandising data. This separation prevents a common implementation problem: treating every WooCommerce property as both searchable text and a filterable field. In Vespa, field type and indexing mode affect memory usage, query behavior, ranking, and update cost. Separate searchable text from exact-match data Fields intended for natural-language queries should generally be indexed as

Designing a Vespa Schema for WooCommerce Products

Start with the WooCommerce search model A Vespa schema should reflect how customers and downstream services search WooCommerce data, not simply mirror the WordPress database tables. For most stores, the searchable unit should be a product or a purchasable variation. Each document should contain the text used for relevance, the structured values used for filtering, and the identifiers required to link results back to WooCommerce. A practical document model commonly includes: A stable product or variation identifier Parent product and variation identifiers Title, description, short description, and searchable attributes SKU and optional brand or product-type fields Price and stock status Category and taxonomy identifiers Facet values such as color, size, material, and brand A product URL or canonical permalink Optional image, rating, and popularity fields

Modeling WooCommerce Products as Vespa Documents

Why the document model matters WooCommerce product data is designed for transactions and administration. Vespa is designed for retrieval, filtering, ranking, and serving results at low latency. A successful integration starts by translating the product catalog into documents that match how customers search and how the storefront filters products. A useful product document should contain: A stable product identifier from WooCommerce Searchable text such as the product name, short description, and description Structured attributes such as price, stock status, brand, and categories Facet fields such as color, size, material, and product type Ranking signals such as sales count, review score, and popularity URLs and display fields needed by the storefront Do not copy the WooCommerce database schema one-for-one. Store fields that support the user experience,

Vespa.ai & WooCommerce: From Product Catalog to Search Engine

Why a WooCommerce Catalog Needs a Search Layer WooCommerce stores product data in WordPress tables, which is effective for catalog management and transactional workflows. It is not always the best system for high-volume, relevance-sensitive product discovery. As catalogs grow, agencies commonly need faster autocomplete, filters across many attributes, typo tolerance, ranking controls, and search results that remain available without placing heavy load on the WordPress database. Vespa.ai can act as a dedicated search engine in front of WooCommerce. WooCommerce remains the source of truth for products, prices, stock, and orders, while Vespa stores an optimized search representation of each product and evaluates queries at low latency. Define the Product Document The first implementation step is to decide which WooCommerce fields belong in the Vespa document.

Vespa.ai for WooCommerce: Why Search Infrastructure Matters

Search Is a Core WooCommerce System For a small catalog, WooCommerce search may appear to be a minor feature. As a store grows, it becomes part of the revenue infrastructure. Customers expect relevant results, fast response times, useful filters, typo tolerance, and consistent behavior across product names, SKUs, attributes, categories, and descriptions. That creates challenges for agencies managing stores with tens or hundreds of thousands of products. The WordPress database remains responsible for orders, customers, product management, and checkout, but it is not always the best place to perform complex, high-volume search queries. A dedicated search platform such as Vespa.ai can take responsibility for indexing and serving product discovery requests while WooCommerce remains the system of record. Separating Commerce Data from Search Workloads A practical