Hello,
We apologize for the issue you are facing with the 403 Forbidden error when trying to access your "Blog" link. This error typically means that your website’s server is denying access to the requested page. Here are some common causes and potential solutions:
Common Causes of 403 Forbidden Error:
- Incorrect File Permissions: Ensure that your WordPress files have the correct permissions. For directories, it should be set to 755 or 750, and for files, it should be 644 or 640.
- Corrupt .htaccess File: A corrupt
.htaccess file can lead to this error. You may want to regenerate it by renaming the existing one and then saving your permalink settings in WordPress.
- Plugins or Themes: Sometimes, a plugin or theme may cause conflicts leading to this error. Try deactivating plugins one by one to identify if any of them are causing the issue.
- Banned IP Address: If the IP address of Googlebot is banned on your site, it could result in a 403 error.
- Security Plugins: Security plugins might block access for certain reasons. Check their settings to ensure they are not blocking legitimate requests.
Steps to Fix the Error:
- Reset File Permissions: You can reset file permissions using an FTP client like FileZilla. Connect to your site and set the permissions as mentioned above.
- Check .htaccess File: If you suspect the
.htaccess file is corrupt, you can rename it and regenerate it by going to Settings > Permalinks in your WordPress dashboard.
- Deactivate Plugins: Temporarily deactivate all plugins and check if the issue persists. If it resolves, reactivate them one by one to find the culprit.
For more detailed guidance, you can refer to our article on fixing the 403 Forbidden Error.
If these steps do not resolve the issue, please reply to this ticket, and a human agent from the Rank Math Support team will assist you further.
Thank you for raising this concern!
Sources:
How To Fix Blocked Due to Access Forbidden (403) Error in Google Search Console » Rank Math
Hello,
Thank you for contacting us and sorry for any inconvenience that might have been caused due to that.
Could you please share a screencast of the issue by using a tool like https://loom.com so that we can check this further for you? A visual representation of the issue will help us to understand it better.
Looking forward to helping you.
Thank you.
Hello,
Since we did not hear back from you for 15 days, we are assuming that you found the solution. We are closing this support ticket.
If you still need assistance or any other help, please feel free to open a new support ticket, and we will be more than happy to assist.
Thank you.
