Welcome to the Q&A Forum

@ghrisa65 said in 403 crawl error:

Hi,

Moz( Also reported by GSC)have reported 403 crawl error on some of my pages. The pages are actually working fine when loaded and no visible issue at all. My web developer told me that some times error issues are reported on a working pages and there is nothing to worry about.
My question is, will the 403 error have bad consequences on my SEO/Page ranking etc.

These are some of the pages that have been reported with 403 error but loading fine:

https://www.medistaff24.co.uk/hourly-home-care-in-evesham/

https://www.medistaff24.co.uk/contact-us/

A 403 crawl error is an HTTP status code that indicates that the web server has understood the request, but it refuses to authorize access to the requested resource. In simpler terms, it means you don't have permission to access the web page or file you're trying to view. This error is often associated with issues like restricted access, authentication problems, or improper permissions on the server. (PMP Exam Prep) (Project Management Professional)

In essence, this error tells you that you're not authorized to view the content you're trying to access. It's like encountering a locked door without the right key. This could be due to various reasons, such as restricted areas, private documents, or the need for a login and password.

If you're encountering a 403 error, here's what you can do:

• Double-Check the URL: Make sure you've entered the correct URL and path.

• Check Permissions: If you're the website owner, ensure that the necessary permissions are set correctly on your server for the file or directory you're trying to access.

• Authentication: If the content requires authentication, make sure you're providing valid credentials.

• Contact the Website: If you're trying to access someone else's website and encountering the error, it could be a server-side issue. Contact the website's administrator to let them know about the problem.

• Check for IP Blocking: If you suspect your IP might be blocked, you can try accessing the website from a different network or using a VPN.

The specific solution will depend on the context and cause of the error. If you're having trouble resolving the issue consult with your hosting provider or a web developer for assistance.

Warm Regards
Rahul Gupta
https://suviditacademy.com/

A "403 Forbidden" error is an HTTP status code that indicates that the server understood the request, but it refuses to authorize it. This typically occurs when a web server recognizes the user's request, but the server refuses to allow access due to lack of proper permissions or other security-related reasons.

In the context of a crawl report, a "403 Forbidden" error could indicate that the crawler (such as a search engine bot or web crawler) is being denied access to certain pages or resources on a website. This could be intentional, as the website owner might want to restrict access to certain parts of their site, or it could be unintentional, caused by misconfigured server settings or security measures.

Here are some common reasons for encountering a "403 Forbidden" error in a crawl report:

Permission Issues: The crawler may not have the necessary permissions to access certain parts of the website. This could be due to misconfigured file or directory permissions on the server.

IP Blocking: The website might have implemented IP blocking or rate limiting to prevent excessive crawling or to block specific IP addresses.

User Agent Restrictions: The website might restrict access to specific user agents (the identification string sent by the crawler), which can prevent certain crawlers from accessing the site.

Login Requirements: Some parts of the website might require user authentication or a valid session to access. If the crawler doesn't provide the necessary credentials, it could be denied access.

Security Measures: The website might have security measures in place that block access from known crawlers or bots to prevent scraping or other malicious activities.

URL Filtering: The server could be configured to deny access to specific URLs or patterns.

CAPTCHA Challenges: Some websites use CAPTCHA challenges to verify that the request is coming from a human user. Crawlers may not be able to solve these challenges.

To address a "403 Forbidden" error in a crawl report, you can take the following steps:

Check Permissions: Ensure that the files and directories being accessed by the crawler have the correct permissions set on the server.

IP Whitelisting: If you are the website owner, consider whitelisting the IP address of the crawler if you want it to have access.

User Agent: If you are the crawler operator, ensure that your crawler uses a legitimate and recognizable user agent. Some websites might block unidentified user agents.

Authentication: If the website requires authentication, provide the necessary credentials in the crawler's requests.

Respect robots.txt: Make sure your crawler follows the rules specified in the website's robots.txt file to avoid accessing restricted areas.

Contact Website Owner: If you are encountering "403 Forbidden" errors on someone else's website, consider reaching out to the website owner to clarify the access restrictions.

Remember to always follow ethical crawling practices and respect website terms of use when crawling or scraping content from the internet.

A "403 creep blunder" commonly alludes to a status code that is returned by a web server when a web crawler or a client is endeavoring to get to a specific page or asset, yet they don't have the important consents to do as such. The HTTP status code "403 Illegal" shows that the server grasped the solicitation, however it will not approve it.

There are a couple of normal purposes behind experiencing a "403 Prohibited" mistake while creeping a site:

Inadequate Authorizations: The web server might require legitimate confirmation or approval to get to specific pages or catalogs. On the off chance that the crawler's certifications are not legitimate or missing, a "403 Prohibited" blunder can happen.

IP Impeding or Rate Restricting: Assuming the server identifies extreme solicitations from a specific IP address in a brief timeframe, it could obstruct that IP address for a brief time or uphold rate restricting to forestall misuse. This can prompt a "403 Illegal" mistake for ensuing solicitations.

Misconfigured Server Authorizations: At times, the server's record or registry consents may be set inaccurately, prompting specific documents or indexes being blocked off. This can set off a "403 Prohibited" mistake while attempting to get to those assets.

Content Limitation: Sites could have specific regions that are intended to be confined to explicit clients or gatherings. On the off chance that the client or crawler doesn't have the important honors, they will get a "403 Illegal" mistake while attempting to get to these areas.

Web Application Firewall (WAF): A few sites use WAFs to safeguard against vindictive exercises. On the off chance that the WAF recognizes the slithering way of behaving as dubious or unapproved, it could obstruct the entrance with a "403 Taboo" mistake.

To investigate and determine a "403 slither mistake," you can attempt the accompanying advances:

Actually look at Consents: Guarantee that the client specialist or crawler you are utilizing has the fitting authorizations to get to the assets on the site.

Survey IP Obstructing and Rate Cutoff points: Assuming that you're being rate-restricted or hindered, you could have to change your creeping conduct or contact the site overseer to whitelist your IP address.

Look at URL and Boundaries: Twofold check that the URLs and any boundaries you are involving in your solicitations are accurately arranged and substantial.

Authentication: Assuming that the site requires validation, ensure you are giving the right qualifications in your solicitations.

Contact Site Chairman: Assuming you accept the issue is on the site's side, contacting the site executive or specialized help could help in settling the issue.

Rememb