Spin up a new Experience Cloud Site from Setup. You enable the feature once per org, then run the creation wizard for each site you need. Plan licensing and sharing before you start, because both are easier to get right up front than to retrofit.
- Enable Digital Experiences
From Setup, enter Digital Experiences in Quick Find, open Settings, and select Enable Digital Experiences. This is a one-time, org-level step that turns the platform on before any site can exist.
- Open the All Sites page
From Setup, enter Digital Experiences in Quick Find again and select All Sites. This page lists every site in the org and shows how many of your 100 slots are in use.
- Start the creation wizard
Click New. The wizard opens with a gallery of templates. Pick the one that matches your use case and runtime needs, then continue.
- Name the site and set its URL
Enter a Site Name and a URL path prefix. The prefix must be unique within the org and becomes part of the site address, so choose it deliberately because changing it later breaks bookmarks and links.
- Build, then activate
Open the site in Experience Builder to add pages, components, theme, and audiences. When it is ready, return to All Sites and activate it to make it reachable at its URL.
The internal name that identifies the site in Setup and in the Network record. Name it by purpose, not by sequence.
The unique path segment under the org domain that addresses the site. Stored as UrlPathPrefix on the Network record and unique per org.
The starting template, which sets the initial pages and the runtime (Aura or Lightning Web Runtime) the site uses.
- Active, inactive, preview, and Visualforce sites all count toward the org limit of 100; archive sites you no longer use to reclaim a slot.
- The Aura versus LWR runtime is set by the template and is not a casual switch later, so choose it against your component and performance needs.
- Lock down the guest user profile before activating; an open guest profile is scoped to that site but can still expose records you did not intend.
- External user licenses are consumed per named user and are tracked per site, so a popular site can run its license pool dry without warning.