> 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/bulk-price-editor-sami/field-guides/category-template-visibility.md).

# Category, template and visibility

Assign a Shopify product category, change the theme template, or hide products from search engines in bulk.

## Category

The **Category** field assigns a category from Shopify's standard product taxonomy. The edit method is **Set category**. Click the picker, browse or search the taxonomy, and choose the category. Every matching product gets that category.

Product categories drive tax rules and the product data Shopify sends to channels, so pick the most specific category that fits.

## Theme template

The **Theme template** field changes the template suffix a product uses, for example `product.pre-order`. It uses the standard text edit methods; the most useful is **Replace entire text** with the suffix name. See [Title, handle, vendor, type and SEO](/bulk-price-editor-sami/field-guides/text-fields.md) for the full list.

## Search engine visibility (seo.hidden)

This field controls whether products appear in search engine results. Choose:

* **Visible**: search engines may index the product page.
* **Hidden**: the product page is excluded from search engines.

Reverting any of these tasks restores the previous value on each product.


---

# 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://docs.samita.io/bulk-price-editor-sami/field-guides/category-template-visibility.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.