How to Fix 404 Error Pages on Your WordPress Site

Few things waste hard-earned traffic like a 404 error. A visitor clicks a link expecting your content — from Google, from social media, from another website — and instead hits a dead end: “Page not found.” Every 404 is a small leak in your site, and enough leaks quietly drain your rankings and revenue. The good news is that 404s are normal, expected, and completely manageable once you know how to find them and what to do with each one. This guide shows the full process, from detection to permanent fixes.

Quick Answer

To fix 404 errors in WordPress, first find them using Google Search Console’s Pages report or a plugin like Redirection, which logs broken URLs. For each broken URL, either restore the missing page, update the links pointing to the wrong address, or add a 301 redirect from the old URL to the closest matching live page. Finally, make your 404 page helpful — with a search box and links to popular content — so any future stragglers still find their way.

What a 404 Error Actually Is

A 404 is the server’s way of saying: “I looked for that exact address, and nothing exists there.” It happens when a page was deleted, its URL changed (a new slug or permalink structure), a link was typed wrongly, or someone linked to you with a mistyped address. A healthy site accumulates some 404s over time — they are not an emergency and Google does not punish you for having a few. The problems start when important pages, or large numbers of internal links, point into the void. Google’s own guide to HTTP status codes explains how search engines interpret 404 and related responses.

Step 1: Find Your 404 Errors

You cannot fix what you cannot see. Use one or more of these sources:

1. Google Search Console. Open Pages (Indexing) and look for “Not found (404)” in the “Why pages aren’t indexed” table. This lists broken URLs Google has actually tried to visit — the ones that matter most. If you have not set it up yet, our guide on setting up Google Search Console takes ten minutes.
2. The Redirection plugin. Beyond managing redirects, it keeps a 404 log of every broken address visitors hit on your site, including ones Google has not found yet.
3. A broken-link scan. Tools like Screaming Frog (free up to 500 URLs) or an online broken-link checker crawl your whole site and report internal links pointing to 404s.
4. Your host’s error logs, for the technically comfortable — raw, complete, but harder to read.

Collect the list into a simple spreadsheet with two columns: the broken URL, and where the link was found. You will work through it in the next steps.

Step 2: Decide the Right Fix for Each URL

Not every 404 deserves the same treatment. Sort yours into four groups:

Group A: The page should exist — restore it

If the page was deleted by accident or during a redesign, the best fix is bringing it back at the same URL (from a backup, the Trash, or by republishing). The 404 vanishes and every existing link works again.

Group B: The page moved — add a 301 redirect

If the content now lives at a new address, redirect the old URL permanently to the new one. A 301 redirect passes the visitor and nearly all the search value to the new page. Always redirect to the closest relevant page — the same article’s new URL, or its parent topic — never lazily to the homepage, which Google treats as a soft error and visitors experience as a dead end anyway.

Group C: The link is wrong — fix the link

If the broken URL is caused by a typo in your own content (a link you control), correct the link itself. Update the post, menu, or widget that contains it. Redirects are a safety net, not a substitute for correct internal links — fixing the source keeps your site clean.

Group D: The page never existed and has no value — leave it

Random mistyped URLs, old spam-bot probes (strange addresses with random characters), and long-dead pages with no links or traffic can stay as honest 404s. A correct 404 for genuinely non-existent content is the right answer, not a failure.

Step 3: Add Redirects in WordPress

The Redirection plugin is the standard tool:

1. Install and activate Redirection, then run its quick setup.
2. Go to Tools → Redirection → Add New.
3. Enter the Source URL (the broken address — just the path, like /old-post-name/) and the Target URL (the live page).
4. Confirm the action is “Redirect to URL” with a 301 (permanent) status, and add it.
5. Visit the old address in your browser to verify it lands on the new page.

The plugin’s 404 log doubles as an ongoing to-do list: check it monthly and redirect anything meaningful that appears. Server-level redirects in .htaccess or your host’s redirect tool are faster at scale, but the plugin is safer for most users because a typo cannot take the site down.

Step 4: Make Your 404 Page Helpful

Some visitors will always land on missing pages — old bookmarks, shared links you cannot control. A good 404 page rescues them:

• A friendly, on-brand message (“That page has moved or retired”) rather than a cold error.
• A search bar — the visitor came looking for something specific, so let them find it. A search block or widget takes only a minute to add.
• Links to your homepage, your most popular posts, and your main categories.
• Your normal header, menu, and footer, so the site still feels intact.

Most themes provide a styled 404 page automatically; you can customise its content with a plugin (such as 404page) or your theme’s settings.

Common Mistakes to Avoid

• Redirecting everything to the homepage. It looks like a fix but acts like a soft 404 to Google and confuses visitors. Redirect to relevant pages or do not redirect at all.
• Deleting pages without checking their traffic and links. Before removing anything, check Search Console: a page with backlinks or visits deserves a redirect plan, not a silent deletion.
• Changing your permalink structure casually. It rewrites every URL on your site at once — a 404 factory. If you must change it, plan sitewide redirects first.
• Ignoring the 404 log forever. New broken URLs appear as other sites link to you imperfectly and as you edit content. Ten minutes a month keeps the list at zero.
• Creating redirect chains. A → B → C hops slow everything down and dilute value. Point every old URL directly at its final destination and update older redirects when targets move again.

Conclusion

404 errors are a normal part of a living website — the skill is in catching them and handling each one correctly. Monitor with Search Console and a redirect plugin’s log, restore what should exist, redirect what moved to its closest match, fix typos at the source, and let genuinely dead addresses stay honestly dead. Finish with a helpful 404 page as your safety net, and broken links stop being a leak and become one of the best-maintained parts of your site.

Frequently Asked Questions

Do 404 errors hurt my SEO?

A small number of natural 404s does not harm rankings — Google expects them. Problems arise when valuable pages 404 (losing their rankings and backlinks), when your own internal links point to many broken pages, or when a site migration leaves thousands of old URLs dead. Those are the cases this guide fixes.

What is the difference between a 301 and a 302 redirect?

A 301 is permanent: it tells search engines the page has moved for good and transfers its ranking value to the new URL. A 302 is temporary and does not fully transfer value. For fixing 404s from moved or renamed content, always use 301.

How do I find 404 pages on my site for free?

Google Search Console’s Pages report lists the 404s Google has found, and the free Redirection plugin logs every 404 your visitors hit. Between those two you will catch everything that matters without paying for tools.

Should I redirect a deleted product or post to a category page?

If no close replacement exists, the parent category is a reasonable target — it is relevant, and visitors can browse similar items. It is far better than the homepage. If the category is also irrelevant, leaving an honest 404 is cleaner than a misleading redirect.

Why do I see weird random URLs in my 404 log?

Bots constantly probe websites for vulnerable files and forgotten admin pages, generating nonsense 404s. These are harmless background noise of the internet — you do not need redirects for them. Only act on URLs that real visitors or search engines are genuinely trying to reach.