Key takeaways
- A saved Shopify Search & Discovery setting does not guarantee a visible storefront change; the published theme and assigned template must render the relevant search, filter, or recommendation surface.
- Search failures, collection-filter failures, and product-recommendation failures need separate test paths because each surface uses different catalog data and storefront components.
- Troubleshooting should begin with one reproducible symptom, one URL, and one controlled change rather than an app reinstall or several simultaneous configuration edits.
- Replacing Shopify Search & Discovery makes sense only after confirming that the issue is a capability gap rather than an access, catalog, theme, publication, or configuration problem.
When the query Search and Discovery app Shopify not working describes your issue, record the affected URL, published theme, template, device, test term or filter, expected result, and actual result. As of August 2026, this symptom-led process is safer than treating every product-discovery problem as an app failure. Work through the 12 checks in order, but stop as soon as the evidence identifies a responsible layer and owner.
Which storefront surface is actually failing?
Start by classifying the symptom as an admin, search, filtering, or recommendation problem. These surfaces may feel connected to a shopper, but they do not fail for the same reasons. A missing collection filter does not prove that keyword search is broken. A missing recommendation block on a product page says little about search or collection navigation.
Check 1: Create a controlled reproduction. Open the published storefront in a private browser window. Test one URL and one action, such as searching for navy linen shirt, selecting Size M in a collection, or opening a known product page. Record the result, then repeat the same action on mobile and desktop without changing the configuration between attempts.
Use the symptom to choose the first investigation:
- If the app page will not open or a setting will not save, start with admin access and browser state.
- If search returns no products, irrelevant products, or an unexpected order, test search queries and product eligibility.
- If filter values are absent, empty, or ignored, test the collection and search-results templates.
- If related or complementary products are absent, test the assigned product template and visible recommendation block.
- If the problem occurs only on one theme, market, device, or template, treat it as a rendering or publication issue first.
Agencies should request the storefront URL, test steps, and a screen recording before asking for collaborator access. That evidence can distinguish an admin misunderstanding from a shopper-facing defect and prevents an unnecessary theme edit.
Admin access and saved state come first
Confirm that the affected user can open the correct Shopify store, access the app, edit its settings, and save one controlled change. Browser trouble inside Shopify admin and storefront rendering trouble are separate incidents, even when they appear at the same time.
Check 2: Isolate admin access. Confirm the store identity and user permissions. If the app does not load, try a private window and a second browser, then temporarily disable extensions that alter scripts, cookies, or privacy behavior. Do not uninstall an app merely because one browser session fails. Use the Shopify Search & Discovery login and access checklist when the problem occurs before a storefront test is possible.
Check 3: Verify that a deliberate change persists. Change one low-risk setting, save it, leave the screen, and return. Confirm that the value remains. Note the change and time rather than relying on memory. If the value does not persist, stop storefront testing and resolve the access or save failure first.
Check 4: Confirm the published theme and assigned template. Merchants sometimes inspect an unpublished theme preview while customers use the published theme. They may also edit a default template while the affected product or collection uses an alternate template. Identify the live theme, assigned template, and exact storefront URL. If a saved configuration works in one theme but not another, the likely owner is the theme developer or agency rather than the catalog team.
Use a theme copy for diagnosis when a code change might affect shoppers. Reproduce the issue there, document the difference, and retain a rollback path before changing the published theme.
Search failures require query and catalog checks
A search problem should be tested with a fixed query set that separates product eligibility from query interpretation. One failed search term is not enough to diagnose the responsible layer. Use at least five queries: an exact product title, a product type or category phrase, an identifier such as a SKU if customers use one, a common synonym, and a deliberate misspelling.
Check 5: Establish a search baseline. Run all five queries in a private window and record the first five results. If an exact product title fails, inspect that product before changing synonyms or merchandising. Confirm that the product is active, available to the relevant sales channel, and eligible for the market and customer context being tested. Search tuning cannot surface a product that is unavailable on that storefront.
Check 6: Separate zero results from poor ranking. Zero results means no eligible item was returned. Poor ranking means the expected product exists but appears below less useful results. The first case calls for product eligibility, catalog terminology, and query interpretation checks. The second calls for a relevance and merchandising review. Use the same queries after every change; otherwise, the before-and-after comparison is unreliable. The Shopify Search Relevance Audit Tool can structure that test set.
Check 7: Test one vocabulary relationship. Choose a shopper term that differs from the catalog wording. Customers may search sofa while titles use couch, or trainers while product data uses sneakers. Configure only the intended relationship, save it, and rerun the same query. Avoid large groups of loosely related terms. Treating dress, skirt, formal, and party as equivalents may increase result counts while reducing precision.
If several recurring queries return nothing, record the failed terms before editing products. Fix repeat language mismatches first. The guide to fixing zero-result Shopify searches explains how to distinguish an unavailable product from a catalog vocabulary problem.
Collection filters fail across configuration, data, and theme layers
A Shopify collection filter appears only when its configuration, underlying product data, and theme rendering line up. Test those layers in that order. Removing and adding the same filter repeatedly will not repair missing product values or a template that does not expose filtering controls.
Check 8: Confirm filter enablement and page scope. Verify that the intended filter is configured, then test it on an affected collection and the storefront search-results page. Record whether the control is missing everywhere or only on one template. If it appears on search results but not on a collection, inspect the collection template. If it fails on both surfaces, return to configuration and data before editing theme code.
Check 9: Inspect the source data. Select three products that should produce a visible filter value. For a vendor filter, confirm that the vendor field is populated consistently. For options such as Size or Color, confirm that the relevant products and variants carry those exact option names and values. For a metafield-backed filter, inspect both the field definition and each product value. Blue, Navy, and Midnight remain separate values unless the chosen setup intentionally groups them.
Use known counts to test combinations. Suppose a collection contains 40 shirts, 12 are navy, and five navy shirts are Size M. Selecting Navy and M should return the five known eligible products. If Navy works alone but Navy plus M returns zero, the issue is combination-specific. Inspect the five products, the selection logic, and their storefront eligibility rather than declaring the entire filter system broken.
Check 10: Test the complete filter interaction. On mobile and desktop, open the controls, select a value, add a second value, clear each selection, use the browser back button, and reload or share the resulting URL. A hidden mobile drawer, obstructed apply button, stale selection, or unclear zero-product state can make technically functioning filters unusable. The Shopify Storefront Filtering Readiness Checklist provides a focused QA sequence. After repairing the defect, use Shopify search facet best practices to decide which values merit storefront space.
Recommendation changes need product-page evidence
Recommendation troubleshooting starts with the exact product page and visible block, not with a general storefront inspection. First determine whether the disputed items are related products, complementary products, or output supplied by the theme, custom code, or another app. Similar storefront labels can conceal different owners.
Check 11: Verify the block and product context. In the theme editor, identify the template assigned to the affected product and confirm that the relevant recommendation section or block is present. Test three products: the reported item, an established item with complete catalog data, and a newer or less complete item. Record whether the whole block is absent, the block appears but contains nothing, or products appear but differ from the merchant's expectation.
An absent block points toward the assigned template or theme rendering. An empty block calls for checking recommendation configuration and product eligibility. Unexpected choices may represent a merchandising expectation rather than a technical failure. Define the expected result precisely. Product A should show Product B as a complementary item gives the next owner something testable; recommendations look wrong does not.
If another app or custom theme code controls the same block, do not disable it on the published store without a rollback plan. Reproduce the issue in a theme copy and identify which component owns the visible output. Changing two recommendation sources at once destroys the evidence needed to isolate the conflict.
Escalation starts when the failure has an owner
Escalate only after collecting enough evidence for another person to reproduce the issue. A report that says filters do not work forces a developer or support team to repeat every basic check. A useful report includes the store, published theme, assigned template, URL, device, browser, test action, expected result, actual result, first observed time, and configuration changes made before the symptom appeared.
Check 12: Assign the narrowest responsible layer. Use the table to choose the next owner instead of replacing software to solve a catalog or theme problem.
| Criterion | What to check | Why it matters |
|---|---|---|
| Admin access | App opens, permissions permit edits, and a saved value persists | Storefront testing is unreliable if the configuration never saved |
| Product eligibility | Status, sales-channel availability, market context, and required data | An unavailable product cannot appear through search tuning |
| Theme rendering | Published theme, assigned template, block presence, and mobile controls | A configuration can exist without a visible storefront component |
| Query behavior | Exact title, category phrase, identifier, synonym, and misspelling | Different query failures point to different search causes |
| Filter combinations | Single values, combined values, clear action, and result counts | Successful single-value tests can conceal combination failures |
| App or code overlap | Theme customizations and other tools acting on the same surface | Multiple components can replace or overwrite visible output |
Send incomplete or inconsistent product data to the catalog owner. Send template-specific rendering failures to the theme developer or agency. Escalate an admin failure with the affected user, browser, timestamp, screenshot, and persistence test. For search behavior, attach the fixed query set and expected products. For filters, include the source values and known result counts.
Set a practical escalation threshold: if a second operator can reproduce the same failure in a private window using the written steps, the issue is ready to hand off. If the second operator cannot reproduce it, first compare account state, market, URL, theme, template, device, and browser.
Replace the native setup only for a confirmed requirement gap
Evaluate another search app only after the native setup is functioning as designed but still cannot meet a documented store requirement. Replacing the app too early can move a theme, data, or governance problem into a new system without removing its cause.
Write the gap as a testable requirement. For example: A shopper searching waterproof commuter bag must see eligible waterproof work bags before unrelated accessories, or mobile shoppers must be able to combine Size, Color, and Availability without opening an empty result set. Then decide how the requirement will be tested, who owns merchandising, and which catalog fields support it.
The decision rule is straightforward:
- Keep the native setup when it supports the required shopper journey and the remaining defect belongs to access, product data, or theme rendering.
- Review theme or custom development when the requirement is mainly presentation-specific and the store can maintain the resulting code.
- Evaluate an app when search relevance, filtering, merchandising control, or operational workflow remains inadequate after the baseline works correctly.
Use the Shopify Search & Discovery versus Hyper Search & Filter comparison to frame that decision. If the documented gap warrants another option, evaluate Hyper Search & Filter against the fixed queries, filter combinations, mobile tests, and ownership requirements collected during this checklist. Do not judge a replacement with easier tests than the native setup received.
FAQ
How do I fix Shopify Search & Discovery when it is not working?
Start by reproducing one failure on the published storefront, then test admin persistence, product eligibility, the assigned template, and the affected search, filter, or recommendation surface. Do not reinstall the app or edit several settings at once. For search, use five fixed queries and distinguish zero results from poor ranking. For filters, confirm configuration, source data, single selections, combined selections, and mobile controls. For recommendations, identify the product template and the component supplying the visible block. Escalate only after another operator can follow the written steps and reproduce the same result.
Where can I find Shopify Search & Discovery documentation?
Use Shopify's Help Center and the Shopify Search & Discovery app listing as the primary sources for current setup, compatibility, and feature guidance. Search the documentation using the exact setting or surface involved, such as synonyms, product boosts, storefront filters, related products, or complementary products. Documentation explains intended behavior, but it cannot identify which theme template or catalog field is failing on a particular store. Pair it with the Shopify site search setup guide when you need a storefront QA sequence rather than a feature description.
How can I tell whether the problem is product search or filtering?
Test a keyword query and a collection filter independently on the published storefront. If an exact product-title search cannot find an eligible product, investigate product search, catalog eligibility, and query handling. If search finds the product but a collection filter is missing, empty, or ignores a selection, investigate filter configuration, source data, and the collection template. A failure limited to the search-results page may involve that page's template, so also test the same filter on a collection before assigning the cause.
Should I uninstall and reinstall Shopify Search & Discovery?
No, not before confirming that the app installation itself is the failing layer. Reinstallation may remove useful configuration context while leaving a browser, permission, catalog, or theme problem untouched. First test the app in a private window, verify the affected user's access, confirm that a saved change persists, and compare the published theme with a controlled theme copy. Preserve screenshots and settings before any removal so the original state can be reconstructed.
When should I replace Shopify Search & Discovery with another app?
Replace it only when a repeatable business requirement remains unmet after access, catalog data, configuration, and theme rendering have been verified. Define the requirement with a query, expected products, filter combination, device, and pass condition. Then run the same acceptance tests against each option. Stores considering custom code should also compare maintenance ownership and theme-change risk; the Shopify search API build-or-app guide provides a framework for that choice.
