ubricHelp

What is Googlebot's HTML size limit?

Rubric check: page HTML over Googlebot's 2 MB limit (check id html_oversized)

Googlebot reads the first 2 MB of an HTML file, measured uncompressed. Google indexes only what it downloaded, so text, links and markup after that point are invisible to Google.

Free, no card. Your report opens with this check first.

Why it matters for SEO

Few pages need anywhere near 2 MB of HTML. The pages that pass it are usually stuffed with inline data: a large JSON state object from a JavaScript framework, inline SVG icons, base64 images or a whole style sheet pasted in.

Because the cut is at the end, the content lost is often the bottom of the page: later sections, footer links and structured data placed near the closing body tag.

Does this matter for ChatGPT and AI Overviews?

AI crawlers have their own limits and don't publish all of them. A very heavy page is slow to fetch and parse, so some tools may read only part of it or give up.

Smaller HTML is safer for every crawler, and it makes the page faster for people too.

How Rubric scores it

StandardStandard checks are the baseline every other tier is measured against.

Why this tier: Googlebot stops reading at 2 MB.

It is judged on every page Rubric scores.

Every Rubric score starts at 100. When this check fails, it takes up to 12 points off. Even one failing page costs at least 6 points (half of the most), and the rest comes off as the share of affected pages grows. A warning costs less than a failure.

This check doesn't cap your score. It only takes off its own points.

From the engine's scoring files, scoring 2026-v2.1 (engine d5c591d).

How common it is

Found on 11 of 299 sites where Rubric could judge it (3.7%). That is 10 of 286 judged sites in Rubric's 313-site test set and 1 of 13 sites audited on Rubric between 11 Nov 2026 and 17 Nov 2026 under the current check rules (scoring 2026-11k or later). Measured 17 Nov 2026 with scoring 2026-v2.1.

3.7% of the sites Rubric could judge have this problem. Check yours.

Free, no card. Your report opens with this check first.

How accurate the check is

Lab test: passed. On test pages built with this problem, it caught 2 of 2. On clean test pages, it stayed quiet 1 of 1 times. (Engine build bbcec7c.)

Real sites: people checked 2 of its findings by hand and 0 were wrong (0%). Last checked 14 Nov 2026. That's a small sample, so treat the rate as rough.

Holdout test 5 (sites the check had never seen): 0 of 8 findings judged wrong.

Lab as of 16 Nov 2026; judged findings as of 15 Nov 2026.

How to fix it

WordPress

  1. Check the page size: view source and save the file, or use the Network tab in your browser's developer tools (look at the document's uncompressed size).
  2. Common causes are page builders that inline styles for every element, and plugins that embed large data. Turn on your builder's option to load CSS from a file rather than inline.
  3. Very long pages (huge archives, endless comment threads) can be split with pagination: Settings > Discussion > Break comments into pages.

Shopify

  1. Large collection pages with many products per page and big inline JSON are the usual cause. In the theme editor, lower the number of products per page on the collection template.
  2. In Online Store > Themes > Edit code, look for snippets that print | json data for every product or variant and trim what's printed.
  3. Remove inline SVG sprites or base64 images from theme.liquid and load them as files.

Webflow

  1. Large Collection Lists with many items and rich text can push a page over the limit. Use pagination on the Collection List or lower its item limit.
  2. Replace large inline SVG code in Embed elements with uploaded SVG images.
  3. Publish and re-check the size.

Custom code

Measure the uncompressed HTML:

code
curl -s https://example.com/page | wc -c

Move inline state, SVG sprites and CSS into separate files, load images by URL rather than base64, and paginate very long lists.

More html validity checks · The full AI SEO glossary

Free, no card. Your report opens with this check first.