# 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 --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.mapsindoors.com/cms/core-concepts/searchability.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.