Who this is for
Sites with relevant rankings but weak click-through, unclear result snippets or several pages splitting the same search intent.
On-Page Automation flags lower-than-expected click-through rates and queries shared by several pages.
Part of the SEO & AI Search module. Part of this works today and part does not. The scope below says which is which.
Practical purpose
Prioritise an existing page revision before commissioning another page. Built and tested, with the first run through the Ciny controls pending. A person applies every change.
These are investigation signals, not diagnoses. Check the search intent, results layout and purpose of each page before changing titles, merging content or redirecting a URL.
Service scope
Sites with relevant rankings but weak click-through, unclear result snippets or several pages splitting the same search intent.
Query and page data, existing titles and descriptions, the actual offer and the owner who can approve a revision.
Click-through and page-overlap findings with proposed actions. A person reviews and releases the change.
Illustrative example
A title can name the service more clearly while keeping the promise accurate. That is a better test than adding a superlative the business cannot substantiate.
Compare comparable query-page windows, allowing for position changes and seasonality. Google may rewrite a title or snippet in search results.
How it works
Expected CTR by position is calculated from your snapshots where the data allows, rather than an industry chart that may not match your market. A textbook fallback is used when it does not.
Flag pages below the observed CTR curve. Inspect titles, intent and search-result features before proposing a test.
Multiple pages can legitimately appear for a query. Compare their intent and usefulness before deciding whether they should remain separate, be revised or be consolidated.
Rewrite, merge, redirect or leave alone. A finding without a recommended action is just a chart.
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 CTR curve and cannibalisation detection are built and tested on stored Search Console snapshots, with no live run through Ciny's controls yet. An action feed can pass findings to your own developer or coding agent. The SEO engine does not edit or publish your pages.
Signals in
Alex · Keyword tracker + action feed
Agree the workflow
Scope notes
A page earning fewer clicks than the site's observed CTR curve suggests. It merits investigation, but the cause could include intent, titles, result features or the mix of queries. The flag does not prove which fix will help.
From your own Search Console snapshots where there is enough data. When there is not, a textbook curve stands in.
No. It produces a recommended change. The SEO engine has no publish or deploy step, so a person on your side applies it.
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.