Warum es zählt
Googlebot fetches only the first 2MB of an HTML URL, HTTP headers included: bytes past that cutoff are not fetched, rendered or indexed. Google warns that bloated inline base64 images, large blocks of inline CSS or JavaScript and megabytes of menus can push a page's text or structured data past the limit, a real risk for single-page apps that inline large hydration state. Scripts, stylesheets and API responses the page loads each have their own limit.
So setzen Sie es um
Move base64 images, large inline scripts and styles and serialised application state (hydration JSON) to external files or endpoints, keep navigation markup compact, and place the meta tags, title, canonical, hreflang and essential JSON-LD high in the head, with the main content before long secondary blocks.
So prüfen Sie es
For every template, curl -s <url> | wc -c stays under about 1.5 MB, and the main heading and the JSON-LD appear within the first 2 MB of the response (curl -s <url> | head -c 2000000 | grep -c 'application/ld+json').
So deckt Regensbot sie ab
Entschieden aus einer URL.
Ein Audit liest die Antwort, die Header, das HTML, robots.txt, die Sitemaps und die Structured Data, und der Befund zeigt, was es gesehen hat.
Quellen
Google-Dokumente02
- 01Inside Googlebot: demystifying crawling, fetching, and the bytes we processSearch Central blog (31 March 2026) (öffnet in einem neuen Tab)
- 02Overview of Google crawlers and fetchers (user agents)Google (öffnet in einem neuen Tab)
Aussagen in der Wissensbasis02
- D1-C136QuelleHow crawling worksGoogles Dokumentation
- D1-C137QuelleHow crawling worksGoogles Dokumentation
Die Aussage-IDs verweisen auf die Wissensbasis zu Search Central Live 2026. Die Wissensbasis (öffnet in einem neuen Tab)
- Quelle
- Die Aussage ist das zitierte Dokument selbst.