How to Fix 404 Errors in WordPress: A Step-by-Step Guide

A 404 error means WordPress or the web server could not find the requested page. A single broken URL is usually easy to fix, but repeated 404 errors can prevent visitors from reaching important content and can make site maintenance harder.

Fortunately, most WordPress 404 problems have a clear cause. This guide walks through a practical troubleshooting process, starting with the simplest checks and moving toward more advanced fixes.

What Causes a 404 Error in WordPress?

Common causes include:

• A page or post was deleted or moved.
• The URL or slug changed.
• Permalink settings need to be refreshed.
• An internal link points to the wrong URL.
• A plugin or theme is interfering with URL handling.
• A custom post type or taxonomy has incorrect rewrite rules.
• A server configuration is preventing WordPress from handling the request correctly.

The important part is identifying which situation you have before changing settings. Randomly changing plugins, themes, or server files can create additional problems.

1. Check the URL First

Start with the simplest possibility: make sure the URL is correct. Check spelling, capitalization where relevant, the slug, and any trailing path segments.

If you reached the error by clicking a link on your own website, inspect the link target. If the URL contains an obvious typo, correct the link instead of changing WordPress settings.

2. Check Whether the Page Still Exists

Open the WordPress dashboard and search for the page or post. Confirm that it has not been moved to the Trash, changed to Draft, or replaced by another page.

If the content was intentionally removed, do not recreate a page simply to eliminate the 404. A removed URL may need to stay unavailable or be redirected to the most relevant replacement when one genuinely exists.

3. Refresh WordPress Permalinks

One of the most common WordPress 404 fixes is refreshing the permalink rules.

1. Go to Settings → Permalinks in the WordPress dashboard.
2. Review your current permalink structure.
3. Click Save Changes without making an unnecessary change.
4. Test the affected URL again.

Saving the permalink settings can cause WordPress to regenerate its rewrite rules. This is particularly useful when existing pages suddenly begin returning 404 errors after a configuration or site change.

4. Test the Homepage and Other Pages

Check several URLs rather than testing only the page that reported the error.

• Homepage
• One normal page
• One blog post
• A category or tag archive
• A search result

If only one URL is broken, the problem may be specific to that content. If many URLs are returning 404 errors, investigate permalink, rewrite, plugin, theme, or server configuration issues.

5. Check for Changed Slugs

If a page’s slug was changed, the old URL may no longer point to the content. WordPress can sometimes create redirects for changed post URLs, but you should not assume that every old URL will automatically resolve correctly in every setup.

Find the current permalink from the editor and compare it with the URL that produces the 404. If the content has permanently moved, use a proper redirect from the old URL to the most relevant new URL.

6. Find and Fix Broken Internal Links

If visitors can reach a 404 through your menus, buttons, related-post links, or article text, the problem is often an outdated internal link.

Update the link to the current URL rather than creating duplicate pages just to preserve an old address. When maintaining a growing WordPress site, periodically checking important internal links can prevent these problems from spreading.

7. Check Recent Plugin or Theme Changes

If the 404 errors appeared immediately after installing, updating, activating, or configuring a plugin or theme, investigate that change.

Plugins that register custom post types, taxonomies, redirects, security rules, or URL structures can affect how requests are handled. Themes can also contain custom rewrite logic.

Before disabling anything on a production site, make sure you have a recent backup and understand what the plugin or theme controls. If possible, reproduce the problem on a staging site.

8. Consider Server-Level Problems

If WordPress settings appear correct but URLs still return 404 errors, the problem may be outside WordPress itself. Depending on your hosting environment, this can involve web-server rewrite rules, document-root configuration, caching layers, or security software.

At this point, check your hosting documentation or contact your hosting provider. Avoid editing server configuration files unless you understand the environment and have a way to recover from a mistake.

9. Check Caching

A caching plugin, hosting cache, CDN, or browser cache can sometimes make troubleshooting confusing because you may continue seeing an old response after fixing the underlying problem.

After making a legitimate fix, clear the relevant cache and test the URL again in a private browser window. If a CDN is involved, follow its cache-purge procedure as needed.

10. When Should You Redirect a 404?

Do not redirect every missing URL to the homepage. A redirect is useful when a page has a clear, relevant replacement.

For example, if an article moved from an old URL to a new URL, a permanent redirect can help visitors and search engines reach the replacement. If there is no genuinely relevant replacement, keeping the URL unavailable can be more appropriate than sending visitors somewhere unrelated.

How to Prevent WordPress 404 Errors

A few maintenance habits can reduce future problems:

• Use stable, descriptive slugs.
• Update internal links when URLs change.
• Keep plugins and themes maintained.
• Test important URLs after major updates.
• Maintain backups before significant changes.
• Review important broken links periodically.
• Document major URL changes when managing a large site.

Final Checklist

When you encounter a WordPress 404, work through the problem in this order:

1. Verify the URL.
2. Confirm the content still exists.
3. Refresh the permalink settings.
4. Test several other URLs.
5. Check whether the slug changed.
6. Fix broken internal links.
7. Review recent plugin or theme changes.
8. Investigate caching.
9. Escalate to server-level troubleshooting if necessary.
10. Add a redirect only when there is a genuinely relevant replacement.

This approach keeps troubleshooting controlled and avoids making unnecessary changes to a working WordPress installation.