Is that 404 real?

A soft 404 is a page that appears missing or empty but answers with a successful HTTP status, often 200. Google can identify that mismatch and exclude the URL from indexing. Indie404 checks the status and bounded response text as a useful diagnostic; it does not reproduce Google's classifier.

HTTP 404 means the resource was not found at that address. HTTP 410 says it is intentionally gone and likely permanently unavailable. Choose the status that describes the resource.

Indie404 requests one made-up address on the site you enter and reads the status code, the redirects, and the page that comes back. It then fetches the home page and compares the two, so it can tell a real not-found page from a copy of the home page served under a missing address.

The same fetched HTML also shows whether the missing page contains an ordinary link to the measured home page. This observation is separate from the HTTP verdict. Indie404 inspects up to 100 anchors in the first 256 KiB, shows a matching link and its response source, and does not test visual placement, CSS visibility, or keyboard navigation.

The rules are the status semantics in RFC 9110 and the soft 404 guidance from Google Search Central, both named beside the result.

A generated missing path returned an unexpected success, redirected away, or failed with a server error. The outcome names the measured pattern and the suggested fix.

Redirecting missing URLs to an unrelated home page may be treated as a soft 404 by Google. Keep a useful error page with the appropriate missing status. Indie404 does not know Google's classification of a URL.

Configure a not-found handler in the framework or host, then verify the response status on the deployed site. A file or an error design alone does not prove the status. For example, Next.js not-found.js returns 200 for streamed responses and 404 for non-streamed responses.

Do not redirect missing pages to the home page, and do not render the not-found design inside a route that answers 200.

No. The check starts with one generated missing path on the origin you enter. Turn on the optional nested probe to add one generated path with two segments and compare its answer with the root. The recovery-link observation follows the same two responses without another request. A blog folder, an API, or a language prefix can still use a different handler, so check those real sections separately.

Yes. No account, no card, no premium plan, no upgrade nag, no hidden paywall. Indie404 is free, all of it.

There is no public lookup history. A network check sends the public input needed for that check to its named source. Local file tools process file contents in your browser. Cookieless analytics counts visits and fixed actions, never entered values or file contents. Anything the tool saves for you stays in your browser.