An out-of-stock product is a product a customer cannot buy right now. How you handle it decides whether an AI assistant recommends it anyway, recommends a replacement, or stops recommending your brand because the last recommendation ended in a dead end. The rule is simple to state and easy to get wrong in practice: tell the truth about availability, in the same words, in every place a system reads it, and keep the page alive so the truth has somewhere to live.
Google's product structured data docs say that when you add structured data to your product pages, users can see price, availability, review ratings, shipping information, and more right in search results. Availability is one of the facts a shopper acts on immediately. If the page says in stock and the checkout says sold out, the shopper blames the brand, and the system that recommended the product learns not to trust the next recommendation either.
Name the state correctly
Out of stock is not one state. It is several, and each one needs a different answer:
- Temporarily out of stock. You will have it again, and you are not taking orders for it right now. The page should say so, and say when it is expected back if you know.
- On backorder. You are taking orders now, and the product will ship when it is available again. The page must show the expected shipping date.
- On preorder. The product has not been released yet, and you are taking orders for the release. The page must show the availability date.
- Sold out for a variant. One size or color is gone, and the others are still available. The page should show which variants are available and which are not, not a single blanket status for the whole product.
- Discontinued. You will not sell it again. The page should say so, and point the shopper to the replacement.
Getting the state wrong is worse than saying nothing. A backorder listed as out of stock loses a sale you could have made. A discontinued product listed as temporarily out of stock wastes a shopper's time and teaches an assistant that your availability data cannot be trusted.
Keep the page live
Do not delete the product page when it goes out of stock, and do not return a not-found error for it. A deleted page breaks every link that pointed to it, erases the reviews and the ranking it earned, and tells a system the product never existed. A live page with a clear out-of-stock status keeps the reviews, keeps the links, and gives the assistant a place to send a shopper who asks about that product.
What a live out-of-stock page should do:
- Say clearly, near the top, that the product is out of stock, and say whether it is coming back. A shopper should not have to scroll to the buy button to learn the product cannot be bought.
- Disable the buy button, or replace it with a clear alternative, such as a notify-me button or a link to the replacement. Google's Merchant Center help says that for out-of-stock products, you can display clear text such as sold out or item not available, or use a disabled or greyed-out buy button.
- Show the alternatives on the same page. The closest in-stock product, the next size up, the newer model. A shopper who came for one product and finds a good replacement is a sale saved. A shopper who finds a dead end is a sale lost.
- Keep the product information visible: the description, the photos, the reviews, and the price it sold for. The page is still useful as a reference, even when the product cannot be bought today.
If the product is permanently discontinued, keep the page live with a discontinued status and a link to the replacement, or redirect it to the replacement product or the parent category once it has no traffic left to serve. Do not leave a discontinued page claiming to be temporarily out of stock. That is a false promise, and a system that reads it will treat your availability data as unreliable.
Make the markup, the page, and the feed agree
Availability lives in three places, and all three must say the same thing:
- The visible page. The words a shopper sees, and the state of the buy button.
- The structured data. The availability value in your Product markup, using the schema.org ItemAvailability values. The vocabulary lists the values plainly: InStock, OutOfStock, Discontinued, BackOrder, PreOrder, PreSale, LimitedAvailability, SoldOut, and others. Use the value that matches the real state. A temporarily unavailable product is OutOfStock. A product you will not sell again is Discontinued. A product you are taking orders for before release is PreOrder, and a product you are taking orders for while waiting on stock is BackOrder.
- The product feed, if you use one. Google's Merchant Center help says the availability values in your data source should always match the information on your website, and that the availability attribute is required for all products. It also says to provide the most up-to-date data, and to show a consistent availability across the landing page, structured data, checkout page, and data source. A mismatch in one of these will trigger a product disapproval.
The most common failure is a feed that updates slowly while the page updates fast, or a page that updates fast while the markup is cached. Check all three after a stock change, not just the one you edited. A mismatch is not a small error. It is a product that gets disapproved, or a recommendation that ends in a sold-out page.
For variants, the rule applies per variant. Google's Merchant Center help says the availability of a product variant in your data source should match the availability of the same product variant on its landing page. If one size is out of stock and the others are not, mark that size as out of stock and leave the rest alone. A product-level status that hides a variant-level shortage will send shoppers to a size that does not exist.
Use backorder and preorder properly
Backorder and preorder are not polite ways to say out of stock. They are promises to take an order now and deliver later, and they carry their own rules.
- Backorder is for a product that is out of stock now and will be back in stock later, and you are accepting orders for it. Google's Merchant Center help says you must provide the availability date attribute to indicate the day it will be shipped, and that the date should be visible on the landing page.
- Preorder is for a new product that has not been released yet. You must provide the availability date to indicate the day it becomes available for delivery, and the date should be visible on the landing page.
- Do not use preorder for an existing product that is out of stock and will be back later. That product is a backorder, not a preorder.
- Do not use out of stock when you do not want the product to show. If the product is available for sale but you want to stop it showing on a destination, use the excluded destination or pause attribute instead. Google's Merchant Center help says that if it finds a product in stock on your landing page but set to out of stock in your data, it will disapprove the product.
If you cannot give a real availability date, say so, and do not take the order. A backorder with no date is a promise with no deadline, and a shopper who waits for a date that never comes will not come back.
Offer the next step, not a dead end
An out-of-stock page that only says sold out is a dead end. An out-of-stock page that offers the next step is a sale in progress:
- A notify-me option for the same product, so the shopper can be told when it is back. Keep the promise: send the notification when it is actually back, not when you hope it will be.
- The closest in-stock alternative, with a short note on how it differs. The shopper came for a specific product. Show them the one that does the same job.
- A link to the category page, for the shopper who wants to browse rather than wait.
- For a discontinued product, a clear link to the replacement, with a note on what changed. A shopper who bought the old model is the most likely buyer of the new one.
An assistant that recommends a product needs to know what happens when the shopper clicks. If the click leads to a clear next step, the assistant can recommend with confidence even when the first choice is gone. If the click leads to a dead end, the assistant will stop recommending the brand.
The fundamentals
These mechanics are shared across every engine and covered in full in their own guides:
- •The llms.txt format and a complete sample, see our guide to writing a good llms.txt file
- •The markup this engine reads, see our product schema guide
- •The complete crawler rule reference, see our robots.txt guide for AI search
Say you run a running shoe brand
Say you sell running shoes, and your most popular trail shoe sells out in the most common size. You do not delete the page. You keep it live, and you mark that size as out of stock in the markup, on the page, and in the feed, while the other sizes stay in stock. The page shows a clear sold-out note on that size, a notify-me button for it, and a link to the same shoe in the closest size, plus a link to the newer model that replaced it for runners who do not want to wait. A shopper asks an assistant for the trail shoe in their size, and the assistant can see that size is out of stock, and can recommend the next size or the newer model instead of sending the shopper to a dead end. A few weeks later the size is back, the notify-me emails go out, and the page goes back to in stock in all three places at once. The recommendation survived the stockout because the truth was in every place the assistant reads.
What this guide does not cover
This guide covers how to handle a product that cannot be bought right now. It does not cover the product schema in full detail, which is our product schema guide, or the price and availability markup for variants, which is our guide to marking up product variants, or the transaction layer that turns a recommendation into a sale. Availability gets you recommended without a dead end. The rest of the system has to be ready when the shopper arrives.
Check your own brand now
Run the free scan. It takes seconds, no signup, and shows whether AI crawlers can read your pages today: aizii.ai/aeo-scan
Run the free scanSources
- Google Search Central, Product structured data (specific): https://developers.google.com/search/docs/appearance/structured-data/product
- Schema.org, ItemAvailability type (specific): https://schema.org/ItemAvailability
- Google Merchant Center Help, Availability (specific): https://support.google.com/merchants/answer/6324448
Note: links marked specific point to the page that supports the claim in this guide. Links marked general docs point to the vendor's general docs section for that topic, not to a page that proves every step. Check the vendor docs for the current path before relying on a menu name or click path in this guide.
