Bot intelligence record

Google Feed Fetcher

Usually allow

Use the google.com/feedfetcher identifier to separate Google feed fetching or subscription-style retrieval from normal visitor requests in server logs.

Feed Feed Fetch Verified Bot Confidence: Medium Verified: Yes robots.txt: No
Operator
Google
Family
Google
Type
Feed
Source type
Verified Directory
Last checked
2026-05-20

User-Agent Pattern

Google
google.com/feedfetcher
Verification note

User-agent strings are identification signals, not proof of identity. Confirm important allow, block, or rate-limit decisions with logs, DNS or IP evidence, request behavior, or operator documentation when available.

Robots.txt Snippet

Click snippet to copy
User-agent: google.com/feedfetcher Disallow: /

Click the snippet to copy it, or highlight the text manually.

Handling Guidance

Depends

This bot is usually safe to allow when the request source is verified and the traffic matches your site policy.

Feed fetching, subscription updates, podcast retrieval, or content syndication checks.

Record Details

Structured data
Operator
Google
Family
Google
Type
Feed
Purpose
Feed Fetch
Identity type
Verified Bot
Confidence
Medium
Last verified
2026-04-30
Last checked
2026-05-20
Source type
Verified Directory
Verification
Validate the identifying user-agent or signature against the operator documentation before creating hard allow rules.
Spoofing risk
User-agent strings can be spoofed. For allow-listing or low-friction rules, pair the published identifier with operator documentation or cryptographic verification when available.

Notes

Google Feed Fetcher is listed in the Botcrawl directory as a feed retrieval bot from Google. The primary identifier for log review is google.com/feedfetcher.

Identification

  • User-agent pattern: google.com/feedfetcher
  • Family: Google
  • Type: Feed
  • Kind: Fetcher

Common use

Feed fetching, subscription updates, podcast retrieval, or content syndication checks.

Verification and handling

Confirm the user-agent against server logs and use published operator documentation, IP ranges, reverse DNS, or other trust signals when available.

Directory guidance marks the risk level as Safe and the blocking decision as Depends. Do not rely on the user-agent string alone because user-agent strings can be copied or spoofed.

Robots.txt handling: No.

Evidence and Source

  • Validate the identifying user-agent or signature against the operator documentation before creating hard allow rules.
  • Match `google.com/feedfetcher` as a case-insensitive substring in HTTP user-agent logs. Use bot_http_agent for full user-agent examples when the client sends a longer browser-like string. Do not treat a user-agent match alone as proof of identity for allow-listing.
  • Feed fetching, subscription updates, podcast retrieval, or content syndication checks.
  • User-agent strings can be spoofed. For allow-listing or low-friction rules, pair the published identifier with operator documentation or cryptographic verification when available.

Monitor This Bot In Edge

Botcrawl Edge

Use Botcrawl Edge to see matching traffic, create allow or block rules, and control this bot across connected sites.