LWR Sites for Experience Cloud

LWR Sites for Experience Cloud
Get to Know the LWR Templates
Pages and Components
Differences in Behavior
New Publishing Model
Custom URL Paths
Lightning Web Security
Caching Policy
Head Markup
Accessibility
LWR Template Limitations
Start Building Your LWR Site
Brand Your LWR Site
Create a Multilingual LWR Site
Add More Customizations
Manage Data in LWR Sites
Experience Delivery (Beta)
PDF

Custom URL Paths in LWR Sites

Unlike Aura sites, LWR sites in Experience Cloud support custom URL paths, meaning no more /s cluttering up your site’s URL—for example, https://mycustomdomain.com/mypage.

Before Winter ’23, you could create an authenticated or an unauthenticated LWR site. Unauthenticated sites supported custom URL paths, but authenticated sites included /s at the end of the base URL—for example, https://mycustomdomain.com/s/mypage.

LWR sites created in Winter ’23 or later no longer include /s in their URLs and are authenticated sites by default. Authenticated sites allow users to log in and access user-specific data, but you can also include public pages or make the entire site publicly accessible.

Sites that don’t use /s can still access Visualforce pages by instead appending vforcesite to the base URL—for example, https://mycustomdomain.com/vforcesite/mypage. You can also find the vforcesite URL in Setup | Custom URLs.

Unauthenticated LWR sites created before Winter ’23 are open to anyone on the web and don’t support login or authentication. Therefore, the Members, Contributors, Login & Registration, and Emails areas in the Administration workspace are unavailable because their settings don’t apply to unauthenticated sites.

Note