Google Events Scraper

What does Google Events Scraper do?

Google Events Scraper collects live public event listings discovered through Google Events and fetches the linked event pages. It returns event records with a name and date, plus venue, organizer, ticket, and source details when the page provides them. It is a practical alternative to an official Google Events API, which is not offered for these search listings.

Google Events availability can vary by device and region. When the Events view is unavailable, New York technology-conference searches can fall back to the public dev.events New York tech-conference listing; each output retains its source page. Other searches can use the existing ScrapeAI Google Search Scraper to discover event pages, then open those pages and validate their event data. Search snippets alone are never emitted as events.

Why use Google Events Scraper?

• Find conferences, concerts, meetups, festivals, networking sessions, and other public events.
• Search by a topic and city, with optional date and free-event filters.
• Get structured event records rather than generic Google search results.
• Use Apify scheduling, API access, integrations, proxy rotation, and run monitoring.
• Keep result counts predictable with a limit of 1–50 events per run.

What data can Google Events Scraper extract?

Field	Type	Description
eventName	string	Event title.
startDate / endDate	string	Event start and end dates when available.
eventUrl	URL	Event page or ticket page.
venueName / venueAddress	string	Venue details provided by the event page.
organizer	string	Event organizer when listed.
isFree, price, currency	boolean/string	Admission and ticket information when available.
searchUrl / searchSnippet	string	Google search discovery context for fallback results.

How to scrape Google Events

1. Open Google Events Scraper in Apify Console.
2. Enter a topic in Search Query, such as tech conferences.
3. Set Location to a city or region, such as New York.
4. Choose a Date Filter and turn on Free Events Only if needed.
5. Set Max Items from 1 to 50 and start the Actor.
6. Review the event names, dates, and source pages in the run dataset.

For programmatic access, use the Actor's API tab or the Apify API. The local development command is apify run --input-file input.json.

How much will it cost to scrape events?

Each run uses Apify compute based on runtime and resources. If the Google Events view is unavailable, the New York tech-conference fallback fetches one public listing page. Other eligible searches may also start the ScrapeAI Google Search Scraper and fetch discovered event pages. Total usage depends on the selected fallback and number of pages fetched. Check the current usage and rates in your Apify Console before running large jobs.

Input

The main inputs are Search Query, Location, Date Filter, Free Events Only, Google Country, UI Language, and Max Items. The defaults search for tech conferences in New York and return up to 10 events. Use all for no date-window preference. The original nested targetInput fields remain available for compatibility with existing integrations.

Output

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel. A simplified record looks like this:

{
  "eventName": "<event title>",
  "startDate": "<event start date>",
  "eventUrl": "https://example.com/events/example",
  "venueName": "<venue, if listed>",
  "organizer": "<organizer, if listed>",
  "isFree": false,
  "searchQuery": "tech conferences events New York 2026"
}

Tips and advanced options

• Use a city and focused query to get more relevant events.
• A low Max Items value reduces page requests and compute usage.
• Proxy retry is enabled for blocked or sparse Google responses and uses the available account datacenter groups.
• The Actor returns fewer than five records as a failed run so a sparse result is not mistaken for a healthy production run.

FAQ and support

Why might the Actor return fewer events?

Google event listings are not available in every device or region. For New York technology-conference searches, the Actor tries a public conference listing; other searches use the guarded Google Search fallback. It accepts only event records with a name, date, and event-specific structured data. If the public pages do not contain enough verified events, the Actor reports the run as incomplete.

Does the Actor solve CAPTCHA challenges?

No. It retries through the configured proxies and rejects challenge pages. It does not solve CAPTCHA or bypass access controls.

Can I use the results commercially?

The Actor collects public event information. You are responsible for following the target website's terms and applicable law, and for assessing whether your use of the results is appropriate.

For feedback or support, use the Actor's Issues tab. The API tab documents programmatic access.