---
title: 'Search configuration'
description: 'Make records discoverable and troubleshoot missing search results.'
---

# Search configuration

Set `searchable: true` on attributes whose content users need to find. Choose useful identifying fields such as SKU and name instead of marking every field searchable.



## Configure and check

1. Add searchable attributes to the entity definition.
2. Deploy the updated schema and publish the matching Studio configuration.
3. Save a known synthetic record with a distinctive value.
4. Search for it through Studio global search, then narrow with the entity filter.
5. Confirm the result opens the intended record.

Use a stable display attribute so users can distinguish results. For local attributes, consider which scoped values your users search for. Relationship fields require the supported relationship configuration; do not assume arbitrary nested content is indexed.

## Missing results

Check project selection, entity filter, access spaces, attribute configuration, and indexing state. Reloading the list and searching the index are different operations. A record may exist in GraphQL even when a search result is missing.

See [search integration](/docs/api/search), [entity reference](/docs/schema/entity-reference), and [spaces](/docs/schema/spaces).


---

[View full sitemap](/docs/sitemap.md)
