Bot intelligence record
Google Calendar Importer
Usually allowIdentify Google Calendar fetches used to sync URL-based calendar feeds.
- Operator
- Family
- Type
- Feed
- Source type
- Official
- Last checked
- 2026-05-20
User-Agent Pattern
GoogleGoogle-Calendar-Importer
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 copyUser-agent: Google-Calendar-Importer
Disallow: /
Click the snippet to copy it, or highlight the text manually.
Handling Guidance
NoThis bot is usually safe to allow when the request source is verified and the traffic matches your site policy.
Syncing URL-based calendar feeds into Google Calendar.
Record Details
Structured data- Operator
- Family
- Type
- Feed
- Purpose
- Feed Fetch
- Identity type
- Official Documented
- Confidence
- High
- Last verified
- 2026-05-20
- Last checked
- 2026-05-20
- Source type
- Official
- Verification
- Verify the user-agent with Google user-triggered fetcher documentation, then confirm source identity with Google published IP range objects or reverse DNS when allowing privileged access.
- IP ranges
- https://developers.google.com/crawling/docs/crawlers-fetchers/google-user-triggered-fetchers
- Spoofing risk
- User-agent strings for Google-Calendar-Importer can be spoofed. Treat user-agent detection as a classification signal, then verify with Google documentation, published Google IP range objects, reverse DNS, request path, and feed-sync behavior before allow-listing.
Notes
Google Calendar Importer is used by Google Calendar to sync URL-based calendar feeds.
Identification
Match the Google-Calendar-Importer user-agent in HTTP request logs.
Recommended Handling
Normally allow this if your site publishes ICS or URL-based calendar feeds. User-triggered Google fetchers generally ignore robots.txt because the request is initiated by a user action.
Evidence and Source
- Verify the user-agent with Google user-triggered fetcher documentation, then confirm source identity with Google published IP range objects or reverse DNS when allowing privileged access.
- Match `Google-Calendar-Importer` in HTTP user-agent logs. Expect requests against calendar/feed endpoints rather than full-site crawling.
- Syncing URL-based calendar feeds into Google Calendar.
- User-agent strings for Google-Calendar-Importer can be spoofed. Treat user-agent detection as a classification signal, then verify with Google documentation, published Google IP range objects, reverse DNS, request path, and feed-sync behavior before allow-listing.
https://developers.google.com/crawling/docs/crawlers-fetchers/google-user-triggered-fetchers
Monitor This Bot In Edge
Botcrawl EdgeUse Botcrawl Edge to see matching traffic, create allow or block rules, and control this bot across connected sites.
