Google Events Scraper

Search Google Events using the same values a visitor would enter on the site: event keywords, location, and date filter. The Actor supports one query or a deduplicated list of queries and enforces one global maxItems limit.

What it returns

Records use a stable schema with event identity, rank, title, displayed and ISO dates when available, venue and address, coordinates, organizer, performers, price, ticket and event links, images, search context, extraction method, and timestamps. Optional fields are omitted when Google does not expose them; the Actor does not fill missing facts with null, empty strings, or guessed values.

Extraction uses only the requested Google Events page:

• Current Google Events result cards are the primary source.
• Event JSON-LD embedded directly in that same Google page may enrich a matching record.
• No third-party search engine or unrelated indexed snippet is used as fallback data.

Inputs

Field	Purpose	Default
query	Primary event search	tech conferences
queries	Additional event searches	[]
location	City, region, or country	New York
dateFilter	any, today, tomorrow, weekend, week, next_week, or month	any
searchMode	auto, dedicated events, or ordinary Google web Events pack	auto
maxItems	Global maximum unique records	50
maxPages	Load/scroll cycles per query	3
gl, hl	Google country and language	us, en
maxConcurrency	Parallel searches	2
maxRequestRetries	Bounded temporary-failure retries	2
proxyConfiguration	Apify or user-provided proxy configuration	Residential

Example:

{
  "query": "concerts",
  "queries": ["music festivals", "jazz shows"],
  "location": "New York",
  "dateFilter": "weekend",
  "searchMode": "auto",
  "maxItems": 30,
  "maxConcurrency": 2,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"]
  }
}

Reliability and blocking

Browser fingerprints use a country/language-consistent desktop profile. When Residential proxy is selected without a country, the country is aligned with gl. Sessions are short-lived and temporary network failures receive bounded retries.

Explicit CAPTCHA and unusual-traffic pages are classified as TARGET_BLOCKED, are not retried, and are never stored as dataset records. Unsupported-browser/location pages, selector drift, and true no-result pages are distinguished from each other. The Actor does not solve or bypass interactive challenges.

Local development

npm ci
npm test
apify run

The checked-in INPUT.json disables proxy usage for a reproducible local diagnostic. Use the input schema's Residential proxy default for Apify Cloud runs.