Menu
Managing search indexes
Create a search index, load data, try searches, set up agentic search and product questions, tune the results and track how it performs, all from the designer.
On this page
What a search index is
A search index is your own data (products, articles, FAQs, store locations) loaded so it can be searched by meaning as well as by exact words. A shopper asking for "something warm for hiking in the rain" gets sensible results without those words appearing in your product titles.
The Search page is where you set an index up, load data, try searches, tune the results and watch how it performs. Your workflows then read and write the index with the Search connector. There is no separate API to call.
Creating an index
Search → New search index takes three steps.
- What are you searching? Pick the closest template (products, articles, FAQs or locations), or choose Start from your own data: paste or upload a few example records and the fields are worked out for you.
- Fields. Review what each field is for and how results should look (title, picture, subtitle). Then say whether prices or availability differ by country, currency or customer group. If they do, add a segment for each one.
- Name. Choose how it appears in the designer and in workflow steps.
Everything can be changed afterwards.
What each field is for
Every field has a few purposes you can switch on:
- Understand meaning: searches find this by what it means, not only by its words. Best for titles and descriptions.
- Match words: the exact words typed are matched too. Good for names, brands and product codes.
- Filter by: narrow results to exact values, like a brand or a price limit.
- Show as choices: a list of the values available with a count for each, like a brand list.
- Sort by: order results by this field, like price or newest.
- Show in results: include the field in what search returns.
Products with variants (sizes, colours) keep those inside the product. A search for "red, size 10" only counts a product if one variant is both red and size 10.
The tabs
Overview
How the index is doing at a glance: how many documents you have, how many are ready to search, prices, and the last rebuild. Below that is how search is performing over the last 7, 30 or 90 days: the most common searches, searches that found nothing (the best place to start improving), speed, clicks and purchases, and experiment results. At the bottom are quality checks: a set of example searches with the results you expect, which you can run after any change to see whether search got better or worse. Use Refresh to reload it all.
Data
- Documents: everything in the index. Find a document by its key, filter by status, open one to see it as stored, and add or delete documents. Add data accepts JSON, CSV or pasted records. Sending a record that already exists updates it, so importing again is safe.
- Prices: appears once you have segments. Upload or paste prices per product (and variant), segment and amount. Sales can have start and end dates. Changing a price never needs a rebuild.
- Needs attention: documents that could not be added or searched, with the reason for each. Fix the record and send it again.
Segmentation
Lists your segments with their prices and segment values, and is where you create and change them. See Segmentation below for when to use them.
Try search
Type a search the way a shopper would and see what comes back, the same as a workflow would get. Narrow by filters and choices, switch segment, and open Why this result on any hit to see how it was found. Mark results as good or poor to build a test set, and pin or move down a result for that search.
Agentic search
Lets shoppers ask open-ended questions that an AI agent turns into a search. See Agentic search below.
Product questions
Writes likely shopper questions for each product and shows them on your product pages. See Product questions below.
Configuration
Three sections, chosen from the list on the left.
- Synonyms: words that mean the same, so a search for one also finds the other. Applied to what people type, no rebuild needed.
- Rules: for a particular search, show chosen products first, move others down, or hide them. Create a rule by saying when it applies: search words (exactly, or containing some words), filters (for example the category is Footwear), or both. At least one is needed. Then search for products in Find products and drag them into Show first, Move down or Hide, or between those lists. Preview opens a wide panel showing the search now next to the search with your rule, so you can check the result before saving. A rule can be given a start and an end date and time, such as for a flash sale, and turned off without deleting it.
- Ranking: how much to favour meaning versus exact words, how forgiving to be of typos, and boosts for things like newer or better-rated results. Save several versions and choose which is live. You can also compare two rankings on real visitors and see which gets more clicks and purchases.
Settings
- General: name and description.
- Fields: change what fields are for, add or remove fields, and choose how results look. Changes are reviewed before anything happens (see below).
- Rebuilds: rebuild now or on a schedule.
- Delete this index: permanent.
Changing fields safely
When you press Review changes you are told exactly what will happen:
- Applies right away: adding a field, changing what shows in results, changing which fields can be filtered or sorted. Search keeps working and nothing is rebuilt.
- Needs a rebuild: changing what a field means for search, its language or type, or how long text is split. The new version is built alongside the live one, checked, then switched to automatically. You'll see an estimate first.
- Not allowed: changes that would break existing data. The reason is shown.
Search is never interrupted. If more than one in ten documents would not fit the new structure, the rebuild stops and nothing changes; the documents that did not fit are listed under Needs attention.
Rebuilds
Settings → Rebuilds lets you rebuild at any time, for example after a big data fix, and to schedule it weekly, monthly or quarterly. You can require a quality check to hold before switching. Once the new version is live the old one is removed, so a rebuild cannot be undone; to change something back, change it and rebuild again.
Segmentation
Use segments when the same product is offered differently by country, currency or customer group. A search for a segment returns only what is sold there, at that segment's price in that segment's currency. Nothing is converted between currencies. Prices are kept apart from the product data, so updating them is quick and never triggers a rebuild.
The Segmentation tab lists your segments with their prices and segment values. A saved segment's key and currency cannot change because existing prices are in that currency; add a new segment instead. Its settings have three parts:
- Segment key selection: which fields prices and segment values refer to. The variant key is a field inside any list on the product, like a variant's sku; choosing it makes that list the variants. The product key prices a product that has no variants as a whole, and defaults to the document key. Changing either rebuilds the index.
- Segment attributes: what describes each segment, like country or channel, for finding segments and choosing one in a search.
- Per-product fields: product data that differs per segment, like delivery time, searched with the chosen segment's value.
Agentic search
Experimental. Lets a shopper ask an open-ended question, like "best-reviewed waterproof jackets under $200", and an AI agent plans and runs the search for them. It is not available on every search setup yet.
- Open Agentic search and choose a Provider: Included model (managed for you, nothing to set up and no separate bill), or OpenAI or Anthropic with your own account.
- For your own account, choose a Connection of that type (Manage connections opens the list) and enter the model's exact name as that provider expects it in API requests.
- Select Enable agentic search. The status shows Enabling…, then Ready. If it shows Error, the reason is listed; fix it and enable again.
Once it is Ready, Try it lets you ask a question and see the full result. Each question is independent for now, with no memory of the one before. Disable turns it off again.
This is separate from Building an assistant, which is for chat assistants that can use an index.
Product questions
Writes the questions shoppers are likely to ask about each product, using only what the index knows about it, so your product page can offer them as one-click prompts. It has three panels.
Settings
- Write questions for this index: when on, questions are written for new and changed products automatically. Unchanged products, and questions you edited by hand, are left alone.
- Questions: how many per product, from 1 to 10.
- Language: leave empty to match the product.
- Fields to use: leave empty to use everything. Pick a whole group, or just some fields inside it. Leave out stock and price so they don't trigger rewrites.
- Guidance: optional, up to 1,000 characters, for what matters to your shoppers, for example "Focus on fit and fabric. Never ask about price."
- Model: the included model costs nothing extra, or use your own connection and model.
Once on, you see how many products there are, how many have questions, how many were edited by hand and how many need attention. Write for all products skips products whose questions are already up to date. Rewrite everything writes every product again from scratch, including ones you edited, and asks you to confirm because it can't be undone. Questions are written in the background, so numbers update as it goes.
Your store has an allowance of products that can have questions, shown across all indexes. When it is reached, new products don't get questions but products that already have them stay up to date. If the feature isn't included for your store, contact your organisation owner or upgrade your plan.
Data
Every product with its questions. Find a product by its key, or filter by Ready, Edited by hand or Needs attention. Open a product to reword a question, drag to reorder, remove one or add your own. Editing a product's questions marks it Edited, and automatic updates then leave it alone. A product that needs attention shows why the last attempt failed; run Write for all products again to retry it.
Storefront widget
Shows the questions on your product pages. Your workflow decides what to return and the widget draws it. Set it up in the order of the panel:
- Where questions come from: choose the workflow, its endpoint and method, the Product parameter the product id or SKU is sent under (put it in the path as
:sku, or send it as a parameter), and, only for an unusual response, where the questions are in it. - When a shopper clicks a question: Let my page decide sends a click event your page can listen for; Show an answer from my workflow calls a second endpoint with the product, the question, its id and its topic, and shows the text it returns under the question; Ask my AI assistant opens the assistant chat on the page and asks it there.
- Look and feel: start from a preset, then choose the layout (chips, list or cards), chip style, theme (light, dark or match the device), title and subtitle, colours, how many questions to show, corner rounding, font, icon, topics and animation. A live preview updates as you change them.
- Add it to your product page: choose the website domain and API domain, copy the snippet, and replace the product placeholder with your platform's product id or SKU. Save the widget first, otherwise it uses the default style. Variants and click events has a second snippet for scripting.
To read the same questions inside a workflow, use Get Product Questions in the Search connector.
Typical setup
- Create the index from a template, or from a few example records.
- Check what each field is for, especially Understand meaning.
- Add data from Data → Add data, or build a workflow that fetches your products and writes them with Upsert Documents.
- Watch Data → Needs attention until it is empty.
- Try some real searches in Try search, and fix what looks wrong in Configuration.
- Add a Search step to a workflow (or Search Multiple Indexes to search products and content together, see the Search connector), or expose the index to an assistant via an MCP server.
- Optionally turn on Product questions and add the storefront widget to your product pages.
- Use the Overview to see what people search for and where nothing is found.
Deleting an index
Deleting removes the index, every document in it, its prices, rules and history. It cannot be undone, and any workflow step still pointing at it will start failing.
Last updated 15 October 2026