Understand the single 404 redirect rule

This module does not provide a redirect-rule editor. Its behavior is equivalent to:

WordPress frontend request is a 404
    → choose the normal or Polylang-language homepage
    → return a permanent 301 redirect

Requests it affects

The redirect runs during WordPress template routing, after WordPress has classified the request. It therefore depends on the final WordPress 404 state.

It does not repair:

• server-level 404 responses that never reach WordPress;
• a CDN response produced before the origin;
• an application that returns 200 OK for missing content;
• a PHP or server error that is not a WordPress 404;
• incorrect links inside stored content.

Precedence with other redirect providers

Another plugin, theme callback, server rule, or CDN can redirect before or during the same journey. The first response that ends the request wins. Do not run two blanket 404 strategies without defining which one owns the outcome.

When to choose another tool

Use a dedicated redirect manager when old URLs need specific replacements, temporary redirects, regular-expression matching, exclusions, logs, or scheduled expiry. Use a real 404 response when no equivalent resource exists.

If this module is appropriate, enable it once and test representative missing URLs in every active language.