An empty filter result returns HTTP 200
In the reportZero-result filter pages return 200 instead of 404
facet_empty_result_returns_200 · Review item
The recorded filter response says it has no results but answers 200. Return 404 or 410 at that address, or provide actual results there. An empty grid alone does not trigger this rule.
Severity: Medium. Review the static result reading before changing a filter page that may show results after browser scripts run.
Why it matters
Google advises returning 404 at the original address for empty filter combinations.
What to do
- Inspect the recorded requested address, status and local zero-result indicator.
- For a truly empty combination, serve an appropriate not-found response at its own address. Keep useful views available.
- Run a new full audit of all retained old members and their control/source pages.
When to leave it as it is: If the server response is intentionally incomplete and the browser supplies results, inspect the rendered view and the server response before changing its status.
What we read
A filter pattern must be proved from original local GET controls with supported action, names and values. A query keyword or matching text alone does not establish a filter.
We reuse original captured HTML, links, member responses and the same main-content preparation. We do not generate filter combinations or introduce a new sentinel request.
The stable subject uses the rule, origin, exact path and sorted proved filter names. Changing values, representatives or samples does not replace the old member/source obligations. Report examples are limited; comparison debt retains the full original set.
A positive requires direct 200 with complete server HTML, a unique main/listing region, an exact visible zero-result indicator and no contradictory positive count or linked listing item.
An empty container, cart count, hidden/template text, browser-only shell or missing message is unknown. An affirmative nonempty reading requires a positive result count and at least one linked listing item.
Example & evidence
Illustrative example, not a live audit.
GET /catalog?color=red&size=s
HTTP 200
<main><h1>Kettles</h1><p>No results found.</p></main>
No positive result count or linked listing item is present.Confirm & check again
Check for yourself: Request the exact filter address and inspect its status and page source. Compare the result count, listing items and visible zero-result message; a browser may show additional content.
Check again: Full audit — Run a new full audit. Every old member must have a qualified same-address 404 or 410, or affirmative nonempty results in current complete server HTML, with the original controls and sources checked. Message disappearance, noindex, a canonical, a generic redirect, a different sample or missing coverage does not prove a fix.
Limits & sources
The audit does not render JavaScript or count products in a browser. An explicit static indicator is a heuristic, and incomplete or contradictory evidence is not a clean result.
Confidence: Medium The indicator is explicit in captured server HTML, but browser results remain unconfirmed.
Sources
- Google, Managing crawling of faceted navigation URLs — Recommends a not-found response at the original address for empty filter combinations. The narrow static classifier and retained comparison policy belong to the product. Checked 13 October 2026.
Editorial review: 2 November 2026