Discontinued Product Pages

TL;DR — A discontinued product is one you’ll never sell again — that’s the key difference from something that’s just temporarily sold out. Before you delete the page, ask two things: do you sell something similar now, and did the page earn any links or traffic? If you have a similar replacement, redirect the old page to it. If you don’t, but the page was popular, redirect it to the closest matching category. Only let a page truly disappear (return “not found”) if it’s gone for good and nothing links to it. The big mistake is deleting a page that earned links and rankings — you throw all that away.

Discontinued is not the same as out of stock

These two get lumped together, but they need opposite treatment:

• Out of stock means the product is unavailable right now but coming back. You keep that page live and just mark it unavailable, so Google notices the moment it returns. (That’s a whole topic on its own — see out-of-stock products.)
• Discontinued means it’s gone for good. The manufacturer stopped making it, or you dropped the line. It is never coming back, so there’s nothing to wait for.

This page is about the second one — the permanent goodbye — because it’s a different decision entirely.

The page still has value — don’t just delete it

Here’s what people miss: a product page you’ve had for a while has quietly built up value. It ranks for searches. Other sites link to it. People bookmark it. When you delete it the instant the product is discontinued, all of that evaporates.

So the question isn’t “should I delete this?” It’s “where should this page’s value go?” That points you to one of a few answers.

The simple decision

1. You sell a similar replacement. Redirect the old page to the new one. A redirect (specifically a 301, the permanent kind) can carry the old page’s value forward — as long as the replacement is genuinely similar. Google doesn’t publish a transfer percentage or guarantee the same rankings land on the new URL, but a relevant redirect gives the successor the best shot at inheriting what the old page earned. Evidence for this claim Permanent redirects are appropriate when a discontinued URL has a genuinely equivalent replacement. Scope: Redirect relevance matters; unrelated redirects may be treated as soft 404s. Confidence: high · Verified: 2026-07-14 Google: Redirects and Search Redirecting a discontinued blender to your new blender is great. Redirecting it to your homepage is not — Google sees through that.

2. No replacement, but the page was popular. Redirect it to the closest relevant category — “all blenders,” say. That keeps the value in a sensible place.

3. No replacement, and nobody linked to it. Just let it return “not found” (a 404). This sounds scary, but 404s don’t get you penalized — Google has said this over and over. For a genuinely dead page nobody cared about, it’s the correct answer. Evidence for this claim Serving a 404 for content that no longer exists is normal and does not itself cause a sitewide penalty. Scope: Existing links and user value should still inform whether a relevant redirect or useful archive is better. Confidence: high · Verified: 2026-07-14 Google: 404 errors

4. It’s gone, but still worth keeping around. Sometimes a discontinued product still gets searched for, or has manuals and support info attached. In that case, keep the page up, clearly say it’s discontinued, point people to alternatives, and make the page actually useful. Don’t leave a bare “not available” shell — Google may quietly drop a thin dead-end page.

The one trap

Don’t redirect a discontinued product to your homepage (or some random unrelated page) just to “save the link value.” Google treats an irrelevant redirect like that as a dead page anyway — so you lose the value and you send shoppers somewhere useless. Redirect to something relevant, or don’t redirect at all.

Want the technical version — exact status codes, the Discontinued schema value, the soft-404 mechanics, and how to find which dead pages actually earned links? Switch to the Advanced tab.

TL;DR — Discontinued = permanently gone, which is the opposite of a temporary stockout and takes the opposite treatment. This is an end-of-life decision. Genuinely similar replacement → 301 to it. No replacement, page has backlinks/traffic → 301 to the closest relevant page (parent category, not the homepage). No replacement, nothing worth saving → 404/410 (not a penalty). Real reference value → keep live at 200 as a Discontinued tombstone with substantive content. Neither move guarantees a specific ranking or link outcome — Google doesn’t publish a transfer figure — but a relevant redirect gives the successor the best shot. The two failure modes that cost you: 404ing a backlinked page (equity lost for nothing) and redirecting to an irrelevant page like the homepage (Google reads it as a soft 404, equity lost anyway). Use schema.org/Discontinued, not OutOfStock — Discontinued signals never returning — but that’s just vocabulary; it doesn’t guarantee a rich result or Merchant listing on its own. Canonical and noindex are separate tools that don’t replace this decision: canonical picks among duplicates, and noindex only kicks in after Google has already crawled the page. Keep the tombstone page substantive, because a thin “no longer available” page gets algorithmically classified as a soft 404 regardless of its 200 status. A single discontinued variant needs the same care — check whether sibling variants are still active before you redirect or remove it.

Frame it as end-of-life, not availability

The out-of-stock decision hangs on “is this coming back?” For a discontinued product that question is already answered — no — so the framing changes. The job now is purely about where the page’s accumulated value should go, and whether the URL is worth keeping alive at all. That splits four ways:

1. Similar replacement exists → redirect to it.
2. No replacement, page earned links/traffic → redirect to relevance.
3. No replacement, nothing worth saving → let it go (404/410).
4. Real reference value → keep a tombstone page live.

My general take, from my Ahrefs writeup on out-of-stock and discontinued products, is that there’s no universal right answer here — it depends — so the practical move is to set rules you’re comfortable with and apply them consistently across the catalog rather than hand-deciding every dead SKU.

Branch 1 — similar replacement exists: 301

If you’ve genuinely replaced one product with a successor, redirect. Mueller’s line is direct:

“If you’re really replacing one product with another it might make sense to just redirect.”

A 301 to a closely comparable replacement can carry forward the link value the old page earned — if the pages are similar enough, as I put it in that Ahrefs piece: a 301 “will also maintain any link value if the pages are similar enough.” That’s a practitioner rule of thumb, not a Google guarantee — Google documents the redirect mechanism and destination-relevance guidance but doesn’t promise a specific ranking or link outcome for any individual redirect. The whole thing turns on relevance: the target has to actually be the same kind of product. A v2 of the same item, the same model in a new year, the nearest equivalent SKU — those are fair redirects. “The closest thing we still sell” that isn’t really close is where this starts sliding toward a soft 404 (see the trap below).

Update your internal links to point at the replacement, not the dead URL, so you don’t leave a chain of internal redirects behind.

Branch 2 — no replacement, but the page has equity: 301 to relevance

No successor product, but the page earned backlinks or still pulls traffic. Redirect it to the closest relevant page — almost always the parent category. The homepage is a last resort and a weak one, because of the soft-404 mechanic: Google can treat a redirect from a specific product to an irrelevant destination as a soft 404, which means the link equity is lost anyway. You’d get the downside of a 404 without even the cleanliness of one. So redirect to relevance, or don’t redirect.

Landing a shopper on a page where there’s nothing relevant to buy — whether from internal search or a category link — is also just a bad experience. As I framed it in the Ahrefs article, landing “on a page—where there’s nothing to buy” isn’t great for the user, and that UX judgment tracks the SEO one: relevant redirect target or none.

Branch 3 — no replacement, nothing worth saving: 404/410

If the discontinued product has no meaningful backlinks and no traffic, let it return 404 — or 410 Gone, which explicitly means “permanently gone” and which Google treats as unavailable. Evidence for this claim Google treats 404 and 410 responses as signals that a URL's content is unavailable. Scope: Google does not promise a fixed processing-speed difference between 404 and 410. Confidence: high · Verified: 2026-07-14 Google: HTTP status codes This is the technically correct answer, and it is not a penalty. Gary Illyes has been blunt about it:

“Whoever came up with the idea that having 404s gives a site any sort of penalty, you’re wrong. Utterly wrong.”

Mueller’s more recent position matches — proper error codes are simply the correct way to handle URLs that no longer exist, even at very large scale. One practical note Illyes has added: don’t run expensive backend work (database calls, product carousels) on your 404 template, because those requests don’t convert and the cost scales badly once dead URLs multiply. A lean, helpful 404 page is enough.

Branch 4 — keep it live as a Discontinued tombstone

Some discontinued products still deserve a live page — the test is whether it still does a genuine job for someone: ongoing search interest, attached support documentation (manuals, firmware, spec sheets), compatibility notes people still need, or a natural place to point to the successor. Backlinks are one input into that decision, not the trigger on their own — a page with links but nothing left to tell a visitor is a worse tombstone candidate than a page with real reference value and no links at all. In that case keep the URL at 200 and set the schema availability to https://schema.org/Discontinued — the value that specifically means the item “has been discontinued,” as opposed to OutOfStock which means temporarily unavailable. Explain on the page that it’s discontinued and point clearly to alternatives.

Do this for a genuine user reason, not to hoard a little link equity. A tombstone page kept purely “for SEO,” with nothing useful on it, is exactly the thin dead-end that gets classified as a soft 404 — which brings us to the trap that catches people.

The soft-404 trap

Even a valid 200 page can get quietly dropped, because Google can algorithmically classify it as a soft 404 based on the content, not the status code. For dead products this is the main risk. Evidence for this claim Google can classify a thin unavailable page that returns 200 as a soft 404. Scope: Soft-404 classification depends on rendered content and other signals. Confidence: high · Verified: 2026-07-14 Google: Soft 404 errors Mueller has described the mechanism:

“I suspect what is happening here is that our algorithms are looking at these pages and they’re seeing maybe there’s a banner on the page saying ‘this product is no longer available.’”

That “no longer available” messaging — or a thin template with no real product information — reads to Google like a dead page even when the server says 200. It can happen on a tombstone page and on the destination of a redirect: if you 301 a discontinued product to a page whose main message is “this product is no longer available,” Google can treat that destination as a soft 404 too, quietly undoing the redirect’s benefit.

The defense is substance. Keep a real product description, specs, images, reviews, and genuine alternatives on any discontinued page you keep live — and make redirect targets pages that stand on their own, not “sorry, gone” notices. Flagged pages show up under Search Console → Pages → Not indexed → Soft 404. There’s no fixed timeframe for when Google will apply it; it’s content-driven, not a countdown.

The link-equity math — find what’s worth rescuing before you delete

The entire reason not to blanket-404 discontinued products is that a backlinked page returning 404 stops passing that link equity to the rest of your site. The links don’t transfer; they evaporate. So before a bulk cleanup, find out which dead or dying product URLs actually earned something worth a redirect:

• Ahrefs → Site Explorer → Best by links, filtered for 404/410, surfaces removed pages that still have backlinks — your redirect candidates.
• Ahrefs → Site Audit → Links report finds the internal links still pointing at dead products, plus any redirect chains to clean up.
• Site Audit → page content / HTML search for “discontinued” or “no longer available” text shows everywhere that messaging appears across the crawl, so you can audit it at scale.

Redirect the ones with equity to a relevant page; 404/410 the rest without guilt.

A note on Merchant Center

If you run Shopping ads or free listings and you keep a discontinued product page live, the Discontinued availability signal should be consistent across the page, your feed, and any structured markup — a mismatch between what the landing page shows and what the feed says is a classic cause of product disapproval. Most discontinued items you’ll simply drop from the feed entirely once they’re gone; the consistency rule matters mainly for tombstone pages you deliberately keep. And keep the layers straight: schema.org/Discontinued is just vocabulary — it tells any consumer of your structured data what the item’s state is, but valid markup by itself doesn’t guarantee a rich result, a Merchant listing, or any particular index state. The Product structured data has to satisfy Google’s separate eligibility requirements, and the feed has to satisfy Merchant Center’s separate product-data spec. Getting the schema value right is necessary, not sufficient.

Canonical and noindex don’t make this decision for you

Two tags get reached for here that solve different problems entirely — neither one is a lifecycle response:

• Canonical (rel="canonical") is a duplicate-consolidation signal: it tells Google which URL among a set of similar or duplicate pages is the one to treat as authoritative. It says nothing about a URL being gone, and it doesn’t substitute for the actual HTTP response a discontinued page should return. Pointing a canonical from a dead product page at a live one doesn’t replace the redirect, tombstone, or 404/410 decision above.
• noindex removes a page from Google Search after Google has crawled it and seen the tag — it doesn’t communicate “this URL is gone,” and it doesn’t transfer any value to another URL. It also doesn’t clean up the internal links, sitemap entries, or feed rows still pointing at the discontinued product; you still have to do that separately. noindex is occasionally useful for a discontinued page you’re keeping live for some non-search reason (an internal reference, a support link you don’t want in Search) but it is not a stand-in for choosing 301, 404, 410, or a tombstone.

If you’re tempted to reach for canonical or noindex “to be safe” instead of making the actual lifecycle call, that’s a sign the real decision — redirect, retain, or retire — hasn’t been made yet.

Discontinued variants vs. a discontinued product family

A single variant going away (one color, one size) is a different situation from the whole product being discontinued, and the two get confused. If your catalog uses item_group_id to relate variants, check whether siblings in that group are still active before you touch the URL:

• One variant discontinued, siblings still sold. Don’t blanket-404 or redirect the variant to the homepage. Point shoppers toward the surviving variants — either a 301 to the closest active variant if there’s a clearly comparable one, or keep the retired variant referenced from the parent/family page so people who search for it land somewhere useful. Update the item_group_id relationships and any variant selector so the dead option no longer appears as choosable.
• Whole product family discontinued. This is the ordinary case the rest of this page covers — apply the branch decision (replacement, equity, tombstone, or removal) to the family’s canonical URL, and carry that same decision through to every variant URL underneath it rather than deciding each variant separately.

Either way, the canonical and redirect choices only make sense once you know the actual surviving-variant relationships and what a shopper searching for that specific variant is actually trying to do — don’t default to “redirect every variant to the main product page” without checking that it’s still relevant to what they wanted.

Where this sits in the cluster

Discontinued-product handling is the permanent-removal slice of ecommerce product-page lifecycle. Its natural sibling is the temporary case — an out-of-stock product you keep live at 200 — and it borders product page SEO (the schema and content that keep these pages substantive), category pages (your most common redirect target), and the broader Ecommerce SEO pillar. The redirect-vs-404 judgment is a general technical-SEO pattern too: the difference between a clean 404/410 and a misfiring redirect that Google reads as a soft 404 applies well beyond products.

AI summary

A condensed take on the Advanced version:

• Discontinued ≠ out of stock. Discontinued means permanently gone, so it takes the opposite treatment from a temporary stockout. This is an end-of-life decision about where the page’s earned value should go.
• Similar replacement exists → 301 to it. Can carry link value forward when the pages are genuinely similar (Mueller: “If you’re really replacing one product with another it might make sense to just redirect”) — Google doesn’t publish a transfer percentage or guarantee the outcome, but relevance gives the successor its best shot.
• No replacement, page has backlinks/traffic → 301 to the closest relevant page (parent category, not the homepage).
• No replacement, nothing worth saving → 404/410. 404s are not a penalty (Illyes: “Utterly wrong”; Mueller agrees). Keep 404 templates lean — no expensive backend queries.
• Real reference value → keep a 200 tombstone with schema.org/Discontinued availability and substantive content (description, specs, alternatives). The test is genuine ongoing usefulness, not backlinks alone — that markup is just vocabulary and doesn’t itself guarantee a rich result or Merchant listing.
• Canonical and noindex aren’t lifecycle tools. Canonical only consolidates duplicates; noindex only removes a page from Search after Google crawls it and neither communicates “this URL is gone” or cleans up internal links/feeds for you.
• Variants: a single discontinued variant with active siblings needs different handling than the whole product family going away — check the surviving-variant relationships before you redirect or remove it.
• Soft-404 trap: Google can classify a 200 page as a soft 404 based on content — thin pages or “no longer available” messaging read like dead pages, on tombstones and on redirect destinations. Substantive content is the defense; no fixed timeframe.
• Two costly mistakes: 404ing a backlinked page (equity lost for nothing) and redirecting to an irrelevant page like the homepage (Google reads it as a soft 404, equity lost anyway).
• Schema: use Discontinued, not OutOfStock — Discontinued means never returning. Keep it consistent with any Merchant Center feed to avoid disapproval.

Official documentation

Primary-source guidance from Google and schema.org.

Google — Search Central

• Don’t remove products / temporarily pause an online business — Google’s stance on not removing products from Search, and the recommended alternatives (update structured data, follow Merchant Center best practices, request a recrawl).
• Redirects and Google Search — how permanent (301) redirects consolidate signals; the tool of choice when a discontinued product has a genuine successor.
• How HTTP status codes affect Google Search — how Google treats 404, 410, and soft 404s, and why 410 is processed as “permanently gone.”
• Robots meta tag specifications — the unavailable_after directive, useful for time-bound listings you know will expire.
• Merchant listing structured data — the supported availability values and the “don’t specify more than one value” rule.
• Canonicalization — how canonical signals pick a representative among duplicate or similar URLs; it’s not a mechanism for declaring a page gone.
• Block Search indexing with noindex — noindex only takes effect after Google crawls the page and sees the tag, and doesn’t communicate HTTP absence.
• Product structured data — Product eligibility requirements; valid availability markup doesn’t guarantee a rich result or listing.

Google — Merchant Center

• Availability [availability] — the feed values and the disapproval that follows a page/feed availability mismatch.

Schema.org

• ItemAvailability — the full enumeration of availability values.
• Discontinued — the value for a permanently discontinued item.
• OutOfStock — the temporary-unavailability value, for contrast.

Quotes from the source

On-the-record statements from Google. Because much of Google’s guidance here came through Office Hours and hangouts relayed by the trade press, most of these are near-verbatim relayed quotes rather than passages on a Google-hosted page.

Google’s documented position — don’t remove products from Search

• “No. If you do this, customers won’t be able to find first-hand information about your products on Search, and there might still be third-party information for the product that may be incorrect or incomplete.” — Google Search Central docs, answering whether to use the URL Removal Tool for products that are no longer available. Jump to the doc

John Mueller — redirect when you’re really replacing a product (Google Webmaster Hangout, Feb 2019)

• “If you’re really replacing one product with another it might make sense to just redirect.”
• “If one product is gone completely and is no longer available then you could put it in this soft 404 state where you say this product is no longer available.”
• On why a redirect can backfire: “I suspect what is happening here is that our algorithms are looking at these pages and they’re seeing maybe there’s a banner on the page saying ‘this product is no longer available.’”

  Relayed via Search Engine Journal, not a Google-hosted verbatim page. Coverage

Gary Illyes — 404s are not a penalty

• “Whoever came up with the idea that having 404s gives a site any sort of penalty, you’re wrong. Utterly wrong.”

  Widely-quoted statement from Gary Illyes (Google), relayed via The SEM Post. Coverage

Which treatment does this discontinued product get?

Work top to bottom. The first “yes” is your answer.

Step 0 — Confirm it’s actually discontinued (not just out of stock). Is this product permanently gone (manufacturer stopped it, or you dropped the line), with no expectation it returns?

• No — it’s coming back / seasonal → this isn’t a discontinued-product decision. Keep it live at 200 with OutOfStock schema; that’s the out-of-stock playbook.
• Yes — permanently gone → continue.

Step 1 — Do you sell a genuinely similar replacement?

• Yes → 301 the old URL to the replacement. Update internal links to the successor. (Only if it’s truly similar — a v2, same model new year, nearest equivalent. Not “the closest thing we happen to sell.”)
• No → continue.

Step 2 — Does the page have backlinks or meaningful traffic? Check Ahrefs → Site Explorer → Best by links (filter 404/410) or your analytics.

• Yes → 301 to the closest relevant page — the parent category. Not the homepage (Google can read that as a soft 404 and the equity is lost anyway).
• No → continue.

Step 3 — Does the page still have genuine reference value? Ongoing search interest, attached manuals/support docs, or it’s a notable product people still look up.

• Yes → keep it live at 200 as a Discontinued tombstone: substantive content, clear “discontinued” messaging, links to alternatives, schema availability = Discontinued.
• No → let it return 404 (or 410 for “permanently gone,” processed a touch faster). Remove internal links to it. This is not a penalty.

A caveat that overrides Steps 1–3: whatever page you send the shopper to — redirect target or tombstone — it must read like a real, useful page, not a “this product is no longer available” notice. Google can classify that destination as a soft 404 and quietly undo the benefit.

What not to do

The common ways discontinued-product handling goes wrong — and why.

Deleting a backlinked page straight to a 404. A discontinued page that earned links returns 404, and all that link equity evaporates instead of consolidating anywhere. 404 isn’t a penalty, but throwing away earned equity is pure waste. Check for backlinks before you bulk-delete, and 301 the ones worth saving.

Redirecting everything to the homepage. The myth is that a homepage redirect “preserves the link value.” It doesn’t. Google can treat a redirect from a specific product to an irrelevant destination as a soft 404, so the equity is lost anyway — and you’ve also dumped shoppers somewhere useless. Redirect to relevance (a similar product or the parent category) or don’t redirect.

Redirecting to a “no longer available” landing page. Even a relevant-looking redirect backfires if the destination’s main message is “this product is no longer available.” Mueller’s point about banners applies to the destination: Google can read that page as a soft 404 too. Redirect targets need to stand on their own.

Keeping a thin tombstone “just for SEO.” A live 200 page with nothing on it but “discontinued” is the textbook soft 404. Keep a tombstone only when it genuinely helps users, and keep it substantive — description, specs, alternatives.

Using OutOfStock schema on a permanently discontinued item. OutOfStock signals “temporarily unavailable, may return,” which is the wrong message for something that’s gone for good. Use Discontinued. And never list more than one availability value.

Leaving the page live but with a page/feed mismatch. If you keep a tombstone but your Merchant Center feed still says the item is purchasable (or vice versa), that inconsistency is a classic cause of product disapproval. Keep the page, the feed, and the markup telling the same story.

Running heavy backend logic on your 404 template. Per Illyes, database calls and product carousels on 404 pages waste server resources on requests that don’t convert — and the cost scales badly once dead URLs multiply. Keep the 404 page lean and helpful.

Worked examples

Tombstone page — Discontinued schema (JSON-LD)

For a discontinued product you’re keeping live at 200 with real reference value, mark the offer’s availability as Discontinued:

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Acme Blender 3000",
  "description": "The Acme Blender 3000 has been discontinued. See current models below.",
  "sku": "AB-3000",
  "offers": {
    "@type": "Offer",
    "priceCurrency": "USD",
    "price": "129.00",
    "availability": "https://schema.org/Discontinued"
  }
}

Note the single availability value — Google’s guidance is not to specify more than one. Discontinued (not OutOfStock) is what tells search engines the item is gone for good rather than temporarily unavailable.

Permanent removal — 410 Gone (server response)

For a discontinued product with no replacement and nothing worth rescuing, 410 states “permanently gone” more explicitly than 404:

HTTP/1.1 410 Gone
Content-Type: text/html

Both 404 and 410 drop the URL from the index over time; 410 is processed a touch faster. Keep the served page lean.

Successor redirect — 301 (server response)

When a genuinely similar replacement exists, permanently redirect the old URL to it:

HTTP/1.1 301 Moved Permanently
Location: https://example.com/blenders/acme-blender-4000/

The target here is the successor product, not the homepage — that relevance is what lets the 301 consolidate the old page’s link value.

Time-bound listing — unavailable_after

For a listing you know will expire on a fixed date (an event-tied or auction-style item), Google’s robots meta tag can stop showing it after that date:

<meta name="robots" content="unavailable_after: 2026-12-31" />

It accepts RFC 822, RFC 850, and ISO 8601 date formats; an invalid format is ignored. This is a niche tool for genuinely date-bound listings — not the answer for an ordinary discontinued product.

Discontinued-product checklist

Run this when a product is permanently gone.

First, confirm the classification

• It’s genuinely discontinued (permanent), not out of stock (temporary) or seasonal.

Similar replacement exists

• 301 the old URL to the genuinely similar successor.
• Redirect target is truly comparable (not “closest thing we sell”).
• Internal links repointed to the replacement — no chains left behind.

No replacement, but the page has equity

• Checked backlinks/traffic (Ahrefs → Best by links, filter 404/410).
• 301 to the closest relevant category — not the homepage.
• Redirect destination is a real, useful page (not a “no longer available” notice).

No replacement, nothing worth saving

• Returns 404 or 410 (410 = “permanently gone,” processed faster).
• Internal links to the dead URL removed.
• 404 template is lean (no heavy backend queries).

Keeping a tombstone

• Live at 200 with substantive content — description, specs, alternatives.
• Schema availability set to Discontinued (single value, not OutOfStock).
• Merchant Center feed consistent with the page (no mismatch → no disapproval), or the item removed from the feed.

Audit pass

• Search Console → Pages → Not indexed → Soft 404 reviewed.
• No internal links left pointing to 404’d products.
• No redirect chains created.

Discontinued-product cheat sheet

Decision table

Discontinued vs OutOfStock

• Discontinued — never returning. Use it on tombstone pages you keep live.
• OutOfStock — temporarily unavailable, may return. Wrong value for a discontinued item.
• Never specify more than one availability value.

Status codes

• 301 — permanent move; consolidates equity to a relevant target.
• 404 — gone; drops from the index over time.
• 410 — permanently gone; processed a touch faster than 404.
• 200 — live; carries the Discontinued schema signal on a tombstone.

The traps

• 404ing a backlinked page → equity lost for nothing.
• Homepage/irrelevant redirect → soft 404, equity lost anyway.
• “No longer available” redirect destination → destination read as a soft 404.
• Thin tombstone → algorithmic soft 404.
• Page/feed availability mismatch → product disapproval.
• Heavy backend logic on 404 pages → wasted server cost (Illyes).

Find redirect candidates (Ahrefs)

• Site Explorer → Best by links → filter 404/410 → pages with equity to rescue.
• Site Audit → Links → internal links to dead products + redirect chains.

Tools for discontinued-product cleanup

• Google Search Console — Pages report — the Soft 404 bucket (under Not indexed) is where thin discontinued/tombstone pages and misfiring redirects show up; the clearest signal your handling is leaking.
• GSC — URL Inspection — confirm how a specific discontinued URL is actually handled (indexed, soft 404, redirect resolved).
• Ahrefs — Site Explorer → Best by links — filter for 404/410 to find removed pages that still have backlinks: your redirect candidates.
• Ahrefs — Site Audit (Links report) — surface internal links still pointing at dead products and any redirect chains to clean up.
• Ahrefs — Site Audit (page content / HTML search) — search the crawl for “discontinued” or “no longer available” text to audit that messaging at scale.
• Screaming Frog SEO Spider — crawl the catalog for broken internal links, redirect chains, and status codes on product URLs.
• Google Merchant Center — Diagnostics — catch availability disapprovals when a tombstone page and feed disagree.

Diagnosing discontinued-product failures

Search Console classifies a live tombstone as Soft 404

Likely cause: the 200 page is mostly a “no longer available” notice with little remaining product or support value. Fix: keep the page only when it can provide substantive description, specifications, documentation, reviews, or useful alternatives; otherwise use the appropriate redirect or 404/410. Confirm the live page remains useful and recheck the Pages report after recrawling.

A redirect lands in the Soft 404 bucket

Likely cause: the replacement or category target is not relevant enough to the old product, or the destination itself looks unavailable. Fix: redirect only to a genuinely similar successor or the closest relevant category. If none exists, let the old URL return 404 or 410 instead.

Merchant Center reports an availability mismatch

Likely cause: the landing page, feed, and structured data disagree about whether the item is purchasable or discontinued. Fix: remove the discontinued item from the active feed or make every surviving signal consistently use the correct state. Confirm the rendered page and feed item match before requesting review.

Internal crawls keep finding dead product URLs

Likely cause: category pages, recommendation modules, sitemaps, or old redirect chains still reference the discontinued URL. Fix: update internal links to the final approved destination and remove dead URLs from sitemaps. Confirm a fresh crawl finds no internal links to removed URLs and no new chains.

Triage a discontinued-product inventory

Paste a CSV with the old URL, permanent/temporary status, replacement URL, replacement-similarity notes, backlinks, recent organic traffic, reference/support value, current status, and Merchant Center state.

Classify each discontinued-product row using this exact order:
1. If it is temporary, keep the URL live; it is not a discontinued-product case.
2. If a genuinely similar successor exists, recommend a 301 to that successor.
3. Otherwise, if the old URL has backlinks or meaningful traffic, recommend a 301 only to the closest relevant category.
4. Otherwise, if it has genuine reference or support value, recommend a substantive 200 tombstone with Discontinued availability.
5. Otherwise, recommend 404 or 410.

Never recommend a homepage redirect. Do not invent similarity, backlinks, traffic, or reference value. Mark missing inputs NEEDS DATA.

Return: old URL, classification, evidence, recommended status/target, internal-link action, sitemap action, schema/feed action, validation test, and risk if the recommendation is wrong.

CSV:
[PASTE CSV]

The end-of-life value-routing framework

Discontinued-product handling routes the old URL’s remaining value rather than applying one cleanup rule to every SKU.

1. Permanence gate. Temporary stockouts stay live. Only permanently retired items enter this framework.
2. Replacement value. A genuinely similar successor can inherit the old URL through a 301. Mere category proximity is not enough.
3. Earned equity. A page with backlinks or meaningful traffic may justify a redirect to the closest relevant category when no successor exists.
4. Reference value. A page with manuals, specifications, support history, or continuing demand may remain at 200 as a substantive tombstone.
5. No remaining value. A URL with no replacement, equity, or reference purpose should return 404 or 410 without guilt.

The framework has one override: relevance. An irrelevant redirect does not preserve value just because it returns 301; Google may treat it as a soft 404.

Prove each end-of-life treatment works

Validate a successor redirect

Test to run: request the old URL without following redirects, then follow the chain and inspect the final page. Expected result: one permanent redirect leads to a genuinely relevant replacement that returns 200. Failure interpretation: the rule is missing, chained, looping, or points to a weak destination. Monitoring window: HTTP behavior is immediate; Google’s consolidation and reporting follow recrawling. Rollback trigger: the target becomes unavailable, irrelevant, or is classified as a soft 404.

Validate a live tombstone

Test to run: inspect the rendered page, response, canonical, and structured data, then compare them with the Merchant Center feed. Expected result: the URL returns 200, remains self-consistent, provides substantive reference content, and uses Discontinued where availability markup remains. Failure interpretation: the page is too thin or its page/feed signals conflict. Monitoring window: technical checks are immediate; Soft 404 classification can change after recrawling. Rollback trigger: the page loses its genuine reference value or repeatedly appears as Soft 404.

Validate a removed URL

Test to run: request the retired URL and crawl internal links and sitemaps. Expected result: the URL returns 404 or 410, has no internal links, and is absent from active sitemaps and feeds. Failure interpretation: cleanup is incomplete or a template still emits the old URL. Monitoring window: status is immediate; index removal follows recrawling. Rollback trigger: a newly discovered relevant successor or meaningful backlink profile changes the value-routing decision.

Discontinued-product lifecycle metrics

Correct treatment rate

Metric: share of discontinued SKUs whose live response and destination match the approved lifecycle class. What it tells you: whether catalog rules consistently route products to successor, category, tombstone, or removal. How to pull it: join the product lifecycle feed with crawl results and redirect destinations. Benchmark / realistic range: the operational goal is complete agreement for the audited inventory; document intentional exceptions. Cadence: each catalog retirement cycle and monthly for active stores.

Soft 404 footprint

Metric: discontinued or redirected product URLs appearing in Search Console’s Soft 404 bucket. What it tells you: whether tombstones are too thin or redirects are landing on irrelevant destinations. How to pull it: export Page Indexing examples and match them to the discontinued-product inventory. Benchmark / realistic range: establish the current baseline and investigate every growing pattern rather than relying on a universal count. Cadence: monthly and after bulk retirements.

Redirect quality and chain depth

Metric: discontinued-product redirects that reach one relevant 200 destination without an intermediate hop. What it tells you: whether value routing remains direct as later catalog changes occur. How to pull it: crawl the historical URL inventory with redirect-chain reporting. Benchmark / realistic range: one hop to the approved target is the implementation standard; exceptions need an explicit reason. Cadence: after bulk changes and quarterly.

Feed and page availability agreement

Metric: share of retained product URLs whose feed, visible page, and structured-data availability agree. What it tells you: whether lifecycle changes create Merchant Center mismatches. How to pull it: compare feed exports with rendered-page extraction. Benchmark / realistic range: these signals should agree for every retained URL. Cadence: on every feed cycle, with alerting on mismatches.

Resources worth your time

My writing

• How Should You Handle Out-of-Stock Products? It Depends — my first-party framework covering both temporary stockouts and permanent discontinuation, the redirect-relevance rule, and the Ahrefs workflows for finding pages worth rescuing.
• The Beginner’s Guide to Technical SEO — where redirects, status codes, and soft 404s fit in the bigger picture.

From around the industry

• Google: Don’t remove out-of-stock products from Search (Google Search Central) — the documented stance and recommended alternatives.
• Redirects and Google Search (Google Search Central) — how 301s consolidate signals.
• Why expired product pages may become soft 404s (Search Engine Journal) — Mueller on redirects, soft 404s, and the “no longer available” banner problem.
• 404 error pages do not cause a Google penalty (The SEM Post) — the widely-cited Illyes statement in context.
• Matt Cutts on SEO for unavailable ecommerce products (Search Engine Land) — the 2014 tiered guidance; useful history, now largely superseded.
• schema.org/Discontinued (schema.org) — the availability value for permanently discontinued items.

Test yourself: discontinued products

Five questions on handling product pages that are gone for good. Pick an answer for each, then check.

Discontinued Products

A discontinued product is an item you'll never sell again — the manufacturer stopped making it, or you dropped the line. The SEO decision is end-of-life: 301-redirect the URL to a genuinely similar replacement or the closest relevant category if it earned links or traffic, 404/410 it if it didn't, or keep it live as a Discontinued tombstone page only when it still helps users. This is distinct from a temporary out-of-stock product, which you keep live at 200.

Related: Out of Stock Products, 301 redirect, Soft 404

Discontinued Products

A discontinued product is an item a store will never carry again — the manufacturer stopped producing it, or the retailer permanently dropped the line. It’s the permanent end of a product’s life, which makes it different from an out-of-stock product that’s merely unavailable right now and expected to return.

That distinction drives the SEO decision, because the goal is the same either way: don’t throw away the rankings and links the page earned. For a discontinued product the treatment is end-of-life, and it splits by whether the URL is worth keeping alive:

• Has a genuinely similar replacement. 301 redirect the old URL to the successor product. That can carry forward the link value the old page earned — as long as the replacement is close enough that Google (and shoppers) see it as the same kind of thing; Google doesn’t publish a transfer figure or guarantee the outcome.
• No replacement, but the page earned links or traffic. 301 to the closest relevant page — usually the parent category, not the homepage. A redirect from a specific discontinued product to an irrelevant page (like the homepage) can be treated by Google as a soft 404, so the equity is lost anyway.
• No replacement and nothing worth keeping. Let it return 404 (or 410 Gone, which Google processes a touch faster). 404s are not a penalty — Google’s own people have said so repeatedly.
• Keep it as a tombstone. If a discontinued product still does a genuine job for someone — ongoing search interest, support docs, compatibility notes people still need — keep the page live at 200 and set the schema availability to Discontinued, explaining it’s discontinued and pointing to alternatives. Backlinks are one input, not the trigger on their own. Do this for a genuine user reason, with substantive content, or Google may treat the thin dead-end page as a soft 404 regardless.

Canonical and noindex are not lifecycle tools for a discontinued page: canonical only consolidates duplicate URLs, and noindex only removes a page from Search after Google has crawled it and sees the tag — neither one communicates “this URL is gone” or cleans up internal links and feeds for you. A single discontinued variant (one size or color) with active siblings needs different handling than the whole product family being discontinued — check the surviving-variant relationships first.

The recurring mistakes are the same ones that hurt any product cleanup: 404ing a backlinked page (you lose that equity for nothing) and redirecting to somewhere irrelevant (Google reads it as a soft 404, so the equity is lost anyway). In schema.org terms, use Discontinued — not OutOfStock — precisely because it signals “never returning,” whereas OutOfStock signals “temporarily unavailable.” That markup is vocabulary only; it doesn’t itself guarantee a rich result or Merchant listing.

Related: Out of Stock Products, 301 redirect, Soft 404

Changelog