暫定日本語訳：Discontinued 商品 ページ

暫定日本語案: TL;DR — A discontinued 商品 is one you’ll never sell again — that’s the 暫定日本語案: key difference from something that’s just temporarily sold out. Before you delete 暫定日本語案: the ページ, ask two things: do you sell something similar now, and did the ページ earn 暫定日本語案: any リンク or traffic? If you have a similar replacement, redirect the old ページ 暫定日本語案: to it. If you don’t, but the ページ was popular, redirect it to the closest matching 暫定日本語案: category. Only let a ページ truly disappear (return “not found”) if it’s gone for 暫定日本語案: good and nothing リンク to it. The big mistake is deleting a ページ that earned 暫定日本語案: リンク 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 商品 is unavailable right now but coming back. 暫定日本語案: You keep that ページ 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 商品.)
• 暫定日本語案: 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 ページ is about the second one — the permanent goodbye — because it’s a 暫定日本語案: different decision entirely.

暫定日本語案: The ページ still has value — don’t just delete it

暫定日本語案: Here’s what people miss: a 商品 ページ you’ve had for a while has quietly built up 暫定日本語案: value. It ranks for searches. Other sites リンク to it. People bookmark it. When you 暫定日本語案: delete it the instant the 商品 is discontinued, all of that evaporates.

暫定日本語案: So the question isn’t “should I delete this?” It’s “where should this ページ’s value 暫定日本語案: go?” That points you to one of a few answers.

暫定日本語案: The simple decision

暫定日本語案: 1. You sell a similar replacement. 暫定日本語案: Redirect the old ページ to the new one. A redirect (specifically a 301, the 暫定日本語案: permanent kind) can carry the old ページ’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 ページ 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 ページ 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 ページ 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 商品 still gets searched for, or has manuals and support 暫定日本語案: info attached. In that case, keep the ページ up, clearly say it’s discontinued, point 暫定日本語案: people to alternatives, and make the ページ actually useful. Don’t leave a bare “not 暫定日本語案: available” shell — Google may quietly drop a thin dead-end ページ.

暫定日本語案: The one trap

暫定日本語案: Don’t redirect a discontinued 商品 to your homepage (or some random unrelated 暫定日本語案: ページ) just to “save the リンク value.” Google treats an irrelevant redirect like that 暫定日本語案: as a dead ページ 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 スキーマ value, 暫定日本語案: the soft-404 mechanics, and how to find which dead ページ actually earned リンク? 暫定日本語案: 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, ページ has 暫定日本語案: backlinks/traffic → 301 to the closest relevant ページ (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 コンテンツ. Neither move guarantees a specific ranking or リンク 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 暫定日本語案: ページ (equity lost for nothing) and redirecting to an irrelevant ページ 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 ページ. Keep the tombstone ページ substantive, 暫定日本語案: because a thin “no longer available” ページ 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 暫定日本語案: 商品 that question is already answered — no — so the framing changes. The 暫定日本語案: job now is purely about where the ページ’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, ページ earned リンク/traffic → redirect to relevance.
3. 暫定日本語案: No replacement, nothing worth saving → let it go (404/410).
4. 暫定日本語案: Real reference value → keep a tombstone ページ live.

暫定日本語案: My general take, from my Ahrefs writeup on out-of-stock and discontinued 暫定日本語案: 商品, 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 商品 with a successor, redirect. Mueller’s line 暫定日本語案: is direct:

暫定日本語案: “If you’re really replacing one 商品 with another it might make sense to just 暫定日本語案: redirect.”

暫定日本語案: A 301 to a closely comparable replacement can carry forward the リンク value the old 暫定日本語案: ページ earned — if the ページ are similar enough, as I put it in that Ahrefs piece: a 暫定日本語案: 301 “will also maintain any リンク value if the ページ 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 リンク outcome for any individual redirect. The whole thing turns on relevance: the 暫定日本語案: target has to actually be the same kind of 商品. 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 リンク 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 ページ has equity: 301 to relevance

暫定日本語案: No successor 商品, but the ページ earned backlinks or still pulls traffic. Redirect 暫定日本語案: it to the closest relevant ページ — 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 商品 to an irrelevant destination as a soft 暫定日本語案: 404, which means the リンク 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 ページ where there’s nothing relevant to buy — whether from 暫定日本語案: internal 検索 or a category リンク — is also just a bad experience. As I framed it 暫定日本語案: in the Ahrefs article, landing “on a ページ—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 商品 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 サイト 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, 商品 暫定日本語案: carousels) on your 404 template, because those requests don’t convert and the cost 暫定日本語案: scales badly once dead URLs multiply. A lean, helpful 404 ページ is enough.

暫定日本語案: Branch 4 — keep it live as a Discontinued tombstone

暫定日本語案: Some discontinued 商品 still deserve a live ページ — the test is whether it still 暫定日本語案: does a genuine job for someone: ongoing 検索 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 ページ with リンク but nothing left to 暫定日本語案: tell a visitor is a worse tombstone candidate than a ページ with real reference value 暫定日本語案: and no リンク at all. In that case keep the URL at 200 and set the スキーマ 暫定日本語案: 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 ページ that it’s discontinued and 暫定日本語案: point clearly to alternatives.

暫定日本語案: Do this for a genuine user reason, not to hoard a little リンク equity. A tombstone 暫定日本語案: ページ 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 ページ can get quietly dropped, because Google can algorithmically 暫定日本語案: classify it as a soft 404 based on the コンテンツ, not the status code. For dead 暫定日本語案: 商品 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 ページ 暫定日本語案: and they’re seeing maybe there’s a banner on the ページ saying ‘this 商品 is no 暫定日本語案: longer available.’”

暫定日本語案: That “no longer available” messaging — or a thin template with no real 商品 暫定日本語案: information — reads to Google like a dead ページ even when the server says 200. It 暫定日本語案: can happen on a tombstone ページ and on the destination of a redirect: if you 301 a 暫定日本語案: discontinued 商品 to a ページ whose main message is “this 商品 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 商品 description, specs, images, reviews, 暫定日本語案: and genuine alternatives on any discontinued ページ you keep live — and make redirect 暫定日本語案: targets ページ that stand on their own, not “sorry, gone” notices. Flagged ページ show 暫定日本語案: up under 検索 Console → ページ → Not インデックス登録済み → Soft 404. There’s no fixed 暫定日本語案: timeframe for when Google will apply it; it’s コンテンツ-driven, not a countdown.

暫定日本語案: The リンク-equity math — find what’s worth rescuing before you delete

暫定日本語案: The entire reason not to blanket-404 discontinued 商品 is that a backlinked ページ 暫定日本語案: returning 404 stops passing that リンク equity to the rest of your サイト. The リンク 暫定日本語案: don’t transfer; they evaporate. So before a bulk cleanup, find out which dead or 暫定日本語案: dying 商品 URLs actually earned something worth a redirect:

• 暫定日本語案: Ahrefs → サイト Explorer → Best by リンク, filtered for 404/410, surfaces 暫定日本語案: removed ページ that still have backlinks — your redirect candidates.
• 暫定日本語案: Ahrefs → サイト Audit → リンク report finds the internal リンク still pointing at 暫定日本語案: dead 商品, plus any redirect chains to clean up.
• 暫定日本語案: サイト Audit → ページ コンテンツ / HTML 検索 for “discontinued” or “no longer 暫定日本語案: available” text shows everywhere that messaging appears across the クロール, so you 暫定日本語案: can audit it at scale.

暫定日本語案: Redirect the ones with equity to a relevant ページ; 404/410 the rest without guilt.

暫定日本語案: A note on Merchant Center

暫定日本語案: If you run Shopping ads or free listings and you keep a discontinued 商品 ページ 暫定日本語案: live, the Discontinued availability signal should be consistent across the ページ, 暫定日本語案: your feed, and any structured markup — a mismatch between what the landing ページ shows 暫定日本語案: and what the feed says is a classic cause of 商品 disapproval. Most discontinued 暫定日本語案: items you’ll simply drop from the feed entirely once they’re gone; the consistency 暫定日本語案: rule matters mainly for tombstone ページ 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 暫定日本語案: 商品 structured data has to satisfy Google’s separate eligibility requirements, 暫定日本語案: and the feed has to satisfy Merchant Center’s separate 商品-data spec. Getting 暫定日本語案: the スキーマ 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 ページ 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 ページ should return. Pointing a 暫定日本語案: canonical from a dead 商品 ページ at a live one doesn’t replace the redirect, 暫定日本語案: tombstone, or 404/410 decision above.
• 暫定日本語案: noindex removes a ページ from Google 検索 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 リンク, sitemap 暫定日本語案: entries, or feed rows still pointing at the discontinued 商品; you still have 暫定日本語案: to do that separately. noindex is occasionally useful for a discontinued ページ 暫定日本語案: you’re keeping live for some non-検索 reason (an internal reference, a support 暫定日本語案: リンク you don’t want in 検索) 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 商品 family

暫定日本語案: A single variant going away (one color, one size) is a different situation from the 暫定日本語案: whole 商品 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 ページ so people who 検索 暫定日本語案: 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 商品 family discontinued. This is the ordinary case the rest of this 暫定日本語案: ページ 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 商品 ページ” without checking that it’s still relevant to what they 暫定日本語案: wanted.

暫定日本語案: Where this sits in the cluster

暫定日本語案: Discontinued-商品 handling is the permanent-removal slice of ecommerce 暫定日本語案: 商品-ページ lifecycle. Its natural sibling is the temporary case — an 暫定日本語案: out-of-stock 商品 you keep live at 200 — and it borders 暫定日本語案: 商品 ページ SEO (the スキーマ 暫定日本語案: and コンテンツ that keep these ページ substantive), 暫定日本語案: category ページ (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 商品.

暫定日本語案: 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 ページ’s earned value should go.
• 暫定日本語案: Similar replacement exists → 301 to it. Can carry リンク value forward when the 暫定日本語案: ページ are genuinely similar (Mueller: “If you’re really replacing one 商品 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, ページ has backlinks/traffic → 301 to the closest relevant ページ 暫定日本語案: (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 コンテンツ (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 ページ from 検索 after Google crawls it and 暫定日本語案: neither communicates “this URL is gone” or cleans up internal リンク/feeds for you.
• 暫定日本語案: Variants: a single discontinued variant with active siblings needs different 暫定日本語案: handling than the whole 商品 family going away — check the surviving-variant 暫定日本語案: relationships before you redirect or remove it.
• 暫定日本語案: Soft-404 trap: Google can classify a 200 ページ as a soft 404 based on content 暫定日本語案: — thin ページ or “no longer available” messaging read like dead ページ, on tombstones 暫定日本語案: and on redirect destinations. Substantive コンテンツ is the defense; no fixed 暫定日本語案: timeframe.
• 暫定日本語案: Two costly mistakes: 404ing a backlinked ページ (equity lost for nothing) and 暫定日本語案: redirecting to an irrelevant ページ like the homepage (Google reads it as a soft 404, 暫定日本語案: equity lost anyway).
• 暫定日本語案: スキーマ: 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 スキーマ.org.

暫定日本語案: Google — 検索 Central

• 暫定日本語案: Don’t remove 商品 / temporarily pause an online business — Google’s stance on not removing 商品 from 検索, and the recommended alternatives (update structured data, follow Merchant Center best practices, request a recrawl).
• 暫定日本語案: Redirects and Google 検索 — how permanent (301) redirects consolidate signals; the tool of choice when a discontinued 商品 has a genuine successor.
• 暫定日本語案: How HTTP status codes affect Google 検索 — 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 ページ gone.
• 暫定日本語案: Block 検索 インデックス登録 with noindex — noindex only takes effect after Google crawls the ページ and sees the tag, and doesn’t communicate HTTP absence.
• 暫定日本語案: 商品 structured data — 商品 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 ページ/feed availability mismatch.

暫定日本語案: スキーマ.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 ページ.

暫定日本語案: Google’s documented position — don’t remove 商品 from 検索

• 暫定日本語案: “No. If you do this, customers won’t be able to find first-hand information about 暫定日本語案: your 商品 on 検索, and there might still be third-party information for the 暫定日本語案: 商品 that may be incorrect or incomplete.” 暫定日本語案: — Google 検索 Central docs, answering whether to use the URL Removal Tool for 暫定日本語案: 商品 that are no longer available. 暫定日本語案: Jump to the doc

暫定日本語案: John Mueller — redirect when you’re really replacing a 商品 (Google Webmaster Hangout, Feb 2019)

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

  暫定日本語案: Relayed via 検索エンジン Journal, not a Google-hosted verbatim ページ. 暫定日本語案: Coverage

暫定日本語案: Gary Illyes — 404s are not a penalty

• 暫定日本語案: “Whoever came up with the idea that having 404s gives a サイト 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 商品 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 商品 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-商品 decision. 暫定日本語案: Keep it live at 200 with OutOfStock スキーマ; 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 リンク 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 ページ have backlinks or meaningful traffic? 暫定日本語案: Check Ahrefs → サイト Explorer → Best by リンク (filter 404/410) or your analytics.

• 暫定日本語案: Yes → 301 to the closest relevant ページ — 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 ページ still have genuine reference value? 暫定日本語案: Ongoing 検索 interest, attached manuals/support docs, or it’s a notable 商品 暫定日本語案: people still look up.

• 暫定日本語案: Yes → keep it live at 200 as a Discontinued tombstone: substantive 暫定日本語案: コンテンツ, clear “discontinued” messaging, リンク to alternatives, スキーマ 暫定日本語案: availability = Discontinued.
• 暫定日本語案: No → let it return 404 (or 410 for “permanently gone,” processed a 暫定日本語案: touch faster). Remove internal リンク to it. This is not a penalty.

暫定日本語案: A caveat that overrides Steps 1–3: whatever ページ you send the shopper to — 暫定日本語案: redirect target or tombstone — it must read like a real, useful ページ, not a “this 暫定日本語案: 商品 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-商品 handling goes wrong — and why.

暫定日本語案: Deleting a backlinked ページ straight to a 404. 暫定日本語案: A discontinued ページ that earned リンク returns 404, and all that リンク 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 リンク value.” It doesn’t. Google 暫定日本語案: can treat a redirect from a specific 商品 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 商品 or the parent category) or don’t 暫定日本語案: redirect.

暫定日本語案: Redirecting to a “no longer available” landing ページ. 暫定日本語案: Even a relevant-looking redirect backfires if the destination’s main message is 暫定日本語案: “this 商品 is no longer available.” Mueller’s point about banners applies to the 暫定日本語案: destination: Google can read that ページ as a soft 404 too. Redirect targets need to 暫定日本語案: stand on their own.

暫定日本語案: Keeping a thin tombstone “just for SEO.” 暫定日本語案: A live 200 ページ 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 スキーマ 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 ページ live but with a ページ/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 商品 暫定日本語案: disapproval. Keep the ページ, the feed, and the markup telling the same story.

暫定日本語案: Running heavy backend logic on your 404 template. 暫定日本語案: Per Illyes, database calls and 商品 carousels on 404 ページ waste server resources 暫定日本語案: on requests that don’t convert — and the cost scales badly once dead URLs multiply. 暫定日本語案: Keep the 404 ページ lean and helpful.

暫定日本語案: Worked examples

暫定日本語案: Tombstone ページ — Discontinued スキーマ (JSON-LD)

暫定日本語案: For a discontinued 商品 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 検索 engines the item is gone 暫定日本語案: for good rather than temporarily unavailable.

暫定日本語案: Permanent removal — 410 Gone (server response)

暫定日本語案: For a discontinued 商品 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 ページ 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 ページ’s リンク 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 商品.

暫定日本語案: Discontinued-商品 checklist

暫定日本語案: Run this when a 商品 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 リンク repointed to the replacement — no chains left behind.

暫定日本語案: No replacement, but the ページ has equity

• 暫定日本語案: [ ] Checked backlinks/traffic (Ahrefs → Best by リンク, filter 404/410).
• 暫定日本語案: [ ] 301 to the closest relevant category — not the homepage.
• 暫定日本語案: [ ] Redirect destination is a real, useful ページ (not a “no longer available” 暫定日本語案: notice).

暫定日本語案: No replacement, nothing worth saving

• 暫定日本語案: [ ] Returns 404 or 410 (410 = “permanently gone,” processed faster).
• 暫定日本語案: [ ] Internal リンク to the dead URL removed.
• 暫定日本語案: [ ] 404 template is lean (no heavy backend queries).

暫定日本語案: Keeping a tombstone

• 暫定日本語案: [ ] Live at 200 with substantive コンテンツ — description, specs, alternatives.
• 暫定日本語案: [ ] スキーマ availability set to Discontinued (single value, not OutOfStock).
• 暫定日本語案: [ ] Merchant Center feed consistent with the ページ (no mismatch → no disapproval), 暫定日本語案: or the item removed from the feed.

暫定日本語案: Audit pass

• 暫定日本語案: [ ] 検索 Console → ページ → Not インデックス登録済み → Soft 404 reviewed.
• 暫定日本語案: [ ] No internal リンク left pointing to 404’d 商品.
• 暫定日本語案: [ ] No redirect chains created.

暫定日本語案: Discontinued-商品 cheat sheet

暫定日本語案: Decision table

暫定日本語案: Discontinued vs OutOfStock

• 暫定日本語案: Discontinued — never returning. Use it on tombstone ページ 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 スキーマ signal on a tombstone.

暫定日本語案: The traps

• 暫定日本語案: 404ing a backlinked ページ → 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.
• 暫定日本語案: ページ/feed availability mismatch → 商品 disapproval.
• 暫定日本語案: Heavy backend logic on 404 ページ → wasted server cost (Illyes).

暫定日本語案: Find redirect candidates (Ahrefs)

• 暫定日本語案: サイト Explorer → Best by リンク → filter 404/410 → ページ with equity to rescue.
• 暫定日本語案: サイト Audit → リンク → internal リンク to dead 商品 + redirect chains.

暫定日本語案: Tools for discontinued-商品 cleanup

• 暫定日本語案: Google 検索 Console — ページ report — the Soft 404 bucket (under Not 暫定日本語案: インデックス登録済み) is where thin discontinued/tombstone ページ and misfiring redirects show 暫定日本語案: up; the clearest signal your handling is leaking.
• 暫定日本語案: GSC — URL Inspection — confirm how a specific discontinued URL is actually 暫定日本語案: handled (インデックス登録済み, soft 404, redirect resolved).
• 暫定日本語案: Ahrefs — サイト Explorer → Best by リンク — filter for 404/410 to find removed 暫定日本語案: ページ that still have backlinks: your redirect candidates.
• 暫定日本語案: Ahrefs — サイト Audit (リンク report) — surface internal リンク still pointing at 暫定日本語案: dead 商品 and any redirect chains to clean up.
• 暫定日本語案: Ahrefs — サイト Audit (ページ コンテンツ / HTML 検索) — 検索 the クロール for 暫定日本語案: “discontinued” or “no longer available” text to audit that messaging at scale.
• 暫定日本語案: Screaming Frog SEO Spider — クロール the catalog for broken internal リンク, 暫定日本語案: redirect chains, and status codes on 商品 URLs.
• 暫定日本語案: Google Merchant Center — Diagnostics — catch availability disapprovals when a 暫定日本語案: tombstone ページ and feed disagree.

暫定日本語案: Diagnosing discontinued-商品 failures

暫定日本語案: 検索 Console classifies a live tombstone as Soft 404

暫定日本語案: Likely cause: the 200 ページ is mostly a “no longer available” notice with little remaining 商品 or support value. Fix: keep the ページ only when it can provide substantive description, specifications, documentation, reviews, or useful alternatives; otherwise use the appropriate redirect or 404/410. Confirm the live ページ remains useful and recheck the ページ 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 商品, 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 ページ, 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 ページ and feed item match before requesting review.

暫定日本語案: Internal crawls keep finding dead 商品 URLs

暫定日本語案: Likely cause: category ページ, recommendation modules, sitemaps, or old redirect chains still reference the discontinued URL. Fix: update internal リンク to the final approved destination and remove dead URLs from sitemaps. Confirm a fresh クロール finds no internal リンク to removed URLs and no new chains.

暫定日本語案: Triage a discontinued-商品 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-商品 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 ページ with backlinks or meaningful traffic may justify a redirect to the closest relevant category when no successor exists.
4. 暫定日本語案: Reference value. A ページ 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 ページ. 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 ページ, 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 コンテンツ, and uses Discontinued where availability markup remains. Failure interpretation: the ページ is too thin or its ページ/feed signals conflict. Monitoring window: technical checks are immediate; Soft 404 classification can change after recrawling. Rollback trigger: the ページ loses its genuine reference value or repeatedly appears as Soft 404.

暫定日本語案: Validate a removed URL

暫定日本語案: Test to run: request the retired URL and クロール internal リンク and sitemaps. Expected result: the URL returns 404 or 410, has no internal リンク, 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 発見済み relevant successor or meaningful backlink profile changes the value-routing decision.

暫定日本語案: Discontinued-商品 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 商品 to successor, category, tombstone, or removal. How to pull it: join the 商品 lifecycle feed with クロール 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 商品 URLs appearing in 検索 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 ページ インデックス登録 examples and match them to the discontinued-商品 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-商品 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: クロール 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 ページ availability agreement

暫定日本語案: Metric: share of retained 商品 URLs whose feed, visible ページ, 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-ページ 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 商品? It Depends — my first-party framework covering both temporary stockouts and permanent discontinuation, the redirect-relevance rule, and the Ahrefs workflows for finding ページ 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 商品 from 検索 (Google 検索 Central) — the documented stance and recommended alternatives.
• 暫定日本語案: Redirects and Google 検索 (Google 検索 Central) — how 301s consolidate signals.
• 暫定日本語案: Why expired 商品 ページ may become soft 404s (検索エンジン Journal) — Mueller on redirects, soft 404s, and the “no longer available” banner problem.
• 暫定日本語案: 404 error ページ do not cause a Google penalty (The SEM Post) — the widely-cited Illyes statement in context.
• 暫定日本語案: Matt Cutts on SEO for unavailable ecommerce 商品 (検索エンジン Land) — the 2014 tiered guidance; useful history, now largely superseded.
• 暫定日本語案: スキーマ.org/Discontinued (スキーマ.org) — the availability value for permanently discontinued items.

暫定日本語案: Test yourself: discontinued 商品

暫定日本語案: Five questions on handling 商品 ページ that are gone for good. Pick an answer for 暫定日本語案: each, then check.

変更履歴