> For the complete documentation index, see [llms.txt](https://help.pickzen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pickzen.com/create/creating-questions/end-slide-layouts/recommending-content.md).

# Recommending content

A typical use case of the [automatic redirect](/create/creating-questions/end-slide-layouts/automatic-redirect.md) is for recommending content. Imagine you don't want to recommend products, instead, you want to recommend content entries of your site or blog. In this case, you wouldn't have products per se, but you would create "products" that represent those entries.

For example, you could have a set of "products" like these:

![](/files/-Ls7_cOW1DZv_oNVdRXy)

With the following information:

![](/files/-Ls7_lvZ-E_M-U_vcwhQ)

Only the ID, Name, and Url would be necessary to create these kinds of products because the user will be redirected to the specified Url. The product itself won't be displayed in the recommendations.

You can use all the capabilities of Pickzen to recommend these kinds of products (linking, rules, attributes, etc.) in order to improve the engagement of your site.


---

# 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://help.pickzen.com/create/creating-questions/end-slide-layouts/recommending-content.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.