Step 2: Approach 2 - Subdomain Integration
An alternate approach is called the Subdomain path where Yext can host the entire search results page. In this approach, all of the content of the search results page will be served by Yext, including a simplified version of your header/footer. Follow the steps below if you’d like to proceed with this option.
1. Choose a subdomain
This subdomain (e.g. search.mydomain.com) will be where Yext hosts the Search experience. We suggest one of the following:
search.mydomain.com
answers.mydomain.com
2. Create a CNAME record
Create a CNAME record pointed to mysubdomain.mydomain.com.pagescdn.com.
. Keep in mind the following as you follow this step:
- Be sure to include the subdomain in its entirety. For example, if you selected
search.mydomain.com
, then your CNAME will point tosearch.mydomain.com.pagescdn.com.
- Note the trailing dot (
.
) - it is required by the DNS specification when setting up a CNAME to another domain (pagescdn.com
, in this case). Some DNS providers may handle this automatically; your IT team will know how to configure the record correctly. - If you have an internal DNS, make sure to set up the CNAME record there, too (
mysubdomain.mydomain.com
pointed tomysubdomain.mydomain.com.pagescdn.com.
), otherwise the subdomain will not display on your internal network.
If you are hosting your data in the EU cloud region, point the CNAME record to mysubdomain.mydomain.com.eu.pagescdn.com.
instead. For example, if you selected search.mydomain.com
, then your CNAME will point to search.mydomain.com.eu.pagescdn.com.
3. Let us know which subdomain you’ve selected.
We will perform a few tests and confirm the configuration is active. Please note, no content will appear until we’ve deployed your site to our production environment. Prior to launch you may see an error message stating that no content is present.