There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes.

https://community.vercel.com/t/debugging-404-errors/437

Vercel Community

Debugging 404 Errors

Sometimes things don’t go as expected when deploying a website. If you see a 404 on your site, that means the page or resource couldn’t be found. There are...

A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.

Hi Jimmy,

For a Lovable export, this is often a Vite/React app, so I’d first check whether Vercel is deploying the folder that actually contains the app and whether the build output is being served correctly.

In the Vercel project, check Settings → Build and Deployment:

1
Framework Preset: Vite
2
Install Command: npm install
3
Build Command: npm run build
4
Output Directory: dist
5
Root Directory: the folder that contains package.json
6

Then redeploy and open the latest deployment URL directly.

A quick way to separate the causes:

1
npm install
2
npm run build
3
ls dist
4

If dist/index.html is not created locally, the issue is in the project/build. If it is created locally, then the Vercel settings are probably pointing at the wrong root directory or wrong output directory.

Since this looks like a single-page app, I’d also add a rewrite so client-side routes do not 404 after refresh:

1
{
2
  "rewrites": [
3
    {
4
      "source": "/(.*)",
5
      "destination": "/index.html"
6
    }
7
  ]
8
}
9

Put that in vercel.json at the same level as package.json.

Vercel’s Vite guide shows the same SPA rewrite pattern here:

https://vercel.com/docs/frameworks/frontend/vite

vercel.com

Vite on Vercel

Deploy Vite projects to Vercel and configure environment variables, Vercel Functions, server-side rendering, and SPA rewrites.

One thing that would help narrow it down: does the Vercel build log show npm run build completing and creating a dist folder?