Page says not found but answers 200
What it is
The server answers the URL with status 200 (OK), but the page itself says the page was not found: its title or main heading reads “Page not found”, “404” or the same in another language. Visitors land on a dead end, while crawlers are told the address is a live page. It usually comes from a catch-all route or CMS template that shows a not-found message without setting the status.
Why it matters
Google calls this a soft 404 : it has to guess that the page is empty, keeps crawling the address, and reports it in Search Console instead of dropping it cleanly. Other search engines and AI crawlers may not guess at all and keep an empty page as a real one. When your sitemap lists such addresses, crawlers spend their visits on dead ends instead of your real pages.
How Asky checks it
Asky reads the page’s title and first visible H1, split at separators such as | or -. The page is reported when it answers 200, has under 300 words of its own copy (menus and footer left out), and a part of either is a whole not-found message with at most a site name at either end: “404”, “Page not found”, “We can’t find that page” or the same in nine other European languages. Text about 404s, such as “What is a 404 error and how to fix it”, is not a match. The page gets no other finding. A page that answers 404, even with full content, is a 4xx error instead.
Reported as an error with high severity.
How to fix it
- Open the URL and check the status in your browser’s developer tools (Network tab) or with an HTTP status checker.
- If the page is gone, make the address answer 404, or 410 when it is gone for good. In most CMSs that means fixing the catch-all route, rewrite rule or template that serves the not-found text with status 200.
- If the content moved, redirect the address to its new URL with a 301 instead.
- If the page should exist, restore or republish its content so it no longer shows the not-found message.
- Remove the address from your sitemap and update internal links that still point to it.
Example
https://example.com/old-offer shows “Page not found” but the status gives it away:
curl -s -o /dev/null -w "%{http_code}\n" https://example.com/old-offer
# 200 before the fix, 404 after