Who this is for
Teams reviewing search visibility changes across a relevant query set and needing to separate a short fluctuation from a sustained change.
Rank Tracking Automation shows you what moved and when.
Compare position, clicks and CTR across reported Search Console snapshots.
LiveStatus today · Agent: Piper
Part of the SEO & AI Search module. It runs for Ruh AI today. Account access and the connections it needs are agreed before it runs for you.
Practical purpose
Search Console average position per query, period comparisons, movers and lost keywords.
Identify changes worth investigating without treating a position change as proof of its cause. This is the averaged position Google reports, not a live rank check.
The position is Google's averaged figure, not a live rank check. Live rank checks, alerts, volume and CPC are in build. A missing query is a reason to investigate reporting limits, demand and ranking changes, not proof that a ranking has disappeared.
Service scope
Is this the right fit?
What to bring
The tracked queries, data source, matching reporting periods and consistent country and device filters. Current data sync is manual.
What you receive
Query positions, period comparisons and grouped movement observations. A change in position does not establish its cause.
Illustrative example
A query can lose average position while earning more clicks as it appears in new contexts. Review the page and impressions before calling that a failure.
How to evaluate the work
Use clicks, impressions, CTR and position together. Search Console average position is not a fixed rank for every user or location.
How it works
The workflow, step by step.
Compare the available query data
Search Console provides reported position, clicks and CTR. Search volume, CPC and live checks require separate supporting data and may not exist for every query.
Movement is compared window to window
The biggest position changes against the previous period, so a slide gets caught early rather than diagnosed later.
Silent losses are surfaced
Flag queries present in a previous window but absent now. Reporting limits or lower demand can also explain a gap, so investigate before calling it a lost ranking.
Alerts are in build
Drop, gain and new-keyword alerts are generated at each sync and de-duplicated. They are not yet shown in a dashboard or sent anywhere.
Evidence and scope
Search context and workflow facts.
5,400US searches a month for rank tracker
234,238Search Console rows stored for Ruh AI, 31 Jan to 10 Sep 2026
90-dayposition chart per keyword, on Google's averaged figure
Search volume: Google Keyword Planner, United States, pulled 31 Aug 2026. It is historical search demand, not a traffic forecast. Other figures describe the documented Ruh AI record, workflow scope or stated limitations. They are not promised results for your business. Read the Ruh AI evidence and measurement limits.
The system behind it
Keyword tracker
Built on stored Search Console snapshots, which is what makes window-to-window comparison and coverage gaps possible at all. Ruh AI's tracker held 234,238 Search Console rows from 31 Jan to 10 Sep 2026.
- Running on live data
- built for Ruh AI first
- approval controls depend on the workflow
Signals in
- Your data
- Your brand pack
- What worked last month
Piper · Keyword tracker
Agree the workflow
- data and access
- approval and delivery
- checks and limitations
Scope notes
Good to know.
- Each install serves one business and one site.
- The Ciny team runs each sync on demand, so positions are as current as the latest sync.
- It shows what moved, and a person reviews why before recommending a change.
How many keywords can it track?
The tracker uses reported queries rather than a hand-picked watchlist. The Ruh AI dataset read on 27 Aug 2026 had 34,062 distinct queries. Google withholds some data, and imports remain subject to reporting limits.
Can it tell me why a ranking dropped?
It shows reported movement and missing queries between windows. Neither establishes the cause. A reviewer must check data completeness, demand and the search results before recommending a change.
How often does it update?
Syncs run on demand, started by the Ciny team, and the latest few days of Search Console data are provisional.
Work in practice
Read the evidence. Then talk about your business.
Two stories with different evidence levels. Read each source and its limits.
All case studiesFirst-party measurement
Ruh AI
Organic leads, with the evidence attached.
Weekly organic leads rose from 6 in early July to 20 in the week of 24 August 2026. August paid spend was $0.
Discuss your goals- Weekly organic leads
- 6 to 20
- Evidence
- First-party
Published Ruh AI customer story
Rapid Innovation
A more connected marketing workflow.
Ruh AI reports 37% more leads for Rapid Innovation after introducing AI-supported research, publishing and lead qualification.
Discuss your goals- Reported leads
- +37%
- Source
- Ruh AI story
These studies explain the wider work behind Ciny. They do not establish results for every capability. Live, Available, In build and Planned labels still apply.
Explore Rank Tracking Automation. Start with the right scope.
We agree account access, connections and approvals with you before anything is switched on.