Quick answer
A permalink change can affect routing and existing external links. Find whether the page is missing, the slug changed, or the server rewrite is failing before modifying redirects or web-server rules.
Before you start
Record a working URL and failing URL, current permalink pattern, page ID, and the time the problem began. Preserve the current rewrite configuration. Test any repair on staging before applying it to a busy site.
Steps
- Confirm the page is published and that its current slug and parent page are correct. Check the site address and any subdirectory or language prefix.
- Review Settings, Permalinks without choosing a new structure just to troubleshoot. If the existing structure is correct, a deliberate save can refresh rewrite rules, but server configuration still needs to support them.
- Check whether only old URLs fail or all friendly URLs fail. Old URLs may need an approved redirect map; widespread failures can point to rewrite or server configuration.
- Test the intended destination, an old address, a real missing page, and navigation links after a narrow repair. Confirm HTTPS and canonical behavior without introducing loops.
Verify the result
Valid pages should return the intended content, approved old URLs should redirect once to their equivalent destination, and genuinely missing pages should remain meaningful 404s.
Troubleshooting and recovery
Do not paste an unrelated .htaccess file over the site's rules. If a save does not solve the issue, ask support to inspect the exact server and CMS routing with the before-state available.
Related help
- Plan redirects when website page addresses change
- Check WordPress URLs and media after a migration
- Use website error logs to diagnose a failed request
Official references
Reviewed October 31, 2026. Interfaces, vendor availability, and account features can change. Check your current account before making changes.
