> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-engage/17.latest/marketers-and-editors/analytics/search-terms.md).
# Search Terms
Track and analyze search terms entered by visitors on your website to gain insights into user behavior and improve site content.
The **Search Terms** feature within **Analytics** allows you to monitor and analyze the keywords visitors use when searching within your website. By using these terms, you gain valuable insights into what your audience is looking for, helping you optimize your content strategy and improve user experience.
Search terms automatically track keywords entered in your website's search field. By default, it looks for the `"q="` parameter in the URL's query string and stores the associated keywords.
You can identify common user interests and personalize their experience by tracking search terms both site-wide and per-profile basis. This helps in delivering more targeted content, improving engagement, and increasing conversion rates.
Search terms
## Configure Search Term Parameters
To configure the search terms parameters:
1. Go to the `appsettings.json` file.
2. Locate the `InternalSiteSearch` parameter.
3. Set values for `SearchTermParameters`, `SearchBoxParameters`, or `CategoryParameters` depending on your needs.
For more information, see the [Configuration](/umbraco-engage/17.latest/developers/settings/configuration.md) article.
---
# 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.umbraco.com/umbraco-engage/17.latest/marketers-and-editors/analytics/search-terms.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.
