Search Console and Bing Webmaster Tools in one place

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.

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.

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 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 checks the keywords you chose.
• Ask your agent: get_search_performance returns the same totals and top rows to a coding agent over MCP.