404 Monitor & Redirect Manager

Core SEO creates a redirect when you rename a product or category and lets you add single redirects by hand. It does not show which URLs end in "Page not found", and it has no patterns, no regular expressions, no 302 or 410, no bulk import and no hit counters. This add-on adds those and keeps core SEO in charge of everything it already does: core redirects and existing pages come first.

No. On a normal page view the add-on reads one small cached list (the override rules, usually empty) and writes nothing. The rules are only evaluated for URLs that would end in a 404, and 404s and redirect hits are collected in a buffer file and written to the database in batches, at most once a minute.

Yes. Redirects and 404 pages are never cached, so every old URL still reaches the add-on and is redirected or logged. When you save an Override rule for a page that exists, the add-on clears the page cache so the rule applies at once.

By default search engine bots (Googlebot, Bingbot and similar) are counted in their own column, because they show which old URLs search engines still request. Other bots, vulnerability scanners and scripts are skipped. You can log visitors only or everything (setting Bot requests). Typical scanner URLs such as /wp-login.php are ignored by the Ignored URLs setting.

The log stores no IP addresses (not even hashed), no user or session IDs and no cookies. Referrers are kept without their query string. Entries are deleted automatically after the retention period.

301 for content that moved for good (search engines transfer the ranking to the new URL). 302 for temporary moves, for example a seasonal landing page. 410 for content that is gone for good and has no replacement: search engines drop the URL faster than after a 404.

By default it is passed to the target, without tracking parameters (?color=red&utm_source=news becomes ?color=red). Switch Pass the query string off per rule to drop it.

Yes, enter the full URL as the target. Relative paths always stay on the storefront the visitor is on.

No, core SEO creates that redirect itself. Use rules for URLs core does not know: an old shop system, deleted products, external links with typos.

Its target is itself redirected by another rule, so visitors take two hops. Edit the rule and point it to the final URL. Loops (/a → /b → /a) cannot be saved.

Only your own storefront, without following redirects, and with a header that keeps the request out of the log. It never requests other domains.

Without a valid license (no key after the 14-day start period, an invalid or revoked key, a domain the license does not cover, or no successful check for 14 days), your redirect rules stop applying on the storefront and new 404 errors are not logged. Core SEO redirects keep working, and your rules, the 404 log and the admin pages stay available. Once the license is valid again, the rules apply again.

Open Add-ons → Manage add-ons → 404 Monitor & Redirect Manager: the License card at the top says what is wrong: no key, a key for another add-on, a revoked license, or a domain that the license does not cover. Fix it on the License tab and click Check now. See License.

Yes. Subdomains of your licensed domain (for example staging.example.com) and local development hosts (localhost, private IP addresses, .local, .test) are covered by the same license.

Nothing changes for 14 days: the add-on keeps working and retries every hour. Only if no check succeeds for 14 days are the rules switched off until the next successful check.

No. The check runs only in the admin panel or from cron, at most once a day, never while customers browse or check out.