---
title: "Creating easy to identify URLs for CDN/reverse proxy"
slug: "creating-easy-to-identify-urls-for-cdn-reverse-proxy"
abstract: "Lists typical scenarios with examples on how to identify URLs to be served by Sitecore Discover web service."
---
# Creating easy to identify URLs for CDN/reverse proxy

> [!note]
> Sitecore has deprecated hosting pages with Discover.
>
> We recommend that you [use the Discover JS SDK](https://doc.sitecore.com/discover/en/developers/discover-developer-guide/deprecated-integration-methods/integrate-pages-hosted-with-discover/integrate-using-discover-sdks.html "Integrate using Discover SDKs") to integrate your website or [the Discover API](https://doc.sitecore.com/discover/en/developers/discover-developer-guide/deprecated-integration-methods/integrate-pages-hosted-with-discover/integrate-using-discover-rest-apis.html "Integrate using Discover REST APIs") for a website or application integration.

For your CDN/reverse proxy to identify which URL requests to pass through to Sitecore Discover, you must make them easy to identify. This topic lists typical ways of achieving this and also provides examples.

<details>
<summary><h2>Subdomain</h2></summary>

Include an identifier as a subdomain as shown in the following example:

```

# adding a subdomain
scd.<your-domain.com>/<category-name>?<additional-params>
```

</details>

<details>
<summary><h2>URL path</h2></summary>

Include an identifier in the URL path as shown in the following example:

```xml
# using a url path
<your-domain.com>/scd/<category-name>?<additional-params>
```

> [!note]
> If you use a subpath, you must use a 301 redirect for the original path for SEO traffic, until the search engine indexes update.

</details>

<details>
<summary><h2>URL query parameter</h2></summary>

Include an identifier as a query parameter as shown in the following example:

```xml
# using a query parameter
<your-domain.com>/<category-name>?<additional-params>&scd=1
```

> [!note]
> You must not block search engines from traversing paths with query parameters.

</details>