Why an analysis fails
When a page cannot be analysed, the reason falls into one of five categories. These are the categories the system genuinely uses, so knowing which one you hit tells you exactly where to look.
Timeout
The page did not become readable in time. There are two separate limits: the page has 60 seconds to respond at all, and its body has to be present within 5 seconds of that response.
The second limit catches far more pages than the first. Sites that render everything in the browser often send an almost empty document first and fill it in later. That is the most common real failure we see.
Serve your main content in the initial HTML response rather than building it with JavaScript after load. This also helps with real AI crawlers, most of which do not run JavaScript at all.
Unreachable
The connection itself failed. This covers DNS problems, refused connections, and certificate errors.
Open the exact URL in a private browser window. Check the certificate is valid and not expired, and that the domain resolves without a www or non-www redirect loop.
Crashed
The browser session ended before the page finished loading. This usually points at an extremely heavy page rather than at anything you configured wrongly.
Try a lighter page on the same domain. If that works, the problem is page weight, not the site.
Extraction failed
The page loaded, but we could not read its metadata. Unusual content security policies and malformed markup are the usual causes.
Run the page through an HTML validator. Broken or unclosed tags in the head section are a frequent cause.
Unknown
Something failed that does not match any known pattern.
Email support@geo-score.online with the URL and the time you ran it. The full technical error is kept in our logs even though it is not shown to you, so we can look it up.