if a generated WordPress archive represents a nonexistent resource, it should return HTTP 404. Returning HTTP 200 with an empty layout can confuse visitors, search engines, themes, and analytics.
Why it happens
A custom archive is not automatically a valid page just because its URL matches a rewrite rule. The data lookup still has to prove that the requested archive exists.
This matters for filtered archives, virtual routes, and pagination. A page can look empty because the filter has no matches, or because the requested page number is beyond the available results. In both cases, a real 404 response is usually clearer than an empty success page.
Why an empty 200 response causes problems
- Cause: the route matches, but the query returns nothing. Fix: mark the main request as 404.
- Cause: the theme expects a post object on a successful page. Fix: let WordPress use its normal 404 handling.
- Cause: search engines see a thin page as valid. Fix: send the appropriate 404 status; an additional
noindexdirective may be used.
A practical handling sequence
-
Validate the route parameters before building the query.
-
Run the lookup and calculate the real pagination range.
-
If there are no matches, or the page number is out of range, set the main WordPress query to 404.
-
Send the HTTP 404 status, prevent caching, and output
noindex. -
Confirm that valid archives still return 200 and remain indexable.
Common mistakes
Changing only the page text is not enough. A heading that says “Not found” still looks successful to crawlers when the HTTP status is 200.
Adding only noindex is also incomplete. It discourages indexing, but it does not tell browsers, caches, monitoring tools, or search engines that the requested resource is missing.
Do not apply the empty-state logic to every query. Secondary queries used by widgets or related-content sections can be empty without making the whole page a 404. Base the decision on the main request.
How I would test it
- A populated archive returns 200.
-
An empty archive returns 404 and
noindex. -
Pagination beyond the last page also returns 404.
-
Normal archives and secondary queries remain unchanged.
Define what an empty route means
An unknown generated archive or an out-of-range page can warrant 404, while an existing category with no posts or an internal search with no results may intentionally show a 200 empty state. Apply the rule to the route’s semantics. A genuine 404 already communicates removal to crawlers; noindex is supplementary, not a substitute for the status.
An empty generated archive is a routing decision, not only a display state. The concrete next action is to test one known-empty archive and verify its HTTP status and robots output.