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
Copy file name to clipboardExpand all lines: src/content/docs/support/troubleshooting/general-troubleshooting/troubleshooting-crawl-errors.mdx
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -67,23 +67,23 @@ Troubleshooting steps for the most commonly reported crawl errors are mentioned
67
67
68
68
### HTTP 4XX Errors
69
69
70
-
[HTTP 4XX errors](https://developers.cloudflare.com/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.
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.
71
71
72
72
### HTTP 5XX Errors
73
73
74
-
[HTTP 5XX errors](https://support.cloudflare.com/hc/articles/115003011431)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.
74
+
[HTTP 5XX errors](/support/troubleshooting/cloudflare-errors/troubleshooting-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
75
76
76
### DNS Errors
77
77
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](http://www.example.com)* with your Cloudflare domain):
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):
79
79
80
-
`dig +short SOA``_www.example.com_`
80
+
`dig +short SOA``www.example.com`
81
81
82
-
For domains on a CNAME setup, the result response contains cdn.cloudflare.net. For example:
82
+
For domains on a [Partial (CNAME) setup](/dns/zone-setups/partial-setup/), the result response contains cdn.cloudflare.net. For example:
83
83
84
84
`example.com.cdn.cloudflare.net.`
85
85
86
-
For domains on a Full setup, the result response contains the cloudflare.com domain in the nameservers listed. For example:
86
+
For domains on a [Full setup](/dns/zone-setups/full-setup/), the result response contains the `cloudflare.com` domain in the nameservers listed. For example:
0 commit comments