Shopify Search & Discovery metafield missing? Prove the product owner, value, S&D config, and one live surface.

Use this page when the value itself is missing from Search & Discovery: Admin has no value, the app cannot select the metafield, or boosts/filters never see the field you expect. If the filters list is empty because nothing is configured, use Search & Discovery filters empty. If filters are configured but broken while values exist, use Search & Discovery filters broken.

Do not add a second metafield or reinstall Search & Discovery yet. Capture the shop, product IDs, filter or boost name, market, and exact surface where the metafield should drive results.

Open Settings → Custom data and confirm the definition is owned by Product. Record the exact namespace and key, for example search.priority_tag, the type, validations, and whether storefront / Storefront API access is enabled.

Open the exact products used in the live search or collection test. Save a short unmistakable test value, refresh, and confirm it survives in Admin. A filled definition on draft products, a different namespace, or a label that only looks right is not proof Search & Discovery can index it.

Compare the saved definition with Search & Discovery → Filters and any search boost / ranking rules that reference metafields. The app must select the same namespace.key and a supported type. A successful Admin request can still omit the field from S&D when access is wrong, the type is unsupported, or the app is on an older config version.

Verify the Search & Discovery app is installed and updated, and that the Online Store channel is included. Log field presence without logging secrets. If a plain text test is visible in Admin but never selectable in S&D, fix definition access/type rather than rebuilding the collection template.

Search & Discovery behavior is context-sensitive. Record the query or collection handle, market, currency, catalog publication, and whether products with the test value are available on Online Store. Confirm the metafield belongs to that product context and that classic theme Liquid filters are not the only surface under test.

Keep the diagnosis distinct from the storefront filter metafield blank and storefront search not returning paths. They can affect related discovery UX while reading different resources and fields.

Use one product set and one S&D surface (filter or boost). Record product IDs, namespace.key, type, saved test value, S&D config status, app version, and whether the live search or facet shows the expected output. Repeat logged out on the published theme, then test a second query only after the first path is proven.

If the field is still missing, classify it as definition/value, storefront access, unsupported type, S&D config, unpublished products, market/catalog, or app version. Do not call an empty-filters failure until the metafield values are demonstrably present and selectable in Search & Discovery.

Stay DIY when one definition, saved value, Search & Discovery config, or published-app check explains the miss. Keep the proof packet so future discovery changes are reversible.

Pay for the $997 one-time install when several Shopify surfaces, apps, catalogs, and ops alerts need to be wired and documented on one live store. Nico at Latch AI Ops can connect the agreed workflow in a 72-hour window after collaborator access. No earnings claim, conversion guarantee, or theme rebuild is included; owner passwords are not requested.