How to Publish Selected Salesforce Community Sites
Publish only the Experience Cloud sites included in your release, review individual results, and verify the customer-facing changes.
Published by Cloud Exam Coach · · 5 min read
← Back to all learning resourcesDefine a precise release scope
Suppose a release changes two branded portals but leaves three others untouched. Build a list of the two target names and URLs before opening the publishing panel. Similar names across sandbox and production make the organisation identifier as important as the site name.
Prepare each target
In Salesforce Setup, open Digital Experiences, then All Sites. Confirm the org and match the inventory against the approved release list. Open Experience Builder for each target and check the intended changes in preview. Publishing can expose other unpublished changes in the same site; coordinate with other editors first.
Deploy required components and configuration before publishing. A successful publish cannot repair a missing component, incorrect permission, or unresolved domain configuration.
Publish the selection
With Sites Manager installed, refresh its inventory on All Sites. Select only the intended targets, inspect the selection again, and use Publish Selected. If an inactive site is reported, decide separately whether activation is authorised; do not activate unrelated sites to clear a batch warning.
- Check the org, site names, and selected count before confirmation.
- Review the outcome for each selected site.
- Record successful targets separately from failures.
- Retry only failed targets after correcting their reported issue.
Validate the released experience
Open the public URLs and test the changed page, navigation, authentication, and the relevant form or integration. Check a signed-out session as well as an appropriate member account when both audiences are in scope. A preview under an administrator account does not establish what visitors can see.
Use the native workflow when needed
For a small release, open each target in Experience Builder and use its Publish action individually. The extension reduces repeated navigation; it does not bypass Salesforce permissions or provide a transaction across multiple sites. Keep a recovery plan for each target and verify its status after any interrupted batch.