Skip to content

404 Error Page Test

Short answer

Request a made-up URL on your site and check it returns a real 404, not a soft 404, and that the error page offers navigation, search and a home link.

What it does not do: It requests one made-up URL, so it cannot list the broken URLs that visitors or crawlers actually reach; the Page indexing report in Search Console does that.

Free · No signup · Fetched by our server
We fetch the URL on our server to run the check. Results aren't saved.

What It Does

Tests how your site handles unknown URLs by requesting a path that does not exist. Checks that the response has a 404 status rather than 200 (a "soft 404", which Google Search Console reports as an indexing problem) and whether the page helps visitors, with your branding, navigation, a search box and a link back home.

Why It Matters

Soft 404s — pages that say "not found" but return HTTP 200 — are reported in Google Search Console and can waste crawl budget on dead URLs. A helpful 404 page with navigation also gives lost visitors a way back into the site.

How It Works

  1. Enter your domain and click Test

  2. We request a non-existent URL and capture the response

  3. Verify HTTP status is 404, not 200 ("soft 404")

  4. Check the page for navigation, a search box, a link back home, and your site's branding

Sample input + output

INPUT
url: https://rankproof.eu
OUTPUT
Score: 75/100 — Returns a proper 404 status, but the error page could guide visitors better.
Status code: 404 (/rp-test-404-…)
Page size: 45.7 KB
Usability score: 75/100
Links on page: 50
Passed: Returns a real error status
Passed: Custom error page (not generic)
Passed: Has site navigation
Needs attention: Has a search box
Passed: Has a link back home
Passed: Shows your site's branding

How to read the result

Score (75) and headline
The score starts from the status code. A made-up address that answers 200 (a soft 404) scores 0, however good the page looks. A real 404 is scored on four signals of 25 points each. In the sample, 75 means the status is right and one of the four signals is missing.
Status code (404) and the test path
We request an address that cannot exist on your site, /rp-test-404- followed by a number, and follow any redirects. 404 is the right answer. 200 means the server claims the page exists, so search engines may keep the error page in their crawl. Any other status, such as 410, 403 or 500, gets a warning: 410 suits a page you removed on purpose, not an address that never existed.
Page size (45.7 KB) and the custom-page check
An error page under about 1,000 characters counts as generic: usually the server's bare default, with no menu and no way back. A generic page keeps at most 60% of the score even when the status is right. The sample page uses the site's normal layout, so it passes.
Usability score (75/100)
The four signals: your domain name appears on the page (branding), a <nav> or <header> element (navigation), a search field marked type="search" (search box) and a link to the home page. In the sample only the search box is missing, which is a warning, not a failure.
Links on page (50)
Every link on the error page, menus and footer included. It is not scored: it shows how many ways out a lost visitor has. An error page with a handful of links is close to a dead end.

Who Uses This

  • Technical SEO

    Validate the 404 template after every CMS or framework upgrade — catch the day a custom error handler returns 200 by mistake.

  • UX Designer

    Confirm the 404 page has a search box, navigation and a link back home, so lost visitors can find their way.

  • DevOps Engineer

    Run this after every deploy — confirm a non-existent URL still returns 404, not 200.

Common problems and how to fix them

  1. Soft 404: the error page answers 200

    Make the server or framework send the 404 status together with the page, not just the "not found" text: in a framework, return the not-found response from the catch-all route; on a server, point the 404 error to your page as below. Run the test again after every deploy.

    # nginx: your own page, with the 404 status
    error_page 404 /404.html;
    location = /404.html { internal; }
    
    # Apache (.htaccess)
    ErrorDocument 404 /404.html
  2. Every unknown address redirects to the home page

    Search engines treat such redirects like soft 404s, and visitors land on a page that does not answer their click. Keep 301 redirects for pages that moved to a close equivalent and let every other address answer 404.

  3. A bare server error page

    Serve your own error page with the 404 status and build it from the site's normal layout, so the logo, menu, footer and a link home appear on it.

    # nginx: your own page, with the 404 status
    error_page 404 /404.html;
    location = /404.html { internal; }
    
    # Apache (.htaccess)
    ErrorDocument 404 /404.html
  4. No search box

    Add a search form whose field uses type="search". If the site has no search, link the main sections or popular pages instead: the check still warns, but the visitor has a way forward.

  5. Old addresses keep getting visits

    This test checks one made-up address. To find the real broken ones, open the "Not found (404)" reason in the Page indexing report of Search Console, redirect those with an obvious replacement and leave the rest as 404.

Frequently Asked Questions

What's the difference between hard 404 and soft 404?
A hard 404 returns the HTTP 404 status. A soft 404 returns HTTP 200 with "not found" content. Google Search Console reports soft 404s as an indexing issue, and crawling them wastes crawl budget that could go to real pages.
Should I redirect 404s to the homepage?
No. Google may treat such redirects as soft 404s. Return a real 404 with helpful navigation, or redirect with 301 to a closely related page if the content moved.
Should the 404 page be `noindex`?
It does not need to be. Google does not index pages that return a 404 status, so a real 404 status is enough.
What should be on a good 404 page?
Clear "page not found" message, search box, top-category links, popular content recommendations, contact/support link, branded design.
How can I see all my 404s?
The Page indexing report in Google Search Console lists the not-found URLs Google has crawled.

Sources

The documentation this tool and the explanations on this page are based on.