WordPress 404 Redirects: Use Redirection Selectively

A WordPress 404 error means a requested URL does not currently have a page. Sometimes that is expected: a visitor typed an address that never existed. Sometimes an important page moved and people still follow its old link. In the second case, a redirect to a genuinely equivalent page helps visitors and search engines find the new location. The Redirection plugin can manage those rules and show 404 logs without editing server configuration.

Do not redirect every missing URL to the home page. A correct 404 is often the honest response when content is gone and there is no suitable replacement. Google does not treat each 404 as a site-wide SEO penalty. What matters is whether valuable URLs, internal links, or user journeys are broken.

When does a redirect make sense?

Google’s redirect guidance explains that a permanent redirect signals that the destination should be treated as the new canonical location. That does not mean any redirect is beneficial. A page about one service sent to an unrelated home page may confuse the visitor and be treated as a soft 404.

Find the missing URLs worth fixing

Start with internal links, old URLs that still get external visits, and pages changed during a redesign. Open the missing URL yourself. Check whether a suitable replacement exists. If the page simply moved, note the old and new addresses. If a link inside your own site is wrong, update that link as well; a redirect should not be the only repair.

Redirection’s 404 tracking documentation describes its log and how to create a rule from a logged URL. A log can contain typos, crawlers probing nonexistent paths, and genuine visitor requests. Do not turn every line into a redirect. Sort by meaningful traffic and whether the original intent can be served.

Consider privacy and storage. The plugin’s logging options describe what is recorded and allow configuration. Set retention to match the site’s needs and avoid keeping unnecessary visitor data indefinitely.

Install the Redirection plugin

In a WordPress dashboard with permission to manage plugins, go to Plugins → Add New, search for “Redirection,” check the author and plugin identity, then install and activate it. Make a backup before changing a production site’s URL behavior, especially if other SEO or hosting tools already manage redirects.

Follow the setup screen and confirm that its REST API access works. The plugin notes that a disabled WordPress REST API can interfere with its interface. Check whether another plugin, theme, or server rule already redirects the same source path to avoid competing rules.

Create a permanent rule for a moved page

1. Open Tools → Redirection in WordPress.
2. Enter the old path as the source, for example /old-service/.
3. Enter the new, relevant destination, for example /services/current-service/.
4. Choose the permanent redirect behavior for a permanent move and save the rule.
5. Visit the old URL in a private browser window and verify that it reaches the intended page.

Check the final HTTP status and destination with a redirect checker or browser developer tools. A rule saved in the dashboard is not proof it works publicly. Test for loops and chains: an old URL should ideally reach the final current page directly, rather than pass through several retired URLs.

When changing a post slug, WordPress or an SEO plugin may already make a redirect. Test before adding a duplicate rule. Keep a small record of why each redirect exists so future editors can remove or update obsolete ones safely.

Use the 404 log as a triage list

Open the plugin’s 404 log and inspect repeated requests. A meaningful old article URL may deserve a redirect to its updated version. A misspelled path inside your navigation needs an internal link fix. A random path requested once by an automated scanner usually needs no action.

Prioritize URLs with known backlinks, regular visits, or a clear business role. Check Google Search Console’s page indexing and link reports where applicable, but interpret them in context. A report with many 404s is not itself evidence of a penalty; it may include URLs that were properly removed.

After adding rules, monitor whether people still hit old paths and whether the new destination meets their need. A redirect to an irrelevant page can produce a technically successful status and a poor experience.

Keep the redirect list maintainable

Review the rules after a site migration or large content cleanup. Remove duplicates and make old paths point directly to the final page. If two plugins or the host manage redirects, identify which layer owns each rule. A redirect chain can continue functioning while obscuring which setting should be changed later.

Record the reason for important rules, especially campaign URLs or pages with external links. Confirm the target remains live after future edits. A redirect is part of ongoing site maintenance, not a one-time checkbox.

Frequently asked questions

Should every 404 point to the home page?

No. Redirect only when a close replacement exists. Otherwise a proper 404, with helpful navigation, is clearer.

Does a 404 automatically harm my Google rankings?

No site-wide penalty follows from an ordinary missing URL. Important moved content and broken internal paths deserve repair because users cannot reach what they expected.

Is a 301 always the right status?

Use a permanent redirect when the move is permanent. A temporary move has different semantics. Google’s redirect documentation explains the distinction.

Does installing Redirection fix all broken links?

No. The plugin helps manage rules and inspect logs. You still need to choose relevant destinations and correct internal links.

Fix the route, then verify the destination

For a moved page, pair a relevant 301 redirect with updated internal links and a public test. For deleted content with no successor, let the URL return a genuine missing-page response. That selective approach keeps the site useful and avoids turning every unknown address into a confusing home-page detour.