Key takeaways
- A useful synonym map connects the words shoppers enter with the terms used in product titles, descriptions, product types, tags, and merchandising language.
- Every proposed synonym needs an ambiguity rating because equivalent words in one product category can represent different buying intents in another.
- Seasonal terms need activation and review dates so temporary campaign language does not remain in search configuration after the relevant collection or inventory disappears.
- Synonym requests should move through proposed, tested, approved, and retired statuses rather than going directly from a message or meeting into live search.
- Merchandising teams should test synonyms against named queries and expected products, not judge them by whether the configuration accepts the terms.
This Shopify Search & Discovery synonyms template turns an unstructured word list into a working queue for merchandising teams. Copy the columns below into a spreadsheet, add terms from search reports and customer language, then assign an owner before configuring anything. The objective is not to collect every related word. It is to document which terms should produce overlapping products, where that relationship becomes unsafe, and when the decision needs another review.
How should a synonym map be structured?
Use one row per shopper-term and catalog-term relationship, then add five decision fields: shopper term, catalog term, ambiguity, seasonality, and review status. Evidence, owner, expected result, and next review date make the map maintainable when several people work on search.
Copy this starter table into a spreadsheet and replace the sample rows with language from your store:
| Shopper term | Catalog term | Ambiguity | Seasonality | Expected result | Evidence | Owner | Review status | Next review |
|---|---|---|---|---|---|---|---|---|
| couch | sofa | Low | Evergreen | Sofa category products | Repeated search wording | Search merchandiser | Proposed | 2026-09-15 |
| trainers | sneakers | Medium | Evergreen | Athletic footwear, not training equipment | Support and search wording | Footwear buyer | Needs test | 2026-09-15 |
| holiday dress | party dress | High | Nov-Dec | Current occasion dresses | Campaign terminology | Apparel merchandiser | Seasonal approval | 2027-10-01 |
Keep shopper terms in the form people actually use, including abbreviations and regional wording. Keep catalog terms aligned with the language that consistently identifies the intended products. Do not clean up a shopper phrase until it stops resembling the query that exposed the problem. If several shopper terms map to one catalog concept, create separate rows first. Merge them into a group only after each term passes the same relevance test.
Evidence should come before configuration
Start with failed or weak queries, not a brainstorming session. Review searches that return no products, searches that return an obviously incomplete set, and terms that customer support repeatedly translates into catalog language. A request such as adding tee as a synonym for T-shirt is actionable only when the team can name the expected products and exclusions.
For each candidate, save three items in the evidence column: the source, an example query, and the date observed. Then write the expected result before testing. For example, a store might expect the query trainers to return 24 athletic footwear products while excluding resistance bands and training guides. The number is not a universal target; it is a snapshot that makes later changes visible.
Use Shopify Search Relevance Testing: Build 25 Queries to create a repeatable query set. If the problem could involve indexing, product data, or theme presentation rather than terminology, follow the diagnosis sequence in Shopify site search: diagnose first before adding synonyms. Synonyms cannot correct unavailable products, misleading product data, or a broken results surface.
Ambiguity and seasonality determine the safe action
Rate ambiguity before approval: low means the terms are interchangeable across the relevant catalog, medium means they overlap within a category, and high means the shopper term could represent a different product intent. Low-ambiguity examples can move to testing quickly. Medium-ambiguity terms need category-specific expected results. High-ambiguity terms may be better handled through catalog wording, a dedicated collection, search merchandising, or no synonym at all.
Consider shell. An outdoor store might use it for waterproof jackets, while a home store might use it for decorative shells and a computing retailer for command-line products. Treating shell and rain jacket as universal equivalents could hide or dilute valid intents. Record that risk rather than forcing the row through approval.
Mark seasonality as evergreen, date-bound, or campaign-only. Date-bound rows need a start date, end date, and post-season review. Before a peak period, use the checks in Optimizing Shopify Search & Filter for Peak Sales Days to verify inventory, query behavior, filters, and merchandising together. Retire a seasonal relationship when its destination products are no longer stocked or when shoppers use the term differently outside the campaign window.
How do you turn approved rows into synonym groups?
Configure only rows that have an owner, an expected result, and a test status. Group terms by one stable product concept rather than by loose association. Sofa and couch may describe the same concept in a furniture catalog; sofa and living room should not be grouped merely because they are related. The second pair represents a product and a room-level shopping mission.
Use this operating sequence:
- Select a proposed row with evidence and a named expected result.
- Run the shopper term before making a change and record representative products, exclusions, and zero-result behavior.
- Configure the synonym relationship in the search system being evaluated.
- Repeat the same query on desktop and mobile result surfaces.
- Test every term in the group, plus one ambiguous query that should remain unaffected.
- Mark the row approved only when the intended products appear without introducing a more serious relevance problem.
Search behavior can involve native settings, theme presentation, predictive suggestions, and third-party search layers. The Shopify predictive search versus semantic search guide helps separate query interpretation from suggestion behavior. If native controls no longer match the store's search and merchandising requirements, compare those requirements with Hyper Search & Filter after completing the template.
Review status keeps the map operational
Use a controlled status list: proposed, needs test, approved, seasonal approval, rejected, and retired. Avoid vague labels such as done or review later because they do not tell the next operator whether a term is live, validated, or waiting for evidence. Every non-retired row should have one accountable owner and a review date.
As of August 2026, merchandising teams should still verify current Shopify behavior and field availability in official documentation before changing production search settings. Store configuration, themes, catalogs, and installed search tools vary, so the spreadsheet should record what was tested on the actual storefront rather than assume one setup applies everywhere.
Review approved evergreen rows quarterly or after a substantial catalog taxonomy change. Review seasonal rows four to six weeks before reuse, while there is time to correct product data and campaign naming. Reopen a row immediately when its expected product set changes, relevant products disappear, or an ambiguous result starts outranking the intended category. For a broader control decision, use Shopify Search & Discovery vs Hyper Search & Filter to compare requirements instead of choosing by synonym count alone.
FAQ
How do I use synonyms in Shopify Search & Discovery?
Use synonyms by defining a group of terms that should represent the same search concept, then test each term against the expected Shopify products. Start with a row from the template, confirm its ambiguity rating, and record baseline results before configuring the group. After the change, test all included terms and at least one nearby term that should not be affected. The exact controls and resulting behavior should be confirmed in the current Shopify interface and on the live theme used by the store.
Which Shopify products need synonym groups?
Products need synonym support when shoppers consistently use language that differs from the terms identifying those products in the catalog. Common candidates include regional terms, abbreviations, category jargon, older product names, and plain-language alternatives to technical names. Prioritize cases with no results or clearly incomplete results. Do not add a group merely because two words are associated; require evidence that shoppers use both terms for the same product intent.
How should I document Shopify search relevance examples?
Document each example with the query, test date, expected products, representative actual products, exclusions, result count, device, and pass or fail decision. Screenshots can help with investigation, but structured text is easier to compare during later reviews. Keep a fixed query set and rerun it after catalog, theme, or search configuration changes. The Shopify Search Relevance Audit Tool can help organize the wider assessment around those examples.
Where can I find Shopify Search & Discovery documentation?
Use Shopify's official Help Center and the guidance linked from the current Search & Discovery app interface. Check the publication or update date where one is shown, because available controls and terminology can change. Theme documentation may also be necessary when the issue concerns how search results, predictive suggestions, or filters are displayed. For an operational overview of the different control surfaces, see What Is Search and Discovery on Shopify? A Control Map.
