# Google Search

**Overview**\
Google Trends tracks the relative search interest of keywords across time. In TickerTrends, this data is normalized on a scale of 0–100, showing the proportion of search activity relative to peak demand. This makes it a powerful signal for consumer interest, cultural relevance, and early indicators of business momentum.

**Historical Length**\
Available from 2004 to present.

**Granularity**\
Weekly data is the default, but depending on the time frame, Google also supports daily granularity for shorter ranges. In TickerTrends, we standardize the feed to ensure consistency for long-term historical tracking.

**Update Frequency**\
Data is updated weekly. Users typically see a roughly one week lag between real-world search activity and TickerTrends availability, although users can contact us if they need less lag times.

**Methodology**\
Google Trends provides indexed scores rather than absolute search counts. We rely on Google Trends normalization techniques and display data they provide. We use linear interpolation to interpolate between weekly datapoints they provide. 

**Example Visualization**

<figure><img src="/files/FE9Lcvw5i58G0HUacCLU" alt=""><figcaption></figcaption></figure>

**Use Cases**

* Identify spikes in consumer demand for a product line before earnings reports.
* Track cultural relevance of a brand compared to competitors.
* Spot seasonal patterns, such as holiday shopping interest or back-to-school trends.
* Gauge early adoption of new product launches by monitoring breakout keyword searches.


---

# Agent Instructions: 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:

```
GET https://docs.tickertrends.io/tickertrends/documentation-v2/2.-data-coverage-and-data-types/2.2-data-types/google-search.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.