Sitejet documents basic page passwords, but cPanel and Plesk integrations may implement protection differently. Verify enforcement on the published site before relying on a setting.
Steps
- Identify the exact pages or directories that should be restricted and inspect the protection controls available in your integration.
- Where the builder's page password feature is supported, open Pages, the page settings, and More Settings to review its password field.
- Save and follow the integration's publishing process. If the feature is unavailable, review the hosting panel's documented directory-protection options.
- Open the public page in a signed-out private session and verify that access is actually blocked.
- Test linked files directly as well as the page itself.
Check the result
Protection is established only for the resources that reject unauthorized requests in the live environment.
Before you continue
Basic page passwords are unsuitable for sensitive personal or financial information. Hiding a menu item or requesting noindex does not restrict access. Never upload confidential material just to test whether protection works.
Official documentation: Sitejet guide.
