Connecting Google

Two of AugRank’s connections go through Google: Search Console, which is where your ranking, impression and click figures come from, and Analytics, which tells you whether the pages gaining impressions are actually gaining visits. Both are read-only — AugRank never changes anything in either — and both are optional. The product audits and writes without them; the dashboards are just emptier.

Both share one Google sign-in. You connect once, from the setup wizard or from Settings → Connections, and Analytics rides on that same authorisation.

Before you start: which Google account?

This is the step that goes wrong most often, and it goes wrong before AugRank is involved at all. Google only lets AugRank read a site that the signed-in account already has access to in Google’s own tools. So, before you press Connect:

1. Open search.google.com/search-console and sign in. If your site is listed there, note which Google account you used — that is the one to connect.
2. If your site is not listed, somebody else may own it: a web developer, an agency, a colleague who set it up. Ask them to add your Google account in Search Console under Settings → Users and permissions. Any level works — Owner, Full or Restricted; all three can read the reports. What does not work is an owner Google has not yet verified: the property is listed for that account but reports nothing, and AugRank will say it found no matching property.
3. If nobody owns it yet, you verify it yourself — see Verify your site below. It takes about ten minutes and one change to your domain’s DNS.

Connecting Search Console

1. In the setup wizard, or on Settings → Connections, press Connect Google Search Console.
2. Google opens. Choose the account from the step above and allow the one permission it lists: View Search Console data for your verified sites.
3. You come back to AugRank. It reads the list of sites that account can see and picks the one that matches your domain — a domain property (the whole of example.com, every subdomain) is preferred over a URL prefix (https://example.com/ only), because it carries more data.

When it works, the Connections row reads Connected and names your site. If it does not, you will see one of these instead:

“We connected, but found no matching property”

The sign-in worked, but that Google account does not have your site — or has it only as an owner whose verification never completed. AugRank offers three ways out, right on the screen:

• Switch account. Press Connect again and pick a different Google account. Use this if you have more than one and simply chose the wrong one.
• Ask whoever manages your site. AugRank drafts the email; you send it. They add your account in Search Console, and you press Connect again.
• Verify the site yourself. AugRank shows the exact DNS record to add. See the next section.

Verify your site

Verification is how you prove to Google that you control a domain. You do it once, in Google’s tool, and it is what turns “no matching property” into a connection.

1. Go to Search Console, press Add property, choose Domain, and type your domain without https:// or www — just example.com.
2. Google shows a TXT record: a line of text beginning google-site-verification=. Copy it.
3. Sign in to wherever your domain is registered — GoDaddy, Namecheap, BigRock, Cloudflare, Hostinger — open its DNS settings, and add a new record: type TXT, name @ (or leave it blank, depending on the registrar), value the line you copied.
4. Back in Search Console, press Verify. If it says the record was not found, wait — DNS changes take from a few minutes to an hour to appear — and try again. Nothing is lost by waiting.
5. Once verified, return to AugRank and press Connect again with the same Google account.

If you are not sure where your domain is registered, whoever built your website will know, and the wizard’s Draft email route is written for exactly that conversation.

Connecting Google Analytics

Analytics needs no second sign-in. When you connect Google, AugRank also asks for read access to Analytics; what is left is telling it which Analytics property is your site, because a property is named by whoever created it and often does not mention the domain at all.

1. Open SEO → Search performance and, in the Traffic panel, press Choose an Analytics property.
2. AugRank lists every Analytics property the connected Google account can see, each with the account it belongs to and its numeric id, so two similar names can be told apart. Press Use this on yours.

Two things commonly stop this:

• “This Google account owns no Analytics properties.” The Analytics for your site lives under a different Google account, or nobody has set one up. Ask whoever manages your site to add your account in analytics.google.com under Admin → Property access management as a Viewer — that is all AugRank needs — then press Choose again.
• “Permission not granted.” The Analytics box was unticked on Google’s consent screen. Go to Settings → Connections, Disconnect Google, and connect again leaving both permissions ticked.

Only GA4 properties are listed. If your site still has an older “Universal Analytics” property, Google stopped collecting data for it in 2024 and it reports nothing; create a GA4 property in Analytics first.

Connected, but empty

Both connections can be working perfectly and still show nothing, and the screens say so rather than reporting an error:

• Search Console needs a few days of traffic before it reports anything for a newly verified site, and its figures always run two to three days behind. A site verified today shows its first numbers towards the end of the week.
• Analytics reports only what the tracking code has seen. A GA4 property whose tag is not on the site’s pages has nothing to show. Whoever built the site installs the tag; AugRank only reads the result.

Disconnecting

Settings → Connections → Disconnect deletes the stored authorisation from AugRank at once. It does not remove anything from your Google account; to revoke AugRank’s access from Google’s side as well, open myaccount.google.com/permissions. Ranking data already read stays in your AugRank workspace; nothing new is read.