WordPress 404 errors: three approaches to recover your pages
Fix WordPress 404 errors according to their cause: missing content, broken permalinks, or an old address, with three approaches and no required plugin.
Read the guide →

Site appearance
Fix 404 errors, unexpected redirects and HTTPS problems in WordPress. Check addresses during and after a migration.
9 guides
Fix WordPress 404 errors according to their cause: missing content, broken permalinks, or an old address, with three approaches and no required plugin.
Read the guide →Is the HTTPS certificate invalid for your WordPress domain? Check covered names, www, DNS, and the CDN, then correct the certificate with the right provider.
Read the guide →Find blocked HTTP images, styles, and scripts in WordPress, then fix their source: content, migration, theme, or CDN, with backups and checks.
Read the guide →Does a WordPress restore stop at “Unknown collation”? Compare the servers, then choose a compatible destination or an appropriate export.
Read the guide →Does a WordPress URL expected to return 404 open a post with a similar slug? Distinguish old slugs from native guessing, then check the public response.
Read the guide →WordPress settings disappeared after an SQL replacement? Check a serialized value and repeat the migration on a copy with WP-CLI or a plugin.
Read the guide →Find WordPress links left on the old domain, correct the right fields and test a targeted replacement on a copy before repeating it.
Read the guide →Compare DNS and HTTPS responses for the new domain, identify the old server or redirect, then correct the destination with rollback planned.
Read the guide →Check MX records and the active DNS zone after a WordPress migration, then distinguish incorrect routing from a missing mailbox or alias at the provider.
Read the guide →