---
title: URL Redirects
slug: personalized-search/url-redirects
description: How to make GET calls to the Monetate Personalized Search API for URL redirects associated with customers' search queries
image:  https://archbee-image-uploads.s3.amazonaws.com/ceIfEvQHzQk1IVxoRWUh7/K9eTL4jKm7UQINb6zNziJ-20250912-181225.png
docTags: 
createdAt: 2025-01-03T15:14:04.693Z
---

You might want some terms a customer searches for to go to a specific page instead of returning a list of records. For example, if a customer searches for *return policy*, you want Personalized Search to automatically send the customer to your Returns Policy page. See [Create URL Redirects](https://docs.monetate.com/docs/personalized-search-url-redirects) in the Monetate Knowledge Base for the steps to set up URL redirects in the Personalized Search user interface.

Once you set them up, you retrieve and configure URL redirects using the Personalized Search API, allowing you to cache them. After making the Engine API [decision request](docId\:lQST4ABe9zqX_k3ta8Nnh), configure URL redirects by making a GET call to the following URL:

:::CodeblockTabs
Personalized Search API Endpoint

```html
https://engine.monetate.net/api/search/v1/site-search/{name}/{instance}/{domain}/url-redirects?action_id={action ID}
```
:::

You can find the action ID in the response to the relevant Omnichannel Personalized Search experience. Refer to [Omnichannel Personalized Search Action Request](docId\:XzJY8yCNDlMWjLE-2oXMw) for more information.

Here's an example response to the GET call:

:::CodeblockTabs
Example URL Redirect Response

```json
{
  "monetate_keywordUrlMap": [
    {
      "keywords": [
        "google"
      ],
      "url": "https://www.google.com"
    },
    {
      ... Additional redirects ...
    }
  ]
}
```
:::

You can then check for these URL redirects locally instead of making a Personalized Search API call, thus improving performance for these terms.