What this usually means
Permalink 404 errors happen when WordPress rewrite rules, server configuration, custom post type slugs or migration settings stop matching the requested URL. The safest fix is to confirm the cause before changing files, plugins, server settings or database values on a live website.
Symptoms to look for
- Pages show 404 but exist in admin
- Custom post types return 404
- Images or pretty URLs fail
- 404 errors after migration
Developer-level causes
When this problem is more than a simple setting, a developer should check logs, file changes, plugin behavior, database state and hosting configuration before applying a fix.
- Rewrite rules not flushed
- Broken .htaccess rules
- Apache mod_rewrite disabled
- Custom post type slug conflict
Steps to check
- Save Settings > Permalinks to flush rewrite rules.
- Review .htaccess or nginx rewrite configuration.
- Check custom post type and page slug conflicts.
- Confirm server rewrite support is enabled.
- Retest key SEO URLs and redirects.
When to ask for help
Ask for technical support if the website is down, revenue is affected, malware is suspected, wp-admin is blocked, checkout is failing, search traffic is at risk or the issue returns after a temporary fix. A specialist can review logs, isolate the cause and repair the site with less risk.
Related service
This guide connects to our Hosting and Server Issues service for hands-on repair.
FAQ
Can I fix this WordPress problem myself?
You can run the basic checks if you have a verified backup and understand the risk. If the site is down, hacked, taking orders or showing PHP/database errors, developer support is safer.
What access is usually needed?
The safest repair usually needs WordPress admin access plus hosting, SFTP, database or log access depending on the error. If wp-admin is blocked, hosting access may be enough to start.
Which service fixes this issue?
This article is related to Hosting and Server Issues, which covers diagnosis, repair, testing and a final report.