meridianlabs/google-trends-scraper
meridianlabs--google-trends-scraperDestructive
This tool calls the Actor "meridianlabs/google-trends-scraper" and retrieves its output results. Actor description: Bulk Google Trends API and pytrends alternative. Each keyword lookup returns interest over time, interest by region, rising related searches and a plain-English summary: rising or falling, year on year, peak, seasonality. $5 per 1,000 keyword lookups; failed lookups are free.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| geo | No | Country code, or country-region code, as used by Google Trends: e.g. US, GB, AU, US-CA, AU-NSW. Leave empty for worldwide. Example values: "US" | |
| category | No | Optional Google Trends category ID to narrow ambiguous keywords (0 = all categories). Example: 71 = Food & Drink. You'll find it after cat= in a Google Trends URL. | |
| keywords | No | Search terms to look up. Each keyword is one keyword lookup ($0.005; failed lookups are free). Duplicates are removed. Optional if you give Google Trends URLs below. Example values: ["halloween costume","air fryer","pickleball"] | |
| waitSecs | No | Max seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget. | |
| timeRange | No | How far back to look. Google picks the data resolution from the range (e.g. daily for 90 days, weekly for 5 years, monthly for 2004 to present). Seasonality and year-on-year change need weekly data spanning more than a year: use Past 5 years. Example values: "past_5_years" | past_12_months |
| searchType | No | Which Google search to measure: web search, YouTube, News, Image search or Google Shopping (the same choice as the search-type menu on trends.google.com). Example values: "web" | web |
| trendsUrls | No | Paste Google Trends explore URLs, e.g. https://trends.google.com/trends/explore?q=air%20fryer&geo=US&date=today%205-y. Each URL keeps its own terms (up to 5 compared), location, time range, category and search type; the settings below don't apply to URLs. | |
| failOnErrors | No | Useful for schedules and monitoring: the run is marked failed (so Apify can alert you) if any keyword errors. Failed keywords are still not charged. | |
| includeRegions | No | Adds interest by region: which countries (worldwide lookups), states/regions (country lookups) or US metro areas search the keyword most, 0–100, highest first. Included in the keyword lookup price. Example values: true | |
| maxConcurrency | No | How many keywords to look up at once. Higher is faster; the price is the same. Example values: 5 | |
| compareKeywords | No | Off: each keyword gets its own 0–100 scale (100 = its own peak). On: keywords are compared in groups of up to 5 (Google's limit) so their numbers are directly comparable. Still charged per keyword. | |
| customTimeRange | No | Only used when Time range is Custom. Format: YYYY-MM-DD YYYY-MM-DD, e.g. 2024-01-01 2025-06-30. | |
| regionResolution | No | Level for interest by region. Google's default: countries for worldwide lookups, states/regions for a country. City-level data is not available (Google withholds it from automated lookups), so for a state such as AU-NSW, where Google defaults to cities, the row comes back partial without regions. Example values: "auto" | auto |
| includeRelatedQueries | No | Adds Google's top and rising related searches ("related queries"), with growth such as +350% or Breakout. Each is flagged with whether it shares a word with your keyword, because Google's rising list sometimes contains unrelated noise. Included in the keyword lookup price. Example values: true |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tip | No | Advisory guidance RAG Web Browser wrote to its key-value store under the reserved "TIP" key | |
| runId | Yes | Actor run ID | |
| stats | No | Run statistics | |
| status | Yes | Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED | |
| actorId | Yes | Stable Apify Actor ID from the run record | |
| summary | Yes | Past-tense summary of the run state | |
| exitCode | No | Actor process exit code; populated for terminal states (especially FAILED) | |
| nextStep | Yes | One primary follow-up action with identifiers interpolated | |
| storages | Yes | Dataset and key-value store metadata, keyed by alias. "default" is always the primary entry. | |
| actorName | No | "username/actor-name" | |
| startedAt | No | ISO timestamp when the run started | |
| finishedAt | No | ISO timestamp when the run finished (terminal states only) | |
| statusMessage | No | Pass-through from Apify run.statusMessage | |
| apifyConsoleUrl | No | Personalized Apify Console link to the run; present only for Console sessions |