Key Takeaways
A 404 means the requested page could not be found, but the cause may be a mistyped URL, missing content or a problem with WordPress rewrite rules. A few careful checks can help identify the right fix.
- Check the URL before changing site settings; a small typo can be the whole problem.
- Review permalink settings if many pages return 404 errors at once.
- Restore a page or publish it again if its content should still exist.
- Redirect old URLs to relevant destinations when content has moved permanently.
- Monitor broken links after updates and make your 404 page useful to visitors.
What a 404 error means in WordPress
A 404 error appears when a visitor requests a URL that cannot be found. In WordPress, that may mean the content is genuinely missing, or that the site is not resolving a valid URL correctly. The message can look different from one site to another, but the underlying response is the same: the requested resource was not found.
How a 404 response differs from a server error
A 404 is a specific response indicating that the requested page or file could not be found. A server error, such as a 500 response, points instead to a problem handling the request. The distinction matters: if just one old address fails, the page may have moved; if many pages fail at once, a broader configuration problem is worth checking.
A browser may show a plain error message, while a WordPress site may display its own designed page with navigation and other helpful links. The appearance alone does not tell you whether the underlying issue is isolated or widespread, so check the affected address and test other pages too.
What visitors see when a page cannot be found
Visitors usually land on a message such as “Page not found” or “404”. Some sites show only a short explanation; others offer a search box, navigation links or a route back to the homepage. A clear custom page can help someone recover from a wrong turn rather than leaving straight away. For examples of how these pages can differ, see this guide to WordPress 404 pages.
How missing pages affect user experience and SEO
A broken link interrupts a visitor who expected to reach useful content. If the page has genuinely been removed, a 404 is often the honest response; it is not automatically a sign that the whole site has an SEO problem. However, repeated broken internal links can frustrate visitors, while outdated external links may send them to dead ends. Fixing the cause and pointing people to a relevant destination helps preserve a sensible path through the site.
Why WordPress pages return 404 errors
WordPress builds page addresses using settings and rewrite rules, so an error can appear even when the site itself is still running. The cause might be a changed URL, deleted content or a conflict in the configuration that routes requests. Start by asking whether the problem affects one address or several; that simple distinction can make troubleshooting less of a guessing game.
How changed permalinks can break existing URLs
A permalink is the address used for a post or page. Changing the permalink structure or editing an individual page’s slug can leave old links pointing to an address WordPress no longer recognises. The content may still be available at a new URL, but visitors and search engines following the old one can receive a 404 unless the old address is redirected.
If a group of pages began failing after a change to permalink settings, the rewrite rules may also need refreshing. A short set of permalink reset steps can help with that kind of WordPress issue, though it will not restore content that has actually been deleted.
What happens when a page or post is moved or deleted
Moving a page, changing its slug or deleting it removes the old destination unless you deliberately preserve it. Any menus, internal links, bookmarks or links on other websites that still use the old URL may then lead to a 404. When the content has a clear replacement, a redirect is usually kinder to visitors; when it should still exist, restoring or republishing it may be the better answer.
How plugin, theme or server settings can cause errors
A plugin or theme can affect how WordPress handles requests, and server settings determine how those requests reach WordPress in the first place. A recent update or configuration change is a useful clue, especially if several unrelated URLs have begun failing together. Hosting changes or incorrect rewrite rules can also be involved, so avoid editing server files at random; first note what changed and whether the problem is limited to one page.
How to find the source of a 404 error
Troubleshooting is easier when you gather a little evidence before making changes. Note the exact URL, when the issue began and whether other pages on the site still load normally. Then compare the failing address with the page’s intended URL and check whether the error appears consistently in a private browser window or on another device.
Check the affected URL and its spelling
Look closely at the address, including its spelling, hyphens, trailing characters and any capital letters. If the link came from your own site, open the page where it appears and check the link target rather than relying on the visible words. A 404 troubleshooting guide can provide further context if you are working through several broken links.
When you have a list of affected addresses, these clues can help separate a mistyped link from a missing page or a broader site issue:
| What you notice | Possible cause | Useful next check |
|---|---|---|
| One URL fails and nearby pages work | Typo or a changed slug | Compare it with the current page address |
| Several post URLs fail together | Permalink or rewrite-rule issue | Review permalink settings |
| A deleted page’s old address fails | Content is no longer published | Decide whether to restore or redirect it |
| Many unrelated URLs fail after a change | Plugin, theme or server configuration | Review recent updates and server settings |
These are starting points rather than proof of a cause. Confirm what the page should do before changing settings, particularly if a URL is used in menus, campaigns or links from other sites.
Review WordPress permalinks and rewrite rules
In the WordPress dashboard, open the permalink settings and check that the current structure is the one the site is meant to use. If the structure looks right but pages still fail, saving the settings can prompt WordPress to refresh its rewrite rules. This is a low-impact check, but it cannot fix a misspelt URL or bring back a page that is no longer published.
Use analytics and Google Search Console to spot broken links
Analytics data may show visits landing on URLs that people cannot use, while Google Search Console can report pages Google has tried to crawl but could not access. Review the affected paths and look for patterns: a cluster of similar addresses can point to one old URL format or a batch of changed pages. Reports can take time to reflect recent changes, so verify a suspected error by visiting the address yourself before acting on it.
How to fix common WordPress 404 errors
Choose a fix that matches the cause, and change one thing at a time. If a single URL is wrong, correct the link or page address; if many valid pages fail, investigate permalink and server rules. Keeping a note of what you change makes it easier to undo a step if it does not help.
Refresh permalink settings to rebuild rewrite rules
If the page content exists but valid post or page addresses return 404 errors, refresh the permalink settings in the WordPress dashboard. Go to Settings, then Permalinks, and save the existing settings without changing the structure unnecessarily. For many sites, this prompts WordPress to rebuild its rewrite rules and can resolve a routing problem.
After saving, test more than one affected URL and check that the homepage and dashboard still work. If the problem remains, avoid repeatedly changing the permalink format: the issue may sit in server configuration or come from another recent change.
Restore or publish the missing page
If the page should be available, check whether it is in the trash, saved as a draft or set to private. Restore it or publish it as appropriate, then confirm its URL and test the page while logged out. If you create a replacement with a different slug, update links that you control and consider redirecting the old address when it still receives visits.
Check .htaccess and web server configuration
On some WordPress installations, .htaccess contains rules that help route requests to the right page. A damaged or incomplete file can interfere with that process, although not every server uses .htaccess; some rely on other web server configuration. Before making changes, save a copy of the current settings and check with your host if you are unsure which rules apply. A wrong edit can affect more than the page showing the 404.
How to redirect visitors to the right page
A redirect sends a visitor from an old address to another URL. It is useful when a page has moved, but it is not a universal substitute for finding the real cause of a 404. First decide whether the original content should return or whether a clear replacement now exists; then choose the simplest route that serves the visitor’s intent.
Choose between a 301 redirect and restoring the original URL
A 301 redirect is generally used when a page has moved permanently and there is a genuinely relevant destination. If the content has only disappeared by mistake, restoring the original page at its original URL may be more appropriate. Consider the old page’s purpose and any links pointing to it rather than sending every missing address to the homepage.
Set up redirects with a WordPress plugin or server rules
Redirects can be configured with a suitable WordPress plugin or through server rules, depending on the site setup and the access available to you. Whichever method you use, enter the old address and the correct destination carefully, then test the redirect in a private browser window. Keep a record of the change so it can be reviewed if the destination or site structure changes again.
Avoid redirect chains and irrelevant redirect targets
A chain occurs when one URL redirects to another that redirects again, adding unnecessary steps before a visitor reaches the page. Review existing redirects when URLs change, and point an old address directly to the most relevant current destination where possible. Sending unrelated missing pages to a generic page may confuse visitors, so leave a 404 response where there is no suitable replacement.
How to prevent and monitor future 404 errors
Some broken links are an ordinary consequence of maintaining a site, but a few habits can reduce how often visitors encounter them. Treat URL changes as part of publishing and migration work, not as a small detail to tidy up later. After changes go live, check the pages and links that matter most.
Update internal links when URLs change
When you change a page slug, update links in menus, posts, landing pages and other places you control. If the old URL has already been shared or indexed, add a redirect to the new address as well. Check the final link by opening it after publishing; a link can look correct in an editor and still point to an outdated path.
Create a useful custom 404 page
A custom 404 page should explain plainly that the requested page was not found and offer a practical next step. A search box, a link to the homepage and a few useful sections can help visitors continue without pretending the missing page still exists. Keep the page simple and make sure its own navigation works; more ideas for custom 404 page design can help you shape the experience.
Monitor broken links after site updates and migrations
After an update or migration, test important pages and review reports for new 404s. Give particular attention to URLs that changed format, moved between sections or were carried across from an older site. If errors appear, compare them with your change log and correct the underlying link or destination rather than adding redirects without checking where visitors ought to go.
Conclusion
A WordPress 404 is a useful signal, not a diagnosis by itself. Check the address, confirm whether the content should exist and look for patterns before changing settings; then restore the page, refresh rewrite rules or redirect to a genuinely relevant destination. Regular checks after publishing and site changes help visitors find their way when URLs move.
Frequently Asked Questions
What does a 404 error mean in WordPress?
It means the requested URL could not be found. The content may be missing, or WordPress or the server may not be resolving the address correctly.
Why do only some WordPress pages show a 404?
An individual page may have a typo in its URL, a changed slug or unpublished content. If many pages fail at once, review permalink settings and recent site or server changes.
Can refreshing permalinks fix a WordPress 404?
It can help when rewrite rules are causing valid pages to fail. It will not correct a wrong link or restore content that has been deleted.
Should I redirect every 404 page to the homepage?
No. Redirect only when there is a relevant destination, such as a replacement page. A homepage redirect can confuse visitors who expected specific content.
Is a 404 error bad for SEO?
A 404 on a page that has genuinely been removed is not automatically a site-wide SEO problem. Broken links to useful content should still be corrected, and moved pages may need a suitable redirect.
What is the difference between a 404 and a 500 error?
A 404 says the requested resource could not be found. A 500 response indicates that the server encountered a problem while handling the request.
How can I find broken URLs on my site?
Check links manually, review analytics for visits to failing pages and use Google Search Console to identify crawl issues. Confirm reported URLs by visiting them before making changes.