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 to integrate your website or the Discover API 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.

Subdomain

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

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

URL path

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

RequestResponseshell
# 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.

URL query parameter

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

RequestResponseshell
# 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.

Do you have some feedback for us?

If you have suggestions for improving this article,