At the same time, this update sends a clear signal: technical efficiency is becoming increasingly important for Google<\/strong>. With AI-powered search, rising computing costs, and ever-growing amounts of content, Google has to use its resources more selectively and expects websites to do the same.<\/p>\n In this article, we\u2019ll take a closer look at what exactly has changed<\/strong>, what it means for your website, how to check whether your pages are affected<\/strong> using Seobility, and what you can do to keep your HTML files lean and crawlable<\/strong>.<\/p>\n Until recently, Googlebot would fetch up to 15 MB of HTML content per page<\/strong>. That limit has been significantly reduced: Googlebot now crawls a maximum of 2 MB per file<\/strong>.<\/p>\n In practice, this means that if an HTML file exceeds 2 MB, Google fetches only the first part of the page content<\/strong>. Anything beyond that limit is ignored and therefore not indexed<\/a>.<\/p>\n This restriction doesn\u2019t apply only to HTML files. Other text-based resources, such as CSS and JavaScript files<\/strong>, are subject to the same 2-MB limit, with each file being evaluated individually. The only exception is PDF files, which still have a much higher crawl limit of 64 MB.<\/p>\n Google hasn\u2019t officially announced this change, but it is already documented in the English version of Google\u2019s Search Central documentation<\/a>:<\/p>\n Google hasn\u2019t provided an official explanation. The update was introduced quietly, without any announcement or detailed reasoning.<\/p>\n It\u2019s reasonable to assume that Google is trying to save resources<\/strong>. Crawling, rendering, and processing large files are expensive, and costs continue to rise as the web grows.<\/p>\n At the same time, Google is putting more emphasis on AI-powered search features, such as AI Overviews<\/a><\/strong>. Generating these responses requires processing massive amounts of data efficiently. Lean, well-structured pages make this much easier.<\/p>\n From an SEO standpoint, this change aligns with trends we\u2019ve been seeing for years, such as the introduction of Core Web Vitals<\/a>. Google increasingly rewards websites that are technically clean, efficient, and user-friendly<\/strong>.<\/p>\n Bloated code, unnecessary scripts, and overly complex pages add little value and are becoming less acceptable. A solid technical foundation and clear content are increasingly important.<\/p>\n The new limit applies to all text-based files<\/strong> fetched when a page is loaded. Each file is evaluated separately<\/strong> and has its own 2-MB limit.<\/p>\n HTML files are most affected, as they contain the actual page content: text, headings, internal links, and structured data<\/a>.<\/p>\n If an HTML file exceeds 2 MB, important content toward the end of the page may no longer be seen by Google<\/strong>.<\/p>\n CSS files also fall under the new limit. Large or unoptimized stylesheets can cause Google to retrieve only part of the file. This does not directly affect the content, but it can influence how Google renders<\/a> and understands your page<\/strong>.<\/p>\n Google also crawls JavaScript<\/a> files up to 2 MB. This becomes especially relevant for websites that rely heavily on JavaScript to load content dynamically. When Google cuts off a JS file, parts of the content may never appear for search engines<\/strong>.<\/p>\n (That said, websites should not rely on JavaScript alone to load critical content, a topic we cover in our JavaScript SEO guide<\/a>.)<\/p>\n When an HTML file exceeds the 2-MB limit, Google stops processing the remaining content<\/strong>. As a result, Google may:<\/p>\n If Google can\u2019t fully process a page, it can\u2019t evaluate it properly. This can lead to several issues:<\/p>\n To better understand the real-world impact of this change, we analyzed data from Seobility.<\/p>\n We reviewed the HTML file sizes of around 44.5 million pages<\/strong> crawled with Seobility. The result is clear:<\/p>\n Only 0.82% of all analyzed pages exceed 2 MB.<\/strong><\/p>\n For the vast majority of websites, the new crawl limit is currently not an urgent issue. But if<\/em> one of your pages is affected, you need to take action<\/strong>.<\/p>\n Here\u2019s how HTML file sizes break down across the analyzed pages:<\/p>\n While the numbers are low, this issue doesn\u2019t affect only small or poorly-maintained websites. Even large, well-known platforms with experienced SEO teams can hit the new limit.<\/p>\n In spot checks, we found HTML pages exceeding 2 MB on well-known German sites, including OMR Reviews<\/strong> (approx. 3.4 MB) and Zalando<\/strong> (approx. 2.6 MB).<\/p>\n These examples don\u2019t reflect poor quality. It\u2019s quite the opposite: complex websites with filters, personalization, tracking setups, and dynamic content naturally generate larger HTML files.<\/p>\n These examples show that the new crawl limit is a structural issue, not a beginner\u2019s mistake<\/strong>.<\/p>\n Seobility helps you quickly identify pages with unusually large HTML files.<\/p>\n (If you\u2019re not using Seobility\u2019s Website Audit<\/a> yet, you can test it free for 14 days<\/a>.)<\/p>\n<\/li>\n This gives you a clear overview of your largest HTML pages and shows where action may be needed.<\/p>\n Seobility also provides a dedicated report highlighting pages with unusually large HTML files.<\/p>\n Seobility deliberately uses a threshold of 0.5 MB (500 KB) in this report<\/strong>. This value is well below the current Google limit and is recommended to keep HTML files lean and easily crawlable<\/strong>.<\/p>\n Even if a page is below Google\u2019s 2 MB limit, it may appear in this report as an indicator of optimization potential.<\/p>\n If some of your pages are larger than 2 MB, there\u2019s no need to panic. In most cases, the issue can be resolved with relatively simple optimizations.<\/p>\n Start with the HTML itself, as this is where your actual content lives.<\/p>\n Large HTML files often contain unnecessary or bloated code<\/strong>: elements that exist in the markup but don\u2019t provide real value. Removing this code usually doesn\u2019t affect how the page looks.<\/p>\n Inline CSS and inline JavaScript<\/strong> can also inflate file size quickly. Whenever possible, move this code into external files that Google loads separately.<\/p>\n It\u2019s also worth reducing HTML comments, excessive whitespace, and deeply nested elements<\/strong>. Many modern build tools can handle this automatically.<\/p>\n If you\u2019re using a page builder<\/strong> like Elementor or WPBakery, keep in mind that these tools often generate a lot of extra code. Try to:<\/p>\n CSS and JavaScript files should be minified<\/strong> to reduce their size. Minification removes everything the browser doesn\u2019t need, such as comments and extra spaces.<\/p>\n This can usually be done easily via:<\/p>\n For JavaScript, it may also help to split large files<\/strong> so that only the code required for a specific page is loaded. This is often referred to as code splitting<\/em>.<\/p>\n Finally, review all third-party scripts<\/strong> (analytics, marketing tools, consent banners) and ask yourself whether they\u2019re really needed on every page.<\/p>\n Sometimes the issue lies in the page structure, not the code.<\/p>\n Very long pages<\/strong> with large amounts of content can easily exceed the limit. Splitting content into multiple, well-structured pages often helps.<\/p>\n Infinite scroll<\/strong> requires special care. When pages continuously append content to the HTML, file size grows quickly. Combine infinite scroll with classic pagination<\/a> so Google can access all content reliably.<\/p>\n Regardless of structure, make sure important content appears early in the HTML<\/strong>. That way, it remains visible to Google even if a page approaches the crawl limit.<\/p>\n To ensure the new Google limit does not become an issue for your website over time, it makes sense to follow a few basic best practices. They not only support efficient crawling but also improve performance and user experience.<\/p>\n Even though Google allows up to 2 MB, it\u2019s wise to aim much lower.<\/p>\n A good rule of thumb: Keep HTML files under 500 KB whenever possible.<\/strong><\/p>\n This leaves enough buffer for new content, features, or scripts, and usually improves page speed<\/a> as well, which is an important Google ranking factor.<\/p>\n Large files often grow gradually. New plugins, tracking tools, or design tweaks can slowly bloat your pages over time.<\/p>\nWhat exactly did Google change?<\/h2>\n
![\"Google's](\"https:\/\/www.seobility.net\/wp-content\/uploads\/2026\/02\/google-documentation.png\")
<\/p>\nWhy is Google doing this?<\/h2>\n
Likely reasons<\/h3>\n
SEO perspective<\/h3>\n
Which file types are affected?<\/h2>\n
HTML files (most critical)<\/h3>\n
CSS files<\/h3>\n
JavaScript files<\/h3>\n
What does this mean for your website?<\/h2>\n
\n
Potential SEO impact<\/h3>\n
\n
How many websites does this actually affect? Insights from Seobility data<\/h2>\n
\n
Even large websites can run into this limit<\/h3>\n
How to check with Seobility if your pages are affected<\/h2>\n
\n
![\"Open](\"https:\/\/www.seobility.net\/wp-content\/uploads\/2026\/02\/subpages-tab.png\")
<\/p>\n![\"enable](\"https:\/\/www.seobility.net\/wp-content\/uploads\/2026\/02\/display-filesize-column.png\")
<\/p>\n![\"Sort](\"https:\/\/www.seobility.net\/wp-content\/uploads\/2026\/02\/sort-by-filesize.png\")
\n<\/ol>\nSeobility report: \u201cPages with large file size\u201d<\/h3>\n
![\"Seobility's](\"https:\/\/www.seobility.net\/wp-content\/uploads\/2026\/02\/report-pages-with-large-filesizes.png\")
<\/p>\nWhat should you do if pages exceed 2 MB?<\/h2>\n
Reduce HTML file size<\/h3>\n
\n
Optimize CSS and JavaScript files<\/h3>\n
\n
Rethink structure and content<\/h3>\n
Best practices: how to stay on the safe side<\/h2>\n
Target HTML file sizes<\/h3>\n
Monitor file sizes regularly<\/h3>\n