Important Notes:
When you set up an Experience Cloud site, that site by default runs under the site.com or force.com domain (for example: mycompany.my.site.com).
Each site runs under its own path on that domain, so if you set up separate sites for your customers and partners you may have two site URLs that look like this:
https://mycompany.my.site.com/customers/
https://mycompany.my.site.com/partners/
The site.com and force.com domains work for sites where the nature of the site is private, and where you're not looking for people to discover your site by its domain name.
Here are the best practices to follow if you want to run your site under a custom domain (for example: site.mycompany.com) for branding or SEO purposes:
Let's say your company website runs under www.mycompany.com. Your company owns that domain name, and probably controls the DNS server that directs traffic to any domain under mycompany.com.
Your company's DNS server must be updated to point requests for site.mycompany.com at your site. This is done by using a CNAME record in your DNS server. Think of a CNAME as an alias, one where we're telling anyone looking for site.mycompany.com to look for your site address instead.
Many DNS servers (including those hosted by popular DNS name registrars like NameCheap and GoDaddy) provide a nice graphical way to update DNS settings, including CNAMEs.
Your DNS provider needs an alias to point your new domain name to. With Experience Cloud, CNAME aliases are supported with the following pattern:
Find your organization's alias:
Note:
In order to serve site content over encrypted connections (a requirement for any area of your site where someone must be logged in), you need to have your site host and serve an SSL certificate that matches the domain.
Many organizations offer SSL certificates for sale, including most common DNS registrars. Contact your IT department to obtain a CA-signed SSL certificate for your new site domain. That process starts by creating a Certificate Signing Request, or CSR.
Create a CSR within Salesforce:
You (or your IT department) use the CSR with an SSL certificate provider to generate an SSL cert for your domain. Certificate Authorities have differing methods of verifying information and issuing certificates, so you need to work with your IT department to get the appropriate certificate issued.
Note: You may use either a wildcard certificate (*.mycompany.com) or a domain-specific certificate (for example: site.mycompany.com) for your site.
After your certificate authority has issued your certificate, navigate back to the certificate record in Salesforce and click Update Signed Certificate to get your certificate into the system.
Note:
After your newly created CNAME propagates across the internet, you’ll be able to create a custom domain record in Salesforce:
000387288

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.