Provide the site entry point
When a browser requests a hostname without a file path, the host needs a default document to return. For a static site, `index.html` normally serves as that entry point and links or loads the rest of the page assets. A bundle of images, scripts, or nested pages alone does not tell the host what to show at the root.
Place `index.html` at the root of the deployment file set, with the exact expected spelling and path. If a build tool writes files into a directory such as `dist` or `out`, deploy the contents of that directory and confirm the entry file is at its top level. Uploading the parent project folder may add an extra directory layer that hides the entry file.
Check the deployed root and asset paths
Before deploying, inspect the file list and verify that the entry document refers to assets using paths that will exist after upload. Paths that work on a development machine can break if they include a local folder prefix or assume a different base URL. Keep the deployed directory structure consistent with the references in the HTML.
After deployment, open the site's root URL and inspect the browser response if it fails. A 404 at the root can indicate a missing or misplaced entry document; a page that loads without styling may instead have broken asset paths. Correct the build output or selected deployment directory, deploy again, and check both the root page and a representative asset URL.