Experience Builder Site Limitations

Be aware of the limitations that apply to Experience Builder sites such as Customer Service and Partner Central.

General Limitations

Lookup fields aren’t supported for custom objects or in Experience Builder sites created before Spring ’16.
When Experience Builder site users save an opportunity, they’re not prompted to add products, even when the Prompt users to add products to opportunities setting is enabled. Only users in sites built with Salesforce Tabs + Visualforce are prompted to add products.
In multilingual sites, the login page for the site appears in the default language. To create login pages in other languages, use custom Visualforce pages.
Google reCAPTCHA only works when access to Google web traffic is allowed. Causes for these disruptions vary, and can include network outages or government-mandated blocks. If a large percentage of your site is blocked from Google web traffic, consider requiring users to log in to post to the site.
The Create New option for lookups isn’t supported in Customer Service sites. Also, only authenticated external users (not guest users) can access asset lookup fields.
For guest users, case validation doesn’t run when cases are submitted through the Contact Support component. Validation runs after the submission is processed in the queue. Salesforce recommends writing custom client-side validation or writing custom Apex before inserting triggers to sanitize the case content.
Customer users can’t be added to account teams.

Partner Sites

Partner Central doesn’t support the language selector.
To protect your sales data, we disable guest user access for the navigation menu in Partner Central by default.
Partner Central doesn’t provide default self-service customer support features, such as navigational topics, articles, and the search publisher. To extend support to your partners, consider exposing cases in your community and creating a quick action button for creating cases.
You can’t export sites built on Partner Central as Lightning Bolt solutions. You can export individual pages, but not the entire site.

Browser Limitations

Note Customers accessing your Experience Builder sites from unsupported browsers receive a warning that site features may not work as intended and are directed to use a different or updated browser for the best experience. They can still choose, after the warning, to use the site with their current browser and reduced effectiveness, if they want. For the list of Salesforce supported browsers, see Supported Browsers for Experience Cloud Sites.

Mobile devices using the BlackBerry or Microsoft Windows operating systems aren’t supported.
Mobile users who perform the pinch-zoom gesture on Experience Cloud site preview images zoom into the center of the image, and not a specific area of the preview image.
Internet Explorer versions before 11 aren’t supported. We’ve created a page that automatically lets your users know that they must either upgrade or use a newer browser.
You can also redirect to your own page that informs users that those browsers aren’t supported. Create a file such as ieRedirect.js, and include this code in the file.
```
if (window.attachEvent && !window.addEventListener) {
	window.location = '<your redirect page>';
}
```
Then link to the redirect file in the head markup of the site. In Experience Builder, click | Advanced, click Edit Head Markup, and add this code.
```
<script src="path/to/ieRedirect.js"></script>
```
Only the latest versions of Chrome, Firefox, and Safari (on Mac operating systems) are supported.

LWR Site Limitations

An LWR site supports up to 500 routes, or unique URLs. For best performance, keep the number of routes below 250. Dynamic content can help keep your number of routes lower. For example, don’t create an individual page with a unique route for each content item. Instead, use record details to represent your content, and then create a single page that shows record details and requires only one route.