Why do I see many URLs in 404 errors that never existed on my site?

A URL can be requested even if it has never existed on your shop. The 404 error pages log records requests that the module identifies as targeting a missing page, in the cases it handles. It is not a record of every 404 error on the server: a request must reach PrestaShop for the module to process it.

These requests may come from:

• an old URL whose content has been removed or moved;
• a typing mistake or an incorrect link;
• an automated request trying paths unrelated to your site.

For example, /wp-admin is a path used to access the WordPress administration area. Its presence in the log of a PrestaShop shop may be caused by a bot looking for that entry point. That URL alone does not reliably identify who made the request or why, and does not prove that they accessed your administration area.

Should you create a redirect for every URL?

No. First check whether the URL relates to real shop content or a link that visitors use. If a link is incorrect, fix it at its source. If content has moved and has a relevant equivalent, redirecting to that equivalent may be appropriate. For a path unrelated to your site, you do not need to create a redirect just to remove a line from the log; a 404 response remains appropriate for a nonexistent resource.

To help your investigation, the table includes the URL, a count, the origin when available, the user agent and the date. Requests are grouped by URL; the count reflects retained entries, not an unlimited history.

The log contents depend on received requests, automatic redirect settings and data retention. A redirected URL is therefore not necessarily listed as a 404 error here. For recorded redirects, see the Redirections logs page.

Why is an expected URL missing from the log?

Check the response returned for the URL and any redirects, then the module’s automatic redirect settings and any redirect set on the product page. These paths may bypass recording in this log. A request handled by the web server, a proxy or a CDN before it reaches PrestaShop cannot be recorded by the module.

If needed, compare this log with your hosting access and error logs. A module entry does not replace checking the HTTP status actually returned to the visitor. A missing entry also does not prove that no request was received.