A website’s document root is the directory mapped to its domain. Uploading files somewhere else in the account will not make them appear at that address. Confirm the domain’s mapping in the hosting panel before replacing a default page.
Identify what your project actually produces
A plain HTML site can be uploaded as files. A frontend project may need a build first; upload its deployable output with the asset directories intact. Source files and a package manifest do not automatically become a running web application on shared hosting.
An application requiring a persistent Node.js process or custom server software needs a compatible service. A static export may work as files, but server-only routes, background jobs and dynamic rendering will not start merely because their source code was uploaded.
Publish into the mapped directory
- Confirm the domain and document root shown for your account.
- Back up existing content before overwriting any file.
- Inspect the archive so you know whether it contains an extra enclosing folder.
- Upload using a supported secure file-transfer method or the panel file manager.
- Place the intended index page at the correct level and preserve asset filenames.
- Visit the homepage, a nested page and a direct image or stylesheet URL.
| Symptom | Check |
|---|---|
| Default hosting page remains | Wrong directory, cached response or old DNS destination |
| Homepage works but images fail | Asset paths and filename capitalization |
| Site only opens under /dist/ | Build output was uploaded with an unwanted parent directory |
| Nested page returns 404 | Missing exported page or required routing configuration |
Keep private material outside the public site
Do not upload deployment credentials, database dumps or full backup archives into a publicly served directory. Hidden filenames are not an access-control policy. Check the published artifact before upload and remove temporary diagnostics after use.
Use a staging copy for an existing site. If visitors reach the wrong server, check domain pointing first.
Sources and references
Hosting documentation. Publication and update dates reflect this edition.
Related articles
- Pointing a Domain to Your Web Hosting Without Breaking EmailChoose between a nameserver change and DNS record changes, preserve mail records and verify the destination.2 min read
- Creating a Private Staging Copy of Your WebsiteTest updates with separate files and data while preventing indexing, real emails and accidental production writes.2 min read
- Backing Up and Restoring a Website’s Files and DatabaseBuild a usable recovery set, protect it outside the public directory and test restoration before an outage.2 min read
