> For the complete documentation index, see [llms.txt](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/docs/sources/source-compliance-google-trends-demand.md).

# Source Compliance: Google Trends Demand

> Implementation-time review completed 2026-05-27. Trend Finder may use this source only as optional metric-only demand enrichment. It is not a normal browser evidence source and must not create source summaries, evidence links, analyst evidence, source diversity, source breakdowns, or public metric chips.

***

## Source Overview

| Field                   | Value                                                   |
| ----------------------- | ------------------------------------------------------- |
| Source ID               | `google-trends-demand`                                  |
| Source name             | Google Trends Demand                                    |
| Primary Apify candidate | `apify/google-trends-scraper`                           |
| Store page              | <https://apify.com/apify/google-trends-scraper>         |
| Verified on             | 2026-05-27                                              |
| Default build/tag       | `latest`, Actor modified `2026-05-26T07:50:39.707Z`     |
| Default run options     | 4096 MB memory, long platform Actor timeout             |
| Pricing observed        | From `$0.30 / 1,000 results` on the Apify Store         |
| Trend Finder status     | Optional opt-in collector, fixture-backed normalization |

The Actor input schema reviewed on 2026-05-27 exposes `searchTerms`, `timeRange`, `geo`, `viewedFrom`, `startUrls`, `spreadsheetId`, `category`, `maxItems`, `customTimeRange`, `maxConcurrency`, `maxRequestRetries`, and `pageLoadTimeoutSecs`. Trend Finder uses only explicit search terms, optional geo/time-range inputs, strict item caps, disabled debug snapshots, single concurrency, and low retry counts.

The reviewed output shape includes one Dataset row per term, with `inputUrlOrTerm`, `searchTerm`, `interestOverTime_timelineData`, `interestOverTime_averages`, regional interest arrays, `relatedQueries_top`, `relatedQueries_rising`, `relatedTopics_top`, and `relatedTopics_rising`. Trend Finder normalizes only the query, optional geo/time range, bounded interest scores, confidence, and short related-query strings.

Live validation note: a one-item run with `searchTerms: ["webscraping"]`, default `timeRange`, `viewedFrom: "us"`, `maxItems: 1`, and a `$0.20` charge cap completed on 2026-05-27 and returned one Dataset row. A narrower `AI agents` / `today 1-m` / `US` sample completed but returned zero rows, so empty live runs remain a non-fatal enrichment warning.

## Terms And Use Boundary

This source collects public Google Trends aggregate demand metrics. Those rows are not canonical evidence links for a topic, so they may influence scoring only as bounded momentum enrichment after a topic match. Apify storage, run IDs, Dataset IDs, Actor input payloads, debug snapshots, and Apify-hosted URLs are not durable browser evidence and must not be emitted to browser payloads.

Approved internal fields:

* Source ID `google-trends-demand`.
* Search query or term.
* Optional geo and time-range labels.
* Normalized demand score from public interest values.
* Normalized growth score from public interest-over-time values.
* Confidence score derived from value coverage and related-query presence.
* Short related-query strings.
* Collection timestamp.

Excluded fields:

* Google Trends URLs, `link` values, topic mids, and related-topic links.
* Debug screenshots, key-value-store URLs, Apify run URLs, Dataset IDs, Actor IDs, request echoes, and Actor input payloads.
* Regional rows as browser evidence.
* Related topics as source evidence or source diversity.
* Raw Google Trends rows, screenshots, HTML, images, cookies, or telemetry.
* Any author, profile, contact, transcript, body, media, or private fields if an Actor output changes unexpectedly.

## Retention And Attribution

| Policy               | Value                                                                                     |
| -------------------- | ----------------------------------------------------------------------------------------- |
| Storage location     | Internal scoring memory only; no browser evidence row is written                          |
| Retention period     | No dedicated long-term retention; aggregate outputs retain only final topic scores        |
| Historical retention | Not supported as source evidence                                                          |
| Deletion path        | Delete generated Trend Finder aggregate data and local snapshots                          |
| Attribution          | Do not display as an evidence source; keep source ID only in internal warnings and traces |

## Runtime Controls

| Env key                                               | Default | Notes                                             |
| ----------------------------------------------------- | ------- | ------------------------------------------------- |
| `FINDTREND_GOOGLE_TRENDS_DEMAND_ENABLED`              | off     | Must be true-like before any Actor run occurs.    |
| `FINDTREND_GOOGLE_TRENDS_DEMAND_TERMS`                | lens    | Comma, semicolon, or newline separated terms.     |
| `FINDTREND_GOOGLE_TRENDS_DEMAND_GEO`                  | unset   | Optional Google Trends geo code.                  |
| `FINDTREND_GOOGLE_TRENDS_DEMAND_VIEWED_FROM`          | `us`    | Residential proxy country hint.                   |
| `FINDTREND_GOOGLE_TRENDS_DEMAND_TIME_RANGE`           | unset   | Uses Actor default unless explicitly set.         |
| `FINDTREND_GOOGLE_TRENDS_DEMAND_MAX_ITEMS`            | `1`     | Clamped to at most 5 terms per run.               |
| `FINDTREND_GOOGLE_TRENDS_DEMAND_MAX_TOTAL_CHARGE_USD` | `0.20`  | Clamped to at most `$1.00`; lower caps may abort. |
| `FINDTREND_GOOGLE_TRENDS_DEMAND_TIMEOUT_SECS`         | `240`   | Clamped between 30 and 900 seconds.               |

## Historical Window Stance

| Field                  | Value                                                                              |
| ---------------------- | ---------------------------------------------------------------------------------- |
| Historical support     | Not a browser evidence source                                                      |
| Source ID              | `google-trends-demand`                                                             |
| Safe override fields   | None for evidence collection                                                       |
| Unsupported reason     | Demand rows are metric enrichment, not reviewed bounded historical evidence items. |
| Compliance declaration | No Trend Finder Apify source declaration is added                                  |

Do not add `google-trends-demand` to the normal Apify source declaration list without a separate source-role/schema change. It must remain metric-only unless Trend Finder gains an explicit internal demand-signal source model.

## Compliance Checklist

* [x] Current Apify Actor ID verified on 2026-05-27
* [x] Input fields reviewed
* [x] Pricing model recorded
* [x] Output shape reviewed and fixture-backed
* [x] Metric-only boundary documented
* [x] Apify storage excluded as durable browser evidence
* [x] Retention and deletion path documented
* [x] Attribution requirements documented
* [x] Historical-window stance recorded as not applicable to evidence
* [x] Live capped validation completed with credentials on 2026-05-27


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/docs/sources/source-compliance-google-trends-demand.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
