Quick answer: Google says Googlebot currently fetches up to 2MB per URL, including HTTP headers. Content beyond that point is not fetched, rendered, or indexed.
Why this matters
- Oversized HTML can push titles, canonical tags, structured data, or main text past the cutoff.
- Inline Base64 images and large CSS or JavaScript blocks can increase HTML size quickly.
- Most normal pages will never reach 2MB, but bloated templates can.
What Googlebot processes
- The first 2MB is sent to Google's indexing and rendering systems as though it were the complete file.
- External resources have their own per-URL limits and do not count toward the parent HTML size.
- Google's Web Rendering Service executes retrieved JavaScript but cannot process bytes it never received.
Practical SEO checklist
- Keep the initial HTML lean and move heavy CSS and JavaScript into external files.
- Place the title, meta tags, canonical link, key content, and essential structured data early in the document.
- Remove unused code and avoid embedding large images directly inside HTML.
- Check server logs and response times because Google may reduce crawling when a server struggles.
- Test important pages with Search Console URL Inspection.
EEAT check
- Experience: Review actual page weight and server logs, not assumptions.
- Expertise: Let a developer audit templates and JavaScript-heavy pages.
- Authority: Follow Google's documented crawler limits.
- Trust: State test dates and update the article if Google's limit changes.
Source: Google Search Central, “Inside Googlebot: demystifying crawling, fetching, and the bytes we process,” 31 March 2026. This guide explains official documentation in practical terms; indexing is never guaranteed.
Malaysia