WordPress Posts Return 404 Errors? Check Permalinks Before Redirects
Diagnose WordPress 404 errors by checking the affected URLs, published content, permalinks and server rules before adding redirects.
Quick answer: If the homepage opens but many WordPress posts return 404, check the permalink and server rewrite setup first. If only one old address fails, check whether that page’s slug changed or the content was removed. These symptoms call for different fixes.
A 404 means the requested address was not found. It does not, by itself, prove that the database lost the page. Record the exact failing URL and compare it with the current public link in the WordPress editor.
1. Map the pattern before changing settings
Open the site while signed out and test a small sample: homepage, an ordinary page, a blog post, a category archive and one image. Note whether each works. Check both a copied browser address and a link clicked from your own navigation.
| Observed pattern | First investigation |
|---|---|
| Homepage works; most inner pages fail | Permalink rules and server configuration |
| One old URL fails; the editor’s current link works | Slug changes and outdated links |
| Only one content type fails | The plugin registering that content type and its URL rules |
| Media files also fail | File presence, paths and migration completeness |
| Everything fails, including the homepage | Domain, hosting and the intended site destination |
This table is a diagnostic starting point, not a promise that one symptom has only one cause. A short list of failing examples is more useful to support than “all links are broken.”
2. Confirm that the content exists and is public
Find the affected page or post in WordPress. Check whether it is published, private, scheduled, draft or in the trash. Copy its current permalink rather than rebuilding the address from memory. Look for a changed slug, a parent page change or an unexpected language prefix.
If the current public link works, update your own menu and internal links to that address. Then decide what should happen to the old link. Do not change the entire site’s permalink structure to repair one missing page.
For a missing media file, confirm that the file was transferred and that the page references the correct location. A navigation fix cannot restore an image that never reached the new server.
3. Refresh the existing permalink rules
Take a backup before configuration changes. Open Settings → Permalinks, record the current structure, and save the existing choice without intentionally switching to a new URL format. Retest several failing links.
WordPress’s common errors guide identifies permalink rewrite issues as a possible cause, especially after server moves. It recommends resetting permalinks and seeking hosting help when server rules need attention. The permalink settings reference explains the URL structure options.
If the links still fail, ask the host to check the correct configuration for its server. Apache and Nginx do not use identical rules. Do not paste a generic configuration over security, caching or application rules you do not understand.
4. Check the change that preceded the error
Did the problem start after migration, a plugin update, a domain change or a redesign? On a protected test copy, investigate the component associated with that change. If a custom content type disappeared, confirm that its relevant plugin is active and functioning.
Clear the appropriate site and edge caches after a verified fix, then retest signed out. An old cached error can make a repair appear unsuccessful. Keep the exact URL and test time in your notes so the host can compare the request with logs.
For recent server moves, compare your results with the WordPress migration checklist. If recovery involved a backup, use the restore checklist to check for incomplete files or mismatched data.
5. Redirect only when the content has moved
If a page moved permanently and an equivalent replacement exists, arrange a permanent redirect from the old address to the new one. Google’s redirect guidance explains permanent and temporary options.
If the page is genuinely gone and has no suitable replacement, a proper not-found response can be appropriate. Sending every missing URL to the homepage does not give visitors the answer they expected. Google’s HTTP status documentation also distinguishes successful content from missing pages and soft 404 responses.
6. Verify and keep the record
Test the repaired URL, its old address if redirected, and the links pointing to it. Confirm that the destination has useful content and does not loop. Recheck the important mobile navigation and the sitemap if public URLs changed.
For a planned redesign, read the redesign SEO checklist. To get help with a fault, send StartMyWeb the affected URLs and the recent change, with passwords and customer details removed.
About StartMyWeb · Privacy policy
Editorial note: Prepared with AI assistance and checked against the official documentation linked above. Examples are illustrative; test changes on a recoverable copy before applying them to a live business website.
If this issue is affecting a live business website, I can review the setup and help you plan the safest fix.
Published by Lookman at Start My Web, an independent web and WordPress service working online from Bengaluru. Examples are illustrative; project scope and third-party product terms should be confirmed for your requirements.