Short answer. When an out-of-stock product page 301-redirects to your homepage, Google can disapprove the listing under the issue it calls Generic page: the URL in your feed no longer leads to a page for that product. Keep the page live and let the data say OutOfStock, rather than letting the URL say the product is gone. Reserve 301 redirects for genuinely discontinued products, pointed at a real replacement.
If an out-of-stock product's page 301-redirects to your homepage or a collection page, Google can disapprove that listing, because the URL you submitted no longer leads to a page for that product. The shopper who clicks through from your ad or your organic listing lands on your homepage instead, no product, no add-to-cart, no reason to stay.
This isn't a feed error or a pricing bug. It's an out-of-stock app or a "clean URL" automation doing exactly what it was configured to do: redirect dead inventory away from a 404. The side effect is that a product that's actually still in your catalog, still submitted to Google, still linked from collections, still bookmarked by past visitors, silently stops working as a landing page.
What Google actually calls this
It helps to know the name, because the name is what you filter on in Merchant Center and what you search for when you want a second opinion. Google documents this failure under two issue titles, and the wording of one of them describes a Shopify out-of-stock app precisely.
Generic page is the narrower one. Google's description is that the landing page submitted through the link or mobile_link attribute "redirects to a generic landing page rather than a product-specific landing page", and the product stays disapproved until the URL is corrected. The fix Google states is as short as the problem: "Use a URL that sends users to a product-specific landing page".
Generic or dysfunctional landing pages is the broader one, and the first cause on its list is this article's subject, stated in Google's own words: "The product is out of stock and the website redirects to the homepage or a similar products page." The same list continues into pages missing a title, price, image, availability or buy button, pop-ups covering the product, and pages under maintenance. The out-of-stock redirect is not an edge case Google tolerates and has not thought about. It is the opening line of the documentation.
Two neighbours are worth separating from it, because they look identical in a disapproval email and have different fixes. Different product landing page fires where, in Google's wording, the landing pages in your product data "direct to a different product landing page rather than the specific landing page for that product". That is a wrong-URL problem rather than a redirect problem, and the fix Google gives is to "Update the product landing page URL in your product data to match the landing page URL of your website." Where the page loads but disagrees with the feed, you are in Inaccurate availability status due to inconsistency between feed and landing page, covered further down. Google's own list of website issues that lead to product disapprovals carries the plain-language version of all of them, including "Landing page redirects to a generic page instead of the specific product page".
The three things a redirected product page loses at once
Its SEO. A product page that has been live for months or years has had time to accumulate indexed history, internal links, and sometimes external backlinks. A 301 to the homepage passes none of that value to anything useful: it just tells Google that this specific product is no longer at this address, which is not what you meant if the product is only temporarily out of stock.
Its Merchant Center approval. The link attribute in your product feed still points at the original product URL. Once that URL redirects somewhere that isn't the product, the destination stops satisfying the requirement above, and the listing is disapproved on one of the names in the previous section.
The sale. A shopper who clicked specifically on that product, from a Shopping ad, an organic result, or a shared link, is dropped on your homepage with zero context. The click is spent and the product it was spent on is no longer on screen.
StoreCanary checks this on your store
Not sure if this is happening on your store right now? We check every product URL in your public catalog against your feed and flag silent redirects automatically: read-only, no admin access, about 2 minutes.
Scan my store for freeA real case: a live product, quietly redirecting to "/"
In one of our scans, a French outdoor-apparel store had an active product still listed in its public catalog and still submitted to Google Shopping, but its product page 301-redirected straight to the homepage. Nothing in Shopify admin flagged it as a problem: the product still existed, still had a price, still showed as "active." The redirect was coming from the store's out-of-stock app, which had been configured to send shoppers "somewhere useful" the moment a variant hit zero inventory, rather than keeping the page itself live.
The result matched the pattern above exactly: the product's Merchant Center listing was disapproved, and anyone who found the product through search or a saved link hit a dead end. In our full-catalog scans, which cover more than 90,000 Shopify product pages, we treat this specific failure, an out-of-stock app rewriting a product URL into a blanket redirect, as its own check rather than folding it into a plain broken link.
Why Google calls this a "landing page" issue, not a stock issue
Google's product data specification requires the link attribute to point directly to the page for that specific product, not a category page, not a search results page, and not your homepage. The requirement is set out in Google's product data specification for the link attribute and the broader product data specification overview: the destination must let the shopper view and purchase the exact item advertised. A redirect to the homepage fails that requirement outright, regardless of why the redirect exists. Google's crawler doesn't know, or care, that the product is merely out of stock; it only sees that the submitted URL no longer resolves to a product.
Being out of stock is not itself the offence, and Google's availability attribute says so by listing out_of_stock as a supported value alongside in_stock, preorder and backorder. The same page tells you not to delete the item, and warns against the opposite shortcut too: "Don't set the availability attribute to out_of_stock for products that you're no longer selling." There is a documented state for temporarily unavailable and a different one for gone, and a redirect is neither.
Where the URL resolves but the page and the feed disagree, the name changes. Google's availability-inconsistency page opens on "You received this notification because we found availability mismatches between your product data and landing pages" and sets the bar at "The availability of all of your products needs to match across all three", naming the landing page, the structured data and the checkout page. Google's issues overview also names "Preemptive item disapproval (PID)" for the case where "the price or availability of your products don't match between your product data and website landing pages". So the redirect and the mismatch are two failures on one axis, and fixing the first can expose the second.
The price-mismatch failure we covered separately is a close cousin: in both cases, Merchant Center is comparing what your feed claims against what the live page actually does, and disapproving the gap. See Products disapproved in Google Merchant Center: the price mismatch trap for the pricing version of the same underlying pattern, and Product page unavailable in Merchant Center for the case where Google's crawler cannot reach the page at all.
What nine live storefronts do with a sold-out product URL
The advice in this article assumes the redirect is something a store chose, not something Shopify does. That is worth testing rather than asserting, so on 12 October 2026 we looked for one fully sold-out product on each of ten live Shopify-served storefronts, using each store's own public product endpoint to find a product whose every variant reported itself unavailable, and then fetched that product URL with a Googlebot user agent. Nine stores had such a product in the range we read.
All nine product URLs resolved to the same product page with an HTTP 200. Not one landed on a homepage, a collection or a similar-products page. This is a nine-store reading on one day, not a rate, and it does not tell you what any other store does. What it does establish is that keeping the page live is the default behaviour, and that a product URL redirecting away from its product is an installed or configured decision somewhere in the stack, which is why nothing in Shopify admin reports it as a fault.
One number in that probe nearly became a finding of the opposite kind, and it is worth naming because the same trap is waiting in anyone's own check. Fetched without following redirects, eight of the nine answered 301. Followed, every one of those hops was the store's apex host sending the request to its www or regional subdomain, with the product path intact. A redirect count alone would have read as eight stores redirecting their sold-out products. The thing to measure is the final URL, not the status code.
The second half of the probe is the less comfortable one, and it is about the markup rather than the URL. Of the nine pages, six served Product or ProductGroup structured data in the HTML we fetched, and three served none. Of those six, five declared availability as OutOfStock only. One declared both InStock and OutOfStock on a product whose own catalogue endpoint reported every variant unavailable, which is the mismatch Google's availability page describes, observed rather than illustrated. On the three with no product markup in the served HTML, we are not claiming the markup is absent: a raw fetch is not proof either way when an app injects schema in the browser, and Google's rendered view is the thing to check. The point that survives the caveat is that the URL resolving is the easy half.
The fix: keep the page live, redirect only when truly gone
The correct default for an out-of-stock product is to keep its page live and let the data say "unavailable," not the URL:
- Set availability to OutOfStock, in the page's own markup (
offers.availability), in your feed, and in whatever the checkout says, rather than hiding or redirecting the page. Google's bar is all three agreeing, not the feed alone. - Add a restock notification form ("notify me when back in stock") so the page still converts intent instead of losing it.
- If you genuinely need it to stop showing, use the attribute built for that. Google documents "Use the pause
[pause]attribute to temporarily stop products from showing", withadscovering ads locations andallcovering all Shopping locations. It comes with a deadline: "Only pause a product for 14 days or less." Past that, the same page sends you to[excluded_destination]instead. Either way the product URL stays live and nothing in your store's routing changes, which is the whole difference from a redirect. - Reserve 301 redirects for genuinely discontinued products, and point them at the specific product that replaces it, never at the homepage or a collection. Sent to a real substitute, the redirect preserves both the shopper's intent and much of the page's accumulated SEO value; sent to "/", it preserves neither. For what happens when the destination is nothing at all, see a deleted Shopify product still showing on Google, and for the Search Console report that catches the redirect itself, Redirect error in Search Console.
The same discipline runs through the phantom noindex article: a product can look completely fine inside Shopify admin (active, priced, in your catalog) while the public-facing URL tells Google something entirely different. Out-of-stock redirects are just another way that gap opens up, and the same gap closes your free listings as well as your paid ones.
How to check your own store
- Open Shopify Admin → Online Store → Navigation → URL Redirects, and search for rules pointing product handles at
/or a collection URL. - Open the settings of any out-of-stock, back-in-stock, or "sold out" app you run, and look for an automatic redirect toggle. In the case we describe below that setting was the source, and it is worth checking even on an app you did not install for that purpose.
- In Merchant Center, open the Needs attention view and look for Generic page or Generic or dysfunctional landing pages by name. Both list the affected URLs, which is faster than guessing from the product side.
- Take a currently out-of-stock product and request its URL without following redirects, then again following them, and compare the final URL with the one you asked for. A status code on its own will mislead you, for the reason in the probe above.
- On that same page, check what the markup says about availability, in Google's rendered view rather than a raw fetch. The page resolving and the page agreeing with your feed are two separate tests, and only the second one catches an
InStockleft behind on a sold-out product.
None of this produces an error in Shopify admin. The product still looks active, the feed still submits fine at first glance: what surfaces instead is an accumulation of Merchant Center disapprovals on the Google side, and a checkout funnel losing shoppers before they ever see the product.
Is this happening on your store right now?
Merchant Center will not tell you until it disapproves a listing. The product is live in your store, and Google Shopping is showing a different price, the wrong availability, or nothing at all. The only way to know is to check the feed the way Google reads it.
- 90+ checks, the way Google reads your product feed. Price and availability mismatches, missing identifiers, redirect chains.
- Read-only. No app to install, no admin access, nothing changes on your store.
- The exact fix for each page, in plain English, so you or your developer can act the same day.
Across full-catalog scans of more than 90,000 Shopify product pages, about 1 in 4 stores had at least one critical Google visibility issue.
Scan my store for freeFree scan: issue types, counts and first fixes. Full report on every product page, not a sample: $49 once, no subscription.
Next in this cluster
- "Redirect error" on Shopify: how many redirects Google allows
- "Product page unavailable" in Merchant Center on Shopify
- The full map: 11 reasons a Shopify product disappears from Google
- Products disapproved in Google Merchant Center: the price mismatch trap
- When a redirect keeps a removed product alive in Google Shopping
- The phantom noindex: how Shopify apps silently hide your products from Google
- Your review stars disappeared from Google? The 5 Shopify causes