Broken After a Change
How to Fix the 403 Forbidden Error in WordPress
Updated
403 Forbidden
What's happening
A 403 Forbidden error means your web server understood the request but refuses to show the page, usually because a security plugin, firewall or permission setting is blocking it. Your content is still there; something is deliberately standing in the way.
You might hit it on your whole site, a single page, or the WordPress login. It's the server's way of saying "I can see what you're asking for, but I'm not allowing it."
Why it happens
A 403 is almost always a permission or security rule getting in the way. Common causes: a security plugin or firewall flagging your request, incorrect file permissions on the server, a bad rule in a behind-the-scenes settings file, or your host's protection reacting to something it thinks looks suspicious. Occasionally it's simply your own address getting temporarily blocked.
What you can safely try
- Note exactly where it happens — the whole site, one page, or the login — which narrows down the cause.
- Check whether it started after installing a security plugin.
- Try from a different network or device in case your address was blocked.
- Don't change file permissions by guesswork — the wrong setting can expose or break the site.
When to call us
The fix is finding the exact rule, plugin, or permission doing the blocking and clearing it — without opening your site up to real threats. That's routine for us. If a 403 is keeping you or your visitors out, send it over and we'll get access restored.
Common questions
- Why can I see some pages but not others?
- A 403 blocks access to one specific thing, so it's common to hit it on a single page, the login screen, or the admin area while the rest of the site loads fine. Where exactly it appears is a strong clue to what's causing it.
- Did I do something wrong?
- Almost certainly not on purpose. A 403 usually comes from a security plugin, firewall rule, or server permission being stricter than intended — not from anything you clicked. It's a configuration issue, and it's fixable.
Related terms
Want this fixed for you?
Emergency WordPress Fixes
From $149, flat rate. You approve the price before we start.
Not an emergency? Get a free audit of your site, done by a person, no obligation.