# Search Console and Bing Webmaster Tools in one place

URL: https://serpel.app/features/search-data

Updated: 2026-10-10

Serpel shows Google Search Console and Bing Webmaster Tools in one place: a single page per project with clicks, impressions, click-through rate and average position, and a switch between Google and Bing. You connect each account once, Serpel matches properties to your projects by domain, and reading the data costs no credits. The same numbers are available in the CLI, the REST API and your coding agent over MCP.

## What the search data view gives you

- **Queries and pages:** Clicks, impressions, click-through rate and average position for every search query and every page.
- **Period comparison:** Choose 7, 28 or 90 days. Totals are compared with the previous period of the same length, and a daily chart shows the trend.
- **Connect once:** Google connects with a read-only sign-in and Bing with an API key. Serpel matches properties to projects by domain.
- **A daily history for Google:** Serpel syncs Google data every day and keeps 16 months of history, so reports read from storage.
- **Quick wins:** Queries on positions 4 to 20 with impressions show where a small improvement pays off first.
- **CLI, API and MCP:** Read the same data with `serpel search queries`, a REST endpoint or the `get_search_performance` tool.

## How do you see Search Console and Bing Webmaster Tools in one place?

Create a project for your domain and connect the accounts that hold its data. Google connects with Google’s own sign-in and gives Serpel read-only access. Bing connects with an API key from Bing Webmaster Tools. Account connections are matched to projects by the domain of the property, so a new project finds its data without further setup.

Each project has one connection per provider, and the Search data page switches between Google and Bing. Stored access keys are encrypted with AES-256-GCM.

| Aspect | Google Search Console | Bing Webmaster Tools |
| --- | --- | --- |
| How you connect | Google’s own sign-in, read-only | An API key from Bing Webmaster Tools |
| What you choose | The matching property | The matching website |
| History in Serpel | Synced daily, kept for 16 months | None, always read live |
| Daily chart | Every day, with empty days filled in | Only days that have data |

## What data does Serpel show?

- **Clicks, impressions, click-through rate and average position** as totals, per search query and per page.
- **7, 28 or 90 days**, compared with the previous period of the same length, plus a daily chart.
- **A tracked marker:** queries that you already track as keywords are marked, and you can add any query to rank tracking from the list.
- **CSV export** of the query list.
- **Analytics next to it:** connect PostHog, Plausible or Google Analytics 4 to see visitors and conversions per landing page.

## How fresh is the data, and how long is it kept?

Both providers deliver data with a delay of two to three days, and Serpel caches results for six hours. The reporting period therefore ends two days before today.

For Google, Serpel also keeps its own daily history. The first sync loads the last 90 days, and every daily sync adds the most recent 3 days. Serpel stores the 5,000 rows with the most impressions per day and keeps them for 16 months. When the stored history covers a period without gaps, reports read from it. Otherwise they ask Google live. Bing data is always read live.

## How do you get Search Console data through an API?

Serpel serves the same data through its REST API, so you can read Search Console and Bing numbers without building your own OAuth flow. One endpoint returns clicks, impressions, CTR and position for either provider.

```bash
curl "https://serpel.app/api/v1/projects/$PROJECT_ID/search-performance?provider=google&dimension=query&days=28&limit=25" \
  -H "Authorization: Bearer $SERPEL_TOKEN"
```

The parameter `provider` is required and is `google` or `bing`. `dimension` is `query` or `page`, `days` is 7, 28 or 90, and `limit` goes up to 500. The token needs the `projects:read` scope. The CLI offers `serpel search queries` with the same options, and `--json` prints the raw response. The [REST API](https://serpel.app/developers/api) page lists the other endpoints.

## What can you do with search data in Serpel?

- **Find quick wins:** queries on positions 4 to 20 with impressions, available as `find_keyword_opportunities` over MCP.
- **Get recommendations:** Serpel combines search data, rankings, crawl results, analytics and your code into prioritised opportunities, such as pages with a low click-through rate for their position.
- **Compare with rank tracking:** search data shows queries you don’t track yet, while [rank tracking](https://serpel.app/features/rank-tracking) checks the keywords you chose.
- **Ask your agent:** `get_search_performance` returns the same totals and top rows to a coding agent over [MCP](https://serpel.app/developers/mcp).

## Frequently asked questions

### Can I connect Google Search Console and Bing Webmaster Tools to the same project?

Yes. Each project can have one Google property and one Bing website. A switch on the Search data page changes between them, and both show the same measures.

### Is Serpel’s access to Search Console read-only?

Yes. Google access uses the read-only Search Console scope, and Serpel only reads data. Every stored access key is encrypted with AES-256-GCM, and you can disconnect a provider at any time.

### Does reading search data use credits?

No. Syncing and reading Search Console and Bing data is free. Credits are only used for live data such as rank checks, AI visibility checks, keyword research and crawls.

### Why is the latest data two or three days old?

Google and Bing deliver search performance data with a delay of two to three days. Serpel ends the reporting period two days before today for that reason, and it caches results for six hours.