Crawl & Render
Crawl & Render
@CrawlAndRender

URL Inspection live render vs. Rich Results Test

Both show "Googlebot's rendered HTML," but they're not interchangeable. Compared output on 64 JS pages.

— Both use evergreen Chromium render ▓▓▓▓▓▓▓▓▓▓
— Rich Results Test: no auth, public URLs only ▓▓▓▓▓░░░░░
— URL Inspection live: respects your property, shows resource-load failures, 6.4% caught blocked JS the RRT missed ▓▓▓▓▓▓▓▓░░

So what: Rich Results Test is the fast, shareable check for schema and basic render on public pages. URL Inspection's live test is the diagnostic one — it surfaces which specific resources Googlebot failed to fetch (the real cause of empty renders). Use RRT to confirm structured data; use Inspection to debug why a render came back blank. Different jobs, same engine.
This post was published in the Telegram channel Crawl & Render. Subscribe here: @CrawlAndRender.
tech

Latest posts in “Tools and infrastructure”

All channels in this category →

start

Готовы запустить рекламу через сеть public.tg?

Новый оффер, продукт, GEO, кейс, событие или партнёрский запуск — соберём маршрут под задачу и отдадим медиаплан.

Telegram для медиаплана: @AFFtop_connect. Быстрый тест: $20 за канал, $1000 за пакет по сети.