Fix soft 404s on empty category pages by how long stock is gone

HTML line: <meta name="robots" content="noindex, follow">

Summary

Empty category pages that are waiting on new stock need a temporary indexing signal chosen by how long the gap will last, because a page left flagged as low quality is slow to come back in results after restocking.

Drive that signal from the category's product count, so it comes off by itself when stock returns.

Category pages that return a normal 200 status but list no products are being flagged as soft 404s in Search Console’s Page Indexing report. A thread in r/TechSEO asks what to do when those products are coming back. Removing the pages was not an option, because restocking was planned, sometimes months away.

The poster agreed with Google’s classification. Each page held a header, footer, navigation and a “no products found” message and nothing else.

The usual ways out were all closed. The client would not return a 404 or 410, a redirect to the parent category would confuse shoppers, and noindex risked slow re-indexing once stock returned. One commenter suggested a 302 redirect to a relevant category, or internal links to categories that still have stock. Another suggested putting restocking information on the page itself.

Leaving the pages flagged has a cost

Google’s guide to managing crawl budget tells site owners to fix soft 404s, because those pages “will continue to be crawled, and waste your budget.” For a shop with a few hundred fixed categories, the bigger worry is index quality and what visitors land on. A marketplace with tens of thousands of brand, size and color combinations can see thousands go empty in a season, and at that scale the wasted crawls come out of pages that do have stock.

Recovery is the other cost. A page treated as low-quality while it sits empty is slow to return to results after restocking. That is the same delay the poster feared from noindex, reached by a different route.

Match the signal to the length of the gap

Every option trades one risk for another, so the better bet is to choose by how long the category is expected to stay empty:

  • Days to a few weeks: keep the 200 and accept the flag for a while. Give the page a job with links to sibling categories that have stock, an expected restock date, and a signup for restock alerts. A lone “no products found” line will not clear the soft 404, but relevant internal links plus real copy about the category might.
  • One to three months: use a 302 to the closest parent or sibling category. Google’s redirect documentation says the indexing pipeline does not treat a temporary redirect as a signal that the target should be canonical, and it names a temporarily unavailable service as the use case. A 302 left in place for months tends to act like a permanent redirect for indexing, so watch the original URL in Search Console and reassess as the gap nears three months.
  • Longer than three months: add noindex, follow. Visitors arriving by direct link still get the page, and Googlebot can still follow its links, although links on a long-noindexed page tend to lose their ability to pass signals. Expect a slow return after the tag comes off.

Robots.txt is sometimes offered for long gaps instead, on the theory that Google cannot see the page is empty and the URL keeps its place. The crawl budget guide says blocked URLs are recrawled when the block is removed, but also that blocking “significantly decreases the chance” a URL gets indexed at all. While the block is in place, the stale “no products” version may show in results, and Google cannot see content added to the page or follow its links. A block fits only pages with nothing worth showing while empty, and only where the inventory feed can lift it automatically. An earlier piece on noindex versus robots.txt for millions of stub pages covers the same tradeoff at a much larger scale.

A canonical from the empty child category to its parent is the one option to rule out. A canonical tells Google the two URLs hold the same content, and they do not. Google may fold the child into the parent, and after restocking the child can take much longer to be indexed on its own because Google had treated it as a duplicate.

What to do

  1. Tie the signal to the inventory system. A noindex tag or 302 that depends on someone remembering to remove it will not get removed. When a category’s product count drops to zero, the template should apply the temporary signal, and when the count rises above zero, the signal should come off with no one touching it. An illustrative template rule for the long-gap group, assuming the platform stores an expected restock gap per category:
{% if category.product_count == 0 and category.expected_gap_days > 90 %}
  <meta name="robots" content="noindex, follow">
{% endif %}
  1. Expect Search Console to lag after restocking, because a soft 404 flag can persist until Google recrawls and reprocesses the URL. Request Indexing in the URL Inspection tool queues one URL at a time, so for a catalog, update the lastmod values in the XML sitemap, link the restocked categories from high-priority pages, and keep checking those URLs until they are indexed again.