Technical SEO

Rendering Budget

Quick Definition

Rendering budget is the practical limit on how much JavaScript-heavy content Google's renderer (Web Rendering Service, based on Chromium) can execute and index per page within a reasonable time.

In context

Even though Google renders JavaScript, doing so is expensive and rate-limited. Pages that depend on heavy client-side execution to expose primary content are at risk of having that content missed during the second-pass render. The mitigation: server-side render or static-generate any content that must be indexed, hydrate progressively, and avoid blocking the initial paint on third-party scripts. Test in Search Console URL Inspection 'View Tested Page' — if your primary content is missing, you have a rendering-budget problem.

Example

A Toronto B2B SaaS moved from full client-side React to Next.js with SSR for marketing pages — Search Console immediately stopped reporting 'crawled but not indexed' on the previously affected URLs.

Have a question this didn't answer?

Book a free 60-minute strategy call. We'll explain how this concept applies to your specific situation.