Rankings and Google data
The RankX AI MCP tools for keyword rankings, AI Overviews, Search Console, Google Analytics and index coverage, and how each reports a missing connection.
These tools let an assistant read your Google rankings and traffic from RankX AI. They cover two different sources: what RankX AI measures itself, which is your position on tracked keywords and whether an AI Overview appeared, and what Google reports about you, which is Search Console and Google Analytics once you connect them.
Keep the two apart. Tracked rank is RankX AI checking a keyword; Search Console's average position is Google's own aggregate across every search. They measure different things and must never be read as interchangeable.
| Tool | Scope | What it does |
|---|---|---|
get_ai_conversions | read | Enquiries, sign-ups and sales from visitors who arrived from an AI assistant, by assistant, beside Organic Search and the whole site, from Google Analytics. A figure is empty rather than zero unless the property is confirmed to track it, and Google AI Overviews cannot be separated from ordinary search. |
get_ai_overview_presence | read | How often Google AI Overviews appeared for a Website's tracked keywords, and whether the brand was named or cited inside them. Unknown is a real third state, never zero. |
get_aio_citations | read | The domains and pages Google's AI Overviews cited for a Website's tracked keywords, ranked by how often each was cited. |
get_analytics_breakdown | read | Where a Website's visitors came from and what they used, from Google Analytics: source, medium, channel group, campaign, country, device, browser, operating system, or new against returning. Its user figures are summed per row, so they are not a count of unique visitors. It refuses rather than reporting zero when Analytics is not connected. |
get_analytics_traffic | read | Google Analytics sessions, page views and active users for a Website, by page viewed or by session landing page. It refuses rather than reporting zero when Analytics is not connected. |
get_google_integration_status | read | Whether Search Console and Analytics are connected for a Website, which property each points at, when each last synced, and what to do about it. This is how an assistant explains missing figures instead of guessing. |
get_index_coverage | read | Google's index status across the pages of a Website that have been inspected, plus the findings that follow from it. The response states its own denominator, because it describes pages inspected rather than every page on the site. |
get_rank_tracking | read | Tracked keywords with their latest search positions to depth 20. It distinguishes not in the top 20 from never checked, and reports why a scheduled check was skipped. |
get_realtime_visitors | read | How many people are on the Website right now, from Analytics realtime. This is the only Analytics tool that calls Google live; the other Analytics and Search Console reads serve already-synced data, and inspect_url asks Google only when its 24-hour cache is stale. |
get_search_console_drilldown | read | The link between queries and pages: which search terms bring people to one page, or which pages Google shows for one term. The second mode is how you find two pages competing for the same query. |
get_search_console_opportunities | read | Two analytical views: how many queries sit in each position band with the clicks each earns, and the measured click difference on queries where Google shows an AI Overview. It refuses to conclude on a sample too small to support one. |
get_search_console_performance | read | Clicks, impressions, click-through rate and average position for a Website, broken down by query, page, country, device, search surface or rich-result appearance. |
get_search_console_trend | read | The same figures per day, plus a comparison with the equal-length window before it. The most recent day or two are marked provisional, because Google has not finalised them. |
inspect_url | read | What Google itself says about one page: indexed or not, its own reason if not, which canonical it chose, and when it last crawled. This is the only way to see a page that is not indexed at all. |
list_sitemaps | read | The sitemaps Search Console holds for a Website, when Google last read each one, and any errors it reports. Read only: submitting a sitemap is done in Search Console itself. |
run_rank_check | spend | Runs a live search-position check for one tracked keyword, including AI Overview capture. |
save_keywords | write | Starts rank tracking for up to twenty keywords. Per-keyword results: a duplicate or a plan-limit refusal is reported on its own row and never fails the batch. |
untrack_keyword | write | Stops rank tracking a keyword and frees its slot against the plan limit. Reversible: the history is kept and re-adding the phrase resumes tracking. |
update_keyword | write | Changes a tracked keyword's device, market, language or check frequency. The phrase itself cannot be changed; untrack it and add the new phrase instead. |
The table above is generated from RankX AI itself rather than written by hand, as at 30 September 2026 (source b27dec96). When the product changes, this page changes with it.
A typical request to an assistant with these tools connected:
Did my Search Console clicks fall this month? Compare against the previous equal window and tell me which days are still provisional.
Tracked rankings
get_rank_tracking returns tracked keywords with their latest positions, to
depth 20, and keeps three states apart:
| State | Meaning |
|---|---|
| Ranked | Found, position 1 to 20 |
| Not in the top 20 | Checked, and not in the first twenty results |
| Never checked | No check has run for this keyword yet |
Merging the last two into "no position" would turn an unmeasured keyword into a failing one. The tool also reports why a scheduled check was skipped, so a gap in a series has an explanation.
save_keywords starts tracking up to twenty keywords in one call and returns
per-keyword results: a duplicate or a plan-limit refusal is reported on its
own row and never fails the batch. untrack_keyword is reversible, keeps the
history and frees the slot. update_keyword changes device, market, language or
frequency, but not the phrase: to change the phrase, untrack it and add the
new one.
run_rank_check is the spend tool here. It runs a live position check for one
tracked keyword, including AI Overview capture.
AI Overviews
get_ai_overview_presence reports how often a Google AI Overview appeared for
your tracked keywords, and whether your brand was named or cited inside it.
"Unknown" is a real third state: an overview was detected but not captured.
It is not "you were not mentioned".
get_aio_citations returns the domains and pages Google's AI Overviews cited,
ranked by citation count. These are not the same as the citations AI assistants
give: different engine, different collection, different cadence.
Citations, two kinds explains the
difference, and is worth reading before reporting either.
Both come from the rank tracker on tracked keywords, so adding keywords widens them and adding prompts does not.
Search Console
Four tools read Search Console, and each answers a different question:
get_search_console_performanceanswers "which queries and pages", broken down by query, page, country, device, search surface or rich-result appearance. Its totals match Search Console's own.get_search_console_trendanswers "is it growing or falling, and when did it change", with figures per day compared with the equal-length window before.get_search_console_drilldownanswers "what brings people to this page" or "which pages compete for this term".get_search_console_opportunitiesshows how many queries sit in each position band and the clicks each band earns, and the measured click difference where Google shows an AI Overview.
Three rules apply when reporting any of them.
Position improves as the number falls, so get_search_console_trend reports
it as a delta, not a percentage change.
The most recent day or two are provisional. Search Console publishes on a two to three day delay at source, so those days are marked, counted separately, and must never be reported as a decline.
The AI Overview comparison refuses to conclude on a small sample. It covers the queries the Website tracks for rank, and below a usable sample it says so rather than presenting a two-query gap as a finding.
Query-level detail reaches back 75 days. For a longer window,
get_search_console_performance answers from monthly totals instead of
shortening the window without saying so.
Google Analytics
Three tools read already-synced Google Analytics data, and one asks Google live:
get_analytics_trafficreports sessions, page views and active users by page viewed or by session landing page. Landing pages also carry engaged sessions.get_analytics_breakdownreports where visitors came from and what they used: source, medium, channel group, campaign, country, device, browser, operating system, or new against returning.get_ai_conversionsreports enquiries, sign-ups and sales from visitors who arrived from an AI assistant, by assistant, beside Organic Search and the whole site. Conversion figures stay empty unless the property is confirmed to track them, and Google AI Overviews cannot be separated from ordinary search in Analytics.get_realtime_visitorsreports how many people are on the site right now, over a rolling window of about 30 minutes.
User figures are summed per row, so they are not a count of unique visitors to the site. Reporting them as one is the easiest mistake to make with these tools.
get_realtime_visitors is the only Analytics tool that calls Google live,
because no stored report can answer "who is on the site right now". The other
reads use stored data, which is fast and free, and going live would not make
Search Console fresher: the delay is Google's, not the sync's.
Index coverage
Clicks and impressions exist only for pages Google has indexed, so a page left out of the index is invisible in every other Google tool here. Three tools close that gap.
get_index_coverage reports index status across the pages that have been
inspected, plus the findings that follow: pages not indexed that still earn
impressions, pages where Google chose a different canonical, pages blocked by
robots.txt or a noindex tag, pages that changed after Google last crawled them,
and the rich results Google detected. Its counts describe the pages inspected,
not every page on the site, and the response states its own denominator.
inspect_url asks Google about one page, and it is the only way to see a
page that is not indexed at all. Verdicts are cached for 24 hours, and Google
sets a daily inspection allowance per Website, which the response reports.
list_sitemaps shows the sitemaps Search Console holds, when Google last read
each one and any errors. A sitemap that was never submitted, or that Google has
not read in weeks, stops new pages being discovered. It is read-only, because a
sitemap is submitted in Search Console itself.
How these tools report a missing connection
A Google connection is in one of four states, and only one returns figures. In every other state the tool refuses and names the fix, so a missing connection never reads as zero traffic.
| State | What the tool does |
|---|---|
| Not connected | Refuses, and says to connect it |
| Reconnect required | Refuses, and says to reconnect it, with the last successful sync date |
| Never synced | Refuses, and says to wait for the first sync |
| Ready | Returns figures. An empty range now genuinely means a quiet period |
get_google_integration_status lets an assistant asked "why is there no
traffic data" answer precisely instead of guessing. It is free, and it also
catches a healthy connection with no property selected, which otherwise
looks like "wait for the sync" and never resolves.
Example prompts
Show me tracked keyword positions for my main site, and separate the ones that have never been checked from the ones outside the top 20.
Which queries sit in positions 4 to 10, and how many clicks does that band earn? Then tell me whether an AI Overview is showing on them.
Which of my pages does Google show for 'ai visibility tracking'? I want to know if two of them are competing.
How many enquiries came from visitors who arrived from ChatGPT last month?
Which of my pages are not indexed but still earning impressions?
Where to go next
- Google rank tracking and AI Overview tracking, for what RankX AI tracks.
- Citations, two kinds, before reporting either citation set.
- Why traffic data is missing, for the four connection states in full.
- Metrics defined, for what each figure means.
Questions
Does reading Search Console or Analytics through MCP cost credits?
No. Every Search Console, Analytics and index coverage tool is free to call, and most read data RankX AI has already synced. In this group only run_rank_check spends credits.
Why are the last two days of Search Console data lower?
Google publishes Search Console data on a two to three day delay, so the most recent days are provisional. get_search_console_trend marks them, and they must not be reported as a decline.
Why is there no traffic data for my website?
Ask the assistant to call get_google_integration_status. It says whether Search Console and Analytics are connected, which property each uses and when each last synced. See why traffic data is missing.
Last updated