User-requested fetch

FeedFetcher-Google

Retrieves RSS and Atom feeds for Google services.

See your agent traffic
PurposeUser-requested fetch
HTTP identifierFeedFetcher-Google
IdentityVerify beyond the name

THE SIGNAL

What this visit tells you

A feed request is a subscription retrieval, not an article reader.

Requested URLs
Response codes
Redirect chains

Your next move

Validate the feed response and check whether redirects preserve the subscription URL.

The technical details

Markdown
How to identify it

Look for the FeedFetcher-Google identifier in a request’s User-Agent. This is a name match, not identity verification. Version strings may change.

How to check identity

Use Google’s published IP ranges for this crawler class and its forward-confirmed reverse DNS procedure.

Access and robots.txt

This user-triggered fetcher may ignore robots.txt. Use server access controls for private content.

Seeing 403 or 404 responses?

403 means access was denied; 404 means the resource was not found. Compare the public path, request time, edge security event and origin response to find the cause.

Separate intended restrictions and secret-file probes from pages that should work. A User-Agent name alone does not justify allowing a request.

SourcesReviewed 2026-09-14

Identity and purpose are based on these sources. Analytics interpretation and suggested checks are Apostl guidance.

APOSTL Pulse

See FeedFetcher-Google in context

See their requests. Find the pages that matter.

See your agent traffic