VerflinkDo Broken Links on an Ecommerce Site Hurt Sales and SEO?
Yes to both, but for different reasons, and the SEO half is almost always misunderstood.
The sales damage is direct and immediate: a shopper with intent hits a dead end and leaves. The SEO damage is indirect. A 404 by itself is not a penalty. What costs you rankings is everything a broken link does to the structure around it: authority that lands nowhere, crawl attention spent on URLs that return nothing, pages that look empty to a crawler, redirect chains that dilute the signal they were supposed to carry.
Stores lose money on the first mechanism while worrying about the wrong version of the second. This is what actually happens on each side, and how to see your own situation in a few minutes.
Why store links die faster than other links
Link rot is universal, but a catalog is built to change in ways a blog is not.
- SKU churn. Products get discontinued, replaced by a new model, or dropped when a supplier changes. The URL that ranked, that sits in your own internal links, and that other sites linked to, goes with them.
- Replatforming and redesigns. A migration rewrites URL patterns. Every internal link, every old campaign, every external link written before the move now points at a shape of URL that no longer exists.
- Category restructures. Merging two collections orphans the URLs of both.
- Third parties you do not control. Size guides, supplier spec sheets, review platforms, payment or shipping partners, affiliate destinations. These break on someone else's schedule and never tell you.
- Marketing leftovers. Old posts, help articles and campaign pages pointing at expired promos or seasonal collections that were deleted after the season ended.
None of these produce an alert. The store keeps working. Only the specific paths through it stop working.
The sales side: why the loss stays invisible
A dead link fails quietly, and that is precisely what makes it expensive.
The shopper does not open a support ticket. They go back to the search results and buy from whoever is listed next. In analytics a 404 view often looks like any other pageview unless someone configured an event for it, so the abandoned session lands in the same bucket as everyone who simply browsed and left. Frontend failures are worse: a link that points nowhere, or a button that never fires, may never reach your backend at all, so server logs and uptime monitors stay green while sessions bleed.
The result shows up weeks later as a conversion rate that is slightly lower than last quarter, and it gets blamed on seasonality, ad costs or pricing. The actual cause is a handful of URLs.
Three scenarios, with the arithmetic in the open
The numbers below are not measurements of your store or of the industry. They are a template. Put your own figures in the same slots and the answer is yours, not ours.
Scenario one: a dead product link on a page that ranks. Take a category page or a buying guide that brings in 3,000 organic sessions a month. Suppose 8% of those visitors click through to the one product the page is really about, and 2% of the visitors who reach that product buy at an average order value of 70. That path is worth roughly 3,000 x 0.08 x 0.02 x 70, about 336 a month. If the product URL changed during a catalog cleanup and nothing redirects it, that path is worth zero, and the page keeps ranking and keeps sending people into it. Twelve months of that is roughly 4,000, from one link.
Scenario two: paid traffic into a dead end. Paid is worse because the cost is incurred before the failure. A click that lands on a 404 costs exactly what a click that lands on a working page costs. If you are paying 0.80 a click and one broken destination absorbs 400 clicks before anyone notices, that is 320 spent on delivering people to a page that could not sell them anything. The conversion rate for that campaign drops, the algorithm learns the campaign performs badly, and the bidding gets worse for reasons that have nothing to do with the ad.
Scenario three: the link that works and still costs you. This one is invisible even to a link checker that only reads status codes. An affiliate or partner link redirects through two or three hops and arrives at a page that returns 200. The visitor is fine. The tracking parameter got dropped somewhere in the chain, so the sale is credited to nobody. There is no error to find. The only symptom is a commission report that is quietly smaller than the traffic suggests.
The SEO side, mechanism by mechanism
A 404 is not a penalty. Google's documentation is explicit that pages returning 404 are a normal part of the web and that having them does not demote a site. The URL drops out of the index and that is the end of it. If someone tells you your rankings fell because of 404s, ask which of the mechanisms below is actually in play, because that is where the damage is.
Link equity that lands nowhere. This is the real cost. If other sites linked to a product URL and that URL now 404s, the authority those links carried stops flowing into your site. A 301 to the closest equivalent page keeps most of it. Deleting the URL and doing nothing throws it away.
Soft 404s from the "helpful" fix. The instinct after a cleanup is to redirect every dead product to the homepage. Google treats a redirect to an irrelevant page as a soft 404: the URL is dropped anyway, and you lost the chance to pass the signal to a page that deserved it. The same category covers out of stock pages that return 200 with an empty shell where the product used to be. They look like content to you and like nothing to a crawler.
Crawl attention spent on nothing. On a large catalog, especially one with faceted navigation, a crawler has a finite appetite. Every request spent on a URL pattern that no longer resolves is a request not spent on the products you launched this week. Small stores rarely feel this. Stores with tens of thousands of URLs feel it as new products taking longer to appear.
Internal links that orphan your own pages. A renamed slug does not only break the link a visitor clicks. It removes a path the crawler used to reach that page, and the internal signal that told Google which of your pages matter. Enough of these and parts of the catalog become hard to reach from anywhere.
Redirect chains. A URL that moved twice and now goes A to B to C still works for a visitor with patience. Each hop is another request, and long chains are not guaranteed to be followed all the way. A chain is a sign that a redirect map was never cleaned up after a migration.
What to do, in the order that matters
1. Inventory before fixing. You cannot prioritise what you have not measured. Get a list of every outbound and internal link that fails, with the page each one sits on, and keep confirmed failures separate from uncertain ones. A single timeout is not a dead link. 2. Fix by intent, not by status code. A discontinued product should 301 to the nearest equivalent product, or to its category if there is no equivalent. Never blanket redirect to the homepage. 3. Keep temporarily unavailable pages alive. If the SKU is coming back, leave the URL working with a clear message and alternatives. Deleting it and recreating it later means starting from zero. 4. Re-check after every migration and every catalog change. These are the two events that break the most links, and both are planned, which means the check can be planned too. 5. Then monitor. The first four steps fix today. Link rot happens on a schedule you do not control, so the only thing that keeps the fix from decaying is a check that repeats without you remembering it.
Where Verflink fits
Verflink was built for the inventory step and the monitoring step.
The free scan takes a URL and nothing else. No account, no card, no snippet to install. It crawls your public pages, follows every outbound link through its redirects, and gives you a report that names the page each broken link sits on, so the fix is a task and not an investigation. Confirmed failures are kept apart from uncertain ones on purpose: a single timeout goes in the second group, because a false alarm costs your attention and attention is the thing you have least of.
It also checks something most link checkers do not: whether an affiliate or tracking tag survived the redirect chain. That is scenario three above, the failure with no error code.
A subscription re-crawls the whole site every month and emails you the day a link that used to work stops working. The alert names the page, the destination and what happened, so you can decide in one line whether it matters.
Two honest limits. It is best effort: sites block automated requests, rate limit us or answer differently to different visitors, so some problems will be missed. And it reads your public pages, which means it sees what a shopper who is not logged in sees, not what happens behind a customer account.
Short answers
Do 404s hurt my rankings? Not by themselves. The lost link equity, the soft 404s and the wasted crawl attention around them do.
Should I redirect everything to the homepage? No. That is the most common way to turn a fixable problem into a soft 404 and throw away the signal you were trying to save.
What about out of stock products? Keep the URL alive if the product is coming back. Redirect to the closest equivalent if it is not.
How often should I check? After every migration and every catalog change, and on a schedule in between. Monthly is enough for most stores.
If you want the specific list for your own store rather than the general case, the scan takes about a minute and asks for nothing but the URL. See also how broken links kill ecommerce conversions for the revenue side in more detail, and what link rot is for the mechanism behind all of it.