---
title: Search Console and Bing
status: current
order: 16
---

# Search Console and Bing

See what people searched on **Google** and **Bing** before they saw your site or clicked it: the top searches and pages, with clicks, impressions, CTR and average position, for the last 28 days. The data comes from **Google Search Console** and **Bing Webmaster Tools**, connected with the site owner's own accounts.

You see it in **Visibility → Search** in your site's dashboard (you connect it in **Settings → Integrations**), your agent sees it with `get_search_queries` ([MCP tools](../mcp/tools.md)), and the API has it at `GET /api/v1/spaces/:space_id/search_queries` ([Management API](../api/management.md#search-queries)).

- **Owners and admins** connect and disconnect. **Everyone on the site** sees the data and can press **Sync now**. Editors and authors see "Ask an owner to connect it".
- After you connect, **you pick the property** (Google) or site (Bing) that is this site. The one with your live URL's domain comes selected, but any of the account's works: a preview domain too. **Change property** on the card switches it later (for example, when the site moves to its own domain); Pluma fetches the data again for the new one.
- Pluma syncs the last 28 days every day, by itself. **Sync now** fetches them again, once every 10 minutes at most.

## Google

1. Your site has to be in [Google Search Console](https://search.google.com/search-console), verified, with the same domain as its live URL. A **domain property** (`sc-domain:example.com`) or a **URL-prefix** one (`https://example.com/`) both work; if you have both, Pluma uses the domain one.
2. In **Settings → Integrations**, press **Connect Google** and sign in with the Google account that has the site.
3. Google asks if Pluma may **view Search Console data for your verified sites**. Allow it. That's read-only: Pluma can't change anything in Search Console.
4. Back in Pluma, pick the property for this site and press **Use this property**. The first sync happens right away.

If the Google card says **Not available yet**, this Pluma server doesn't have Google sign-in set up. Bing works without it.

To disconnect, press **Disconnect** on the Google card. Pluma tells Google to forget the access and deletes the Google data it saved for the site. You can also remove Pluma's access from your [Google Account](https://myaccount.google.com/permissions).

## Bing

1. Your site has to be in [Bing Webmaster Tools](https://www.bing.com/webmasters), verified. If it's already in Google Search Console, Bing can import it in a minute.
2. In Bing Webmaster Tools, open **Settings** (the gear icon) → **API access** → **API key**, and generate a key.
3. In **Settings → Integrations**, paste the key in the Bing card, press **Connect Bing**, and pick the site.

The key reads every site in that Bing account. Pluma only uses it for the site whose domain matches. To stop it, press **Disconnect** (Pluma deletes the key and the Bing data), and you can also generate a new key in Bing to replace it.

Bing updates its numbers once a week and gives them by week, so the Bing view moves in weekly steps.

## What you see

For the engine you pick (Google or Bing, when both are connected):

| Number | What it means |
| --- | --- |
| **Clicks** | Times someone clicked through to your site from the results |
| **Impressions** | Times your site showed up in the results someone saw |
| **CTR** | Clicks per impression |
| **Position** | Your average place in the results, weighted by impressions. 1 is the top |

Then, first, the **keywords**: the top searches (what people typed), up to 50. Searches that name your business are tagged **your name**: those people already knew you. It's the data only Google and Bing have, so it gets the most room.

**Opportunities** lists searches where you show up often (20+ impressions) but not near the top (average position 4 to 20), without your own name. Better content for those is the cheapest way to more clicks.

Last, the **pages that got clicks**. Google leaves out very rare searches to protect people's privacy, so the searches add up to less than the total.

## What isn't here

**No AI data.** Google shows AI Overviews and AI Mode results inside Search Console, and Bing has an AI Performance report for Copilot, but **neither is in their APIs**: only in their own websites. So Pluma can't show which AI answers cited your site, from Google or Bing. What you see here is classic search.

To see how AI assistants find your site, use the other views: [Analytics](analytics.md) counts visitors sent by ChatGPT, Perplexity, Gemini and others, and which AI crawlers read your pages; [AI visibility](ai-visibility.md) checks what assistants need to read your site.

## What Pluma stores

- **The connection:** the engine, the property or site it matches, who connected it and when it last synced. **Google's refresh token and the Bing API key are encrypted** in the database, never shown again, never sent to your agent or the API, and never written to the logs.
- **The search data:** for each day (Google) or week (Bing), each search and each page with its clicks, impressions, CTR and position. No data about the people who searched: Google and Bing only give totals.
- It's kept **13 months**, then deleted every day. Disconnecting an engine deletes its data and its key or token right away; deleting the site deletes everything.
- Pluma uses it **only to show it to the site's team and their agents**: not for ads, not shared, not used to train AI models. See the [privacy policy](https://pluma.so/privacy).
