> 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/locking-the-search-results-page-in-your-store.md).

# Locking the search results page in your store

To get started, search for "search" from within Locksmith, like so:

![](https://d33v4339jhl8k0.cloudfront.net/docs/assets/5ddd799f2c7d3a7e9ae472fc/images/5e27859f2c7d3a7e9ae68e75/5e27859f78e77.png)

... and click on the "Search" search result. (So much searching!)

That's it! :)

## Protecting search forms, using Liquid code

Out of the box, this lock *only* protects the /search url of your shop (as in <https://myexampleshop.com/search>).

To hide the search boxes that your theme may include elsewhere in your shop, open up the Liquid file that contains the search form in question, and locate the actual search form. Wrap it with Liquid that looks like this:

```
{% include 'locksmith-variables', locksmith_scope: 'search' %}

{% if locksmith_access_granted %}  
  <!-- your search form here! -->
{% endif %}
```

As you can see, this *does* require manual coding. If you need a hand with this, let us know! :)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.locksmith.guide/tutorials/more/locking-the-search-results-page-in-your-store.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.