Website Management
Redirect returns 404 (double slash in rule)
If a URL you’ve redirected returns a 404 instead of redirecting, the rule may contain a double slash. Remove the extra slash and delete any duplicate/old rule, then test again.
Last updated August 5, 2026
If a redirect is set up but visiting the source URL returns a 404, the redirect rule may contain a double slash.
Symptom
- Visiting the source URL of a redirect returns a 404 instead of redirecting.
Cause
- A double slash (//) exists in the redirect rule, which prevents it from matching correctly.
- There may also be an older, conflicting version of the rule still present.
Fix
- Edit the redirect rule.
- Check both the source and destination paths for any accidental double slashes (//) and remove the extra slash.
- If multiple rules target the same source path, delete the outdated or incorrect one so only the corrected rule remains.
- Save your changes and test the source URL again.
After removing the double slash and any duplicate rule, the redirect should work as expected.
