Google Search Console and GA4 Data in One Place: Read Real Google Numbers and Find Quick Wins

Most SEO tools show you estimates: guessed traffic, modelled keyword volumes, rankings checked from one location. Those estimates have their place, but the only source that knows how often your pages actually appeared in Google, how many people clicked them and which searches brought them is Google itself. That data lives in two free products: Google Search Console, which reports how your site performs in Google Search, and Google Analytics 4 (GA4), which reports what visitors do once they arrive. If you want to understand your organic traffic honestly, these are the numbers to start from.

The problem is that many site owners never open them, or open them and do not know what to look at. Search Console has dozens of filters and a few metrics that are easy to misread (average position is the classic one). GA4 has a new data model that confuses people who learned the old Universal Analytics. And neither tool tells you, in one screen, "here are the searches where a little work on one page could move you onto page one."

This guide covers both sides. First, the education: what Search Console and GA4 measure, the correct definitions of clicks, impressions, CTR, average position, sessions, users and key events, how to add and verify your site in Search Console, and how to find quick wins by hand. Then, exactly how Rutba brings this real Google data into your workspace: one read-only Google connection per workspace, a property picker that only offers what your account can read, a daily sync, a "Google Search" tab for every site, an "almost on page one" list of opportunities, and a site assistant that answers questions with your real numbers instead of guesses.

What "real Google data" means and why it differs from estimates

There are two broad families of SEO data.

First-party data comes from the systems that actually record the events. Google Search Console is first-party data about Google Search: Google logs every time a page of your site is shown in its results and every time someone clicks it. GA4 is first-party data about your own site: the tracking tag on your pages records visits and actions. Nobody has to model or extrapolate these numbers; they are counts (with some privacy filtering and sampling rules, explained below).

Third-party data comes from tools that observe search from the outside. They run searches from a chosen country and device, record which results appear, and combine this with clickstream panels and statistical models to estimate search volume and traffic. This is useful for things Google will never tell you, such as how your competitors rank or which keywords a domain you do not own appears for. But it is an estimate, and for your own site it is always less accurate than what Google reports directly.

Rutba uses both, and it is careful to label which is which. The "Google Search" tab described in this guide shows only Google's own numbers, nothing estimated. Keyword rank tracking and competitor analysis, which are separate features, use a third-party SERP data provider and say so in the interface. Keeping the two apart matters: when you make decisions about your own pages, you should base them on what Google actually recorded.

Why this matters for your business, not just for SEO

Real search data answers questions that matter to anyone who depends on organic traffic:

• Is my visibility in Google growing, flat or falling, and since when?
• Which searches actually bring people to my site, and which pages do they land on?
• Where do I appear often but get few clicks, meaning my title and snippet are not convincing?
• Which searches am I close to winning, where improving one page could bring meaningful traffic?
• Does the traffic I get from search turn into enquiries, sign-ups or sales?

The first four questions are answered by Search Console. The last one needs Analytics. Together they tell you whether your SEO work is producing results for the business, which is the only thing that really counts.

Google Search Console explained: the four core metrics

Search Console's Performance report for Google Search is built on four metrics. Each has a precise definition, published by Google in its Search Console Help documentation, and most misreadings come from ignoring those definitions.

Clicks

A click is counted when a user clicks a link in Google Search results that takes them to a page outside Google, on your site. Clicks on a result that opens something inside Google (for example, some search features) are not counted as clicks to your site. A click is not the same as a visit recorded in your analytics: the user might close the tab before your page loads, block your analytics tag, or decline cookies. That is why Search Console clicks and GA4 sessions from Google organic never match exactly, and they are not supposed to.

Impressions

An impression is counted when a link to your site appears in a search result that a user loaded. For a normal list of results, the link generally counts as an impression when it is on the page of results the user is viewing, even if they did not scroll down to it. Some features have their own rules, for example results inside a carousel or an expandable element may only count when they are actually shown. Impressions measure visibility, not attention: a high impression count means Google showed your page often, not that people looked at it.

CTR (click-through rate)

CTR is clicks divided by impressions, shown as a percentage. If a page received 40 clicks from 2,000 impressions, its CTR is 2%. CTR depends heavily on position (results near the top get more clicks), on the type of search (people searching for a quick fact may get the answer on the results page and never click), and on what else is on the page, such as ads, maps or video results. A "low" CTR is only meaningful when you compare similar searches at similar positions.

Average position

Average position is the metric that is misread most often. For a single search, your position is the position of your topmost result on that page. Search Console then averages this across all impressions. In other words, average position is weighted by impressions: a search where you appeared 1,000 times at position 12 counts far more than a search where you appeared 10 times at position 2.

Two consequences follow:

1. Average position can get "worse" while your SEO gets better. If you start appearing for many new searches at position 40, those new impressions pull the average down, even though nothing you already had lost ground.
2. The site-wide average position is almost meaningless on its own. It mixes your brand searches (often position 1) with long-tail searches deep in the results. It becomes useful when you look at it per query or per page, and when you watch the trend over time.

How Search Console filters and delays its data

A few more facts help you read Search Console correctly:

• Data lag. Performance data usually appears about two days late. The most recent days can also change slightly as Google finalises them.
• Retention. Search Console keeps around 16 months of performance data. If you want a longer history, you need to export or store it somewhere else.
• Anonymised queries. To protect user privacy, Google does not show very rare queries. Their clicks and impressions are included in the site totals but not in the query table, so the sum of the rows you see is usually lower than the chart total. This is normal.
• Row limits. The interface and the API return a limited number of rows per request. Very large sites never see every query in one table.
• Property versus page aggregation. Totals for the whole property count a search once even if several of your pages appeared, while page-level tables count each page. That is why adding up page rows does not reproduce the property total.

Google Analytics 4 explained: sessions, users and key events

Search Console stops at the click. Everything that happens after the click, on your site, is the job of Analytics. GA4 is event-based: every interaction, including a page view, is recorded as an event, and sessions and users are derived from those events.

Sessions

A session is a group of interactions by one user within a period of activity. By default in GA4, a session ends after 30 minutes of inactivity (this timeout can be changed in the property settings). If someone visits in the morning and again in the evening, that is usually two sessions. Sessions are the closest Analytics equivalent to "visits".

Users

GA4 identifies users through a browser identifier set by the tag, and optionally through a user ID or other signals if you configure them. GA4 has several user metrics. "Total users" counts the distinct users who logged any event in the period; "active users" counts those who had an engaged session or certain other activity, and is the "Users" figure many standard GA4 reports show by default. Because people switch devices, clear cookies or decline consent, any user count is an approximation of real people, not a census.

Key events

Key events are the events you mark as important for your business: a form submission, a purchase, a sign-up, a call button click. In 2024 Google renamed what GA4 used to call "conversions" to "key events" (the word "conversion" is now used mainly for Google Ads). Key events are only as good as your setup: if you never marked any event as a key event, the number will be zero, and that says nothing about your business.

Why Analytics and Search Console never agree

New users often expect Search Console clicks to equal GA4 organic sessions. They will not, for several legitimate reasons:

• Search Console counts clicks; GA4 counts sessions, which can include several page views, or none if the tag never fired.
• Consent banners, ad blockers and privacy browsers stop the GA4 tag for some visitors but have no effect on Search Console.
• GA4 attributes traffic to channels using its own rules; some Google traffic may be classified differently.
• Time zones and processing delays can differ between the two products.

The right approach is to use each tool for what it measures best: Search Console for visibility and clicks in Google, GA4 for behaviour and results on your site, and to compare trends rather than expecting identical totals.

How to add and verify your site in Google Search Console

Before any tool, including Rutba, can read your search data, your site must exist as a verified property in Search Console, and the Google account you use must have access to it. If you have never done this, here is the process.

Step 1: Choose the property type

Search Console offers two property types:

A Domain property gives you the complete picture and is what Google recommends when you can edit your DNS. A URL-prefix property is easier when you cannot touch DNS, for example on some managed hosting or when an agency only has access to the website, not the domain. You can have both for the same site; many site owners use a Domain property for the full view and URL-prefix properties for specific sections.

Step 2: Verify ownership

• For a Domain property, Search Console gives you a TXT record value. Add it in the DNS zone of your domain (at your registrar, your hosting control panel such as cPanel, or a DNS service such as Cloudflare). DNS changes can take from minutes to a day or so to propagate. Then return to Search Console and click "Verify". Leave the record in place: removing it can remove your verification later.
• For a URL-prefix property, the simplest methods are usually the HTML meta tag (pasted into the head of your home page; on WordPress, SEO plugins such as Rank Math or Yoast have a field for it) or the HTML file (uploaded to the root of your site). If your site already has the GA4 tag or Google Tag Manager installed with the same Google account, Search Console can verify you through them.

Step 3: Submit your sitemap and check indexing

Once verified, submit your XML sitemap (Indexing, then Sitemaps) so Google can discover your pages, and look at the Pages report to see which URLs are indexed and why others are not. These reports are not part of the performance data, but they explain a lot of what you see in it: a page that is not indexed cannot get impressions.

Step 4: Give the right people access

Search Console has owners, full users and restricted users. If an agency or a colleague manages your SEO, add their Google account as a user rather than sharing your password. For Rutba, the Google account you connect needs at least read access to the property. Rutba only ever asks for read-only permission, so restricted access is enough to read the numbers.

Step 5: Wait for data

A brand-new property starts collecting data from the moment it is created (and for Domain properties, Google may show some history). Give it a few days before drawing conclusions; remember the roughly two-day lag.

How to read your Search Console data by hand

You do not need any tool beyond Search Console to start making better decisions. Here is a practical routine.

1. Set the date range to the last 28 days and compare with the previous period. Twenty-eight days contains exactly four of each weekday, which removes weekly patterns from the comparison. Comparing with the previous 28 days shows the short-term trend; comparing with the same period last year helps for seasonal businesses.
2. Turn on all four metrics (clicks, impressions, CTR, average position) to see how they move together. Rising impressions with falling average position often just means you are appearing for more searches. Falling clicks with stable impressions points to a CTR problem, perhaps a new search feature above you or a less attractive snippet.
3. Open the Queries tab and sort by impressions. These are the searches Google associates with your site. Check that they match what you actually want to be known for.
4. Open the Pages tab and click a page, then go back to Queries. You now see which searches bring traffic to that page. This is the most useful view for improving content.
5. Filter by country and device if your audience is international or mostly mobile. Positions and CTR can be very different on mobile.
6. Look for anomalies: a sudden drop on a specific date may coincide with a site change, a migration, a technical error or a Google update. Annotate it and investigate.

How to find quick wins

"Quick wins" are searches where you already have visibility but are not yet getting the clicks you could. There are two classic patterns.

Pattern 1: Almost on page one. Queries where your average position is roughly between 8 and 20, and that have real impressions. These pages are already considered relevant by Google, but they sit at the bottom of page one or on page two, where very few people click. Moving them up a few positions often makes a much bigger difference than creating a new page from nothing.

To find them by hand: in the Performance report, open Queries, add a filter on position (Search Console lets you filter queries by position with "greater than" and "smaller than"), sort by impressions, and note the page that ranks for each query.

Then, for each candidate:

• Search the query yourself (in a private window) and look at what ranks above you. What does the searcher want: a definition, a comparison, a product, a local result, a how-to?
• Open your page. Does it answer that intent clearly near the top? Does the title use the words people search? Is the content complete compared with what ranks above you, and up to date?
• Improve the page for the reader: a clearer title and introduction, a section that answers the specific question, better structure with headings, updated facts, helpful internal links from related pages.
• Check technical basics: is the page indexable, fast enough, mobile-friendly, linked from other pages of your site?

Pattern 2: Good position, weak CTR. Queries where you rank near the top but get fewer clicks than you would expect compared with your other queries at similar positions. Often the title or meta description does not match what people want, or a rich result or search feature above you takes the attention. Rewriting the title and description to be specific and honest, and adding valid structured data where it genuinely applies, can help. Google may rewrite your title or snippet anyway; you can only make the best version available.

Two warnings:

• Do not chase every query. Focus on those with meaningful impressions and a clear connection to your business.
• Do not change a page every few days. Give Google time to recrawl and re-evaluate it, then compare 28-day periods.

Signs of keyword cannibalisation

If the same query appears with two or more of your pages, Google may be unsure which one to rank, and neither performs as well as one strong page would. Look at query-and-page combinations: when two pages share the same important query, consider merging them, clarifying their different purposes, or pointing internal links to the page you want to rank. This is a judgement call, not an automatic rule: sometimes two pages legitimately serve different intents.

Common problems when reading Google data, and their causes

• "My clicks dropped overnight." Check the date: the last two days are incomplete. Also check whether the drop is site-wide or limited to one page, one country or one device. A site-wide drop on a specific date is worth comparing with your change history and with known Google updates.
• "Average position went down but clicks went up." You probably started appearing for more searches deeper in the results. Look at the trend per query instead of the site average.
• "GA4 shows far fewer organic visits than Search Console clicks." Consent banners, ad blockers, a tag that loads late or only on some pages, or channel classification differences. Check that the GA4 tag is on every page.
• "Key events are zero." No event has been marked as a key event in GA4, or the event is not firing. This is a configuration issue in GA4, not a traffic problem.
• "Search Console shows nothing." The property may be new, may not match the version of the site that receives traffic (http versus https, www versus non-www in a URL-prefix property), or the site may not be indexed. A Domain property avoids the version mismatch.
• "The query table does not add up to the total." Anonymised rare queries and row limits. This is by design.

How Rutba brings real Google data into your workspace

Rutba integrates Google Search Console and Google Analytics 4 so that you see Google's own numbers next to your audits, fixes and content work, without exporting spreadsheets. The integration is built around a few principles: read-only access, one connection per workspace, properties chosen from the ones your Google account can genuinely read, and nothing estimated on the Google screen.

One Google account per workspace, read-only

A workspace in Rutba (a team) connects one Google account. The workspace owner or an admin does this once, in Settings → Google, by clicking "Connect Google" and signing in on Google's own consent screen. Rutba requests only:

• read-only access to Search Console (webmasters.readonly),
• read-only access to Google Analytics (analytics.readonly),
• your Google account email, to show which account is connected.

Rutba cannot change anything in your Search Console or Analytics: it cannot add or remove users, submit sitemaps, change settings or delete data. The scopes it asks for simply do not allow it.

On Google's consent screen you can untick permissions. If you do not grant both Search Console and Analytics, Rutba tells you clearly that not every permission was granted and that you can connect again and tick all the boxes to use both. The sign-in flow is protected against replay: the request is bound to your session and your workspace and expires after 15 minutes, so a Google sign-in cannot be attached to another workspace.

Because the connection belongs to the workspace, every site in that workspace can use it, and every team member with access to a site can see its Google numbers. Only people allowed to manage a site can change which properties it uses.

Choosing each site's properties

After connecting, open a site and go to its Google Search tab. The first time, Rutba shows a property picker:

• a Search Console list containing every property your connected account can read (Domain properties and URL-prefix properties alike; unverified entries are left out),
• an Analytics 4 list containing every GA4 property your account can read, shown with the property name and the account it belongs to.

Rutba reads these lists live from Google only when you open the picker, and it puts the Search Console properties that match the site's domain first, marked with a check. You can link Search Console only, Analytics only, or both. Rutba accepts only a property that appears in your account's list: you cannot type a property ID by hand, so a site can never be linked to data your Google account cannot read.

If the list is empty, the account has no Search Console properties yet, and Rutba tells you to add and verify the site in Search Console first (see the steps above). Click Save and read the data, and Rutba starts reading the last 90 days from Google immediately; it usually takes about a minute. You can change the properties later with Change properties.

What Rutba syncs, and how often

Rutba refreshes every linked site once a day, and also right after you link or change its properties. You can also press Refresh on the tab to request a new sync. Each sync reads:

• 90 days of daily totals from Search Console: clicks, impressions and average position per day;
• 90 days of daily totals from GA4: sessions, total users and key events per day;
• the top 500 query-and-page pairs of the last 28 days from Search Console, with clicks, impressions, CTR and position for each pair. This list is replaced on every sync, so it always reflects the most recent 28 days.

Because Search Console data lags by about two days, Rutba's date ranges end two days before today, and it asks Search Console for finalised data only, so the days you see are complete rather than partial. If Google returns an error for one source, for example Analytics refuses access to a property, Rutba keeps the other source, shows the error message on the tab, and tries again on the next sync.

The daily history is stored day by day, so over time Rutba keeps the days it has synced for as long as the site is linked, while each sync refreshes the most recent 90 days.

The "Google Search" tab of each site

Once the first sync has run, the tab shows Google's numbers for that site. In words, the screen contains:

• Status line. Badges showing the linked Search Console property and Analytics property, the date of the last update, and the Refresh and Change properties buttons. If a sync had a problem, the message appears here.
• Period note. The exact dates of the last 28 days being shown, compared with the 28 days before, and a reminder that Google data is about two days behind.
• Metric cards. For Search Console: clicks, impressions, CTR and average position. For Analytics: sessions, users and key events. Each card shows the value for the last 28 days and the percentage change against the previous 28 days, in green when it improved and red when it got worse. For average position the colour logic is reversed, because a lower number is better.
• 90-day chart. A line of clicks per day over the last 90 days (or sessions per day if only Analytics is linked), so you can spot drops, spikes and trends at a glance.
• Almost on page one. The opportunities list, described in the next section.
• Top queries. The 20 query-and-page pairs with the most clicks in the last 28 days, with clicks, impressions, CTR and position, and the page that ranks for each query.

All numbers on this tab come from Google. Rutba does not estimate, extrapolate or "correct" them. Two calculations are Rutba's own, and both follow Google's method: the 28-day CTR is total clicks divided by total impressions, and the 28-day average position is weighted by impressions, the same way Search Console computes it, so a day with many impressions counts more than a quiet day.

"Almost on page one": your quick-win list

This is the section most site owners use first. Rutba lists up to 15 query-and-page pairs from the last 28 days where:

• your average position is between 8 and 20, the bottom of page one and page two, and
• the query has real impressions (at least 20 in the period), so it is not a one-off.

The list is sorted by impressions, so the searches with the most potential come first. Each row shows the query, the page of your site that ranks for it, its position, impressions and clicks.

This is the same "Pattern 1" analysis described earlier, done for you every day. What it does not do is promise anything: moving from position 12 to position 6 depends on the quality of your page compared with the others, on the intent of the search, and ultimately on Google's ranking systems. What it gives you is a short, prioritised list of pages where improvement most often pays off, based on Google's own data rather than guesswork.

A practical way to use it:

1. Pick the top two or three rows.
2. Search each query yourself and compare your page with what ranks above it.
3. Improve the page for the reader, using Rutba's other tools where they help: the SEO audit to catch technical issues on that page, the fix suggestions for titles, descriptions and structure, the content tools for gaps.
4. Note the date of your change, then check the tab again over the following weeks, comparing 28-day periods.

The site assistant answers with your real numbers

Rutba includes a site assistant ("Ask your site") that answers questions about one site in plain language: "Why did my traffic drop?", "Which pages should I improve first?", "Which searches bring me the most visitors?" When a site is linked to Google, the assistant receives a compact summary of that site's real Google data with each question: the totals of the last 28 days and the 28 days before, the top queries and the "almost on page one" opportunities, labelled as real data from Search Console and GA4, synced daily and about two days behind.

When a site is not linked, the assistant is told exactly that: Search Console is not linked, so clicks, impressions and queries are unknown; or Analytics is not linked, so visitors and conversions are unknown. Its instructions forbid inventing numbers, so it says what is missing and how to get it instead of guessing. Assistant conversations are private to the person who writes them, and asking questions uses your workspace's AI credits, depending on your plan.

Keyword rank tracking and competitors are separate features

It is worth being precise about what the Google integration does not do, because Rutba has other features that look similar.

• Keyword rank tracking (the Keywords tab) checks the position of keywords you choose, for a chosen country and device, by running a search through Rutba's SERP data provider and recording the results up to the first 100 positions. It keeps a history per keyword, so you can track keywords even before they get impressions in Search Console. These positions are snapshots of one search from one location and device, read best as a trend, and they are not the same as Search Console's impression-weighted average position. How often they are checked depends on your plan.
• Competitors (the Competitors tab and content insights) compares your site with competitor domains, either added by you or suggested from the provider's data, and can show content gaps: keywords where a competitor appears in the top 20 and you do not appear in the top 100, according to the provider's database.

Those features use third-party data and are labelled as such. The Google Search tab uses only Google's data. The two complement each other: Search Console tells you the truth about your own site, the provider data tells you about the wider market and your competitors.

Privacy, security and Google's Limited Use policy

Connecting a Google account to any service is a trust decision. Here is exactly how Rutba handles it, as described in Rutba's privacy policy.

• Read-only access. Only webmasters.readonly and analytics.readonly, plus your email. Rutba cannot modify anything in your Google products.
• What is read. The list of Search Console sites and Analytics properties your account can see; and for the properties you link to a site, daily totals (clicks, impressions, average position, sessions, users, key events) and the top queries and pages of the last 28 days. Nothing else.
• Encrypted tokens. The access and refresh tokens Google issues are encrypted at rest and are never sent to your browser. Tokens are refreshed automatically shortly before they expire.
• How it is used. Only to show these numbers to you and your team, to point out improvement opportunities, and, when you ask the site assistant a question, to include a short summary of these numbers in that request so the answer is based on real data.
• Limited Use. Rutba's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is not sold, not used for advertising, and not shared with third parties except the assistant request described above, made at your request.
• No model training. Google user data is never used to develop, improve or train generalised AI or machine-learning models.
• Activity log. Connecting Google, linking a site's properties and disconnecting are recorded in the workspace's audit log, with who did it.

Disconnecting at any time

In Settings → Google, the owner or an admin can click Disconnect. Rutba asks Google to revoke the token and deletes the stored connection, which stops all access immediately. You can also remove Rutba's access from your Google account at any time at myaccount.google.com/permissions. The numbers that were already synced stay in Rutba until you remove the sites; removing a site deletes its numbers.

If Google stops accepting the connection (for example because you removed access in your Google account or the consent expired), Rutba marks the connection as expired, shows a clear message on the site tabs and in settings, and asks you to connect again. It does not keep retrying with a token Google has refused.

Who this is for

• Site owners and small businesses who want to know, in one screen and in their own language, whether search traffic is growing and which pages to improve next, without learning every corner of Search Console.
• Online stores that want to see which product and category searches bring visitors, and whether those visitors become orders (through GA4 key events such as purchases).
• Bloggers and publishers who need to find articles that are close to page one and worth updating, rather than writing new articles blindly.
• Agencies and consultants managing several client sites in one workspace, who want the same view for every site and a quick-win list to plan monthly work. Each workspace connects one Google account, so an agency can use an account that has been given read access to its clients' properties.
• Arabic, Turkish and international sites: the interface is available in Arabic (right to left), English and Turkish, and the queries are shown exactly as people typed them, in any language.

Practical checklist before and after connecting

Before connecting:

• The site is added and verified in Search Console (preferably as a Domain property).
• The GA4 tag is installed on every page, and your important actions are marked as key events.
• The Google account you will connect has at least read access to both properties.
• You know which person in your workspace (owner or admin) will connect it.

After connecting:

• Each site in Rutba is linked to the correct Search Console property and GA4 property.
• The first sync has completed and the tab shows numbers for the last 28 days.
• You have read the "almost on page one" list and chosen two or three pages to improve.
• You have noted the date of any significant change so you can compare 28-day periods later.
• You check the tab regularly (weekly is plenty for most sites) rather than daily.

Mistakes to avoid

• Judging the last two days. They are incomplete. Rutba already ends its ranges two days back, but keep this in mind in Search Console too.
• Treating site-wide average position as a score. It is an impression-weighted average of very different searches. Look at it per query and as a trend.
• Expecting clicks to equal sessions. They measure different things through different systems.
• Linking the wrong property. A URL-prefix property for http://example.com/ will not contain traffic for https://www.example.com/. When in doubt, use a Domain property.
• Optimising for queries that do not fit your business. Impressions for irrelevant searches are not opportunities.
• Changing pages constantly. Give Google time to recrawl, then compare.
• Using tricks to raise CTR or rankings. Misleading titles, fake reviews in structured data or doorway pages violate Google Search Central's guidelines and can do lasting damage. Rutba will not suggest them.
• Believing any tool can guarantee rankings. Google decides rankings. Real data helps you make better decisions; it does not control the outcome.

How Google data connects with Rutba's other services

Real search data is most useful when it drives action. In Rutba it sits next to the other services:

• The SEO audit checks your pages for technical and on-page issues; when a page appears in "almost on page one", the audit tells you what is holding it back technically.
• SEO fixes turn findings into concrete suggestions, such as better titles and descriptions, which is exactly what weak-CTR queries need.
• Safe changes make sure any fix applied to your site goes through a restore point, a health check and automatic rollback if something fails.
• Rutba AI, including the site assistant, uses your Google numbers to answer questions with real data instead of generic advice.
• AI search visibility covers the other side of modern search: whether AI assistants mention your brand, which Search Console does not measure.

Getting started in five steps

1. Create your workspace in Rutba and add your site. You can run the free SEO check first if you want to see your site's state before signing up.
2. Make sure the site is verified in Search Console and that GA4 is installed, using the steps in this guide.
3. Connect Google in Settings → Google (owner or admin), and grant both read-only permissions.
4. Open the site's Google Search tab, choose its Search Console and Analytics properties from the list, and click Save and read the data.
5. Start with "almost on page one": pick a few pages, improve them with the audit and fix tools, and track the 28-day comparison in the following weeks.

Related features such as keyword tracking, competitors and the AI assistant, and the number of sites you can add, depend on your plan; see pricing for the current details.

Your Google data already exists; it is just scattered across tools most people rarely open. Rutba brings Google's own numbers next to your audit, your fixes and your content work, so every decision starts from what really happened in search. Start your free trial and connect Google in a few minutes, or run the free SEO check to see where your site stands today.