You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cloudflare allows search engine crawlers and bots. If you observe crawl issues or Cloudflare challenges presented to the search engine crawler or bot, [contact Cloudflare support](/support/contacting-cloudflare-support/) with the information you gather when troubleshooting the crawl errors via the methods outlined in this guide.
7
+
Cloudflare allows search engine crawlers and bots. If you observe crawl issues or Cloudflare challenges presented to the search engine crawler or bot, [contact Cloudflare support](/support/contacting-cloudflare-support/) with the information you gather when troubleshooting the crawl errors via the methods outlined in this guide.
11
8
12
9
***
13
10
@@ -38,25 +35,26 @@ Review the following recommendations to prevent crawler errors:
38
35
*[Monitor.Us](http://www.monitor.us/)
39
36
*[Updown](https://updown.io/)
40
37
41
-
* Do not block Google crawler IP addresses via **custom rules** or **IP Access rules** within the **Security** app. If you are using [rate limiting rules](/waf/rate-limiting-rules/), make sure they do not apply to the Google crawler.
38
+
* Do not block Google crawler IP addresses via [custom rules](/waf/custom-rules/) or [IP Access rules](/waf/tools/ip-access-rules/). If you are using [rate limiting rules](/waf/rate-limiting-rules/), make sure they do not apply to the Google crawler.
39
+
40
+
Confirm an IP address belongs to Google by consulting Google’s documentation on [verifying googlebot IP addresses](https://support.google.com/webmasters/bin/answer.py?answer=80553).
42
41
43
-
Confirm an IP address belongs to Google by consulting Google’s documentation on [verifying googlebot IP addresses](https://support.google.com/webmasters/bin/answer.py?answer=80553).
42
+
* Do not block the United States via [custom rules](/waf/custom-rules/) or [IP Access rules](/waf/tools/ip-access-rules/).
44
43
45
-
* Do not block the United States via **custom rules** or **IP Access rules** within the **Security** app.
46
-
* Do not block or User-Agents in your .htaccess, server configuration, [robots.txt](http://support.google.com/webmasters/bin/answer.py?answer=35303), or web application.
44
+
* Do not block Google User-Agents in your `.htaccess` file, server configuration, [`robots.txt`](http://support.google.com/webmasters/bin/answer.py?answer=35303), or web application.
47
45
48
-
Google uses a[variety of User-Agents](https://support.google.com/webmasters/answer/1061943)to crawl your website. You can[test your robots.txt via Google](https://support.google.com/webmasters/answer/6062598?hl=en).
46
+
Google uses a[variety of User-Agents](https://developers.google.com/search/docs/crawling-indexing/overview-google-crawlers)to crawl your website. You can[test your `robots.txt` via Google](https://support.google.com/webmasters/answer/6062598?hl=en).
49
47
50
-
* Do not allow crawling of files in the /cdn-cgi/ directory. This path is used internally by Cloudflare and Google encounters errors when crawling it. Disallow crawls of cdn-cgivia robots.txt:
48
+
* Do not allow crawling of files in the `/cdn-cgi/` directory. This path is used internally by Cloudflare and Google encounters errors when crawling it. Disallow crawls of `cdn-cgi`via `robots.txt`:
51
49
52
50
`Disallow: /cdn-cgi/`
53
51
54
52
:::note
55
53
56
-
Errors for cdn-cgi do not impact site rankings.
54
+
Errors for `cdn-cgi` do not impact site rankings.
57
55
:::
58
56
59
-
* Ensure your [robots.txt file allows the AdSense crawler](http://support.google.com/webmasters/bin/answer.py?hl=en\&answer=1061943).
57
+
* Ensure your [`robots.txt` file allows the AdSense crawler](http://support.google.com/webmasters/bin/answer.py?hl=en\&answer=1061943).
60
58
*[Restore original visitor IP addresses](/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips/) in your server logs.
61
59
62
60
***
@@ -67,15 +65,15 @@ Troubleshooting steps for the most commonly reported crawl errors are mentioned
67
65
68
66
### HTTP 4XX Errors
69
67
70
-
[HTTP 4XX errors](/support/troubleshooting/http-status-codes/4xx-client-error/)are the most common type of crawl error. Cloudflare delivers these errors from your web server to Google. These errors are caused for various reasons such as a missing page on your web server or a malformed link in your HTML. The solution depends upon the problem encountered.
68
+
[HTTP 4XX errors](/support/troubleshooting/http-status-codes/4xx-client-error/)are the most common type of crawl error. Cloudflare delivers these errors from your web server to Google. These errors are caused for various reasons such as a missing page on your web server or a malformed link in your HTML. The solution depends upon the problem encountered.
71
69
72
70
### HTTP 5XX Errors
73
71
74
72
[HTTP 5XX errors](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/) indicate that either Cloudflare or your origin web server experienced an internal error. To correlate occurrences of crawl errors with site outages, monitor your origin web server's health. Monitoring your website health both through Cloudflare and directly to your origin web server IPs determines whether errors occurred due to Cloudflare or your origin web server.
75
73
76
74
### DNS Errors
77
75
78
-
Troubleshooting steps vary depending on whether your domain is on Cloudflare via a Full or CNAME setup. To verify which setup your domain uses, open a terminal and execute the following command (replace`www.example.com`with your Cloudflare domain):
76
+
Troubleshooting steps vary depending on whether your domain is on Cloudflare via a Full or CNAME setup. To verify which setup your domain uses, open a terminal and execute the following command (replace`www.example.com`with your Cloudflare domain):
79
77
80
78
`dig +short SOA``www.example.com`
81
79
@@ -91,20 +89,20 @@ Once you’ve confirmed how your domain was setup with Cloudflare, proceed with
91
89
92
90
**CNAME**
93
91
94
-
Contact your hosting provider to investigate DNS errors and provide the date Google encountered DNS errors. Additionally, review the[Cloudflare System Status](http://www.cloudflare.com/system-status)page for any network outages on the date the errors were encountered by Google.
92
+
Contact your hosting provider to investigate DNS errors and provide the date Google encountered DNS errors. Additionally, review the[Cloudflare System Status](http://www.cloudflare.com/system-status)page for any network outages on the date the errors were encountered by Google.
95
93
96
94
**Full**
97
95
98
-
[Contact Cloudflare support](/support/contacting-cloudflare-support/)and provide the date and time that Google observed the errors.
96
+
[Contact Cloudflare support](/support/contacting-cloudflare-support/)and provide the date and time that Google observed the errors.
99
97
100
98
### Requesting troubleshooting assistance
101
99
102
-
If the above troubleshooting steps do not resolve your crawl errors, follow the steps below to export crawler errors as a .csv file from your Google Webmaster Tools Dashboard. Include this .csv file when[contacting Cloudflare Support](/support/contacting-cloudflare-support/).
100
+
If the above troubleshooting steps do not resolve your crawl errors, follow the steps below to export crawler errors as a `.csv` file from your Google Webmaster Tools Dashboard. Include this `.csv` file when[contacting Cloudflare Support](/support/contacting-cloudflare-support/).
103
101
104
102
1. Log in to your Google Webmaster Tools account and navigate to the **Health** section of the affected domain.
105
103
2. Click **Crawl Errors** in the left hand navigation.
106
-
3. Click **Download** to export the list of errors as a .csv file.
107
-
4. Provide the downloaded .csv file to Cloudflare support.
104
+
3. Click **Download** to export the list of errors as a `.csv` file.
105
+
4. Provide the downloaded `.csv` file to Cloudflare support.
Copy file name to clipboardExpand all lines: src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1010.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ A website owner blocked your request based on your client's web browser.
14
14
15
15
### Resolution
16
16
17
-
Notify the website owner of the blocking. If you cannot determine how to contact the website owner, lookup contact information for the domain via the [Whois database](https://lookup.icann.org/). Site owners disable **Browser****Integrity Check** via the **Settings**tab of the **Security** app.
17
+
Notify the website owner of the blocking. If you cannot determine how to contact the website owner, lookup contact information for the domain via the [Whois database](https://lookup.icann.org/). Site owners can [turn off BrowserIntegrity Check](/waf/tools/browser-integrity-check/#disable-browser-integrity-check) in the Security **Settings**page.
18
18
19
19
:::note
20
20
Since the website owner performed the blocking, Cloudflare support cannot override a customer's security settings.
0 commit comments