Step-by-step instructions
- Step 01
Open the netlify.app project URL; if that also 404s, focus on deployment first.
- Step 02
Check that the published folder contains index.html and that the deployment is marked successful.
- Step 03
If the root works but a specific link does not, verify the file path, capitalization and extension.
- Step 04
If /index.html works but / fails, inspect publication settings and any redirect configuration.
- Step 05
If the netlify.app URL works but the custom domain 404s, confirm the custom domain is assigned to this exact Netlify project.
- Step 06
Check DNS record targets for apex and www, including whether a second project accidentally claimed the domain.
- Step 07
Wait for DNS propagation; do not create duplicate projects just to fix a DNS problem.
- Step 08
Test in private mode and check Netlify domain diagnostics and deployment logs.
Before you finish: important checks
- Do not assume a Google Ads campaign changed your domain routing; DNS/deployment determines where it points.
Common problems and fixes
- Homepage correct only in incognito? Clear cache or check service-worker caching.
- Only custom domain wrong? Verify domain assignment and DNS targets, not just source files.
Frequently asked questions
Do I have to repurchase domain?
No, not to correct a typical 404 configuration error.
WordPress, hosting and AI interfaces change. Check the service's current documentation before changing billing, domain DNS, security or important site settings. Rayhan Studio publishes educational help, not guaranteed results.