Search clicks
Search impressions
Average CTR
Daily trend from Google Search Console
Top query groups · Search Console
An exception in Clicks has been detected.
On August 18 you had 180 clicks where we expected 2,400, which is 93% less than expected.
Significant ranking changes detected on tracked queries.
18 keywords moved by 5+ positions in the last 7 days. Top mover: agency reporting software (+12).
Target: 3.2% CTR
Previous Period: 2.8% (Jul 1, 2026 – Jul 31, 2026)
Your MTD average is 2.1% and is -34% below your target of 3.2% CTR.
Target: 8.0
Previous Period: 9.2 (Jul 1, 2026 – Jul 31, 2026)
Your MTD average position is 11.4 vs target 8.0 (worse by 3.4 positions).
Jepto pulls the four core Search Console metrics — clicks, impressions, CTR, and average position — broken down by query, page, country, device, and search appearance.
| Entity | What it contains |
|---|---|
| Property | The Search Console property (site URL or domain property) you connect. |
| Query | Search queries that triggered impressions for your site. |
| Page | Landing page URLs receiving search traffic. |
| Country | Country of the searcher. |
| Device | Desktop, mobile, or tablet. |
| Search appearance | Rich result types (AMP, video, FAQ, etc.). |
| Date | Daily granularity for all time-series reporting. |
Reports, forecasts and alerts — built on the same live connection.
Report on query-level clicks, impressions and position changes — side by side with paid search performance.
Explore reporting Set up automated jobs to monitor search performance, track ranking changes, and trigger alerts when organic traffic shifts.
Explore automation Set monthly targets for organic clicks or impressions and track progress against them.
Explore KPI forecasting Alerts when clicks, impressions or average position move outside normal ranges for key queries or pages.
Explore anomaly detection Query Search Console metrics and dimensions through natural language — no write-back.
Read-only analytics
Use MCP to ask about queries, pages, rankings and organic traffic trends. Jepto maps your question to the right Search Console dimensions and metrics.
schema()
Explore Search Console entities, metrics and dimensions on the connected property.
data()
Query live organic search performance across queries, pages and devices.
actions()
Not available — this is a read-only source. No write-back actions are supported.
execute()
Not available — this is a read-only source. Jepto cannot modify data in the platform.
Sign in with a Google account that has access to the Search Console property.
Click Connect and authenticate with the Google account that has access to your client's Search Console property.
Choose the site or domain property. Add additional connections for more properties.
Assign it to the relevant client so reports and forecasts can pull from it.
Jepto backfills up to 16 months of history, then syncs daily as Google publishes new data.
Everything you need to know about Google Search Console in Jepto.
Yes. Once both are connected to the same client, any report can blend organic queries with paid search terms for a complete search picture.
Jepto backfills up to 16 months on the first sync, matching what the Search Console API makes available.
Search Console data has a reporting delay from Google — typically 2–3 days. Jepto syncs daily as soon as Google publishes the data.
Yes. Each property connection counts as one data source.
If the Google account loses access, Jepto stops syncing new data but keeps history already pulled. Reconnect with a valid account to resume.
Related Articles
Start asking your data smarter questions today. Connect your first data source in minutes.
© Jepto 2026. All rights reserved.