Google Events Scraper
Pricing
Pay per event
Google Events Scraper
📅 Extract Google Events search results into structured event records with titles, dates, venues, locations, source links, and ticket URLs.
Pricing
Pay per event
Rating
0.0
(0)
Developer
Stas Persiianenko
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
13 hours ago
Last modified
Categories
Share
Extract structured event records from Google Events search results for local marketing, SEO research, event discovery, and competitor intelligence.
What does Google Events Scraper do?
Google Events Scraper searches Google Events for one or more queries and saves normalized event records to an Apify dataset.
It is designed for searches such as:
tech events in Austin this weekconcerts in Berlin this weekendmarketing conferences in New Yorkfamily events near Seattle this month
The actor focuses on event cards, not generic Google organic results.
Who is it for?
Local marketers use it to monitor events in target cities.
Event aggregators use it to seed calendars and newsletters.
SEO teams use it to discover event-rich-result competitors.
Venue teams use it to watch similar venues and nearby events.
Agencies use it to collect leads for sponsors, partnerships, and outreach.
Why use this actor?
Google Events combines many event sources into one rich-results experience.
Instead of scraping dozens of event websites separately, you can start with the events Google already surfaces for a query.
The actor returns consistent fields that are easier to export, filter, enrich, and send to downstream tools.
What data can you extract?
| Field | Description |
|---|---|
| query | Search query that produced the event |
| position | Event rank within the query |
| title | Event title |
| dateText | Date or date range displayed by Google |
| startDate | Parsed ISO date when possible |
| timeText | Displayed event time |
| venueName | Venue or host candidate |
| locationText | Location/address text |
| city | Parsed city when obvious |
| description | Short snippet when visible |
| eventUrl | Source event URL when exposed |
| ticketUrl | Ticket/register/RSVP URL when detected |
| imageUrl | Event image when present |
| isOnline | Online/virtual event signal |
| scrapedAt | Extraction timestamp |
How much does it cost to scrape Google Events?
The actor uses pay-per-event pricing.
You pay a small run-start fee plus a per-event charge for records saved to the dataset.
Use low maxEventsPerQuery values while testing new searches.
Google SERP proxy traffic is expensive, so the actor avoids blind retries on block pages.
How to use Google Events Scraper
- Open the actor on Apify.
- Add one or more Google Events queries.
- Choose a date range.
- Set a small maximum events per query for a first run.
- Start the actor.
- Export results from the dataset as JSON, CSV, Excel, XML, or RSS.
Input options
queries is required.
Include the target city or region inside each query.
maxEventsPerQuery controls cost and output volume.
dateRange applies Google Events date chips.
country controls Google localization and proxy country.
language controls result language.
includeTicketLinks enables ticket/register link classification.
Example input
{"queries": ["tech events in Austin this week"],"maxEventsPerQuery": 10,"dateRange": "week","country": "us","language": "en","includeTicketLinks": true}
Example output
{"query": "tech events in Austin this week","position": 1,"title": "Austin tech meetup","dateText": "Thu, Jun 20","startDate": null,"timeText": "6:00 PM","venueName": "Downtown Austin","locationText": "Austin, TX","eventUrl": "https://example.com/event","ticketUrl": "https://example.com/register","scrapedAt": "2026-06-18T18:00:00.000Z"}
Tips for better results
Use specific city names.
Add event category words such as conference, concert, meetup, festival, workshop, or webinar.
Use weekend for entertainment searches.
Use month for conference and trade-show searches.
Run several focused queries instead of one broad query.
Start with 10 events per query, then scale after reviewing output.
Handling Google blocks
Google can show CAPTCHA, consent, or anti-bot pages.
When that happens, the actor logs a warning and skips the blocked query.
This protects your run from retry loops and unnecessary proxy spend.
If a query returns no data, try a more specific location or a different date range.
Integrations
Send event data to Google Sheets for editorial planning.
Send event data to Airtable for calendar workflows.
Use Zapier or Make to trigger outreach campaigns.
Use the Apify API to refresh event feeds daily.
Use dataset webhooks to update dashboards.
Join event results with venue enrichment actors.
API usage with Node.js
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: process.env.APIFY_TOKEN });const run = await client.actor('automation-lab/google-events-scraper').call({queries: ['concerts in Austin this weekend'],maxEventsPerQuery: 10,dateRange: 'weekend',country: 'us',language: 'en'});console.log(run.defaultDatasetId);
API usage with Python
from apify_client import ApifyClientclient = ApifyClient('MY_APIFY_TOKEN')run = client.actor('automation-lab/google-events-scraper').call(run_input={'queries': ['marketing events in New York this month'],'maxEventsPerQuery': 10,'dateRange': 'month','country': 'us','language': 'en',})print(run['defaultDatasetId'])
API usage with cURL
curl -X POST 'https://api.apify.com/v2/acts/automation-lab~google-events-scraper/runs?token=MY_APIFY_TOKEN' \-H 'Content-Type: application/json' \-d '{"queries":["startup events in San Francisco this week"],"maxEventsPerQuery":10,"dateRange":"week","country":"us","language":"en"}'
MCP usage
Use this actor from MCP-compatible AI tools through Apify MCP Server.
MCP URL:
https://mcp.apify.com/?tools=automation-lab/google-events-scraper
Claude Code setup:
$claude mcp add apify-google-events "https://mcp.apify.com/?tools=automation-lab/google-events-scraper"
Claude Desktop JSON configuration:
{"mcpServers": {"apify-google-events": {"url": "https://mcp.apify.com/?tools=automation-lab/google-events-scraper"}}}
Example prompt:
MCP usage: use the Apify Google Events Scraper MCP tool to find tech events in Austin this week and summarize the top venues.
Example Claude Desktop prompt:
Use Google Events Scraper to collect marketing conferences in New York this month, then group them by date.
Example MCP automation prompt:
MCP usage: run automation-lab/google-events-scraper for concerts in Berlin this weekend, export the dataset, and highlight ticket links.
Common workflows
Build a weekly local events newsletter.
Monitor competitor venues.
Find sponsorship opportunities.
Track event SEO visibility.
Create city-specific content calendars.
Discover conferences for sales teams.
Collect event leads for enrichment.
Data quality notes
Google changes markup frequently.
Some fields may be null when Google does not expose them in the visible event card.
dateText is the safest date field because it preserves Google's display text.
startDate is best-effort parsing and should be reviewed before calendar automation.
Legality
This actor extracts publicly visible search-result information.
Respect Google terms, website terms, privacy rules, and applicable laws.
Do not use the output for spam or prohibited profiling.
Only collect and process data you have a lawful basis to use.
FAQ
Is this a Google Events API?
It is an Apify actor that extracts event-like records from Google Events/search result pages. It does not require a separate Google API key.
Why are some fields null?
Google does not expose every date, venue, ticket link, or image in every result. The actor preserves visible values and leaves unavailable fields as null.
Troubleshooting: no events returned
Try a more specific query.
Include a city or region.
Change the date range.
Lower the maximum events while testing.
Check the run log for Google block or consent warnings.
Troubleshooting: missing ticket links
Google may not expose ticket links for every event card.
Enable includeTicketLinks.
Check eventUrl, because the ticket flow may be on the source page.
Run venue/source enrichment after export if you need guaranteed purchase URLs.
Related scrapers
Use https://apify.com/automation-lab/google-search-scraper for organic Google results.
Use https://apify.com/automation-lab/google-maps-scraper for local business discovery.
Use https://apify.com/automation-lab/eventbrite-scraper for Eventbrite listings.
Use https://apify.com/automation-lab/meetup-scraper for Meetup events.
Use https://apify.com/automation-lab/allevents-scraper for AllEvents listings.
Limitations
The actor does not guarantee every event available on Google.
It does not log in to Google.
It does not bypass CAPTCHA pages.
It does not scrape full event detail pages in the MVP.
It extracts what is visible in the event-rich-result page.
Changelog
Initial version extracts Google Events cards by query, date range, country, and language.
Support
If a run fails, include the run ID and input when reporting the issue.
Small reproducible inputs are easiest to debug.
Output exports
Apify datasets can be exported as JSON.
Apify datasets can be exported as CSV.
Apify datasets can be exported as Excel.
Apify datasets can be exported as XML.
Apify datasets can be exported as RSS.
Performance guidance
Use focused queries.
Keep first runs small.
Avoid hundreds of broad searches in one run.
Review block warnings before scaling.
Event query examples
jazz concerts in Chicago this weekend
startup pitch events in London this month
family events in Denver today
AI conferences in San Francisco this month
food festivals near Austin this weekend