> For the complete documentation index, see [llms.txt](https://knowledgebase.ajaxsearchpro.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.ajaxsearchpro.com/miscellaneous/woocommerce/search-product-attributes.md).

# Search product attributes

 WooCommerce product attributes are actually stored as custom fields (post meta) and terms, therefore it’s possible to search them very easily.

## Solution 1 – using regular engine (default)

The easiest and most convenient solution is to enable the search in all custom fields and the search in terms. Both options can be found on the *General Options -> Sources* panel:

![](/files/-MB-GsGXuJs1rh9v7Jrh)

## Solution 2 – using the index table engine

In case you are using the [index table engine](https://goo.gl/ooNYPY), you can be more selective about which fields you want to index. Most product attributes are stored as taxonomy terms, while some built in ones like the product SKU is stored as a custom field.

On the index table options panel you will be able to find them easily. The product SKU is stored as *“\_sku”* on the custom fields list, others may start with "pa\_" or "attribute\_" or "attribute\_pa\_".

The taxonomy based product attributes are the ones that start with the *“product – “* prefix:

![](/files/-MB-HZ2lvl6WSRuXL7br)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://knowledgebase.ajaxsearchpro.com/miscellaneous/woocommerce/search-product-attributes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.