Fixing 404 Page Not Found Errors
The most common cause of a 404 error is a simple typo in the web address. Before investigating further:
- Look carefully at the URL in the browser address bar
- Check for any spelling mistakes, extra characters, or missing hyphens
- Make sure the URL doesn’t have a trailing space or unusual characters
- If someone sent you the link, try navigating to the page through your website’s menu or search instead
If the URL looks correct and the page was definitely working before, move on to the next steps.
The page may have been moved to the Bin (trash) or set to Draft by accident:
- Log in to WordPress
- Go to Pages → All Pages in the sidebar
- Look for the page in question — check both the main list and the Bin tab at the top
- If the page is in the Bin, hover over it and click Restore
- If the page shows as Draft, click into it and change the status to Published
If the page exists and is published but still shows a 404, the issue is likely with your permalinks (see next step).
A common fix for 404 errors is to flush (reset) your permalink settings. This tells WordPress to rebuild its URL structure:
- Go to Settings → Permalinks in the WordPress dashboard
- You don’t need to change anything — just scroll to the bottom
- Click Save Changes
- Visit the page that was showing a 404 and see if it now loads correctly
This simple step resolves the majority of 404 errors, especially after importing content, updating plugins, or making structural changes to your site.
If someone edited the page and changed its URL slug (the part after the last /), the old URL will stop working:
- Go to Pages → All Pages and find the page
- Click Edit to open it
- In the right-hand panel, look at the URL or Permalink section
- Check whether the slug matches what you expect — for example, if the page was at
/about-us/but the slug now saysabout, the old URL won’t work - If needed, change the slug back to the original, or set up a redirect from the old URL to the new one
This is especially common when pages are duplicated or when titles are edited (as WordPress may auto-generate a new slug).
Sometimes a 404 error is cached by your browser or your website’s server cache. Clearing both can resolve ghost 404s:
- Clear your website cache (from the WordPress admin bar or Kinsta Cache plugin)
- Clear your browser cache (or try opening the page in an incognito/private window)
- Try loading the page again after clearing both caches
If the page loads correctly in incognito mode but not in your normal browser, the issue is definitely a browser cache problem.
If none of the above steps have resolved the 404 error, the issue may require technical investigation. Contact InnerMedia support if:
- The page exists, is published, and the slug is correct — but it still shows a 404
- Multiple pages across your site are suddenly showing 404 errors
- The 404 appeared after a plugin update, WordPress update, or server change
- You need to set up bulk redirects (e.g., after a site restructure or domain change)
- The 404 is on a URL that’s indexed by Google and driving traffic
Our team can investigate server-level issues, .htaccess conflicts, plugin interference, and more advanced redirect configurations to get your pages working again.
Completed
If you are still experiencing issues, our support team is here to help.
Was this article helpful?