Salesforce Sites

Salesforce organizations contain valuable information about partners, solutions, products, users, ideas, and other business data. Some of this information would be useful to people outside your organization, but only users with the right access and permissions can view and use it. In the past, to make this data available to the general public, you had to set up a web server, create custom web pages (JSP, PHP, or other), and perform API integration between your site and your organization. Also, if you wanted to collect information using a web form, you had to program your pages to perform data validation.

With Salesforce Sites, you no longer have to do any of those things. Salesforce Sites enables you to create public websites and applications that are directly integrated with your Salesforce organization—without requiring users to log in with a username and password. You can publicly expose any information stored in your organization through a branded URL of your choice. You can also make the site's pages match the look and feel of your company's brand. Because sites are hosted on Lightning Platform servers, there are no data integration issues. And because sites are built on native Visualforce pages, data validation on collected information is performed automatically. You can also enable users to register for or log in to an associated portal seamlessly from your public site.

Note Salesforce Sites is subject to these additional Terms of Use.

The following examples illustrate a few ways that you can use sites:

• Create an ideas site—Use sites to host a public community forum for sharing and voting on ideas about your company, services, or products. Ideas websites can be made public using sites.
• Publish a support FAQ—Provide helpful information on a public website where customers can search for solutions to their issues.
• Create a store locator tool—Add a public tool to your portal that helps customers find stores in their area.
• Publish an employee directory—Add an employee directory to your company's intranet by creating a site restricted by IP range.
• Create a recruiting website—Post job openings to a public site and allow visitors to submit applications and resumes online.
• Publish a catalog of products—List all of your company's products on a public website, with model numbers, current prices, and product images pulled dynamically from your organization.

Because Salesforce Sites are served directly from the Salesforce organization, a site's availability is directly related to the organization's availability. During your organization's maintenance window for major releases, your sites are unavailable; users who try to access a site see a Lightning Platform-branded maintenance page or your custom Service Not Available Page. It's a good idea to inform your site users of the release maintenance windows and related sites unavailability in advance. You can view specific maintenance windows, listed by instance, at trust.salesforce.com/trust/status/#maint.

• Manage Salesforce Sites
  Review the high-level steps to create and manage a Salesforce Site.
• Enable Salesforce Sites
  To use Salesforce Sites with or without a custom domain, you must first enable Salesforce Sites and register your Salesforce Sites domain. Your company's Salesforce Sites domain is used for all the sites that you create.
• Set Up Salesforce Sites
  Enable Salesforce Sites and create public websites and applications that are directly integrated with your Salesforce org—without requiring users to log in with a username and password.
• Configure Site Caching
  Caching your Salesforce Site pages, attachments, and static resources can improve page load times and site performance. It can also help you avoid reaching bandwidth and service request time limits.
• Use Workflow for Salesforce Sites
  With workflow for sites, you can create workflow rules that trigger email alerts when certain site-related criteria are met. For example, create a rule that sends your site administrator an email alert when bandwidth usage reaches 80% of the daily bandwidth limit or when a site's status changes from the active state.
• Track Your Salesforce Sites with Google Analytics
  Salesforce Sites provides out-of-the-box integration with Google Analytics. To track the usage of your sites and site pages, use Google Analytics. You can track the number of visits, the number of page views, the average time spent on the site, and more.
• View Salesforce Sites History
  To review the changes made to your site, view the Site History related list.
• View 24-Hour Salesforce Sites Usage History
  You can avoid exceeding your site usage limits. Monitor the bandwidth and request time usage for each of your sites by viewing the usage data tracked on the 24-Hour Usage History related list.
• Report on Salesforce Sites
  To track your site activity and usage, take advantage of the Sites Usage Reporting managed package. To help you avoid reaching monthly and daily limits for individual sites and for your org, this package includes site usage reports. You can use those reports to you analyze your monthly page views, daily bandwidth, and daily service request time.
• Salesforce Sites Security
  Review how the Sites and Domains settings related to secure connections affect what your users see when accessing your org.
• Salesforce Sites-Related Apex Methods and Expressions
  Lightning Platform provides Apex methods and Salesforce Sites-related expressions to help execute flow and transaction control statements.
• Salesforce Sites Considerations
  Before you create and use Salesforce Sites, review considerations around App Exchange packaging, access and authentication, and potential URL conflicts between sites.
• Salesforce Sites Usage and Billing
  Salesforce Sites usage is governed by monthly and daily allocations. Understanding these allocations is important to the success of your sites.
• Can I use the same domain name for my Salesforce Sites and my Experience Cloud Sites?
  With enhanced domains, your Salesforce org’s My Domain name is the subdomain for Salesforce Sites and Experience Cloud sites. If enhanced domains aren’t deployed in your org, you can’t use the same domain name for Salesforce Sites and Experience Cloud sites.