> For the complete documentation index, see [llms.txt](https://www.locksmith.guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.locksmith.guide/tutorials/more/hiding-products-and-other-content-from-lists-in-your-online-store.md).

# Hiding products and other content from lists in your online store

How to set up Locksmith locks to hide from collections, in-store searches, and any other lists and grids in your Shopify Online Store

Locksmith allows you to hide *locked* content from lists across your store. This includes hiding products from collections and search result pages - only showing them to visitors that have gained access to the appropriate lock(s). This is turned on in your lock settings on your lock page:

<figure><img src="https://277214568-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MUeGWHuijBPr8Og1Gta%2Fuploads%2FStbfiignvfRVan688uKL%2FScreenshot%202025-07-15%20at%2015.07.49.png?alt=media&amp;token=d11eb00a-3665-49aa-ab39-a0dc5f464b07" alt=""><figcaption></figcaption></figure>

## Hide products from the following:

* Searches
* Collections
* Related products
* Featured products
* And more! Any time your theme is showing a list of products, this feature likely has the ability to filter locked products from it - *as long as the list is not displayed by a third party app.*

## Other resource types

Although less commonly needed, you can also turn this feature on for page, blog, and article locks. In these cases, if your theme has a way to display "all pages", or "all blogs", for example, Locksmith can remove these from from those types of displays as well.

## Limitations

* Using **third party apps** that take over the display of your collections or searches will likely prevent Locksmith from hiding products correctly. Most filtering/search/display apps are **not compatible** with hiding products via Locksmith.
* Hiding a large number of products this way can introduce **blank spaces** to your collections. [More information and workarounds here](https://www.locksmith.guide/faqs/faq-i-see-blank-spaces-in-my-collections-and-or-searches-when-locking.md).
* While this setting is capable of hiding products from the search results *page*, it cannot always remove products from search results that are fetched dynamically (i.e. shows results as you type).
* This setting cannot hide filtering options in your theme's filter menu (shown on collection and search pages). Shopify builds the filter options, and their counts, from every matching product, locked or not, before your theme displays them. If your theme draws its filter menu itself, Locksmith's manual code can often hide a particular filter, or the whole filter area, from visitors who don't have access: write to us at **<team@uselocksmith.com>** and we'll add it for you. Filter counts will still include locked products, and filters displayed by a third-party filter app are out of Locksmith's reach.

For more specific information regarding how locksmith works with your in-store search, including some troubleshooting steps, see our guide here:

{% content-ref url="/pages/zROi6atqaMjwYTVodQVb" %}
[Can Locksmith hide content from my in-store search?](https://www.locksmith.guide/faqs/can-locksmith-hide-content-from-my-in-store-search.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.locksmith.guide/tutorials/more/hiding-products-and-other-content-from-lists-in-your-online-store.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
