Google Search Console Search impressions, clicks, and queries in Google
Google Search Console Google Search Console in your report Google Search Console client report
Reportkey reads search analytics for a property from the Google Search Console API and turns them into a client report section: impressions, clicks, CTR and average position compared with the previous period, plus top queries and landing pages.
Sign up, sign in with your Google account and pick a Search Console property. Your first report is ready in 5 minutes.
- A Google account is connected once and reused in every project.
- Impressions, clicks, CTR and average position compared with the previous period.
- Google organic, GA4 and rankings in one report, as a link or PDF.
TL;DR
Reportkey connects Google Search Console through a Google sign-in with access to the property, either a Domain or a URL-prefix property, and shows impressions, clicks, CTR and average position compared with the previous period, plus top queries and landing pages. Google organic data sits next to GA4, rankings and ads, and the report goes out as a link or PDF.
Search Console client report without building dashboards
Google Search Console shows how a site performs in Google before anyone lands on it: how often pages appeared in results, how many clicks they earned and for which queries. For many sites Google is a meaningful share of organic traffic, and agencies want these numbers in the monthly report. Usually they are copied by hand or put into a separate dashboard for each client.
Reportkey does it for you. It reads the property’s search analytics through the official Search Console API and builds a section of a recurring report. The same document can hold GA4 sessions and conversions after the click, tracker rankings and ads. The SEO agency demo report shows what it looks like.
Connecting: a Google account and property access
You start in the integrations section of the dashboard and sign in via Google OAuth with an account that has access to the Search Console property, granting read-only permission. The connected account is stored globally, so any project can use it without signing in again.
In project settings you then pick the property from the list the API returns for that account. Search Console has two property types: a Domain property covering the whole domain with all subdomains and protocols, and a URL-prefix property such as the https version only. Both work, so choose the one the client is used to. If a property is missing, check on the Google side that the account is added to it as an owner or user.
If Google stops accepting the sign-in, for example after access is revoked, the connection is marked for re-authentication. You renew it on the integrations page, and the property selected in the project stays in place.
Impressions, clicks, CTR and average position in Google
The block opens with a period summary compared with the previous range:
Impressions. How many times a link to the site appeared in Google results. It shows whether the site’s presence grows even while clicks are still low.
Clicks. Visits from the results to the site, the figure clients understand best.
CTR. The share of impressions that turned into clicks. A falling CTR with stable impressions suggests weaker snippets or stronger competitors on the results page.
Average position. The site’s averaged place across all impressions. It is not the position of a specific keyword, so do not compare it directly with a tracker table.
Top queries and landing pages
The second half of the value is detail. The query table shows the phrases Google really shows the site for, and the landing page table shows which sections collect clicks. For an agency that is input for the work plan: which pages lose clicks and which topics grow on their own. For an in-house team it answers which sections bring search traffic.
Why query rows don’t add up to the total
This API behaviour confuses clients and specialists alike. Google does not reveal some rare queries, which are anonymized for user privacy, and query and page breakdowns are limited to a number of top rows. Add up the clicks in the query table and you get less than the period total. The report therefore takes the total separately and labels the table as top queries.
Latency matters too. Google publishes data after roughly two to three days, and the last days of a period may fill in later, so closed periods suit recurring reports best. Search Console also counts days in Pacific Time, so day boundaries differ slightly from analytics tools set to Moscow time.
Search Console or a Looker Studio dashboard
The most common way to show Search Console to a client is Google’s free connector in Looker Studio. It works, but every client needs a dashboard that is built, labelled, filtered and maintained. In Reportkey the report template is shared: connect the property in a project and the Google organic block is built along with the other channels. Reports can be built on demand or sent on a schedule; scheduled delivery, AI insights and white-label branding are not on every plan.
Search Console next to Yandex Webmaster, GA4 and trackers
Search Console covers Google, and for Yandex similar data comes from the Yandex Webmaster report. Rankings for a fixed keyword list can come from SE Ranking or Topvisor projects. After the click, web analytics takes over: Search Console clicks and GA4 sessions follow different rules and do not have to match, so the report shows them together and explains the gap.
- Sign up for Reportkey – 14 days free.
- Connect your Google account in the integrations section and pick the property in project settings.
- Add GA4 and a rank tracker, then set up delivery to the client.
All search sources are listed on the SEO integrations and rank trackers page, and prices are on the pricing page.
Metrics
What goes into the Google Search Console report
These are the metrics that the Google Search Console integration already brings into Reportkey reports.
Impressions
Clicks
CTR
Average position
Search queries
Landing pages
What this integration adds to the report
Search impressions, clicks, and queries in Google
Pricing
Google Search Console reporting: plans and free trial
14 days free, no card required. Prices and plan limits are on the pricing page.
Use cases
Why teams connect Google Search Console to Reportkey
Real reporting jobs, typical pain points, and the outcomes teams get from Google Search Console in client reports.
Pain points
- The Search Console Performance report is awkward to show a client: tabs, filters and exports instead of a short monthly summary.
- A Looker Studio dashboard has to be built for every client and then watched so it does not break.
- Google organic data lives apart from Yandex, analytics and ads, so it is hard to show the whole search picture on a call.
Google Search Console
SEO agency whose clients get noticeable Google traffic
Each project pulls data from its own Search Console property. The report puts Google impressions and clicks next to tracker rankings and GA4 sessions, using one template for every client, so nobody builds dashboards by hand.
Google Search Console
Freelancer with several sites
One Google account with access to the client properties is connected once. Each project picks its property, and the client gets a Google Search summary without Search Console access.
Google Search Console
In-house SEO specialist
Management wants a Google Search summary without logging in to Search Console: did impressions and clicks grow against the previous period, and which sections draw the traffic.
Report preview
How Google Search Console appears inside the report
The report keeps the familiar Reportkey layout: source sections and period comparison.
Summary of impressions, clicks, CTR and average position in Google for the period against the previous one, followed by tables of top queries and landing pages.
How to connect
Three steps to the first report
Connect the account once, choose the reporting scope, and save the setup for recurring client reports.
01
Connect the account
Save the Google Search Console connection once so the same datasource can be reused across recurring client reports.
02
Choose the reporting scope
Choose the site from your Google Search Console account that should supply search impressions, clicks, queries, and pages to the report.
03
Save the setup and generate the report
Keep the selected scope in the project and reuse the same report setup next time instead of connecting the source again.
FAQ
Frequently asked questions
Short answers about how the integration works in Reportkey today.
What access do I need to connect Google Search Console?
A Google account that is an owner or user of the Search Console property. Both Domain and URL-prefix properties work. You sign in via Google OAuth once in the integrations section with read-only permission, and the account becomes available in all your projects.
How fresh is Search Console data?
Google publishes search analytics with a delay of roughly two to three days, and the last days of a period may still fill in. Closed periods such as last week or last month work best for recurring reports. According to Google documentation, Search Console keeps about 16 months of history.
Why are query clicks lower than the period total?
Google hides rare anonymized queries to protect user privacy, and query and page breakdowns from the API are limited to a number of top rows. The period total is therefore taken separately and does not equal the sum of table rows, which is why the table is labelled as top queries.
Why don't Search Console clicks match GA4 sessions?
Search Console counts clicks in Google results, while GA4 counts on-site sessions with its own method. A visitor may leave before the page loads, the tag may be blocked, or cookie consent may be declined. The figures differ even with a correct setup, so the report shows them side by side with a note.
How is this different from a Looker Studio dashboard?
Looker Studio has a free Search Console connector, but you build and maintain a dashboard for every client. Reportkey gives you a ready multi-channel document: Google organic, Yandex, analytics and ads in one report sent to the client as a link or PDF.
Why does average position differ from my rank tracker?
Search Console averages position across all of the site's impressions, over every query, device and country. A tracker checks one keyword in one location. These are different measurements and should not be compared one to one.
Related integrations
Often connected together
Working sources that teams usually add to the same report.
Google Search Console client report
Sign up, sign in with your Google account and pick a Search Console property. Your first report is ready in 5 minutes.