Google Search Console data next to your analytics
Connect Google Search Console to your analytics to see clicks, impressions, and index status next to visitor traffic without separate dashboards.
On this page 7 sections
You can query Google Search Console clicks, impressions, and index statuses directly alongside your web traffic with one API. thelastapi reads your Search Console performance data daily and displays it beside privacy-first pageviews, session signals, and deployment health. One integration lets your app, your terminal, or your AI agents monitor Google search traffic and on-site user behavior together.
Here is how Search Console tracking connects with your site analytics, how automated verification works, and how to read the data using our CLI and API.
Why keep search metrics and analytics together
Usually, search performance lives in Google Search Console, while on-site behavior sits in an analytics dashboard. Checking how search visibility affects real visits requires bouncing between tabs:
- Verification is manual. Adding every new project or subdomain means creating properties, choosing DNS or HTML file methods, and waiting for verification.
- Data sits in silos. Search impressions and average position sit apart from actual bounce rates, JavaScript errors, or page conversions.
- Diagnosing drops takes extra steps. When traffic slips, you must check whether pages lost impressions in search or started failing on-site after a deploy.
thelastapi unifies this in the project search API and the Analytics and replay resource. You connect a Google account once, and every project with a live domain is automatically verified, added to Search Console, and queried daily for clicks, impressions, and indexing state.
Connecting Google Search Console
To pull Search Console data, you connect Google once in console ▸ Settings ▸ Search or via the CLI. You can connect through an automated service account key or by signing in with Google.
Using a service account JSON key requires no recurring browser sign-in:
- Open Google Cloud, pick or create a project, and enable both the Search Console API and the Site Verification API.
- Go to IAM ▸ Service accounts ▸ Create service account (no specific roles needed), then Keys ▸ Add key ▸ Create new key ▸ JSON.
- Upload the key to thelastapi:
vibiz search connect google --key key.json --owner-email ana@example.comPassing your email as --owner-email adds you as a verified owner of every site property so you can still inspect properties inside Google's web interface. A single key holds up to 1,000 sites.
Alternatively, you can authenticate via browser:
vibiz search connect googleThis returns an OAuth link. Once connected, your account handles the verification lifecycle automatically.
How automatic verification and sitemaps work
Whenever a project has a live domain of its own, the platform registers it with Google Search Console:
- Domains bought through the platform: A DNS TXT record is added automatically to its zone, registering a Domain property (
sc-domain:example.com) that coverswwwand all subdomains. - Domains connected elsewhere: A verification file (
/google<code>.html) is placed on every production deployment. Verification runs one minute after deploy. - Sitemap submission: As soon as your site serves
https://<domain>/sitemap.xml, it is submitted to Google.
Each day, the platform runs URL inspection on up to 200 pages per project, prioritizing pages never checked, followed by pages whose <lastmod> date changed, followed by older records. It fetches Google's indexing verdict (Submitted and indexed, Discovered - currently not indexed, and others), the last crawl timestamp, and Google's chosen canonical URL.
Reading Search Console metrics with Analytics
Once connected, Search Console performance is returned alongside site data in one API call or CLI command. Daily metrics include 28-day impressions, clicks, average position, top queries, and top pages.
To fetch search performance from your terminal:
vibiz searchTo see which pages are currently missing from Google's index:
vibiz search pages --not-indexedTo read search data over HTTP:
curl "https://thelastapi.dev/v1/projects/prj_123/search" \
-H "Authorization: Bearer $VIBIZ_API_KEY"The response provides both index coverage and daily performance:
{
"google": {
"connected": true,
"property": "sc-domain:example.com",
"verify_method": "dns",
"verified_at": "2026-11-10T10:00:00.000Z",
"clicks_28d": 1420,
"impressions_28d": 38900,
"position_28d": 8.4,
"totals": {
"pages_known": 42,
"indexed": 31,
"not_indexed": 11,
"not_crawled": 4,
"not_inspected": 0
},
"top_queries": [
{ "query": "acme api gateway", "clicks": 310, "impressions": 2400 }
],
"top_pages": [
{ "page": "https://example.com/docs", "clicks": 540, "impressions": 8100 }
]
}
}You can contrast this directly with your on-site traffic from the analytics endpoint:
curl "https://thelastapi.dev/v1/projects/prj_123/analytics?period=7d" \
-H "Authorization: Bearer $VIBIZ_API_KEY"This returns total pageviews, unique visitors, referral sources (such as Google or direct), devices, and custom events. Tracking is cookieless and keeps visitor privacy intact without storing IP addresses.
| Metric | Source | Endpoint | What it tells you |
|---|---|---|---|
impressions_28d | Google Search Console | /v1/projects/:id/search | How often your site appeared in Google search results |
clicks_28d | Google Search Console | /v1/projects/:id/search | Total visits sent to your site from Google search |
position_28d | Google Search Console | /v1/projects/:id/search | Average rank across all recorded search impressions |
visitors_7d | Web Analytics | /v1/projects/:id/analytics | Unique visitors landing on your site |
top_sources | Web Analytics | /v1/projects/:id/analytics | Visitor origin breakdown (e.g., Google, ChatGPT, Direct) |
If you also want to see what users do after clicking a search link, you can review recorded journeys. Check find rage clicks and dead clicks on your site or read session replay for a small site: masked, cheap and useful to see how session replay pairs with analytics data.
Inspecting site health in Mission Control
Search performance data is also tied directly into Mission Control and health checks. Under console ▸ Mission Control, your projects display as an operational board.
Step 3 (Pages & SEO) reviews your sitemap and index health, alerting you if a sitemap URL returns a 5xx error or a 404, or if your home page lacks a <title> tag. Mission Control boards also include a Search clicks 7d column alongside visitor counts and error rates.
To inspect health checks across projects from the CLI:
vibiz healthTo run a manual sync of Google Search Console data rather than waiting for the automated daily fetch:
vibiz search syncManual syncs can be called up to 3 times per 10 minutes per project.
Pushing unindexed pages to Google
If you deploy new content frequently, you can enable push indexing via Settings ▸ Search, vibiz search push on, or API:
curl -X PATCH "https://thelastapi.dev/v1/search/settings" \
-H "Authorization: Bearer $VIBIZ_API_KEY" \
-H "Content-Type: application/json" \
-d '{"google_push": true}'When enabled, pages Google has not yet crawled (Discovered - currently not indexed, URL is unknown to Google, or uninspected URLs) are queued and pushed to Google's Indexing API, newest first. The limit is 200 URLs a day per Google Cloud project. To use push indexing with a service account key, ensure the Web Search Indexing API is enabled in your Google Cloud project console.
Along with Google sync, every production deploy automatically submits new and updated sitemap URLs to IndexNow for Bing, Yandex, Naver, and Seznam. Read more about deployment submissions on the Search docs page. For tracking backend events alongside this data, see server-side event tracking from your backend.
Create your account at thelastapi.dev/start to try the unified platform and CLI.
Frequently asked questions
How often does the platform fetch Google Search Console data?
Clicks, impressions, top queries, and indexing status are refreshed once every 24 hours. You can also trigger an immediate check using `vibiz search sync` up to 3 times per 10 minutes per project.
How does the platform verify domain ownership in Google Search Console?
Domains bought through the platform are verified automatically by adding a DNS TXT record to create a Domain property. Other domains are verified via a `/google<code>.html` file deployed to the production root.
Can an AI agent inspect search indexing and performance?
Yes, agents can call the `vibiz_search` tool with actions like `get`, `pages`, and `sync` or inspect SEO health issues via `vibiz_health` to evaluate unindexed pages, clicks, and search impressions.