404 Error
A 404 error means the requested page was not found on the server. It tells users and crawlers that the URL exists but has no content assigned to it.
Reviewed by Alexander Yarovenko · Updated: 2026-09-18
What is a 404 Error?
HTTP status code 404 Not Found is returned when a server cannot locate the requested resource. It differs from a 410 Gone (which signals permanent deletion) — a 404 is neutral: the page may come back.
SEO Impact of 404 Errors
A 404 on a URL that has backlinks wastes link equity. Googlebot will stop crawling a URL after repeated 404 responses and eventually drop it from the index. Soft 404s — pages that return 200 but show "Page not found" text — are worse because they waste crawl budget silently.
How to Handle 404s
- 301 redirect — if the content moved or a close equivalent exists
- 410 Gone — if the content is permanently deleted and no redirect makes sense
- Fix the link — if internal links point to a 404, update them
- Custom 404 page — help users find relevant content; include navigation and search
Finding 404 Errors
- Google Search Console → Pages → Not found (404)
- Server log analysis for 404 responses
- Crawl tools (Screaming Frog, Ahrefs Site Audit)
How to use this concept in SEO
A genuine missing page should return 404 or 410. Restore or redirect it only when a useful equivalent exists; redirecting every missing URL to the home page creates confusing soft-404 signals.
Audit checklist
- Confirm that the implementation matches the page purpose and the user task.
- Check the HTTP response, rendered HTML, canonical, robots rules, and internal links together.
- Use Search Console and analytics to verify the result instead of relying on one crawler signal.
- Test a representative URL on mobile and desktop after deployment.
- Document the expected outcome so regressions can be detected in the next audit.
Practical example
A deleted audit guide with backlinks is redirected to its updated replacement. A mistyped URL with no substitute keeps a helpful 404 page and a real 404 response.
How to validate the result
Record the current crawl, indexation, performance, and traffic state before changing anything. Recheck the affected template and a representative URL after deployment, then monitor Search Console over the following crawl cycle. A technical change is complete only when the live response and Google’s observed state agree.