UNDERSTAND · GOOGLE SEARCH CONSOLE
Google Search Console insights that tell you what to do next.
Queries, pages, countries and devices from your own Search Console property, organised into striking-distance keywords, ready-made opportunities, branded and non-branded segments and Google update impact. Reading your own data never costs credits.
- Read-only Google connection
- Up to 16 months of history
- No credits for your own data
16 months
of Search Console history, Google’s maximum
4 dimensions
queries, pages, countries and devices
6 decision views
striking distance, opportunities, segments, updates, counting, clusters
0 credits
to read your own Search Console data
INSIDE THE PRODUCT
Everything in Search Console, organised around decisions.
The same first-party data you trust, turned into views that answer the question in front of you.
Striking distance
Find keywords one push away from the top
See query and page pairs ranking just below the top results, sorted by impressions, so a small improvement moves the most traffic.
- Filter to positions 4–10 or 11–20
- See the page Google ranks for each query
- Open any row to see every query that page ranks for
| Query | Position | Impressions |
|---|---|---|
| best phones under 20k | 6.2 | 18.4K |
| redmi note 14 price kenya | 8.7 | 12.1K |
| samsung a16 specs | 11.3 | 9.8K |
| phone shops nairobi cbd | 14.9 | 6.2K |
Opportunities
Get ready-made opportunities, not just rows
Ndovu groups your Search Console data into actions you can assign: pages to push into the top three, titles worth rewriting, decaying pages to refresh and competing pages to merge.
- Push to top 3
- Rewrite title
- Refresh decaying page
- Merge competing pages
- Push to top 3/phones/redmi-note-14/Position 4.2 · 9.1K impressions
- Rewrite title/blog/best-phones-2026/High impressions, low click-through
- Refresh/guides/5g-phones/Clicks down 34% on the last period
- Merge“cheap phones”Two pages compete for the query
Segments
Separate branded demand from the searches you earn
Split performance into branded and non-branded searches, search intent, query modifiers, page types and automatic site sections, so a brand campaign never hides a drop in organic discovery.
- Branded vs non-branded
- Search intent and query modifiers
- Page types and site sections
Google updates & notes
See what changed around a Google update
Compare performance before and after confirmed Google updates, labelled positive, negative or no clear impact, and add your own notes so a title change or migration sits on the trend line.
- Impact around confirmed updates
- Your own notes on the chart
- Compare like-for-like periods
Clusters & counting
See topics and position bands, not just rows
Group queries by shared words or by the page that ranks for them, and count how many queries and pages earn impressions and clicks in each position band.
- Clusters by topic or ranking page
- Queries and pages by position band
- Growth or decline per cluster
Countries & devices
Compare markets and devices side by side
Read clicks, impressions, click-through rate and position by country and by mobile, desktop and tablet, so a mobile drop in one market never hides inside a sitewide average.
- Country breakdown
- Mobile, desktop and tablet
- Same filters as the main view
| Device | Clicks | Avg. position |
|---|---|---|
| Mobile | 9,140 | 8.9 |
| Desktop | 3,020 | 6.4 |
| Tablet | 240 | 9.7 |
WHAT IT MEASURES
Every Search Console number, explained.
What each metric tells you, and where it comes from.
| Metric | What it tells you | Source |
|---|---|---|
| Clicks | Clicks from Google Search results to your site. | Google Search Console |
| Impressions | How often a URL from your site appeared in results someone saw. | Google Search Console |
| Click-through rate | Clicks divided by impressions. | Google Search Console |
| Average position | The average top position of your site in results; lower is better. | Google Search Console |
| Striking distance | Query and page pairs at positions 4–20, sorted by impressions. | Calculated from Search Console |
| Branded share | Clicks from searches containing your brand terms. | Calculated from your brand terms |
| Update impact | Change in clicks before and after a confirmed Google update. | Search Console + update dates |
UNDER THE HOOD
How Search Console insights are built.
How the numbers are produced, so you can judge them for yourself.
Read-only, by dimension
Ndovu asks the Search Console API for clicks, impressions, click-through rate and position by query, page, country, device and date, for the property and search type you choose. The connection is read-only, and nothing is written back to Google.
Opportunities from simple rules
Striking distance is every query and page pair at positions 4–20, sorted by impressions. Other opportunities follow plain rules you can check: high impressions with low click-through for title rewrites, clicks down on the last period for refreshes, and two pages earning impressions for one query for merges.
Segments you can edit
Branded searches are matched against brand words for the project, which you can change. Intent comes from query modifiers such as price, buy, best, vs, how and what, and site sections from the URL path, so every segment can be traced back to a rule.
Updates compared like for like
Update impact compares equal windows before and after each confirmed Google update date, and labels the change positive, negative or no clear impact. Your own notes sit on the same chart, because a release often explains more than an update.
HOW IT WORKS
Connected in minutes. Useful the same day.
Three steps from connecting your data to a decision you can stand behind.
Connect
Sign in with Google and choose the verified property for the project. The connection is read-only.
Explore
Start from the trend, then drill into queries, pages, countries and devices, or open a decision view.
Act and confirm
Work through opportunities, add notes for the changes you ship, and confirm the effect in later weeks.
WITH YOUR AI AGENT
Ask what changed, and get the queries behind it.
Your agent reads your Search Console data and opportunities, then inspects the pages involved before it suggests a fix.
- Uses the same data as the web app
- Paid tools estimate their cost first
- Saves the report to the project
YouWhy did organic clicks drop last week?
get_search_console_performanceget_search_opportunitiesinspect_urls
AgentClicks fell 11%, almost all on mobile in Kenya. Three category pages lost positions for “phone a price” queries. URL Inspection shows one of them was crawled after its canonical changed to a filtered URL.
YouWhich pages should we fix first?
AgentStart with /phones/phone-a/: it had 2,300 clicks last month and now points its canonical elsewhere. Then the two titles with high impressions and low click-through.
Illustration · sample data
USE CASES
Built for the way you work.
How teams put it to work.
Review every client in minutes
Start from the All sites portfolio, sort by biggest decline and open the site that needs attention this week.
Grow category and product pages
Find product and category pages one push from the top three, and merge pages that compete for the same query.
Keep content earning
Spot decaying articles and titles that earn impressions but few clicks, then refresh them first.
Explain every change
Separate brand from non-brand demand and annotate releases, so reports explain themselves.
Separate brand from demand
See whether growth came from brand campaigns or from searches you earned, before you report it.
Check a release
Compare the days around a deploy for the affected section, and inspect the pages that moved.
ALSO INCLUDED
More ways to read the same data.
More capabilities that come with it, in the same project.
Keyword clusters
Group queries by shared topic words or by the page that ranks for them.
Countries & devices
Compare performance by country and by mobile, desktop and tablet.
Query & page counting
See how many queries and pages earn impressions and clicks, by position band.
All sites
Every connected website’s Search Console totals on one page.
Your AI agent
Connected agents can query performance and inspect URLs for your projects.
URL inspection
Index status, last crawl and Google’s canonical for any page.
DATA & LIMITS
Know what the numbers can and cannot tell you.
Where the data comes from, how fresh it is, and the questions it cannot answer on its own.
| Source | What it provides | Freshness & limits |
|---|---|---|
| Google Search Console API | Queries, pages, countries, devices and search appearance. | About three days behind; up to 16 months. Google withholds some rare queries. |
| URL Inspection API | Index status and last crawl for single URLs. | Quota-limited by Google. |
| Confirmed Google updates | Dates used for before-and-after comparisons. | Dates only; they do not prove cause. |
Rare queries are hidden
Google omits some low-volume queries for privacy, so query totals can be lower than page totals.
Position is an average
Average position blends every appearance. Rank tracking shows a single observed position.
Opportunities are estimates
Potential clicks are planning aids, not promises.
Timing is not cause
A change around an update is a reason to investigate, not proof the update caused it.
WORKS WITH
Connected to the tools you already use.
The sources and clients this feature reads from or works alongside.
CHOOSE THE RIGHT VIEW
Which view answers which question.
Start where the question points. Each view keeps its own source.
| Your question | Start with | Why |
|---|---|---|
| Which queries bring me clicks? | Search Console insights | Measured clicks from Google. |
| What happened after the click? | Analytics & AI referrals | Sessions and key events in GA4. |
| Is this page indexed? | Inspect URL | Google’s index status for one URL. |
| How are all my sites doing? | All sites | Every property on one page. |
LEARN & TRY
Guides and free tools for the same job.
Read how the evidence works, or try a free check before you connect a project.
Your data vs market estimates
Which question first-party data and provider estimates each answer.
CTR opportunity finder
Find queries with clicks to gain.
Cannibalization investigator
Find pages competing for a query.
Branded keyword classifier
Split brand from non-brand queries.
FAQ
Search Console insights: common questions.
Straight answers about what it does, what it costs and where its limits are.
Does using Search Console data cost credits?
No. Reading your own Search Console property uses Google’s free API, so it never uses credits. Paid market research such as keyword volumes and backlinks is separate.
Which properties can I connect?
Domain and URL-prefix properties that your Google account can access. Each project connects to one property.
How far back does the data go?
Up to 16 months, the most Google keeps, with Google’s usual reporting delay of about three days.
Does Ndovu change anything in my Search Console?
No. The connection is read-only. URL inspection reads Google’s index status for a page; it does not request indexing.
Can my AI agent use this data?
Yes. Through the MCP server, connected agents such as Claude, Codex or Cursor can query performance and inspect URLs for projects you can access.
How is this different from the Search Console interface?
It is the same data, organised into decisions: striking distance, opportunities, segments, update impact, clusters and notes, next to analytics, crawl and AI evidence in the same project.
Can I add notes to the chart?
Yes. Add notes for releases, campaigns or migrations, and they appear on the trend line beside the data.
How are branded queries identified?
From brand words for the project. Defaults are suggested, and you can add or remove words if the split looks wrong.
Can I see image, video, News or Discover performance?
Yes. Switch the search type between web, image, video, news, Google News and Discover, as Search Console reports them.
Can I compare two periods?
Yes. Compare like-for-like periods, such as the last 28 days against the 28 before them.
Is Bing included?
Bing Webmaster data sits beside Google in the project, kept separate rather than averaged together.
What are the limits of the data?
Data comes from your connected Google Search Console property, with Google’s usual reporting delay of about three days and a maximum of 16 months. Opportunity estimates are planning aids, not promised clicks, and a change that lines up with a Google update is evidence to investigate, not proof the update caused it.
How do I get access?
Platform access is reviewed. Request access with your website and the data sources you use, and the team will help you connect them.
See your own Search Console data in Ndovu.
Tell us about your website. We will review access and help you connect the property.