Identify the application public directory and back up the current site. Record the existing document root, PHP settings and custom web-server rules. Confirm the target is inside the permitted subscription space and does not belong to an unrelated site.

1. Prepare the target directory and deploy the expected public files before changing the live setting. Keep private configuration and storage outside that public directory when the application design requires it.
2. Open the domain Hosting Settings and locate Document root. Enter the intended path in the format requested by Plesk.
3. Review the domain and path carefully, then save. Changing this field is not a substitute for deploying the application or migrating its data.
4. Check application base paths, uploads, redirects and any directory-specific protection. Update only the settings that depend on the moved public entry point.
5. Test a representative public page and deliberately request a private filename that must not be downloadable. Ensure the test itself does not reveal sensitive content to third parties.

Confirm the intended application loads over HTTPS and private files are not served. Check relative assets, uploads, application routing and scheduled tasks whose paths might differ from the web root.

If Plesk shows a default page, inspect the exact target directory and its index file. If the application fails, use its error log and compare filesystem paths before changing permissions. Restore the old document root to recover the prior request mapping when safe. Do not delete the old directory until the replacement is verified and retention requirements are met.

• Uploading website files with Plesk File Manager
• Adding supported Apache and nginx directives in Plesk
• Diagnosing website errors with the Plesk log browser
• Setting the default document for an IIS website in Plesk

• Plesk: General Settings