# search_history

> Returns up to 180 daily site totals plus the exact range of days available. Use it to look at trends day by day.

**Source:** [https://queryhippo.com/docs/tools/search_history](https://queryhippo.com/docs/tools/search_history)

What were my site's daily clicks and impressions over a period?

- Read-only
- No external calls

## When to use it

Returns up to 180 daily site totals plus the exact range of days available. Use it to look at trends day by day.

## Ask your AI

- Show my site's daily clicks and impressions for the last three months.
- What date range of search data do you have for my site?

## Parameters

| Name | Type | Details | What it means |
| --- | --- | --- | --- |
| `propertyId` (required) | `string` | 1–200 characters; pattern ^[a-zA-Z0-9._:-]+$ | The ID of the site to read, as returned by list_sites. You must own the site or have been granted access to it. |
| `start` | `string` | — | Optional first day to include (YYYY-MM-DD). Give it together with end; one without the other returns invalid_input. The range can span at most 180 days. |
| `end` | `string` | — | Optional last day to include (YYYY-MM-DD). Give it together with start; one without the other returns invalid_input. The range can span at most 180 days. |

## What it returns

One row per stored day in the requested range, at most 180 (the latest 180 when you give no dates), with clicks, impressions, average position, clicks from visible queries, and whether the day is complete and finalized. It also gives the first and last stored day and how many days are available, the site's data source, and whether the list was cut at 180 days. Days with no usable data are left out, not shown as zero.

## Notes

- Query data is what Search Console returned for each day, not a complete list of every query.
- Read-only: it reads data QueryHippo has already stored. It does not start a collection, fetch anything or call an AI model.

## Description your AI sees

> Read up to 180 daily site observations and exact available range; query coverage is observed, not exhaustive.

## Full schemas

**Input schema**

```
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "propertyId": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "pattern": "^[a-zA-Z0-9._:-]+$"
    },
    "start": {
      "type": "string"
    },
    "end": {
      "type": "string"
    }
  },
  "required": [
    "propertyId"
  ],
  "additionalProperties": false
}
```