Internal No Response
What This Means
Internal URLs with no response returned from the server. Usually due to a malformed URL, connection timeout, connection error, or connection refused.
What Triggers This Issue
This issue is triggered when an internal URL does not respond with an HTTP response at all. This can be due to a connection timeout, connection error, connection refused or DNS lookup failed.
How To Fix
Malformed URLs often respond with ‘DNS Lookup Failed’ and won’t resolve at all in a browser. They should be updated to the correct location. Other connection issues should be checked in a browser, as they might be due to security identifying the SEO Spider request as a bot. They can often be resolved by using different user-agents (‘Config > User-Agent’), adjusting the crawl speed (‘Config > Speed’), disabling firewalls & proxies or adding your IP address to security platform allowlists. Please read our FAQs on how to approach each of the following common responses: