Fix 404 Errors and Broken Links in WordPress

See what is broken, and what you have already fixed.

After a redesign, old addresses keep getting visits. The Control Panel shows how many 404s you have, which URLs are hit most, and which redirects are doing the work.

• Totals for recorded 404s and active redirects
• The broken URLs people hit most, with Fix it on each row
• The latest 404s, and the redirects that fire most often

Read the rule in a sentence before you save it.

As you add a redirect, a plain-English line updates: what will match, and where it will go. If the target is the same as the source, the rule is skipped so visitors are not sent in a loop.

• Match the full URL, or a URL that contains, starts with, or ends with a string
• Turn on regex, or use Find and replace with capture groups
• The sentence is there so you do not have to guess what a pattern will do

Keep crawlers out of the log, unless you want them.

Bots request far more missing URLs than people do. By default only guest 404s are stored, as the logging settings describe. Turn logging on or off without disabling the plugin.

• Store bot 404s only when you opt in
• Ignore patterns such as *.map or wp-json/* are in PRO
• Deleting log rows after 30, 60, 90, or 180 days is in PRO. Your redirects stay

Send every leftover 404 to one page you choose.

The catch-all is in PRO. It runs only when no specific rule matches, so a URL you already fixed still goes to its own target.

• Useful after a redesign, when you cannot map every old address
• Any single rule can point at a WordPress menu item, so it stays right if the slug changes (free)
• Danger strings, also in PRO, flag probe paths such as .env and can send those requests somewhere else

Take the redirect list with you.

Import and export is in PRO. Export a CSV, edit it, and import it on another site. Matching rules are updated. New ones are added.

• A backup before a migration or a staging refresh
• Your notes, match type, and status code travel with the file