When working with page variations and audience assignments in an Experience sites, each page variation is associated with a specific audience.
If a logged-in user tries to access a page but does not match any of the audiences assigned to that page’s variations, the user will see the following error message:
“Page not available. Maybe the page was deleted, the URL is incorrect, or something else went wrong. If you know the page exists but you still can’t get to it, please ask the community administrator for help.”
In the Experience Builder, when a System Administrator or any other user attempts to preview or navigate to a page where no page variation is assigned to them, the page will load indefinitely. However, administrators can still access the page from the Pages panel within the Builder, manually select a variation, and assign it to the appropriate audience.
This behavior occurs because Experience Builder relies on audience criteria to determine which variation to render. When no matching variation exists, the system fails to load the page content correctly.
Ensure that at least one page variation is set as the Default page.
A default variation acts as a fallback when a user does not meet any audience criteria.
Verify Audience Assignments for all page variations.
Go to Experience Builder → Pages → [Select Page] → Page Variations.
Review and adjust the assigned audiences as needed.
Make sure to Publish the site after making any audience or page variation changes.
If the page fails to load in Builder:
Open the Pages panel in Experience Builder.
Select the target page manually.
Assign or update the page variation to include your user audience.
Save and publish the site.
Recommended Practice:
Always create a default page variation for every page that uses audiences. This ensures a seamless user experience and prevents “Page not available” or infinite loading issues in both runtime and builder environments.
005228025

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.