Interactive decision tree · Free to use
Out-of-stock product SEO decision tree
Choose what to do with temporarily unavailable, seasonal and discontinued products. Get coordinated page, linking, sitemap, structured-data and feed actions.
Keep the product and update the affected offer.
Decide whether the page still has a purpose before changing its URL.
Alder and all supplied figures are fictional practice material. Apply the reasoning to verified evidence from your own store.
Work through your decision
Choose a lifecycle action
Your selections stay in this browser. Export the result without an account. Changing a selection requires a fresh result.
Find out what actually changed
Start with the authoritative product and inventory records. Is one size unavailable, or is the entire product retired? Is replenishment confirmed, seasonal, or unknown? Is a replacement genuinely equivalent? Does the original page still answer useful support questions? Those facts lead to different actions.
Do not delete a product because one variant is unavailable. Do not promise a return date without evidence. An unknown future is an investigation task, not evidence for a permanent redirect.
| Fictional Alder case | Decision |
|---|---|
| Cedar 2 green unavailable; sand still sells | Retain product and describe each variant accurately |
| Snow shelters return next winter with a maintained selection guide | Review a useful recurring category separately from invalid filter URLs |
| Old tent with manuals and compatible spare parts | Retain useful support information; remove obsolete purchase offers |
| Retired peg; no useful page or genuine successor | 404 or 410, with helpful navigation |
For returning products, keep useful information
Keep the stable product URL when the item is expected to return and the page remains useful. Display accurate availability, verified timing when known and suitable alternatives. Optional stock alerts should explain what they do. Keep unavailable variants from presenting an enabled purchase action unless the business genuinely accepts that order type.
Page, structured data and destination-specific feeds must agree about the same offer. Schema.org values and feed values use different formats. Do not copy an OutOfStock schema URL into a feed field expecting out_of_stock. Backorder or preorder claims require an actual supported ordering arrangement and channel-compliant dates.
For retired products, decide the page's remaining purpose
A support page can remain valuable after sales stop. Retain manuals, accurate specifications, care information or spare-part compatibility when that is useful. Make retirement clear, remove misleading buying controls, and distinguish any suggested successor from the original product.
When a genuinely equivalent successor satisfies the original intent and there is no reason to retain the old page, use a permanent redirect to the final destination. Otherwise, a real 404 or 410 is appropriate for a removed product with no continuing purpose. The homepage is not a universal replacement.
Update merchandising links and sitemaps with the page decision. Remove permanently unavailable offers from feeds according to the channel's rules. Do not delete support information simply because it no longer belongs in a shopping feed.
Review the whole customer route
Inspect the product page, selected variant, add-to-cart behavior, category cards, search results inside the store, structured data and feeds. A correct page can still be advertised as purchasable elsewhere. Record timestamps because stock may change between checks.
Shopify themes and integrations may choose a default variant. WooCommerce can manage stock at product or variation level and can hide out-of-stock items. Check those settings against the intended customer journey. Revisit the decision when new stock, support needs or a real successor changes the facts.
Sources and maintenance
Check current platform documentation before implementation. Review these instructions when your platform, catalog behavior or source guidance changes.