Open a product page that you know does not exist and check its response code. If the page says “Product not found” but the server returns 200, the developer needs to fix how missing URLs are handled. Google may identify these pages as soft 404: to Google, a successful response does not match the error content.
First, make sure the product has actually been removed. A temporarily unavailable database, an out-of-stock product, and an unknown URL require different solutions.
Check the response for an unknown URL
In Chrome, open Developer Tools, go to the Network tab, and load the URL directly. Select the document request and check the Status Code. Navigating within the app may load only data, so also check the page by refreshing its full URL.
A developer can save the response with this command:
curl -sS -D headers.txt -o response.html 'https://example.com/product/unknown/'Replace the domain with your own. The first line, headers.txt, will show the HTTP status, and response.html will contain the returned HTML. Compare it with what appears in the browser after scripts run. If the HTML contains only an empty shell, note which data request later reports that the product is missing.
Choose a response based on the product’s status
Suppose you removed model A-101, but model A-102 is temporarily out of stock. You can delete the first product page or redirect it to a suitable replacement. It may make sense to keep the second page if its description is useful to customers and the product is genuinely expected to be sold again.
| What happened | What the visitor should receive |
|---|---|
| The product page never existed | An error page with status 404 |
| The product has been permanently removed, with no replacement | 404 or 410 with clear navigation |
| The product page has moved | A permanent redirect to the same product page at its new address |
| The product is temporarily out of stock | An active product page with accurate availability information |
| Data failed to load because of an outage | A message about a temporary problem; the product is not declared removed |
You don’t need to send every unknown URL to the homepage: the person was looking for a specific product. For more about codes, see the HTTP response codes reference.
Find the setting that always returns 200
Give the developer two URLs: a working product page and an unknown path. Ask them to check how the CMS or app detects that a record is missing and which status it sends to the browser.
A common cause is that the server returns the same HTML shell for every path, and a script later displays “not found.” The status of a document that has already been sent cannot be changed this way. Choose a fix that fits how the app is built: for example, check whether the product exists before sending the HTML, or use the error handling provided for routes.
If the message appears for an existing product, investigate the data failure and cache first. Replacing the response with 404 in this case would hide a working product page rather than restore it. In the task, specify whether the product exists in the catalog and whether other product pages can be opened.
Compare the current page with Search Console
In Search Console, inspect the URL and find the date of its last crawl. The soft 404 message may refer to a version from before the fix. Compare it with today’s response, and keep both dates.
HTTP 200 alone does not guarantee indexing. Google evaluates the content it receives; its rules are described in the documentation on HTTP status codes. Your request confirms the code and page text, while the Search Console message shows how Google processed it.
Check the fix on several URLs
After publishing the fix, check a working product page, a product removed without a replacement, a random unknown path, and a temporarily empty category. Each should have the chosen status and content. A 404 page can still have a header, search, and catalog links—they do not require a 200 response.
Remove the deleted product page from the sitemap and update links you control. For a previous URL with a suitable replacement, check the destination product after the redirect. Then run a page audit; separate causes of incorrect responses are covered in the article about soft 404.