Google Search Console integrationPlanned
Search Console data, turned into a to-do list
The Google Search Console integration is planned. It is designed to read your search performance with read-only access, combine it with ROOKON’s analytics and surface the changes most likely to bring more visitors from search, as part of the Marketing Engine add-on.
The problem
Search Console tells you what happened, not what to do
The data is all there: queries, pages, clicks, impressions and positions. Working out which page to fix first, and whether the fix helped, is left to you.
- Thousands of rows and no priorities
- No link between search traffic and signups
- No record of which change moved which number
Live demo 1 of 2
Your pages, ranked by opportunity
Simulated Search Console data grouped by page, with the opportunities ROOKON finds in it. Select one to see the drafted change.
- Switch to Queries
- Prepare the change for a low-CTR page
rookon · marketing engine · search · acme.example
Simulated data- Clicks
- 4,090
- Impressions
- 50,640
- Avg CTR
- 8.1%
- Avg position
- 7.2
Opportunities found (9)
Low click-through for “invoicing software for freelancers”
6.0% CTR at position 3.4, where your site usually gets 22.6%. 6,840 impressions in 28 days.
Title tag · suggested by your AI provider (simulated)
/
Clearer title for “invoicing software for freelancers”
Search engines can’t be split per visitor, so title and content changes are measured before and after instead of A/B tested.
How ROOKON helps
What you get
Read-only access
ROOKON asks for the webmasters.readonly scope. It can read search performance for the properties you select and cannot change settings, submit sitemaps or remove URLs.
You choose the properties
Connect only the Search Console properties that belong to your project; nothing else is read.
Joined with your analytics
Queries and landing pages are combined with ROOKON’s own conversion data, so opportunities rank by the signups they could bring, not only by clicks.
Tokens stored like keys
The connection token is envelope-encrypted at rest and can be revoked in ROOKON or in your Google account at any time.
Live demo 2 of 2
Did the new title help?
Title and content changes are measured before and after they ship. This simulated impact report uses a 28-day window.
- Read why some changes are still collecting
rookon · acme-cloud · impact of changes
Simulated dataEach change: 28 days before vs. 28 days after.
12 NovLive
Conversion rate · pages ROOKON changed
4.93% → 5.73%
+0.8 pp since the first ROOKON change
Bounce rate · same pages
41.5% → 39.0%
−2.5 pp since the first ROOKON change
ROOKON changes
1 improved of 1 measured
0 no significant change · 0 worse · 3 collecting
Conversion rate · /billing · 7-day rolling
| Time | conversion rate |
|---|---|
| 14 Sept | 3.1% |
| 15 Sept | 3.1% |
| 16 Sept | 2.7% |
| 17 Sept | 2.5% |
| 18 Sept | 2.5% |
| 19 Sept | 2.4% |
| 20 Sept | 2.5% |
| 21 Sept | 2.8% |
| 22 Sept | 2.7% |
| 23 Sept | 2.7% |
| 24 Sept | 2.9% |
| 25 Sept | 2.9% |
| 26 Sept | 2.9% |
| 27 Sept | 3.0% |
| 28 Sept | 2.9% |
| 29 Sept | 3.2% |
| 30 Sept | 3.5% |
| 1 Oct | 3.4% |
| 2 Oct | 3.6% |
| 3 Oct | 3.7% |
| 4 Oct | 3.5% |
| 5 Oct | 3.6% |
| 6 Oct | 3.5% |
| 7 Oct | 3.4% |
| 8 Oct | 3.7% |
| 9 Oct | 3.3% |
| 10 Oct | 3.1% |
| 11 Oct | 3.5% |
| 12 Oct | 3.8% |
| 13 Oct | 3.9% |
| 14 Oct | 3.7% |
| 15 Oct | 3.2% |
| 16 Oct | 3.6% |
| 17 Oct | 3.9% |
| 18 Oct | 3.9% |
| 19 Oct | 3.7% |
| 20 Oct | 3.7% |
| 21 Oct | 3.8% |
| 22 Oct | 4.4% |
| 23 Oct | 4.6% |
| 24 Oct | 4.5% |
| 25 Oct | 4.3% |
| 26 Oct | 4.3% |
| 27 Oct | 4.3% |
| 28 Oct | 4.4% |
| 29 Oct | 3.9% |
| 30 Oct | 3.7% |
| 31 Oct | 3.6% |
| 1 Nov | 3.7% |
| 2 Nov | 3.8% |
| 3 Nov | 3.7% |
| 4 Nov | 3.7% |
| 5 Nov | 3.8% |
| 6 Nov | 3.7% |
| 7 Nov | 3.7% |
| 8 Nov | 3.6% |
| 9 Nov | 3.7% |
| 10 Nov | 3.6% |
| 11 Nov | 3.7% |
| 12 Nov | 4.1% |
Shaded: baseline and after windows of the selected change.
It was better before
“Release v2.15.0: new onboarding checklist”
Bounce rate +2.6 pp (32.9% → 35.5%)
p < 0.001 (Holm-adjusted) · 14 days before vs. after
Either way, ROOKON won’t propose this exact change again. A different approach to the same page is still allowed.
Overlaps with “Release v2.15.0: new onboarding checklist”, “Batch the report queries (one query instead of one per invoice)”, “Make “Company size” optional and add “Just me””, so part of the difference may come from that change.
Observed changes between equal windows before and after each change, tested for significance (two-proportion z-test for rates, Welch’s test for durations, Holm-adjusted, p < 0.05). This shows association, not proof of cause: seasonality, campaigns and other releases can contribute, so overlapping changes are flagged.
How the connection is designed to work
- 01
Connect
An owner or admin signs in with Google and grants read-only access.
- 02
Pick properties
Choose the Search Console properties that match your project’s domains.
- 03
Daily sync
Search performance is imported once a day, since Search Console publishes it with a delay.
- 04
Opportunities
Findings appear in the Marketing Engine, ready to test or to prepare as a change.
FAQ
Common questions
Is the Search Console integration available now?
Not yet. It is planned as part of the Marketing Engine add-on, and this page will be updated when it is available.
What permissions does ROOKON ask for?
Read-only access to search performance (the webmasters.readonly scope) for the properties you choose. ROOKON can’t change anything in Search Console.
How fresh is the data?
Search Console publishes performance data with a delay, so ROOKON is designed to sync once a day rather than in real time.
Can I disconnect it?
Yes. Disconnect it in ROOKON or revoke access in your Google account. The stored token is deleted and imported data follows your retention settings.
Connect search data to real improvements
Sign up today and connect Search Console when the integration is available.