Ciny AI

Competitor Intelligence is in build and needs live evidence.

Competitor Intelligence has a competitor site crawler and search share of voice, both built but not yet run on live data.

In buildStatus today · Agent: Piper

Part of the Website Optimiser module. Part of this works today and part does not. The scope below says which is which.

A competitor site crawl and search share of voice, in build.

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.

Is this the right fit?

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.

What to bring

An agreed competitor set, query group, market, device and collection schedule would be needed for a meaningful comparison.

What you receive

In build. A competitor crawl and share-of-voice view once boundaries and paid search data are agreed. No live competitor dashboard exists today.

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.

How to evaluate the work

Hold the query set and collection conditions constant. Search snapshots cannot establish competitor revenue or the cause of a visibility change.

The workflow, step by step.

  1. Agree the competitors and the boundaries

    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.

  2. Share of voice is computed from search snapshots

    Which domains appear for the queries you track, and the queries where competitors outrank you.

  3. Movement on their side would be surfaced

    A competitor gaining ground on a query you own is a signal, and it currently goes unnoticed.

  4. It ships once it has run on live data

    A live run on agreed competitors comes before it is offered as Live.

Search context and workflow facts.

210US searches a month for competitor analysis tool
4,000 pagescrawl cap per run for each named competitor domain, stored for analysis only
0 live runsrecorded so far. Hence In build

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.

Keyword tracker

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.

  • In build: built, not yet run
  • built for Ruh AI first
  • approval controls depend on the workflow
Read the first-party Ruh AI case study

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

Good to know.

  • It is built and has not yet run on live data, so it is In build.
  • Share of voice is a directional measure.
  • Why a competitor gains ground remains a human judgement.

Before you get started

Prefer to talk it through? Email hello@ciny.ai.

Is this available?

Not yet. It is built but has not run on live data, so we class it as In build.

Why list it now?

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.

What data would it use?

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.

Read the evidence. Then talk about your business.

Two stories with different evidence levels. Read each source and its limits.

All case studies

First-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.

  • PostHog lead events, test entries excluded. Google Ads. August 2026.
  • Measured on our own site. Observed results, not a guarantee or proof of causation.
Discuss your goals
Weekly organic leads
6 to 20
Evidence
First-party
Read the study

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.

  • Source: the published Rapid Innovation story on ruh.ai.
  • Publisher-reported results. Measurement period and methodology are not disclosed. Not a measured Ciny result.
Discuss your goals
Reported leads
+37%
Source
Ruh AI story
Read the study

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 Competitor Intelligence. Ask what works today.

Part of this works today. We show you exactly which part before anything is agreed.