Google Search Console
Connect Google, choose a property to track, and read your real clicks, impressions, CTR and positions on the Search Console page.
Last updated 2026-09-16
Summary#
Connecting Google gives Metric Vault read-only access to your Search Console data. Once you choose a property to track, the Search Console page shows your measured clicks, impressions, click-through rate and average position for any dates in your stored history, compares them with the previous period or the same period last year, and breaks them down by query, page, country and device. You can filter the query and page tables and open any row to see the pages behind a query or the queries behind a page. You can switch to image, video, News, Discover or Google News results, see the last few days before Google has finished counting them, list your sitemaps, and ask Google about a single page straight away. It also finds queries close to the first page, pages that are losing traffic, which pages are indexed, and how fast real visitors find your site. Connecting is free and uses no credits.
Purpose#
Every SEO platform estimates traffic. Estimates are right for competitors, where nobody has the real numbers, and unnecessary for your own site, where you do. Search Console holds the measured figures: which queries showed your pages, how often people clicked, and where you actually ranked.
Search Console itself deletes data after 16 months and has no way to compare two periods. Metric Vault stores your history as it syncs, so comparisons and trends work across the whole period, and opening the page never waits on Google.
Overview#
The connection is between your Metric Vault account and one Google account. What Metric Vault can see is what that Google account can already see in Search Console.
Connecting on its own does not start collecting anything. You choose which properties to track, and only tracked properties are synced. For each one, Metric Vault pulls the most recent days straight away and then works backwards through up to 16 months of history in the background.
Nothing is written back to Google. Metric Vault cannot change a setting, submit a sitemap or request indexing.
Requirements#
- A Metric Vault account you are signed in to.
- A Google account that already has access to the Search Console property. If the site is not verified in Search Console, connecting will not create it. Verify it at Google Search Console first.
- No plan requirement and no credits.
Permissions#
Any signed-in user can connect their own Google account.
When you work inside a teammate's workspace, the Search Console page, Blog Studio and the other tools read that workspace's Google connection, so you see the same Search Console data they do. Only the person who made the connection can disconnect it. See What teammates share.
Google asks you to approve read-only Search Console access and your email address, which labels the connection so you can tell which account is linked. Google Analytics access is not requested when you connect. It is requested only if you later choose Allow Analytics access on the Analytics tab.
Navigation Path#
Connect under Dashboard → Account & Team → Integrations, on the card titled Google Search Console.
Read your data under Dashboard → Track & Report → Search Console.
Step-by-Step Guide#
- Open
Integrationsfrom the sidebar, underAccount & Team. - On the
Google Search Consolecard, pressConnect Google. The page moves to Google in the same tab. - Choose the Google account that has access to your Search Console property.
- If Google shows an "unverified app" warning, see the note below.
- Approve the permissions. Google returns you to a page headed
Google connected!. - Press
Open Search Console. - Choose the property you want to track and press
Start tracking. If the website selected in your website switcher matches one of your properties, it is already chosen for you. - The page shows
Collecting your historywhile the first days arrive, usually within about fifteen minutes. You can leave the page; collecting continues in the background.
Note: Metric Vault is pending Google's verification review, so Google may show an "unverified app" screen. The Seeing a Google warning? button on the card explains what to do: press Connect Google again, click Advanced on the warning screen, then click Go to Metric Vault (unsafe). Access is read-only and you can revoke it at any time at myaccount.google.com/permissions.
Choosing and changing properties#
The dropdown at the top of the page lists every property you can track, with the ones you already track first.
- Choosing a property you already track switches the page to it.
- Choosing one you do not track yet starts tracking it. The page shows
Collecting your historyuntil its first days arrive, and the dropdown stays available so you can switch back. Stop trackingstops collecting new data for the property on screen. Its history is kept, and choosing it again later picks up where it left off.
A property marked Not verified in Search Console cannot be tracked. Verify it in Search Console first.
Following your website#
The page opens on the tracked property that matches the website selected in your website switcher, and changes with it when you switch website.
A domain property, which Google writes as sc-domain:example.com, matches that domain and every subdomain, so blog.example.com uses it. A URL-prefix property such as https://shop.example.com/ matches only that exact address. When both match, the URL-prefix property is used because it is the narrower one.
If you pick a property by hand, the page keeps it until you switch website.
Reading the page#
The top of the page shows which Google account is connected, the property, your access level in Search Console, and when it last synced.
| Element | What it shows |
|---|---|
7 days, 28 days, 90 days, 180 days | The period shown, ending with the newest stored day |
| Search type dropdown | Web, Image, Video, News, Discover or Google News. See Search types and fresh data |
Custom | Opens From and To date fields for any period in your stored history. Press Apply to use them |
Fresh | The last 10 days, including days Google has not finished counting, with an hourly chart |
| Comparison dropdown | Previous period, Same period last year or No comparison. The line under the tiles names the dates compared with |
Clicks, Impressions | Totals for the whole property |
Average CTR | Clicks divided by impressions for the period |
Average position | Weighted by impressions. A lower number is better, so a fall shows as an improvement |
Performance over time | A daily chart of one metric at a time, chosen with the Clicks, Impressions, CTR and Position buttons |
Below the chart, the reports are grouped into four sections: Performance (Queries, Pages, Countries, Devices, Search appearance), Opportunities (Quick wins, Losing traffic), Site health (Index coverage, Core Web Vitals, Sitemaps) and Analytics (Analytics, Search to revenue). Choose a section, then a report under it. Each section remembers the last report you opened.
While a period has impressions but no clicks, the charts show impressions and a note under the tiles says so. Choose Clicks above the chart to switch back.
The reports:
| Tab | What it shows |
|---|---|
Queries | Search terms that showed your pages, with a chart of the top ten |
Pages | Your pages, with the same figures |
Countries | Performance by country |
Devices | Performance by desktop, mobile and tablet |
Search appearance | Clicks and impressions from special result types, such as review snippets or video results |
Quick wins | Queries ranking between 8 and 20 with enough impressions to matter, and the extra clicks a top-5 position would bring |
Losing traffic | Pages whose clicks fell against the previous period, with the likely reason |
Index coverage | Whether each page is in Google's index, and if not, why |
Core Web Vitals | Loading, responsiveness and stability measured by real Chrome users |
Sitemaps | The sitemaps Google has for the property, with submitted URLs, errors and warnings |
Analytics | Organic sessions, engagement, conversions and revenue from Google Analytics |
Search to revenue | Search Console pages joined to their Analytics results, and a Traffic that does not convert list of pages with at least 20 search clicks and no conversions |
Important: Search Console withholds rare queries to protect searchers' privacy, so the rows in Queries never add up to the property total. The tile totals are the property's real totals. Below the Queries table, the page says how many clicks could not be itemised.
Dates and comparisons#
The preset buttons show the last 7, 28, 90 or 180 days that have been stored. The newest day is two days ago, because Search Console publishes each day after a delay.
Custom lets you pick any start and end date between two days ago and the oldest day in your stored history. The fields will not accept a date outside that range.
The comparison dropdown decides what the change figures are measured against:
| Option | Compared with |
|---|---|
Previous period | The same number of days immediately before |
Same period last year | The same dates 52 weeks earlier, so a Monday is compared with a Monday |
No comparison | Nothing. The change figures and the Change column are hidden |
The dates compared with are shown under the tiles. If nothing is stored for them yet, for example a year back while the history is still backfilling, the page says so and shows no change rather than a misleading one.
The Quick wins and Losing traffic tabs use the same dates. Losing traffic always needs a comparison, so with No comparison it uses the previous period. The Analytics and Search to revenue tabs use the same number of days ending two days ago, and ignore custom dates and comparisons.
Search types and fresh data#
The search type dropdown switches every figure on the page to one kind of Google result:
| Type | What it counts |
|---|---|
Web | The main search results. This is the stored history |
Image | Google Images |
Video | The Videos tab and video results |
News | The News tab in Google Search |
Discover | The Discover feed in the Google app and on mobile |
Google News | news.google.com and the Google News app |
Only Web is stored. The other types are read from Google when you open them, and kept for an hour. Because of that:
- tables have no
Changecolumn, though the tiles still compare periods; Quick wins,Losing traffic,AnalyticsandSearch to revenueare hidden, because they are built from stored web history;DiscoverandGoogle Newshave noQueriestab and no average position, because nobody typed a search and there is no ranked list.
Fresh shows the last 10 days, including the days Google is still counting, for any search type. The line under the tiles gives the first date that is not final, and a By hour chart shows the last three days hour by hour in Pacific Time, which is how Google reports hours. Fresh figures are kept for 15 minutes and can still change. Choose a preset or Custom to go back to settled data.
Filtering and drilling in#
On the Queries and Pages tabs, the bar above the table filters the rows:
| Filter | Keeps rows that |
|---|---|
Contains | Include the text, ignoring upper and lower case |
Does not contain | Do not include the text |
Is exactly | Match the text exactly, ignoring case |
Matches regex | Match a regular expression, ignoring case |
Press Filter to apply it and Clear filter to remove it. The line under the bar gives the number of matching rows and their clicks and impressions, counting every match, not only the rows on screen. A regex is checked against the 20,000 busiest rows in the period. When there are more, the page says rarer rows were not included. The filter is cleared when you change tab.
With a comparison on, the Change column shows how each row's clicks moved. New means the row had no clicks in the comparison period.
Select a query to open the pages that ranked for it, or select a page to open the queries it ranked for. This breakdown is read live from Google for the same dates, because the stored history keeps queries and pages apart. It can include recent days the stored figures have not settled yet, so its numbers can differ slightly from the row above it.
Quick wins and losing traffic#
Quick wins estimates extra clicks from your own site's click-through rate at each position, not an industry average. Until enough history has been collected to measure that, it uses a typical curve and says so.
Losing traffic lists pages whose clicks fell by 30% or more, with their clicks, impressions and position before and after. It explains each drop as one of three causes:
| Label | Meaning |
|---|---|
Ranking | You slipped down the results |
Search page | You still rank, but fewer people click, often because of an AI answer or a stronger competing snippet |
Demand | Fewer people are searching for it at all |
Index coverage#
This tab answers a question the performance data cannot. A page with no impressions and a page Google refused to index look the same there: both are absent. Google's URL Inspection API knows which one you have, and why.
Pages by status counts the checked pages under each of Google's answers, largest group first, so the most common reason pages are missing is the first thing you read.
Each row gives the page, whether it is indexed, and what Google did with it in plain words. Where Google chose a different canonical from yours, the one it picked is shown. Details under a page opens the rest of Google's answer:
| Field | What it tells you |
|---|---|
Indexing | Whether indexing is allowed, or blocked by a noindex meta tag, a noindex HTTP header or robots.txt |
robots.txt | Whether robots.txt lets Google fetch the page |
Page fetch | What happened when Google fetched it, such as Fetched successfully, Not found (404) or Server error (5xx) |
Crawled with | Whether Google used its smartphone or desktop crawler |
Rich results | Whether structured data on the page is valid for rich results. Shown only when Google reports it |
Your canonical, Google's canonical | The canonical you declared and the one Google chose |
Checked | When the page was last inspected |
Google allows 2,000 inspections a day per property, so pages are checked in order of impressions and the tab states how many of your pages it has reached. Answers are refreshed every 14 days.
To check one page now, for example one you just published or fixed, enter its full address in the box at the top of the tab and press Inspect now. The answer appears straight away with its details, and is added to the table. The address must belong to the property on screen, and the property must be tracked. You can inspect up to 100 addresses a day.
Sitemaps#
The Sitemaps tab lists the sitemaps Google has for the property:
| Column | Meaning |
|---|---|
Type | Sitemap, Sitemap index, RSS feed, Atom feed or URL list |
Status | Read, Has warnings, Has errors, or Pending if Google has not processed it yet |
URLs submitted | How many addresses the sitemap lists |
Errors, Warnings | Problems Google found when it read the sitemap |
Last read | When Google last downloaded it |
Google no longer reports how many URLs in a sitemap are indexed, so the tab does not show that. Use Index coverage instead. Sitemaps are submitted in Search Console itself, because Metric Vault's access is read-only. The list is kept for an hour.
Core Web Vitals#
This tab shows field data: what real Chrome users measured over a rolling 28 days, which is what Google ranks on. It is not the same as the Lighthouse score in Site Audit, which measures one synthetic load. The two routinely disagree.
The tab shows five measurements. Three are the Core Web Vitals Google ranks on, and two are diagnostics from the same report that usually explain a slow load:
| Metric | Measures | Good | Poor |
|---|---|---|---|
Largest Contentful Paint (LCP) | Time until the main content appears | 2.5 s or less | Over 4 s |
Interaction to Next Paint (INP) | How quickly the page responds to a tap or click | 200 ms or less | Over 500 ms |
Cumulative Layout Shift (CLS) | How much the page moves while it loads | 0.1 or less | Over 0.25 |
First Contentful Paint (FCP) | Time until anything appears. Diagnostic | 1.8 s or less | Over 3 s |
Time to First Byte (TTFB) | Time until the server starts answering. Diagnostic | 0.8 s or less | Over 1.8 s |
Each metric shows the 75th percentile, a verdict against those thresholds, and the share of visits that were good and poor. A page with too few visitors for Google to report on is left out rather than shown as zero.
What is collected, and how often#
| Job | What it collects | How often |
|---|---|---|
| Performance sync | Clicks, impressions, CTR and position for the property, by query, by page, and by country and device | Recent days refreshed every 15 minutes while they settle. Older days are added ten at a time every 15 minutes, so all 16 months take about 12 hours |
| Index coverage | Whether each page is indexed, and the reason if not | A few pages per property every 15 minutes, refreshed every 14 days |
| Core Web Vitals | Field data for the site and its busiest pages | Refreshed every 3 days |
Because everything is stored, opening a tab reads Metric Vault's database rather than calling Google. The exceptions ask Google directly: opening a query or page row, a search type other than Web, Fresh, Search appearance, Sitemaps and Inspect now. Answers are kept for an hour, or 15 minutes for fresh data, so opening the same view again does not ask again.
Elsewhere in Metric Vault#
- Blog Studio. A published post shows a
Search performancepanel with the last 28 days of clicks, impressions and CTR for that post, and its top queries. The post's site must be a property you track; if it is not, the panel says so. - Domain Overview. Running Domain Overview on a domain you have in Search Console adds a
Live from Google Search Consolepanel with its top queries. - Content Decay. Content Decay Detector uses your measured clicks instead of estimated traffic when the domain is a tracked property.
Disconnecting#
On the Google Search Console card, press Disconnect. Only the person who made the connection can do this.
Disconnecting removes the connection, clears cached Search Console answers, and stops tracking every property. Stored history is kept. If you connect again later and choose the same property, its history is there immediately and collecting resumes from where it stopped.
To revoke access at Google as well, open myaccount.google.com/permissions, find Metric Vault, and remove it. See Disconnecting an integration.
Connecting a different Google account replaces the existing connection.
Limitations#
- One Google account per Metric Vault account. Connecting a second replaces the first.
- Only web search is stored. Image, video, News, Discover and Google News are read live, without per-row change or the tabs built on stored history.
- Top 5,000 queries and pages a day. A site with more than that keeps its top 5,000 of each per day.
- Dates are limited to the stored history. A custom range cannot start before the oldest stored day, which is at most 16 months back.
- Analytics tabs use preset lengths. Custom dates and comparisons apply to the Search Console tabs only.
- Drill-downs show the top 25 rows for the query or page opened.
- Inspect now allows 100 addresses a day per account, because it shares Google's 2,000-a-day inspection limit with the background checks.
- Sitemaps are listed, not submitted. Access is read-only.
- Data lags two to three days. Search Console publishes each day after a delay, so the newest days appear last.
- Index coverage is a sample on large sites, limited by Google's 2,000 inspections a day per property.
- Nothing is written to Google. No sitemap submission, indexing requests or settings changes.
Troubleshooting#
| Symptom | Likely cause | Fix |
|---|---|---|
Badge reads Setup required and Connect Google is missing | Google sign-in is not configured for this site | Report it. Nothing in your account causes this |
Invalid or expired connection request. Please start again. | The connection request was already used, often by a second tab | Return to Integrations and press Connect Google once |
OAuth flow expired (> 10 min). Try connecting again. | Too long passed between starting and finishing | Start again and complete it in one go |
Google denied the connection: access_denied | You pressed Cancel on the consent screen | Press Connect Google and approve |
Token exchange failed: redirect_uri_mismatch | The return address is not on Google's approved list | Report it |
| Google shows an "unverified app" screen | Verification review is pending | Advanced, then Go to Metric Vault (unsafe) |
No verified properties were found on this Google account. | The connected account has no verified Search Console properties | Verify the site in Search Console, or reconnect with the account that owns it |
Collecting your history stays at 0% for more than an hour | The first sync has not run yet, or failed | Check the line under the progress bar for the last error. If there is none, wait for the next sync |
This post is not on a Search Console property you track. in Blog Studio | The post's site is not tracked | Choose its property on the Search Console page |
| Totals do not match the rows | Search Console withholds rare queries | Expected. The tiles are the property's real totals |
That is not a valid regular expression. | The text in the filter is not a valid regex | Correct the pattern, or choose Contains instead |
No data is stored for that period yet, so no change is shown. | The comparison period is older than the history collected so far | Wait for the backfill, or choose Previous period |
That address is not part of this Search Console property. | The page is on another domain, or outside a URL-prefix property | Choose the property that covers it, or enter an address on this one |
You have inspected 100 addresses in the last 24 hours. | The daily limit for Inspect now | Wait a day. Pages are still checked in the background |
Google's daily inspection limit for this property has been reached. Try again tomorrow. | The property's 2,000 inspections for the day are used | Try again tomorrow |
Google has no sitemaps for this property. | No sitemap was submitted in Search Console | Submit one in Search Console |
| A drill-down shows slightly different numbers from its row | The breakdown is read live and can include days that are still settling | Expected. The stored figures settle within a few days |
More symptoms are in Google connection problems.
FAQs#
Does connecting Google cost credits? No. Connecting is free, and reading your Search Console data uses no credits.
Can Metric Vault change anything in my Google account? No. Access is read-only.
Which Google account should I use? One that can already open the property in Search Console. If several people have access, any of them works; the data is the same.
Do my teammates see my Search Console data? When they work inside your workspace, yes. Tools there read the workspace's Google connection. Only you can disconnect it.
Can I compare with last year? Yes. Choose Same period last year in the comparison dropdown. It needs history stored for those dates, which the backfill collects over the first few hours after you start tracking a property.
Why is the most recent day missing? Search Console publishes each day after a delay of two to three days. Press Fresh to see the newest days before they are final.
Why is there no average position for Discover? Discover and Google News show content in a feed, not a ranked list of results for a search, so Google reports no position for them.
Why do the query rows not add up to the total? Search Console withholds queries that very few people searched, to protect their privacy. They count towards the total but never appear as rows.
I stopped tracking a property. Is its history gone? No. It is kept, and choosing the property again picks up where it left off.
How do I connect a different Google account? Press Connect Google and choose the other account. The new connection replaces the old one.
See also
Was this article helpful?
Thanks — feedback noted for the docs team.