Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting · Explainer

What Causes the 403 Forbidden Error in WordPress (And How to Tell Which One You Have)

Short answer

A 403 Forbidden error means the server understood your request and refused to carry it out. In WordPress, the usual causes are wrong file permissions, a security plugin or firewall rule, a missing user role, or a blocked IP address. Logging in again does not help, because the refusal is about permission, not about who you are.

Key takeaways

  • A 403 means the server understood the request and refused it, so repeating the same request fails the same way.
  • Logging in again does not fix a 403, because the refusal is about permission rather than identity.
  • WordPress files should be 644 and folders 755, and a 777 folder is a security risk rather than a fix.
  • A firewall or security plugin can return a 403 to some visitors only, which is why the error may not appear for you.
  • Google removes indexed URLs that return a 403, so a site-wide 403 can shrink search traffic fast.

What does a 403 Forbidden error mean?

A 403 Forbidden error means the server understood your request and refused to carry it out.

MDN's 403 reference says the status is tied to application logic, such as insufficient permissions to a resource or action. The server is not confused, and it is not down. It has decided the answer is no.

A 403 is a result, not a full diagnosis. The refusal can come from file permissions, a user role, a firewall rule, an IP block, or a missing index file. The rest of this guide shows how to tell which one you have.

How is a 403 different from a 401?

A 401 means you have not proved who you are, while a 403 means the server knows enough and still refuses.

MDN's 403 reference says that for a 403, authenticating or re-authenticating makes no difference. A 401 asks for a login, so signing in can fix it. A 403 can appear after a successful login, which is the clearest sign that the problem is permission, not identity.

Repeating the same request also fails the same way. MDN says clients that receive a 403 should expect that repeating the request without modification will fail with the same error. If a refresh fixes it, the cause was probably a short-lived block or a caching quirk, not a real 403.

The HTTP standard defines the code the same way. RFC 9110 is the document that sets out HTTP semantics, and it describes 403 as a refusal to fulfill a request the server understood.

What do wrong file permissions look like?

Wrong file permissions cause a 403 when the web server user cannot read the file or folder you asked for.

Linux permissions use three numbers for the owner, the group, and everyone else. WordPress.org's permissions guide says all directories should be 755 or 750, and all files should be 644 or 640. The wp-config.php file should be 440 or 400, so other users on the server cannot read it.

Permissions usually break after a migration, a restore, or an upload with the wrong user account. The 403 then appears on specific files, such as images or stylesheets, while the rest of the site works.

WordPress.org warns that no directory should ever be given 777, even upload directories. Start with the standard 644 and 755 values, and only loosen them one step at a time.

What you seeLikely causeHow to confirm
403 on one image or fileFile permissionsCheck the file is 644
403 on a whole folderFolder permissions or no index fileCheck the folder is 755
403 in wp-admin onlyUser roleCheck the user's role
403 for some visitors onlyFirewall or IP ruleTry another network
403 on every pageServer rule or .htaccessAsk the host to check the server log

How do you tell if a security plugin or firewall is blocking you?

A security plugin or firewall returns a 403 when one of its rules matches your request, even if the file itself is fine.

The block often shows a branded page from the security tool, rather than a plain server error. Check the plugin's event log or the firewall log for your IP address and the blocked address.

The log usually names the rule, such as a blocked country, a bad bot score, or a suspicious request pattern.

Try the same page from another network, such as mobile data instead of office Wi-Fi. If it loads there, the block is tied to your IP address or network, not to the page.

WordPress.org's common errors guide recommends deactivating plugins one by one to confirm a plugin conflict, and the same method works for a security plugin.

If Wordfence is the tool blocking you, see our guide to fixing Wordfence blocking your own admin access.

What if only some visitors see the 403?

A 403 that only some visitors see is almost always a firewall, IP, or country rule rather than a broken file.

The server answers each visitor based on where the request comes from. A rule can block one country, one IP range, or one user agent while letting everyone else through.

That is why the site can work fine for you and still return a 403 to a customer or a search crawler.

Check whether the affected visitors share a network, a country, or a VPN. If they do, look for a rule that matches that group in the firewall or security plugin.

If the 403 hits Googlebot, check the firewall log first, since a blocked crawler can quietly remove pages from search results.

What if a logged-in user gets a 403 in wp-admin?

A 403 inside wp-admin usually means the user's role does not allow that page or action.

WordPress has six built-in roles: Super Admin, Administrator, Editor, Author, Contributor, and Subscriber. WordPress.org's roles guide says each role can perform a set of tasks called capabilities, and a Subscriber has just the read capability.

A user with the wrong role sees a 403 when they open a page their role cannot use.

Check the role under Users in the dashboard, and ask an administrator to raise it if the user needs the page. A 403 in the Site Editor can also come from a missing capability.

WordPress.org notes that a user without the needed capability may receive a 403 when the Site Editor calls those endpoints, since WordPress checks capabilities for each REST API request.

How do you tell a 403 from a 404 or a 429?

The three codes answer different questions: a 403 refuses access, a 404 says the page is missing, and a 429 says you asked too often.

MDN's 404 reference says a 404 only means the server cannot find the requested resource, and it does not say whether the absence is temporary or permanent.

A 403, by contrast, confirms the resource exists and refuses it. MDN's 403 reference adds that a server may send a 404 instead of a 403 when it does not want to admit the resource exists.

A 429 is a rate limit, not a refusal. MDN's 429 reference says the client has sent too many requests in a given amount of time, and the response may include a Retry-After header. A 429 clears when you wait, while a 403 stays until the permission or rule changes.

If you are not sure which code you have, open the browser developer tools and read the status code on the Network tab. The code is the first fact to record before you change any setting. Our guide to fixing the 429 error covers the rate-limit case in full.

What does a 403 do to your search rankings?

A 403 can remove pages from search results, because Google treats it like a page that no longer exists.

Google's crawler documentation says Google does not index URLs that return a 4xx status, and it removes already indexed URLs that return one. A 403 on a single page costs that page. A 403 across the whole site can shrink the site's search traffic within days.

The damage is worse when only crawlers see the 403. Visitors load the page fine, so nobody reports a problem, while Google quietly drops the URLs. Check Google Search Console for 403 errors on indexed pages, and fix the firewall rule that blocks the crawler before you request a re-crawl.

What mistakes should you avoid?

The most common mistake is treating a 403 like a login problem and resetting passwords, which changes nothing about the refusal.

  • Do not set folders to 777 to clear a 403, since that opens the files to every user on the server.
  • Do not keep refreshing the page, since a real 403 returns the same answer every time.
  • Do not block whole countries to stop one bad request, since you may block real visitors and crawlers too.
  • Do not edit .htaccess rules you do not understand, since a wrong rule can turn a small 403 into a site-wide one.

Fix the cause first, then confirm the fix. Our guide to fixing the 403 Forbidden error walks through the steps in order.

Frequently asked questions

Why do I get a 403 on my own WordPress site after logging in?

Your user role probably does not include the capability that page needs. Ask an administrator to check your role under Users, or to grant the missing capability. A security plugin can also block your own IP address, so check its event log before you change roles.

Can a 403 error come from a plugin I just installed?

Yes. Security, firewall, and redirect plugins can all return a 403 when a rule matches your request. Deactivate the new plugin and reload the page. If the error clears, check the plugin settings for the rule that fired, then narrow the rule instead of removing the plugin.

Why does Google Search Console show 403 errors when my site works fine?

Your firewall or security plugin may block Googlebot while letting browsers through. Check the firewall log for blocked requests from Googlebot, and add the crawler to the allowlist if your host supports one. Then ask Search Console to validate the fix so the pages can return to the index.

Is a 403 error the same as a site being hacked?

No. A 403 is a permission answer from the server, and most 403s come from ordinary settings such as file permissions, roles, or firewall rules. A hack is possible if the 403 appeared with other signs, such as new admin users or strange redirects. Check your users and recent file changes if you are unsure.

Should I use 777 permissions to fix a 403?

No. Setting a folder to 777 lets every user on the server read, write, and run files in it, which is a security risk. Use 755 for folders and 644 for files instead, and ask your host to fix the file owner if those values still return a 403.

Sources

  1. 403 Forbidden MDN Web Docs
  2. 404 Not Found MDN Web Docs
  3. 429 Too Many Requests MDN Web Docs
  4. Changing File Permissions WordPress.org
  5. Roles and Capabilities WordPress.org
  6. Common WordPress errors WordPress.org
  7. How HTTP Status Codes Affect Google's Crawlers Google Search Central
  8. RFC 9110: HTTP Semantics RFC Editor

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test