All postsTürkçe

September 27, 2026

PrestaShop 8 and 9: 404 Redirect and Deleted Product URL Guide

A PrestaShop-specific guide to managing deleted products, changed friendly URLs, category moves, and legacy 404 traffic without creating irrelevant redirects.

As a PrestaShop catalog evolves, products disappear, categories move, and friendly URLs change. The new store can work correctly while old paths continue receiving traffic from Google, backlinks, ads, email, or bookmarks.

Common causes of legacy 404s

Typical causes include deleted products, changed friendly URLs, reorganized category structures, old module-generated URLs, version migrations, and retired campaign landing pages.

Where should a deleted product redirect?

Use a relevance-first decision process:

  1. Same product has a new URL → redirect directly to it.
  2. A clear replacement product exists → redirect to the replacement.
  3. No direct replacement, but a tightly relevant category exists → consider that category.
  4. No meaningful destination → preserve a true 404 or appropriate 410.

The homepage should not become the default destination for every retired product.

Friendly URL changes

When only the slug changes and the underlying product remains the same, the old URL should normally redirect directly to the new canonical product URL.

/old-product-name → /new-product-name

Large catalogs need prioritization

Stores with thousands of products can generate a large number of historical URLs. Prioritize the paths that show real demand: organic entry traffic, referrers, campaign parameters, backlinks, and repeated human requests.

How no404 fits in

The no404 PrestaShop integration can act as a visibility and matching layer:

legacy product URL → PrestaShop 404 → no404 checks known match → redirect when relevant → otherwise preserve normal 404.

This keeps native error behavior while exposing lost-traffic opportunities.

After a migration

Crawl historical sitemap URLs, test high-traffic landing pages, watch for redirect chains, monitor Search Console changes, and continue observing live 404 traffic for several weeks.

Conclusion

Good PrestaShop 404 management is not about hiding every missing URL. It is about connecting moved content to a relevant new destination and leaving truly missing content as a real error. no404 helps identify which historical paths still receive human traffic.

Related reading