To provide a branded experience for users who access your external-facing Salesforce
content, serve your Experience Cloud sites on a domain that you own. With a custom domain, your
users access your external-facing Experience Cloud site and its functionality through your
branded URL, such as https://www.example.com. Also, with the many-to-many relationship between
sites and custom domains, you can serve your external-facing content to meet your branding
needs. For example, you can serve content from multiple Experience Cloud sites on one parent
website, or serve multiple sites on one domain through custom paths. Because you can serve
multiple sites on one domain, custom domains simplify the management of your domains and your
corresponding network allowlists. And even if your Salesforce-hosted site URL changes due to a
My Domain change, your custom domain remains constant, reducing the number of updates
required.
Required Editions
| Available in: both Salesforce Classic and Lightning Experience |
| Available in: Enterprise, Performance, and Unlimited
Editions. Also available with Marketing Cloud Account Engagement (Pardot) in
Professional Edition.
|
| Applies to: LWR, Aura,
and Visualforce sites |
You can set up a custom domain to serve your sites at any time. When you set up a custom
domain as you build your Experience Cloud sites, your visitors use your branded custom domain
from the start. This approach can improve your SEO and eliminate future effort to update
hard-coded links and change user behavior.
To learn more and set up a custom domain, see Custom Domains.
If you serve your site content on a custom domain, we also highly recommend that you use a
content delivery network (CDN) to optimize your content and site performance. For more
information, see Content Delivery Networks (CDNs) and Salesforce . If
you set up a custom domain in a Professional Edition org with Marketing Cloud Account
Engagement (Pardot), that domain must use the Salesforce CDN.
