Not found errors

Netlify shows “Page not found” after deploying

The deploy says it's published, but the site shows Netlify's “Page not found: Looks like you've followed a broken link” page.

Checked 16 October 2026

The short answer

Usually the publish directory: Netlify serves the wrong folder, so there's no index.html where it looks. Set Publish directory to your build folder (dist, build, public or _site) and deploy again.

Find your cause

5 causes, most likely first

  1. 1

    The publish directory is wrong

    How to tell: Open the deploy and browse its files: index.html isn't at the top, or the files aren't the built ones.

    Fix

    Set Publish directory to the folder your build creates, then trigger a new deploy.

    Project configuration→Developer settings→Continuous deployment→Build settings

  2. 2

    You dropped the project instead of the build folder

    How to tell: You used Netlify Drop, and the site works at /dist/ or /build/.

    Fix

    Drop the build folder itself, the one with index.html directly inside it.

  3. 3

    A single-page app without a redirect rule

    How to tell: The home page works; only refreshes and direct links fail.

    Fix

    Add a rule that sends every path to index.html, in netlify.toml at the repository root:

    netlify.toml
    [[redirects]]
      from = "/*"
      to = "/index.html"
      status = 200
  4. 4

    The site is in a subfolder of the repository

    How to tell: Your repository holds more than one project, or the site lives in a folder like web/.

    Fix

    Set Base directory to that folder. The publish directory is then counted from it.

  5. 5

    The deploy failed, so an older version is live

    How to tell: The Deploys list shows Failed for the latest one.

    Fix

    Open the deploy log, fix the first error and retry the deploy.

Questions

Also asked

The page is found, but images and scripts are missing. Why?

The HTML loads but asset paths are off. Check the base path settings in your framework (Create React App's homepage field, Vite's base) and that file names match in capitals.

Rather skip build settings altogether?

Build on your computer, where it already works, and drop the folder on 99helpers. The site gets its own address, so there's no base path, workflow or build log to get wrong, and it's online in seconds.

Or skip the setup

Drop it in. It's online in seconds.

A file, a folder or a whole site: 99helpers puts it online at its own address, with no git, no build settings and no DNS to start with. Add your own domain whenever you're ready.