Google-PageRenderer

Link UnfurlerPurpose·Link previewSafety·SafeSEO impact·HighBlocked by·Not yet measuredSnapshot·2026-04

01 /Overview

Google-PageRenderer is a single-page fetcher operated by Google. It fetches one page (or a small set) when triggered by a user action, typically a link being shared on social media, a messaging app, or an RSS reader.

Volume tracks shares and clicks rather than crawl schedules. A trending link can produce a sudden spike, but Google-PageRenderer will not crawl the rest of your site.

Blocking it usually means the link previews on the corresponding platform stop showing your title, image, and description.

See Google-PageRenderer on your own site

02 /Identification

Match the User-Agent header on incoming requests against the pattern below.

regex

Google[-_. /]?PageRenderer

Verify by IP

For higher confidence, also verify the source IP against the operator's published ranges. UA strings can be spoofed; IP ownership is harder to fake.

03 /Control

The polite way is a robots.txt rule. Compliant agents respect it; the others ignore it.

robots.txt

User-agent: Google-PageRenderer Disallow: /

Test a URL

Paste any URL on your site and we'll fetch its robots.txt to check whether Google-PageRenderer is allowed.

04 /Technical fingerprint

Renders JavaScript

IP verification

Published IP ranges

Crawl frequency

Per user action

Honors robots.txt

Yes

Honors Crawl-delay

Varies

05 /Expected behavior

Expect one-off requests triggered by user actions like sharing a link or adding a feed. Volume tracks engagement on the host platform.

The Google bot family

Google runs 103 bots in total. Each one is a separate user-agent so you can allow or block them independently.

Search Engine

DevOps & Monitoring

Ads Network Bot

Training Crawler

Agentic Browser

Security Scanner

SEO Crawler

Brand Intelligence

Shopping Bot

Live-Fetch AI

Ad Verification

AI Coding Tool

Google-Gemini-CLI

Agentic Commerce

Google-AP2-Agent

Common questions

Should I let Google-PageRenderer through?

In most cases, yes. Fetchers power link previews and feed readers. Blocking breaks the user experience on social and messaging platforms. If volume gets noisy, rate-limit it before you block it outright.

Does blocking Google-PageRenderer affect my Google rankings?

No. Google-PageRenderer is not a search-engine crawler. Your ranking on Google or Bing is unaffected by what you do here.

How do I confirm a request is really from Google-PageRenderer?

Two checks. The User-Agent header should match a known Google-PageRenderer string, and the request's source IP should fall inside Google's published ranges. The User-Agent alone is trivially spoofable, so the IP check is what gives you confidence. Google publishes the ranges so you can validate at the CDN or edge.

What breaks if I block Google-PageRenderer?

Link previews, embeds, and unfurls on whatever surface Google-PageRenderer feeds will stop rendering. Users sharing your URLs into Google will see a bare link instead of a rich card. Usually that's the first thing people regret blocking.

How is Google-PageRenderer different from Google's other bots?

Google splits work across multiple user-agents so site owners can decide on each one independently. Training crawlers, live-fetch agents, search indexers, and agentic browsers each get their own name. Worth scanning the rest of the Google family above to see which ones actually matter for your site.

What's the cleanest way to control Google-PageRenderer?

Two layers. Robots.txt for the polite crawlers that read it, and rules at your CDN or edge for the ones that don't. Rankly's Agent Experience handles both from a single config, so you can allow, block, rate-limit, or serve a stripped-down version per bot. Agent Analytics handles the observation half so you know which bots are actually worth a rule.

References

Verify everything above against the operator's own documentation.

Agent Directory See all bots