SEOscanner.app

Rule · HTTP and hosting

HTML stays within Googlebot's 2 MB fetch limit

SEO-HTTP-09C1 Mechanism· w8

Class
C1 Mechanism
Weight
8
Severity on fail
critical
Applies to
Google

Scope and evidence

Evaluated on page (P). The book marks this requirement SEARCH-ENGINE-SPECIFIC, SUPPORTED (documented limit).

{beyond_clause} lists head elements found beyond the limit, for example " The canonical link starts at byte 2,140,512, beyond the limit." Equivalent Bing limits were not established from reviewed Bing sources. Referenced CSS and JavaScript are fetched separately, each under the same limit.

Fail conditions

Each condition has a stable code and a reason template. The evaluator fills the placeholders from observed values only; no sentence in a report is generated.

  • over_limit

    The HTML of {url} is {bytes} bytes uncompressed. Googlebot crawls the first 2MB of a supported file type, measured on uncompressed data, so content after that point is not crawled.{beyond_clause}

The documented fix

Move large inline payloads (serialized application state, inline SVG sprites, base64 images, repeated JSON-LD) into separate files or after the primary content; paginate very long lists.

Sources, quoted

These are the passages the rule rests on, stored once in the knowledge base and emitted exactly as written. A citation marked for specific conditions appears only on findings with those codes.