> 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-blog-posts.md).
# Locking blog posts
Locksmith can search for and lock an *entire* blog, but doesn't search for individual blog posts/articles by default. If you type in "news" (or the title of your blog), you should be able to lock the whole blog, but that'll include every article in there by default.
To lock a *specific* blog post/article, try tagging it in your "Blog posts" page in the Shopify admin area, and then search for that tag in Locksmith. When you search for the tag, it will display as "articles tagged with...":
For more about how to add tags to blog posts, please visit Shopify's guide, below:\
\
[Add tags to a blog post ](https://help.shopify.com/en/manual/online-store/blogs/writing-blogs#add-tags-to-a-blog-post)
{% hint style="info" %}
After adding tags to your blog posts, if the tag doesn't show up right away when searching for it in-app, click on the "Update Locksmith" button on the *Help* page in the app. It should sync up in a minute or so.
{% endhint %}
{% hint style="danger" %}
Locksmith ***cannot*** block RSS feeds from locked blogs.
{% endhint %}
---
# 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/locking-blog-posts.md?ask=&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.
