> For the complete documentation index, see [llms.txt](https://docs.mapsindoors.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mapsindoors.com/cms/core-concepts/searchability.md).

# Searchability

It is independent from visibility — a Location can be rendered on the map without being findable through search, and vice versa.

### Search Status

Every Location has a **Search Status** toggle in the [Location Details editor.](/cms/interface/edit/location-details-editor.md) When turned off, the Location is excluded from all search results — it will still appear on the map (assuming its Display Rule visibility is on), but users cannot find it by searching.

This is most useful for decorative Locations — plants, statues, architectural features — that help create a realistic-looking map but should not appear in a list of navigation destinations. Turning off Search Status on these Locations keeps search results clean and relevant.

> A non-searchable Location can still be selected on the map if it is set to Selectable. If you want it to be truly passive — visible but neither searchable nor selectable — turn off both Search Status and Selectability.

***

### Search Aliases

Search Aliases let you add alternative terms to a Location that will return it in search results, even if the search term doesn't match the Location's name, Type, or Category.

Common uses include:

* Abbreviations or nicknames ("WC" for a restroom, "IT" for the IT support desk)
* Common misspellings or alternative spellings
* Terms from another language that your users might search in
* Internal room codes that staff use but that aren't part of the public-facing name

Aliases are set in the **Search** section of the Location Details editor. Multiple aliases can be added to a single Location.

***

### Searchability and App User Roles

If a Location has an App User Role restriction applied, it will not appear in search results for users who do not have the required role — regardless of its Search Status setting. Searchability and role-based restrictions work together: both must allow access for a Location to appear.

***

### Related concepts

* [Data Concepts](/cms/core-concepts/markdown.md) — what Locations are and how they fit into the data hierarchy
* [Display Rules](/cms/core-concepts/display-rules.md) — controlling map visibility independently from searchability
* [User Roles](/cms/core-concepts/editor.md) — how App User Roles affect which Locations users can find