If an important answer sits beyond Googlebot's HTML fetch limit, inspect the size and order of the document response. A page can appear complete in your browser while the part containing the answer falls outside the fetched portion. Start with the returned HTML, rather than the combined weight of every resource.

As checked on October 30, 2026, Google's current explanation gives Googlebot a 2 MB limit per non-PDF URL, including response headers. The fetched portion goes forward for processing; the unfetched remainder does not. Referenced resources are fetched separately. This is specific guidance about Googlebot, not a universal limit for AI crawlers.

Most teams will never encounter this boundary. For a genuinely oversized document, however, the useful diagnosis is where the essential answer appears and what pushed it there.

Is the HTML response actually the large resource?

Consider a fictional public documentation page for a booking system.…