Host creation and deployment are separate
A host is the destination that receives a deployment. Creating it establishes the resource and address, but no site content is available to visitors until files or code are deployed. This separation lets you prepare the destination before choosing and publishing the build output.
For a static host, prepare the built files and deploy the output directory. For an edge host, deploy the code and runtime configuration the host supports. The host creation settings, including the runtime and framework, should match the kind of artifact you plan to publish.
Verify the public site after deployment
After deployment, open the reserved address and check the root page, important routes, and assets. A host can exist successfully while visitors still see an empty response or a not-found page if no deployment has been made or the wrong output was sent.
If you use a workflow, connect the output from the host creation step to a hosting deployment step that names the host. Review the deployment result and test the public URL; host creation alone is not evidence that content is online. Re-deploy after updating files so visitors receive the new version.