Who this is for
Teams who want to compare their pages and search visibility with named competitors, knowing the tools are built but have not yet run on live data.
Competitor Intelligence has a competitor site crawler and search share of voice, both built but not yet run on live data.
Part of the Website Optimiser module. Part of this works today and part does not. The scope below says which is which.
Practical purpose
Compare your pages and search visibility with named competitors once it runs. It has not run on live data yet, and share of voice needs paid search data switched on.
The crawler reads the sitemaps of competitors you name, stops at 4,000 pages per run and stores titles, headings, word counts and internal links for analysis only. Share of voice needs paid search data, which is switched off, and the first crawl needs boundaries agreed with you.
Service scope
Teams who want to compare their pages and search visibility with named competitors, knowing the tools are built but have not yet run on live data.
An agreed competitor set, query group, market, device and collection schedule would be needed for a meaningful comparison.
In build. A competitor crawl and share-of-voice view once boundaries and paid search data are agreed. No live competitor dashboard exists today.
Illustrative example
A future comparison might show different domains appearing for the same query group across two stored periods. It would not reveal their private sales results.
Hold the query set and collection conditions constant. Search snapshots cannot establish competitor revenue or the cause of a visibility change.
How it works
Name the competitor domains, agree the crawl boundaries and decide whether paid search data is switched on. Search Console data describes your own site, not competitors' rankings.
Which domains appear for the queries you track, and the queries where competitors outrank you.
A competitor gaining ground on a query you own is a signal, and it currently goes unnoticed.
A live run on agreed competitors comes before it is offered as Live.
Evidence and scope
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
The competitor crawler and share-of-voice views are built in the keyword tracker. Neither is connected to Ciny's controls yet, and no live run is recorded.
Signals in
Piper · Keyword tracker
Agree the workflow
Scope notes
Not yet. It is built but has not run on live data, so we class it as In build.
So you can see where it is heading and what it needs before a first run: the competitors you name, agreed crawl boundaries and a decision on paid search data.
Pages crawled from the competitor sitemaps you name, and paid search result snapshots for your tracked keywords. Search Console data describes your own site only.
Work in practice
Two stories with different evidence levels. Read each source and its limits.
All case studiesFirst-party measurement
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 goalsPublished Ruh AI customer story
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 goalsThese studies explain the wider work behind Ciny. They do not establish results for every capability. Live, Available, In build and Planned labels still apply.
Part of this works today. We show you exactly which part before anything is agreed.