How to Fix WordPress 404 Errors With Plugins or Manually
Fix WordPress 404 errors with a plugin for moved URLs or built-in settings for broken permalinks, and leave truly missing pages with a proper 404 response.
Last updated:
Reviewed for accuracy by Jesse Nickles
Find out why the page returns 404
Open the affected URL, then check for its post or page under Posts → All Posts or Pages → All Pages in WP Admin. Match the problem to the right fix before adding a redirect:
| Situation | Recommended action |
|---|---|
| URL changed | Redirect the old URL to its replacement. |
| Page still exists | Check its status, slug, and permalink settings. |
| Page was deleted | Restore it or retain a 404/410 response if no suitable replacement exists. |
If just one URL fails, compare it with the published page's slug and check whether the page was moved or deleted. If your homepage works but many published posts return 404, look for broken permalink rewrite rules rather than redirecting every post. WordPress can load the homepage while the web server fails to route readable post URLs to WordPress. Start at Settings → Permalinks, as described in the official 404 troubleshooting guidance.
Redirect moved URLs with a plugin
If a page moved to a clearly equivalent address, the free Safe Redirect Manager plugin by 10up lets you create a redirect in WP Admin:
- Go to Plugins → Add New Plugin, search for Safe Redirect Manager, then install and activate it.
- Open Tools → Safe Redirect Manager and add a redirect.
- Set Redirect From to the original path, such as
/old-page/. - Set Redirect To to the matching replacement, such as
/new-page/. - Choose 302 under HTTP Status Code and publish the rule for testing.
- Open the old URL in a private browser window. Once it goes to the intended page, change the rule to 301 and save it. Browsers can cache permanent redirects aggressively.
Use a path relative to the WordPress installation for Redirect From; Redirect To accepts a path or full URL. A redirect applies to matching requests even if the original page still works, so use one specific path for one moved page. Broad wildcards or regular expressions can unintentionally redirect unrelated URLs. See 10up's configuration instructions.
Safe Redirect Manager does not log 404 requests. Use Google Search Console or server logs to identify broken URLs, and create redirects only when a genuinely relevant replacement exists. Random requests by bots for nonexistent paths usually do not need redirect rules.
Fix broken permalinks without a plugin
If the page is still published at its intended address but returns 404, refresh WordPress's permalink rules before installing a redirect plugin:
- Edit the page or post and confirm it is Published and its slug matches the requested URL.
- Go to Settings → Permalinks in WP Admin.
- Leave the permalink structure unchanged and click Save Changes. This refreshes WordPress's rewrite rules without changing your chosen URL format.
- Reload the affected URL and another published page to see whether the problem is resolved.
If many published URLs still fail, ask your host to check the web-server routing. Apache sites may need working .htaccess rewrite rules and mod_rewrite; Nginx uses its own configuration and ignores .htaccess. The WordPress setting cannot fix missing server-level routes by itself. Do not paste unfamiliar server rules into a live site; see the official WordPress Nginx guidance and ask your host to review the configuration.
A WordPress redirect plugin cannot repair a server-level 404 when the request never reaches WordPress.
Know when a 404 should stay
If content was permanently deleted with no close replacement, return 404 (not found) or 410 (gone). A legitimate missing page is not automatically an SEO problem. Do not redirect unrelated URLs to your homepage simply to clear errors from a report; Google may treat those irrelevant redirects as soft 404s. Use a 301 redirect when content has genuinely moved to a relevant new page.
A soft 404 can also occur when a page displays a missing-content message but incorrectly returns 200 OK. Search engines may treat that successful response as an error because the page has no real content. Ensure deleted pages return the appropriate HTTP status instead of rendering a fake 404 page with a 200 response. See Google's crawling error guidance.
Check the result
- Open the original URL in a private window. A repaired page should load at its intended address; a moved URL should reach its relevant replacement.
- Inspect the HTTP response in your browser's developer tools or an HTTP status checker. Confirm a permanent move returns
301, its Location header points to the right destination, and the final page returns200without loops or unnecessary redirect chains. - For deleted content with no replacement, confirm the URL returns
404or410, not200with a missing-page message. - Update your site's internal links to point directly to the final working URL rather than relying on redirects.
- If Google Search Console previously flagged the URL, use URL Inspection to check it after the change. Search reports may take time to update.