100 Days of Algolia guides for WordPress & WooCommerce

How to Build a Search-as-You-Type Experience

A search-as-you-type experience helps shoppers find products before they reach a traditional results page. As a visitor enters a query, the storefront can request matching products, categories, or query suggestions and render them in an autocomplete panel. For WooCommerce agencies, this pattern can improve product discovery without replacing the existing catalog, checkout, or search-results templates. Algolia is well suited to this workflow because it provides low-latency search responses, typo tolerance, highlighting, ranking controls, and separate indices for products and suggestions. The implementation should still be designed around WooCommerce data, storefront performance, accessibility, and the customer journey. Define the search experience before writing code Start by deciding what the search box should return. A useful product-search panel commonly includes: Product name, thumbnail, price, and stock status.

Facet Filters vs Numeric Filters

Facet filters and numeric filters solve different discovery problems in WooCommerce search. Facets let shoppers select from discrete values such as brand, color, size, or stock status. Numeric filters compare measurable values such as price, weight, rating, or dimensions. Choosing the correct filter type affects index configuration, frontend widgets, query performance, and the quality of the shopping experience. What is a facet filter? A facet represents a set of named values associated with a record. For a WooCommerce product, common facet attributes include brand, categories, pa_color, pa_size, and stock_status. For example, a product record might contain: { "objectID": "8421", "name": "Trail Running Shoe", "brand": "Northstar", "categories": ["Shoes", "Running"], "pa_color": ["Black", "Red"], "pa_size": ["42", "43"], "price": 129.99, "stock_status": "instock" } The values in brand, categories, and

Faceted Search: Let Users Narrow the Results

Faceted search helps shoppers move from a broad product query to a useful shortlist. Instead of forcing a customer to refine a search term repeatedly, it lets them combine attributes such as brand, size, color, price, and availability. In a WooCommerce store, well-designed facets can reduce product-listing friction while giving agencies a flexible search experience that is independent of the underlying WordPress catalog structure. What a facet is in Algolia A facet is a filterable product attribute that Algolia can return with matching value counts. For example, a search for running shoes might return facet values for Brand, Size, Color, and Gender. The shopper can then select one or more values without changing the original query. To use an attribute as a facet, add it

Building a Great Instant Search Experience

Instant search is more than sending a request on every keystroke. A strong WooCommerce search experience helps shoppers find the right product quickly, keeps the interface responsive, and provides useful paths when the original query is incomplete or misspelled. Define the search experience before choosing widgets Start by mapping the shopper’s path from the first character to the product page. For most WooCommerce stores, that path includes: An input that is visible and easy to focus on, especially on mobile. Suggestions that appear while the shopper types. Relevant products, categories, brands, and popular queries. Facets for narrowing results by attributes such as size, color, material, price, and availability. A clear empty state with useful alternatives when no products match. Autocomplete and full search results serve

How Algolia Query Suggestions Work

Algolia Query Suggestions turns previous searches into suggested queries that appear while a shopper types. For a WooCommerce store, this can help customers discover common product searches faster, reduce spelling friction, and guide users toward queries that are known to return useful results. What Query Suggestions are A query suggestion is a complete or partial search phrase, such as running shoes, waterproof hiking boots, or organic cotton t shirts. Algolia generates suggestions from search behavior and makes them available through a dedicated Query Suggestions index. Query Suggestions are separate from the records in a product index. A product index contains products, prices, attributes, and inventory data. A Query Suggestions index contains phrases that can be presented before the user submits a search. Selecting a suggestion

Autocomplete Is More Than a Text Box

In a WooCommerce store, autocomplete is often treated as a small search-field enhancement. That approach leaves substantial value on the table. A well-designed Algolia autocomplete experience can guide shoppers, expose product categories, surface popular queries, and help customers reach the right product before they submit a full search. Autocomplete is an interface, not just an input A basic implementation waits for a shopper to type a phrase and then displays matching products. A production implementation treats each keystroke as an opportunity to provide useful, structured results. For example, a shopper entering run could receive: Product suggestions such as running shoes and running jackets Category suggestions such as Running Shoes Query suggestions such as running shoes for flat feet Brand suggestions such as RunFast Recent searches

Why Your Search Results Are Relevant — But Still Feel Wrong

A search results page can be technically relevant and still disappoint shoppers. The query may match the product title, description, or attributes, yet the products shown first do not match the shopper’s intent, expectations, or buying context. For WooCommerce stores, this usually happens because relevance is being measured as text similarity while shoppers judge the result by usefulness. A customer searching for black running shoes may technically receive black shoe products, but they may expect adult sizes, in-stock items, popular brands, and products suitable for running—not black dress shoes or accessories. Relevance is not the same as usefulness Algolia can identify records that match a query, but the ranking configuration determines which matching records appear first. If the index contains incomplete attributes, inconsistent values, or

Stop Words, Plurals and Natural Language

WooCommerce shoppers rarely search in the same structured language used by a product catalog. They may enter waterproof hiking boots, boot for hiking, or hiking boot and expect substantially the same products. Algolia can account for some of these variations through stop-word removal and plural handling, but the settings must be configured with the catalog language and business vocabulary in mind. Stop words are useful query noise, not universal noise Stop words are common words that often add little value to a product search. In an English query, words such as the, a, an, and for may not distinguish one product from another. Algolia’s removeStopWords setting allows the engine to ignore language-specific stop words during search. For example, removing for can make shoes for trail

Synonyms: The Simplest Way to Improve Search

When shoppers use a different word from the one stored in your WooCommerce catalog, a technically correct search can still return poor results. A customer may search for sneakers while the product title says trainers, or search for hoodie when the catalog uses sweatshirt. Algolia synonyms solve this mismatch without changing product data. They allow multiple search terms to match the same records, making them one of the fastest improvements an agency can deliver for an existing store. What synonyms do in Algolia A synonym tells Algolia that two or more terms should be treated as related during search. For example, a synonym group containing sneakers and trainers can make products indexed with either term discoverable from both searches. This is different from typo tolerance.

How to Rank Content by Popularity

Popularity ranking is useful when shoppers want to discover what other customers buy most often, rather than finding a product that matches a highly specific query. In Algolia, the usual implementation is to index a numeric popularity signal and use that signal in customRanking. Choose a popularity signal A popularity value should represent meaningful customer interest. For a WooCommerce store, possible inputs include completed orders, units sold, product detail views, add-to-cart events, or a weighted combination of these signals. A simple lifetime sales count is easy to implement, but it tends to favor older products permanently. A time-bounded or decayed metric is usually more useful: popularity = (orders_30d * 10) + (add_to_carts_30d * 3) + (views_30d * 0.1) Calculate this value in the data pipeline

How to Rank Products by Sales in Algolia

WooCommerce stores can use sales performance as a relevance signal so that popular products appear before less frequently purchased products when search results have similar textual relevance. In Algolia, the usual implementation is to index a numeric sales attribute and add it to the index’s custom ranking configuration. Choose the sales metric Before changing the ranking, define exactly what “sales” means. Common options include lifetime units sold, units sold during a recent period, gross revenue, or net revenue after refunds. Lifetime units are simple, but they can cause older products to dominate indefinitely. A rolling 30-day or 90-day metric is often more useful for merchandising because it reflects current demand. For a WooCommerce catalog, a practical attribute might be named sales_count_30d. Keep the value numeric

Popularity vs Relevance: Which Should Win?

For WooCommerce search, the choice between popularity and relevance is not always either-or. Relevance determines whether a product matches the shopper’s intent, while popularity can help decide which of several relevant products should appear first. The safest approach is to make relevance the foundation and use popularity as a controlled ranking signal. Otherwise, best-selling products can dominate results even when they are only loosely related to the query. Why relevance should come first When a shopper searches for waterproof hiking boots, the results should primarily reflect the words, attributes, categories, and searchable fields associated with that request. A popular product that is not waterproof should not outrank a highly relevant product simply because it has more orders. Algolia’s textual relevance ranking evaluates signals such as

Custom Ranking: Put Your Best Products First

Search relevance answers the question “which products match this query?” Business ranking answers a different question: “which matching products should appear first for this store?” In WooCommerce, custom ranking lets an agency apply that second layer consistently across product listings without hard-coding product IDs or manually reordering every result. What custom ranking does in Algolia Algolia’s customRanking setting adds business-oriented ranking criteria after the main textual relevance criteria. It is most useful when several products are similarly relevant to a query and the store needs a predictable tie-breaker. Custom ranking criteria are evaluated in the order in which they are configured. For example, the following configuration prioritizes featured products, then popularity, then profit margin: customRanking: [ "desc(is_featured)", "desc(popularity_score)", "desc(margin_score)" ] With this configuration, a product

Why the Order of Searchable Attributes Matters

In Algolia, the order of searchableAttributes is part of the relevance strategy. It tells Algolia which product fields should receive priority when a query matches more than one attribute. For a WooCommerce catalog, placing the product title before the description can make the difference between a useful result set and a list dominated by incidental keyword matches. How searchable attribute order affects ranking Consider a search for leather wallet. The terms might appear in a product title, brand, category, SKU, short description, or long description. If all of those fields are searchable, Algolia still needs to determine which matches are most important. With the default attribute ranking behavior, attributes listed earlier in searchableAttributes have higher priority than attributes listed later. A match in a product

Words vs Proximity: How Algolia Understands Queries

For WooCommerce stores, a shopper’s query is rarely an exact product title. A search such as waterproof trail shoes may match product names, categories, attributes, descriptions, and synonyms. Algolia’s ranking system evaluates both how many query words a record matches and how close those words appear to one another. These concepts are related, but they solve different problems. What Algolia means by “words” The words ranking criterion rewards records that match more of the words in the query. If a shopper searches for waterproof trail shoes, a product matching all three terms generally has an advantage over one matching only shoes. This is a relevance signal, not a simple exact-string comparison. Algolia tokenizes the query and searches for matching terms across the configured searchableAttributes. The

Exact Match vs Partial Match

Search behavior has a direct effect on product discovery, conversion rate, and support volume in WooCommerce stores. A shopper searching for hoodie should usually find hoodies, while a shopper searching for a highly specific SKU may expect only an exact result. Algolia can support both behaviors, but exact and partial matching solve different problems and should not be treated as interchangeable. What exact matching means in Algolia Exact matching means that the query term matches a complete indexed word or a deliberately constrained query expression. For example, a search for SKU-4812 should favor a product containing that complete identifier rather than products containing only a similar prefix. In Algolia, exactness is primarily influenced by the engine’s ranking and matching configuration. The exact ranking criterion helps

When Typo Tolerance Makes Search Worse

Typo tolerance is intended to rescue shoppers who search for “sneekers” instead of “sneakers” or “iphnoe” instead of “iPhone.” In a WooCommerce catalog, however, the same behavior can make search less useful when every character matters. Product codes, model numbers, sizes, measurements, and brand names often contain short tokens where a one-character edit changes the intended product completely. Why more matches can mean worse search Algolia can find records that differ from the query by one or more character edits. This is valuable for natural-language product searches, but it can reduce precision for structured catalog terms. SKU searches: A query such as ABC-123 may match ABC-128 after typo tolerance is applied. Model numbers: X100 and X110 may represent different generations or accessories. Sizes: A search

Typo Tolerance: Why Algolia Still Finds ‘Iphoen’

Customers do not search like database administrators. They type quickly on mobile keyboards, miss adjacent letters, omit characters, or submit a query before noticing a spelling mistake. Algolia’s typo tolerance is designed to keep those searches useful. That is why a query such as Iphoen can still return products containing iPhone. What Algolia sees in “Iphoen” The difference between Iphoen and iPhone is an adjacent transposition: the final two letters appear in the wrong order. Algolia treats this type of edit as a typo and can match the query to the indexed product text when typo tolerance is enabled. Conceptually, the search engine compares the query tokens with indexed tokens using edit-distance-style rules. Depending on the token length and configuration, an accepted variation can include

The 8 Criteria Algolia Uses to Rank Results

Algolia does not rank WooCommerce search results with one blended relevance score. Its default ranking formula evaluates records against an ordered list of criteria. The first criterion that distinguishes two records determines their order; later criteria are used only when earlier criteria are tied. For a WooCommerce catalog, this means a product with fewer typos can outrank a product with stronger merchandising rules, because typo is evaluated before custom. Understanding the order is essential when diagnosing why a product appears lower than expected. The eight Algolia ranking criteria 1. Typo typo measures how many spelling corrections Algolia must make to match a record. Exact spellings rank ahead of one-typo matches, and one-typo matches rank ahead of records requiring more corrections. For example, a search for

Understanding Algolia’s Ranking Formula

Algolia’s ranking formula determines which records appear first when multiple products match a shopper’s query. For WooCommerce stores, understanding this formula is essential when merchandising products, debugging unexpected results, and explaining search behavior to clients. Ranking is a sequence of tie-breakers Algolia does not normally calculate one simple weighted score for every product. Instead, it evaluates ranking criteria in order. A record that performs better on an earlier criterion ranks ahead of another record, even if the second record performs better on a later criterion. The default ranking order is: Typo: Records matching the query with fewer typos rank higher. Geo: Records closer to the relevant location rank higher when geo-search is configured. Words: Records matching more query words rank higher. Filters: Records matching more

What Does Relevant Actually Mean in Search?

In ecommerce search, “relevant” does not simply mean “contains the words the shopper typed.” A relevant result helps a shopper complete the task implied by the query, in the context of the catalogue, the store, and the shopper’s commercial intent. For a WooCommerce store, that distinction matters. A search for black running shoes should not return every product whose description mentions “running,” followed by unrelated accessories. A search for iPhone 15 case should prioritize compatible cases, not products with the highest overall sales. A search for gift for dad may require merchandising or curated results because the query expresses an occasion rather than a precise product attribute. Relevance is a relationship between query and intent Search relevance is best understood as the degree to which

How to Build a Reliable Algolia Indexing Pipeline

A reliable Algolia indexing pipeline should treat the search index as a projection of WooCommerce data, not as the primary data store. WooCommerce remains the source of truth for products, variations, prices, stock, visibility, and taxonomy relationships. Algolia receives controlled updates, processes them asynchronously, and exposes a fast read model for search. Define the indexing contract first Before implementing hooks or workers, define exactly which WooCommerce entities become Algolia records and how each record is identified. For many catalogs, one record per searchable product is appropriate. For variation-heavy stores, one record per variation may provide better filtering and merchandising control. Use a stable, deterministic objectID. A product-based index might use product_12345, while a variation-based index could use variation_12345. Do not generate random IDs during each

Browse vs Search: Two Very Different Operations

In Algolia, Search and Browse may both return records from an index, but they solve fundamentally different problems. Confusing them can lead to slow catalog imports, incomplete exports, poor shopper experiences, or unnecessary search infrastructure costs. Search is for finding relevant products Use the Search API when a shopper submits a query or changes a discovery control such as a facet, filter, sort option, or pagination page. Algolia evaluates the query against the index and applies its ranking configuration, including textual relevance, typo tolerance, custom ranking, synonyms, and other search settings. A WooCommerce product search might send a request similar to this: const response = await index.search('waterproof hiking boots', { filters: 'stock_status:in_stock AND price <= 200', facets: ['categories', 'brands', 'pa_size'], hitsPerPage: 24, attributesToRetrieve: [ 'objectID',

How to Import Millions of Products Into Algolia

Importing a few thousand WooCommerce products into Algolia is straightforward. Importing several million products, variations, inventory records, and taxonomy combinations requires a controlled indexing pipeline. The important design decisions are record shape, batching, concurrency, retries, incremental updates, and how you switch from an old index to a newly built one. Define the Algolia record before building the importer Do not send the entire WooCommerce product object to Algolia. Search records should contain the fields required for retrieval, filtering, sorting, merchandising, and display. Keep large descriptions, internal metadata, and fields that are never queried out of the index. A product record might look like this: { "objectID": "product_48291", "type": "product", "product_id": 48291, "sku": "SHOE-48291", "name": "Trail Running Shoe", "slug": "trail-running-shoe", "brand": "Example Brand", "categories": ["Men", "Shoes",

Incremental Indexing vs Full Reindexing

For a WooCommerce search implementation, the choice between incremental indexing and a full reindex affects deployment time, search freshness, API usage, and operational risk. Most agencies should use incremental updates for normal catalog activity and reserve full reindexing for controlled maintenance or structural changes. What incremental indexing means Incremental indexing sends only the records that changed since the previous synchronization. A product update, inventory change, price change, taxonomy edit, or product deletion produces a corresponding Algolia operation instead of rebuilding the entire catalog. For example, when product 7421 changes price, the integration can update that product record with an operation such as partialUpdateObject. When the product is permanently removed or becomes unavailable for search, the integration can issue a delete operation for the same objectID.

How to Keep Algolia in Sync With WooCommerce

Keeping WooCommerce and Algolia synchronized requires more than sending a product record whenever a product is saved. A reliable integration must account for catalog changes, inventory updates, variations, deletions, visibility rules, failed requests, and the asynchronous nature of Algolia indexing. Define the source of truth WooCommerce should remain the source of truth for product data. Algolia should contain a search-optimized projection of that data, not a second catalog that store managers edit independently. Before implementing synchronization, document which WooCommerce fields are authoritative and which values are derived for search. A typical product record may include: Identity: product ID, SKU, slug, and product type. Display data: name, description, permalink, images, categories, and brands. Commerce data: price, regular price, sale price, currency, and stock status. Filtering data:

One Index or Multiple Indexes?

Choosing between one Algolia index and multiple indexes affects search quality, operational complexity, analytics, and deployment safety. For WooCommerce agencies, the right decision usually depends on whether the records share the same search experience, ranking strategy, permissions, and lifecycle. What an Algolia index represents An Algolia index is a searchable collection of records with its own configuration. That configuration can include searchable attributes, ranking criteria, custom ranking, synonyms, facets, typo tolerance, rules, and replicas. For a WooCommerce product catalog, an index record might contain a product ID, title, description, categories, attributes, price, stock status, image URL, and variation data. The index should contain the information required by the search interface rather than being a direct copy of the entire WordPress database. Use one index when

Why Your Index Structure Matters More Than You Think

In a WooCommerce search implementation, the index is not merely a copy of the product catalog. It is the structure that determines what Algolia can match, filter, sort, rank, and return quickly. A well-designed index can make a modest catalog feel precise and responsive. A poorly designed one can produce irrelevant results, expensive indexing jobs, awkward facet behavior, and search interfaces that require constant exceptions. What the index structure controls Algolia searches records, not WooCommerce objects. Each record is a JSON document with an objectID and the attributes needed by the search experience. The decisions made when transforming products into those records affect several parts of the application: Relevance: The fields available to search, and their order in searchableAttributes, influence which products rank first. Filtering:

Searchable Attributes: The Most Important Setting You’ll Configure

For a WooCommerce search experience, few settings have as much influence as searchableAttributes. This setting tells Algolia which product fields can match a query and, just as importantly, establishes the priority of those fields. If a shopper searches for a product name, SKU, category, or brand, the result quality depends on whether that value is indexed as searchable. Adding more fields is not automatically better. A broad, poorly ordered configuration can make descriptions outrank product names or cause weak matches to appear above highly relevant products. What searchableAttributes controls Algolia evaluates the fields listed in searchableAttributes when matching text queries. The order of the attributes affects relevance: an attribute listed earlier generally has more importance than an attribute listed later when other ranking criteria are

What Should You Put in an Algolia Index?

Designing an Algolia index is not the same as exporting your WooCommerce database. An index should contain the smallest useful search document for the experiences your store needs to support: product discovery, filtering, sorting, merchandising, autocomplete, or a combination of these. For an agency, the right schema usually begins with the storefront search requirements rather than with the fields available in WordPress. Start with the Search Experience Before selecting fields, document what shoppers must be able to do. A typical WooCommerce catalog may require shoppers to: Search product names, SKUs, brands, categories, and selected specifications. Filter by price, stock status, brand, category, size, color, or other attributes. Sort by relevance, price, newest products, popularity, or rating. See product cards with the correct image, price, sale

How to Design the Perfect Algolia Record

An Algolia record should be shaped around the way shoppers search, filter, sort, and select products—not around the entire WooCommerce product payload. A strong record is deliberately small, stable, and explicit about the values that matter to the search experience. Start with one clear indexing unit Decide whether an Algolia hit represents a product, a variation, or another sellable unit before writing the feed. For most WooCommerce stores, a product-level record is the best default when shoppers select size or color on the product page. A variation-level record is more appropriate when each variation has its own stock status, price, image, URL, or search relevance. Use a stable objectID. It should not change when a product title, price, or taxonomy changes. A WooCommerce product ID

The 5 Algolia Concepts You Need to Understand First

Before connecting Algolia to a WooCommerce store, it helps to understand the objects and decisions that control how search behaves. Algolia is not a drop-in replacement for the WordPress or WooCommerce database query layer. It is a hosted search engine that receives prepared product data, builds an index, and answers search requests against that index. The following five concepts provide the foundation for designing a reliable WooCommerce integration. 1. Indexes Are Searchable Product Collections An Algolia index is a collection of records that can be searched. For WooCommerce, an index commonly represents a product catalog such as products_production or products_staging. An index is more than a database table. Its settings determine which fields are searchable, which fields can be used for filtering, how results are

When Should You Use Algolia?

Algolia is most useful when WooCommerce search is a core part of the buying journey rather than a secondary navigation feature. It can provide fast, typo-tolerant search, faceting, filtering, autocomplete, merchandising controls, and analytics without requiring the WordPress database to handle every complex product query. Use Algolia When Search Drives Product Discovery Algolia is a strong candidate for stores where customers search by product name, SKU, specification, compatibility, brand, or category. This is especially common in large catalogs, wholesale stores, parts suppliers, and stores with technical products. For example, a customer searching for bosch gsb 18v drill may expect results for spelling variations, related product titles, product attributes, and compatible accessories. A basic WordPress or WooCommerce query may return incomplete results or require expensive database

Algolia vs Database Search: What’s the Difference?

WooCommerce stores commonly start with database-backed search and later add Algolia when shoppers need faster, more relevant product discovery. These systems solve related problems, but they operate at different layers and have different strengths. What database search means in WooCommerce Database search runs a query against WordPress and WooCommerce data, usually in MySQL or MariaDB. Product names, SKUs, descriptions, attributes, taxonomies, prices, stock status, and custom fields are stored in relational tables and queried when a shopper submits a search. A basic implementation may use a query equivalent to: SELECT ID, post_title FROM wp_posts WHERE post_type = 'product' AND post_status = 'publish' AND post_title LIKE '%boots%'; Production WooCommerce searches are usually more complex. They may join product metadata, lookup tables, taxonomy relationships, visibility rules, multilingual

One Index or Multiple Indexes?

The decision to use one Algolia index or several should follow the search experience, data boundaries, and operational requirements of the WooCommerce store. It should not be based only on how the catalog is organized in WordPress. What an Algolia index represents An Algolia index is a searchable collection of records with its own settings, searchable attributes, ranking configuration, synonyms, rules, and replicas. In a WooCommerce implementation, an index might contain products, product variations, blog content, documentation, or records from several stores. The right design starts with the question: Do these records need to be searched, ranked, filtered, secured, and maintained in the same way? If the answer is yes, a shared index is often simpler. If the answer is no, separate indexes may be

Why Your Index Structure Matters More Than You Think

Index structure is a search decision, not a database export For a WooCommerce store, an Algolia index should be designed around the questions shoppers ask, not around the tables produced by WordPress and WooCommerce. A product record that mirrors every post field, taxonomy relationship, and metadata value may look convenient, but it often produces large records, inconsistent relevance, and difficult facet behavior. Start by defining the search experience. If shoppers need to find products by name and SKU, filter by brand and size, and sort by price or popularity, the index should contain those values in a predictable shape. Data that has no role in search, filtering, ranking, display, or analytics usually does not belong in the record. A practical WooCommerce product record A product

Searchable Attributes: The Most Important Setting You’ll Configure

Why searchable attributes matter searchableAttributes determines which indexed product fields Algolia examines when a shopper enters a query. In a WooCommerce store, this setting has a direct effect on whether customers find the right product quickly—or receive results dominated by irrelevant descriptions, internal data, or low-value matches. This is not a list of fields that should merely exist in your product records. It is a deliberate ranking strategy. The order of the attributes determines which matches are considered more important when Algolia ranks results. For example, a search for blue running shoes should normally prioritize: A product title containing the phrase A brand or product type match A category match Relevant descriptive copy Supporting fields such as SKU or model number A practical WooCommerce configuration

What Should You Put in an Algolia Index?

Start with the customer’s search experience An Algolia index should contain the product information shoppers need to discover, compare, and select items. It should not be a copy of every column in the WooCommerce database. For an agency project, define the search and browsing experiences first: Which product fields should match a query? Which attributes should customers use as filters? Which values should appear in search results, autocomplete, and category pages? Which products, prices, or stock states must be hidden from a shopper? The answers determine the index schema. Keeping the schema focused reduces record size, simplifies synchronization, and makes ranking easier to manage. The minimum product record Every Algolia record needs a stable objectID. In WooCommerce, this is commonly the product ID, provided that

Records, Objects and ObjectIDs: The Algolia Basics

Why the record is the unit of search Algolia does not index a WooCommerce product, post, or database row directly. It indexes a JSON document called a record. Each record contains the fields Algolia can search, filter, display, or use for ranking. For a simple WooCommerce product, a record might look like this: { "objectID": "product_4821", "name": "Merino Wool Travel Socks", "slug": "merino-wool-travel-socks", "description": "Lightweight merino socks designed for travel and everyday wear.", "brand": "North Ridge", "categories": ["Clothing", "Socks"], "price": 24.99, "inStock": true, "image": "https://example.com/uploads/merino-socks.jpg", "url": "https://example.com/product/merino-wool-travel-socks/" } This is separate from the underlying WordPress wp_posts, post metadata, taxonomy tables, and WooCommerce lookup tables. Your indexing process selects the product data that should be available to the search experience and transforms it into an Algolia

The Anatomy of an Algolia Index

What an Algolia index contains An Algolia index is a collection of JSON records that Algolia searches and ranks. For a WooCommerce store, an index commonly represents a searchable product catalog, but it can also contain categories, brands, blog posts, or other content types. An index is not a direct mirror of a WooCommerce database table. It is a search-optimized, denormalized representation of the data customers need to discover products. A single product record might include its name, SKU, brand, category hierarchy, prices, stock status, image URLs, and selected attributes in one document. Records and objectID Each item in an index is a record. Records are JSON objects, and every record must have a unique objectID. Algolia uses this value to identify records when updating,

What Is Algolia Really Good At?

Fast product discovery at scale Algolia is particularly strong when a WooCommerce store needs to help shoppers find products quickly across a large or complex catalog. It is a hosted search service built for low-latency responses, so it can return matching products while a customer types rather than waiting for a full page reload or a slow database query. This is useful for stores with thousands of products, multiple variations, technical specifications, or inconsistent customer terminology. A search for wireless drill can return relevant products before the shopper has finished typing, while a search for dril can still produce useful results through typo tolerance. Search experiences that feel responsive Algolia works well for autocomplete and search-as-you-type interfaces. A WooCommerce implementation can show product suggestions, categories,