Soft 404 Checker: Test Your Custom 404 Page
Check whether a missing page returns HTTP 404/410 or a likely soft 404. One test path on your site, custom vs default error page hints. Heuristic, not Search Console.
- Paste a URL on your site
- Run the soft 404 check
- Read the verdict and fixes
- Browser-based — no install
- Instant results
Paste one URL on your site. The checker fetches that page and one random missing path on the same origin, then compares status codes, redirects, and HTML to judge a likely hard 404 vs soft 404. Heuristic, one sample — not Search Console.
By Faisal YUpdated
You fixed internal links, submitted the sitemap, and Search Console still shows URLs that should not exist. Sometimes the problem is not the link — it is what your server returns when a URL is missing. A proper 404 or 410 tells crawlers the page is gone. A soft 404 looks like an error to humans or algorithms but sends the wrong HTTP signal — usually 200 OK with thin "not found" copy, or a redirect to the home page . Google's crawling documentation groups these under HTTP status and network issues and describes soft 404s as pages that return success codes while behaving like errors. You can monitor indexing reasons in Search Console ; this guide focuses on server behaviour you control. The Soft 404 Checker fetches your URL and one random missing path on the same origin, then compares status codes, redirects, titles, and visible text. It is a heuristic, one-sample test — not a copy of Google's Page indexing report. ! Three steps: fetch two URLs, compare status and content, output verdict and fixes What a real 404 and 410 look like 404 Not Found means the server has no representation for that URL right now. 410 Gone means the resource was removed intentionally and is not expected to return. Both are valid ways to drop dead URLs from crawl queues when used consistently. A good missing-URL response: Expected shape: The body can be a helpful HTML page with navigation — the critical part is the status line , not the design. What a soft 404 looks like in practice Common patterns: Error template with HTTP 200 — Title says "Page not found" but the status is 200. Redirect missing URLs to / — Users land on the homepage; crawlers may treat it as a soft 404.…
Read the full guideWhat this checker does
The Soft 404 Checker sends **two requests** to your site: one for the URL you paste, and one for a **made-up missing path** on the same origin (`/scrawl-404-test-` plus a random token). It never crawls your site and never asks Google anything. It compares HTTP status codes, redirect chains, titles, headings, visible text length, link counts, and fixed error phrases to estimate whether unknown URLs behave like a **hard 404/410** or a **likely soft 404** (for example HTTP 200 with "not found" copy, or redirects to the home page or login).
Signals are rule-based and capped. Verdicts are worded as **likely** or **appears** — they are not confirmations of how Google classified the URL.
How to read the verdict
- **Hard 404/410 (likely)** — The probe path returned 404 or 410 (possibly after redirects). That is what you want for URLs that do not exist. - **Likely soft 404** — The probe returned 2xx with error-like content, or weak heuristics on a 200 response. The server should return 404/410 instead of 200 for missing pages. - **Redirect to home / login (likely soft 404)** — Missing URLs should not be sent to `/` or a sign-in screen. Google documents home-page redirects for missing URLs as a soft 404 pattern. - **Other error status** — 401, 403, 429, or 5xx on the probe may be a WAF or server issue, not your normal error handling. - **Inconclusive** — The probe could not be fetched or returned an uncommon status.
The table compares your **given URL** with the **probe**. If the given URL itself is 404/410, the tool notes that this is that page's own status while the probe tests general site behaviour.
**Error page style** (when HTML exists) is a rough **custom** vs **bare-default** hint based on navigation, links, and common server default strings — not a design review.
How to fix by verdict
**Return a real 404 or 410** with a helpful HTML body. Do not serve error templates with HTTP 200. Do not use `noindex` on a 200 OK error template as a substitute for a correct status code.
**Stop redirecting unknown URLs to the home page.** Point users to search or key sections on a page that still returns 404.
**Use 410** when content is permanently removed and you want crawlers to drop the URL sooner.
**Keep a useful custom 404 page** — clear message, site navigation or search, links to popular sections. A real 404 status already signals removal; you usually do not need `noindex` on a proper 404 response.
**Redirect only to genuinely equivalent content** — not to unrelated hubs when the original URL is gone.
What this tool cannot do
- **One sample path only** — Shops, blogs, or apps may handle missing URLs differently per section; one random path can miss that. - **No Google Search Console data** — It cannot see Google's "Soft 404" reason in the Page indexing report or how Google classified your URLs. - **No site-wide crawl** — Use [Broken Link Checker](/tools/broken-link-checker) for links on a page or [Bulk Status Checker](/tools/bulk-status-checker) for URL lists you already have. - **No JavaScript rendering** — Client-side "not found" views served with 200 are judged on raw HTML only. - **Servers and WAFs** may answer automated requests differently than browsers. - **Heuristics produce false positives and false negatives** — Treat results as a quick server-level test, then validate important URLs manually.
Looking for broken links on a page? Use the [Broken Link Checker](/tools/broken-link-checker) (the `/tools/404-checker` address redirects there).
How this differs from other Scrawl tools
- **[Bulk Status Checker](/tools/bulk-status-checker)** — HTTP status for many URLs you supply. This tool probes how one site handles a URL that should not exist. - **[Broken Link Checker](/tools/broken-link-checker)** — Finds broken links on a page; does not test site-wide missing-URL behaviour. - **[HTTP Header Checker](/tools/http-header-checker)** and **[Redirect Chain Checker](/tools/redirect-chain-checker)** — Headers or redirect hops for one URL; no missing-path probe or soft 404 verdict. - **[Google Index Checker](/tools/google-index-checker)** — Indexing signals; cannot see server 404 handling. - **[Bulk Meta Robots Checker](/tools/bulk-meta-robots-checker)** — `noindex` across URLs; here `noindex` on the two sampled pages is only a minor signal.
Frequently Asked Questions
What is a soft 404?
A soft 404 is a page that looks like an error to users or crawlers but returns HTTP 200 (or redirects missing URLs to the home page). Google may treat that as a soft 404 in Search Console because the URL should return 404 or 410 instead.
What requests does this tool make?
Exactly two fetches: your URL and one random /scrawl-404-test- path on the same origin. Both go through SSRF-safe validation. No other paths are tested.
Is this what Google sees?
No. Google uses its own crawling and indexing systems. This tool only reports what your server returned to our fetcher for two URLs. It cannot read Search Console's Soft 404 classification.
Can it check my whole site?
No. Use Broken Link Checker to test links on a page, or Bulk Status Checker to paste a list of URLs. This checker is one origin, one probe path, one run.
Why is my 404 page flagged as a likely soft 404?
Common causes: the missing-path probe returned HTTP 200, very short error HTML, error phrases in the title, or the same title as your home page. Heuristics can misfire on minimal but valid error pages — confirm status codes in devtools or with curl.
What are the limits?
One input URL per run, two HTTP requests, HTML capped at 1.5MB, standard rate limits, and private or localhost URLs blocked.
Related tools
404 Checker & Broken Link Scanner
Crawl & AuditPaste a page URL and check every link on it for 404s, redirects, and server erro…
Bulk Status Checker
Crawl & AuditPaste up to 200 URLs and get each one's HTTP status — 200, 301, 404, 500 — with…
HTTP Header Checker
Utility ToolsInspect raw server response headers to verify caching policies, security headers…
Google Index Checker
Technical SEOCheck if any URL is indexed by Google instantly. Find why pages are not indexed…