> For the complete documentation index, see [llms.txt](https://search.guides.reactify.com.au/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://search.guides.reactify.com.au/manage/product/metafields.md).

# Metafields

## Use Metafields for Search & Merchandising

Reactify Search supports Shopify metafields, enabling merchants to enhance product search and merchandising capabilities.

<figure><img src="/files/ZPjsKX6nihmiDpEzqTxT" alt="" width="375"><figcaption></figcaption></figure>

## How Metafields Can Be Used

Once indexed, metafields become available for various configurations, providing more control and customisation, including:

* Faceting in Filters
* Curation Boosting Rules
* Search Result Relevance

### **Faceting in Filters**

Use metafields to create custom filter options for better product discovery.

<figure><img src="/files/DtOWcCuZ57vn8LsJfmAS" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/UFVcE3p5KkspMuilUrN9" alt=""><figcaption></figcaption></figure>

### **Curation Boosting Rules**

Apply boosting rules based on metafield values to prioritise products.

<figure><img src="/files/VN1W33v6hX730a2VW2Wd" alt=""><figcaption></figcaption></figure>

### **Search Result Relevance**

Enhance search accuracy by factoring in specific metafield data.

<figure><img src="/files/Pk8XFFHojVVr83hXVtel" alt=""><figcaption></figcaption></figure>

## Metafields in Curation Cards

Metafields appear alongside key fields like inventory and publish date in curation cards, giving merchants comprehensive data whilst drag-and-drop merchandising.

<figure><img src="/files/NLFz1Cm3ZXRgaryXh3P6" alt=""><figcaption></figcaption></figure>

## Adding Metafields to Reactify Search

1. In the Reactify Search app, navigate to **Manage > Product > Metafields**.
2. Enter the desired metafield namespaces in the provided field to enable indexing.

#### Example Setup

**Metafield Name**: `metafield_feature`\
**Metafield Namespace and Key**: `custom.metafield.feature`\
**Namespace**: `custom`

In Reactify Search, only the **namespace** (`custom`) needs to be entered in the Metafields field in the app. This ensures the relevant metafield data is indexed and ready for use across search and merchandising features.

<figure><img src="/files/zC4VNqzayTyg6GemWcqd" alt=""><figcaption><p>In Shopify, there's a metafield for <code>Feature</code> and <code>Colour</code></p></figcaption></figure>

<figure><img src="/files/hBhphqMGqf2uBM5cf0xS" alt=""><figcaption><p>In Shopify, the metafield's <strong>namespace</strong> <code>custom</code> will need to be entered in the Metafields field in the app</p></figcaption></figure>

<figure><img src="/files/lfls1A5qYiNWj3Sgtqo5" alt=""><figcaption><p>In the Reactify Search, navigate to <strong>Manage > Product > Metafields</strong> then add <code>custom</code></p></figcaption></figure>


---

# 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, and the optional `goal` query parameter:

```
GET https://search.guides.reactify.com.au/manage/product/metafields.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
