> For the complete documentation index, see [llms.txt](https://docs.samita.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samita.io/b2b-lock-password-protect/content-to-lock/specific-url.md).
# Specific URL
Lock any custom URL or path on your store behind access rules, with an option to exclude specific URLs.
The **Specific URL** content type locks any custom path on your storefront that isn't covered by the other content types — a landing page built outside the standard page/collection structure, a search results path, or any URL pattern you want to gate.
## Create the lock
1. Open **Locks** in the app's navigation.
2. Click **Create lock**.
3. Give the lock a descriptive name, for example "Landing page — passcode required."
## Choose Specific URL as the content to lock
4. On the **Lock setup** tab, in the content picker, select **Specific URL**.
Select Specific URL in the content picker to lock a custom URL or path.
5. In the **Restricted URLs** card, type the path you want to lock — the field shows the expected format, for example `/contact-us` — then click the add button beside it. Repeat to add more paths to the same lock.
Enter each path you want to lock, then click add.
{% hint style="info" %}
Enter the path only (starting with `/`), not the full domain. If you need to keep certain paths public inside a much broader lock, use the [Whole website](/b2b-lock-password-protect/content-to-lock/whole-website.md) content type instead — it has an **Exclude url** option, which Specific URL doesn't.
{% endhint %}
{% hint style="warning" %}
Locking a custom URL may require a paid plan depending on your current plan.
{% endhint %}
6. Click the **Unlock rules** tab to continue.
## Add an access rule
7. Add at least one rule — for example, **Secret link**, so the URL only unlocks for visitors who arrive with a valid secret link token.
8. Configure the rule's settings. See [Access rules overview](/b2b-lock-password-protect/access-rules/overview.md) for the full catalogue of available rules.
9. Add every required condition to the access key. All conditions must be satisfied. See [Combining rules](/b2b-lock-password-protect/access-rules/combining-rules.md).
## Choose a lock behavior
On the same **Unlock rules** tab, the right-hand sidebar has a **Blocked visitor behavior** panel — configure it alongside your rule:
10. A locked URL typically shows a full lock screen until the visitor passes. Review [Lock behavior overview](/b2b-lock-password-protect/lock-behavior/overview.md) for the full set of options, including redirecting visitors after they gain access.
## Save
11. Click **Save**. The lock takes effect on your storefront as soon as the app embed is enabled.
## Related docs
* [Access rules overview](/b2b-lock-password-protect/access-rules/overview.md)
* [Lock behavior overview](/b2b-lock-password-protect/lock-behavior/overview.md)
* [Manage locks](/b2b-lock-password-protect/locks/manage-locks.md)
---
# 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://docs.samita.io/b2b-lock-password-protect/content-to-lock/specific-url.md?ask=&goal=
```
`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.
