You are here:
Hide Unneeded Visualforce Pages on Your Experience Cloud Site
To avoid exposing pages that don’t reflect your brand or that allow for alternative ways to log in to your site, be aware of these guidelines when configuring Visualforce pages that are part of your Experience Cloud site. Understand the relationship between Experience Cloud sites and Salesforce Sites, their public Visualforce pages, and steps to take for a proper configuration.
Relationship Between Experience Cloud Sites and Salesforce Sites
When you create an Experience Cloud site, Salesforce creates a Salesforce Site. Salesforce Site technology powers some of the underlying features behind Experience Cloud sites.
For example, some security settings are set at the Salesforce Site level. Salesforce Sites also automatically create and exposes a set of default Visualforce pages. Before you set up an Experience Cloud site, review the settings of the associated Salesforce Site. To get the full picture of what is visible after creating an Experience Cloud site, review the Experience Builder pages and the accompanying Site Visualforce pages.
If you already have a live Experience Cloud site, run a check to see which pages are
visible. One of the default Visualforce pages is named SiteLogin. To check
if your site exposes this page, append /SiteLogin after your Experience
Cloud site domain (without the /s).
| If your Experience Cloud site URL looks like this: | Try accessing: |
|---|---|
| yourcommunity.example.com/ | yourcommunity.example.com/SiteLogin |
| yourcommunity.example.com/s | yourcommunity.example.com/SiteLogin |
| example.com/yourcommunity | example.com/yourcommunity/SiteLogin |
| example.com/yourcommunity/s | example.com/yourcommunity/SiteLogin |
If you see your branded login page or the expected error page for your community, your site seems to be properly configured. However, if you see a default Visualforce page that you didn’t expect to see, continue reading to see how you can fix it.
Default Visualforce Pages Exposed by Salesforce Sites
When a Salesforce Site is created, a new set of default metadata is added to your org.
- Visualforce pages, such as SiteLogin, SiteRegister, and ForgotPassword
- Aura components, such as forgotPassword, loginForm, and selfRegister
- Apex classes, such as MyProfilePageController, SiteLoginController, and SiteRegisterController
- Visualforce components, such as SiteFooter, SiteLogin, and SiteLogin
- Static resource (SiteSamples)
This metadata is intended as examples and templates that you can reuse to expose custom functionality throughout your site.
For example, if you need a fully personalized login experience, you could reuse and customize the sample code provided in the SiteLogin Visualforce page or the loginForm Aura component.
Some Visualforce pages are publicly accessible by default.
- BandwidthExceeded
- CommunitiesLanding
- CommunitiesLogin
- CommunitiesSelfReg
- CommunitiesSelfRegConfirm
- CommunitiesTemplate
- Exception
- FileNotFound
- ForgotPassword
- ForgotPasswordConfirm
- InMaintenance
- SiteLogin
- SiteRegister
- SiteRegisterConfirm
- UnderConstruction
To control what is visible through your site, review those pages and classify them into different categories.
- Keep the pages you need and want to expose publicly. For example, you might want to customize the InMaintenance page, which is shown when your Experience Cloud site is offline, to reflect your brand.
- Remove the pages that you don’t need and shouldn’t make publicly accessible. For example, if you don't need a custom login page on your site, you probably don’t want to leave the default SiteLogin Visualforce page exposed publicly.
- Update Public Accessibility Settings for Standard Visualforce Pages of Your Experience Cloud Site
Review the public accessibility settings of your standard Visualforce pages that are associated with your Experience Cloud site, and update them as needed.
