Why Does Perplexity Describe My Product as Discontinued When the Product Page Is Still Live?
Perplexity describes your product as discontinued, even though its page is still live, because other sources, or signals on your own site, suggest it has gone. Common causes include retailer pages that say "no longer available" or "currently unavailable", and a newer product with a similar name. An old announcement about a different version or region, or a product page that says "out of stock" with no restock date, can do it too. So can structured data or a product feed set to discontinued by mistake, or a page Perplexity cannot fetch properly. Perplexity writes each answer from the sources it cites, so open those first. Then fix your own page and data, correct the retailers and the successor confusion, and make sure Perplexity's crawler can read the page.
What makes a live product look discontinued?
| Signal | Where it comes from | Why Perplexity reads it as discontinued |
|---|---|---|
| "No longer available" on retailer pages | A retailer stopped stocking it, or a listing lapsed | Retailer pages rank well and state it plainly |
| A successor with a similar name | "[Product] 2" launched, and articles say it "replaces" the original | The original is assumed to be retired |
| An old announcement | A post about retiring one size, colour, region or plan | The scope is lost in the summary |
| "Out of stock" with no date | Your own product page during a supply gap | Indefinite unavailability looks like discontinuation |
| Markup or feed values | Availability set to discontinued or out of stock by mistake | Perplexity's live fetches read the visible page, not JSON-LD, but a wrong value can still leak into retailer listings, Google Shopping data and any feed you share with Perplexity |
| Missing from navigation and category pages | Removed from menus during a redesign | The product looks orphaned |
| Page unreadable to the crawler | Blocked, erroring or rendered by script | Perplexity cannot confirm the page's content |
What does a "discontinued" answer cost?
More than it seems. A shopper who reads that a product is discontinued rarely checks further. They choose a competitor, or buy the successor at a higher price when the original suited them better. Retail buyers who research ranges with AI assistants may drop the product from their plans. Support teams field questions from existing owners worried about parts and warranties. Track the claim like any other product issue: note when it first appeared, which assistants repeat it, and whether sales or enquiries for the product changed.
How do you diagnose it?
- Ask Perplexity "Is [product] discontinued?", "Where can I buy [product]?" and "What replaced [product]?" several times, and open every cited source.
- Find the sentence in each source that suggests discontinuation.
- Check your product page as a crawler sees it. View the page source to confirm the name, price and availability are in the HTML, and check the page returns a normal status.
- Check your structured data and feeds for the availability value. Discontinued, out of stock and in stock should match reality.
- Check your robots.txt and bot protection for Perplexity's crawler.
- Check retailer listings for your product.
- Search for your product name with "discontinued" to find articles and posts carrying the claim.
Whether Perplexity is finding your page but leaving it out is covered in how to check whether Perplexity found your page but excluded it.
How do you fix your own page and data?
- State availability in plain text, near the price: "In stock, ships in 2–3 days", or "Temporarily out of stock; back in May 2026".
- If a successor exists but the original is still sold, say so on both pages: "[Product] is still available alongside [Product 2]. [Product 2] adds [differences]." This single sentence removes the most common confusion.
- Correct structured data and feeds so availability matches the page. For products that really are temporarily unavailable, use out of stock or backorder, never discontinued.
- Restore the product to navigation, category pages and your sitemap if it was dropped.
- Make the page readable without scripts, and allow Perplexity's crawler through robots.txt and any bot protection.
- Publish a current product lineup page listing everything you sell, which gives assistants one clear source for "what does [brand] make?"
How to handle stock status across feeds and markup is covered in how retailers should handle AI recommendations for out-of-stock products.
How do you fix the sources outside your site?
- Retailers: ask those showing "no longer available" to restock, relist, or mark the product as available from other sellers. If a retailer has genuinely stopped selling it, ask it to link to your where-to-buy page.
- Articles and posts: where a review says the product was "replaced" or "discontinued", send the publisher a short correction with evidence. For old announcements about a partial retirement, add a dated clarification on your own copy stating exactly what was retired.
- Comparison and price sites: update listings that show the product as discontinued.
- Report the answer in Perplexity, with the thread link, the product page and the reason the claim is wrong.
What if part of the range really was discontinued?
Then be precise about which part. "We discontinued the 500 ml size in 2025. The 1 litre and 2 litre sizes remain available" prevents the whole product being written off. Put that precision on the product page, the announcement and any help articles. A clear record of what was retired helps assistants describe what remains. How to communicate a genuinely discontinued line is covered in how to tell Gemini that a brand no longer sells a discontinued product line.
How long does it take?
Changes to your own page and data can show up in Perplexity's answers once its crawler refetches the page; Perplexity does not publish how often that happens. Retailer and article changes depend on each site. Rerun your questions weekly for a month, and keep a list of which sources still carry the claim. Why Perplexity keeps citing pages that have changed is covered in why Perplexity still cites pages or reviews that were deleted or corrected.
What might an illustrative case look like?
Consider an illustrative kitchen appliance brand whose original blender was still selling well after it launched a "Pro" model. Perplexity answered "Is the [blender] discontinued?" with "Yes, it has been replaced by the [blender] Pro", citing a review headlined "The Pro replaces the original" and two retailers that no longer stocked it. The brand's own page said nothing about the Pro. Its product feed had marked the original as out of stock during a two-week supply gap and never reset it. The brand added "Still available alongside the Pro" to both product pages, fixed the feed, asked the reviewer to add a clarification, and pointed the two retailers to its where-to-buy page. Two weeks later, Perplexity described both models as current.
What do people ask about "discontinued" claims in Perplexity?
Why would Perplexity trust a retailer over my own product page?
Retailer pages often rank well and state availability plainly. If your page is vague about availability or hard to read, the retailer's statement wins.
Can a temporary stock-out cause this?
Yes, especially if the page or feed shows out of stock with no restock information for a long time. Give a date or a range when you can.
Do other assistants make the same mistake?
Often, for the same reasons. Fixing the sources helps every assistant, not only Perplexity.
Published by The Kovmere Team · updated Sep 29, 2026 · More resources