How to fix a 403 Error (Part 2)
If everything’s okay with the server headers from your end you want to start looking deeper. 403 errors are also known as connection errors because they are usually the result of a website requiring registration or a log in code to continue into that site. They are most common when a user attempts to access part of a site that the administrator has placed off limits for example, when someone attempts to access a directory rather than a site that is part of that directory, as normal.
403s can also be caused by something as simple as a syntax error with your .htaccess file or file/ directory permission issues at your server. In fact, it’s very likely indeed that the latter is the case.
Statistically speaking, your 403 error is probably not the fault of something going on in your site, it’s much more likely to be an issue with your host. It is however, important to make sure you are not at fault by going through the steps outlined above.
What you need to do at this stage is get in touch with your server and check that everything is in order and there have been no recent changes that could have affected your site in this way. If everything is currently ship-shape at the server and you have followed the above steps then congratulations, your site is fine. You can now turn your attention to getting yourself back into the Google index.
To do this, you need to…
1.Get rid of your current .htaccess file. Just delete it altogether and replace it with one that you are 100% positive is free of any errors.
2.Verify your site on Google Webmaster Tools. If your site is verified already then delete it in Webmaster Tools and then re-verify it.
What if that doesn’t work? Well, then it might be time for a new web host. Change companies and re-verify the site and you should be fine.
Related posts:
