Discussion starter: an ecommerce SEO question, posted with an answer from Niraj Raut to open the thread. If you have dealt with this on a site, reply with what you saw, especially where it differs.
- eCommerce SEO
- Structured Data
Products out of stock for weeks: do you change status codes, availability markup, or nothing? Did Merchant Center disapprovals change your answer?
Disclosure: Niraj Raut, who posted this answer, runs the SEO consultancy linked at the end of it.
1 reply
-
adminAdmin
For products that are out of stock for weeks and coming back, change the availability, leave the status code alone, and keep the page useful. The page stays a 200, indexable, with its price, and says clearly that the item is out of stock (or on backorder with a shipping date, if you are still taking orders). The structured data and the Merchant Center feed change to match what the page shows.
Merchant Center disapprovals should not change the page decision, but they should change how seriously you treat synchronisation. Google disapproves products when the feed says in stock and the landing page or checkout says otherwise. Being out of stock is not the problem; disagreeing with yourself is. The fix is making the page, the markup and the feed read from the same inventory source at the same time, not hiding or removing the page.
The answer changes when the product is not coming back, when there is no restock date and the page has decayed into an empty shell, or when you run a catalogue so large and thin that index quality matters more than any single product URL.
Four layers that often get treated as one decision
Layer What it controls Temporarily out of stock Common mistake HTTP status Whether the URL stays in the index 200 404, 410 or a redirect for a product returning next month Visible page What users and crawlers see, and what Merchant Center checks against Clear out-of-stock message, disabled buy button, restock date if known, alternatives, back-in-stock alert Page stripped down to a single “unavailable” message that looks like an error page Product structured data How the product appears in merchant listings and product snippets availabilityset to OutOfStock (or BackOrder or PreOrder if orders are accepted), price kept on the OfferLeaving InStock, or removing the price or the whole Offer Merchant Center feed Eligibility and display across Shopping surfaces out_of_stock, orbackorder/preorderwithavailability_dateFeed updated once a day while stock changes every hour Why I would not change status codes for a temporary gap
A 404 or 410 tells Google the page is gone. It drops out of the index, and when stock returns the URL needs a recrawl and a period of re-evaluation before it earns what it did before. For a product due back in three weeks, that is a lot of disruption for no benefit. Redirecting to the category has a similar cost and a worse experience: someone who searched the exact product lands on a list and has to work out why.
Noindex is gentler but has the same problem at the other end. Google has to recrawl the page to see that the noindex is gone, and on a large catalogue low-priority product URLs are not always recrawled promptly.
The real risk of keeping the page is a soft 404. Google’s HTTP status code documentation says that when a server returns a 2xx code but the content is an empty page or an error message, Search Console will report a soft 404. Google’s John Mueller has said publicly that out-of-stock pages can be treated this way when they look like that. The protection is keeping the product content on the page: title, images, description, specifications, reviews, price and a clear availability message. A product page with a sold-out label is still a product page. A page that replaces all of that with “This item is unavailable” is not.
“Do nothing” is the worst of the three options:
If the storefront shows sold out but the JSON-LD still says InStock and the feed still says
in_stock, you get the exact mismatch Merchant Center disapproves, plus merchant listings that promise stock you do not have. Many themes and apps disable the buy button without touching the markup, so check the rendered JSON-LD on a real out-of-stock product rather than assuming the platform handles it.What Merchant Center actually disapproves
Google’s availability attribute help page is explicit: “Match the availability listed in your product data with the availability listed on your landing page and checkout pages.” It continues: “If we find that a product is out of stock on your landing page or during checkout, but the availability attribute is set to in_stock in your product data, we disapprove the product.” The same page asks for a disabled buy button or sold-out text for out-of-stock items, and requires
availability_datefor preorder and backorder.So disapprovals punish lag and inconsistency, not the stock position. The usual causes:
- A feed fetched once a day while the storefront updates stock in real time.
- Cached product pages serving stale availability to Google’s crawler.
- Variant products where the feed item is an in-stock size, but the landing page URL opens on a default variant that is sold out.
- Structured data generated from a different field than the buy button uses (for example a “published” flag rather than the stock level).
- Apps or themes that hide the buy button but leave InStock in the JSON-LD.
If disapprovals are frequent, the remedies are more frequent inventory updates (several scheduled fetches a day, or an API integration for price and availability), variant-specific landing URLs that preselect the feed item’s variant, and markup rendered from the same stock value that drives the buy button. Automatic item updates, where enabled, can correct availability from the page’s structured data, but they paper over a feed problem rather than fixing it. If the goal is to stop paying for Shopping ad clicks on items you cannot sell, the help page points to the
pauseorexcluded_destinationattributes, which is a cleaner lever than misreporting availability.OutOfStock, BackOrder and PreOrder are not interchangeable
BackOrder and PreOrder mean you are taking orders now and shipping later. The page must let people order and show when it will ship, and the feed needs
availability_date. OutOfStock means you are not taking orders. Marking an item BackOrder just to keep the buy button live, without a real restock date, leads to cancellations and a feed that disagrees with checkout.Keep the price on the Offer whichever value you use. Google requires a price on every Offer for merchant listing eligibility, so removing it to “hide” an unavailable item makes the markup invalid rather than more accurate. For products that are gone for good, schema.org has a Discontinued availability value, which is more honest than deleting the Offer.
Variants deserve their own check. If one size of a shoe is gone but the others are in stock, the product is not out of stock. Mark availability per variant (ProductGroup with per-variant Offers on the page,
item_group_idwith separate variant items in the feed) so the page does not advertise the whole product as unavailable.A decision flow for out-of-stock products
Product goes out of stock↓Is it coming back within a foreseeable period?↓Yes: keep the 200 and indexability; set OutOfStock (or BackOrder with a date); add alternatives and a back-in-stock alert; update the feed at the same time↓No, it is discontinued: is there a direct successor or near-identical replacement?↓Successor exists: 301 to it. No successor: keep a Discontinued page if it still earns links or informational searches (specs, manuals, compatible parts); otherwise return 404 or 410Hypothetical example:
A retailer has 4,000 SKUs, and around 600 go out of stock for three to six weeks at each seasonal changeover. The feed is fetched at 2 am, the storefront updates stock live, and Merchant Center shows a spike of availability disapprovals at every changeover. None of the product pages needs a status change. The fix is sending availability updates several times a day, making the JSON-LD read the same stock field as the buy button, and adding a restock date and three in-stock alternatives to the out-of-stock template. The disapprovals were a synchronisation problem that surfaced in Merchant Center first.
Where experienced practitioners reasonably disagree
Some teams redirect any product that has been unavailable longer than a set period (for example 60 or 90 days) to its category. The logic is that a long-dead page converts poorly and a list serves users better. The counter-argument is that exact-product searchers have high intent, and a product page with good alternatives serves them better than a category they must scan. I would settle it with data: if out-of-stock product pages still earn clicks and those sessions convert on alternatives or sign up for alerts, keep them. If they earn neither, the page is not doing its job and the timeout rule is reasonable.
On very large, thin catalogues (marketplaces, dropship stores with hundreds of thousands of supplier SKUs that come and go), noindexing or removing long-unavailable items can be justified to keep crawling focused on live inventory. That is a scale and quality decision, not a default for a typical retailer.
What to monitor
- Merchant Center diagnostics for availability mismatches, by product and date, to see whether they cluster around stock changes or feed fetch times.
- The Search Console Page indexing report for “Soft 404” on product URLs, especially out-of-stock ones.
- The Search Console merchant listings and product snippets reports for markup errors after theme or app changes.
- Organic clicks to out-of-stock pages, plus conversions on alternatives and back-in-stock signups from those sessions.
- Time from restock to both the feed and the markup reading in stock again.
My decision rule
For a temporary gap, do not touch the status code. Do change availability, and change it everywhere at once: page, markup and feed from one inventory source. Treat Merchant Center disapprovals as a sync alarm, not a reason to remove pages. Revisit the URL only when the product is genuinely not coming back, and then choose between a successor redirect, a discontinued page that still earns its place, or removal, based on whether the URL still attracts links, searches or sales.
Need help with this on your own site?
Niraj Raut works with businesses in Nepal, Australia, the UK, Europe and the US on technical SEO, ecommerce SEO, local SEO and AI search.
Add a reply Cancel reply
Replies are open to approved members. Log in or apply to join.