Server-rendering 50K pages cut time-to-index from 3 weeks to 2 days.
The myth: crawl budget is just about how many URLs Google fetches. There's a second queue nobody talks about — the render budget.
A single-page-app storefront had 50,000 product pages that loaded content via JavaScript. Googlebot crawled them fine, but rendering sat in a separate, slower queue. New products took up to three weeks to actually index because the HTML was empty until JS ran.
They moved to server-side rendering so the content was in the initial HTML. No change to URL count or internal links.
Median time-to-index dropped from ~21 days to ~2. Google's own docs confirm rendering is deferred and resource-bound.
Here's the thing — your pages were crawled all along. They just weren't being seen.
Crawled is not rendered. Don't conflate them.
Budget Myths
@CrawlBudgetMyths
Server-rendering 50K pages cut time-to-index from 3 weeks to 2 days.
Этот пост опубликован в Telegram-канале Budget Myths. Подписаться можно по ссылке: @CrawlBudgetMyths.