Connect your website with Google: Search Console and Analytics
With the Google connection, the ERP knows what Google does with each page of your website: how many times it shows it (impressions), how many times people click it (clicks), in what position it appears, which queries bring traffic to it and, with Analytics, how many visits and conversions it gets. With that it measures each page after it is published and finds the pages of yours that Google shows for the same query. You connect it in Marketing → Search visibility, Sites tab, your website’s Google card.
What do I need?
Three things, which are usually prepared by whoever looks after your website or by ERP support:
- A Google service account: a Google account for programs, not for people. It is created in Google Cloud and its key, a
.jsonfile, is downloaded. The ERP signs in to Google with it and only reads Search Console and Analytics. - Your Search Console property: the domain one (
sc-domain:tuweb.com) or the URL prefix one (https://tuweb.com/), exactly as it appears in Search Console. - Your Analytics (GA4) property: its number (for example
412345678), in Analytics → Admin → Property settings → Property ID. It isn’t the measurement ‘G-…’ ID.
How to create the service account and how to give it access is in the support guide, step by step.
If you also want the Looker Studio dashboard, you need a Google sheet shared with the service account as Editor: the ERP writes your website’s map to it. It is in the Looker Studio dashboard.
How do I connect it?
- Open your website in the Sites tab and scroll down to the Google card.
- Expand Company service accounts and click New service account. Give it a name if you want and paste the entire content of the key’s
.jsonfile. Click Add. - The account is selected for your website. The card shows its email (something like
erp@tu-proyecto.iam.gserviceaccount.com): add it as a user in Search Console (the ‘Restricted’ permission is enough) and in Analytics (‘Viewer’ role). - Type the Search Console property and the Analytics one. If you type only the domain (
tuweb.com), the domain property is assumed; an address is saved with its trailing slash, as Google gives it;properties/412345678works the same as412345678. - Click Test connection.
The key is stored encrypted and isn’t shown again: of the account, only its email can be seen. To change it, paste the new one into its box and click Change the key. The same account works for all the company’s websites.
Adding and changing the connection or the properties requires the Create permission on Search visibility; testing it, Changes; deleting an account (only if no website uses it), full access.
What does ‘Test connection’ say?
It tests each thing separately and says which one fails and why:
| Line | OK | If it fails |
|---|---|---|
| Account | The key is valid | Google doesn’t accept the key: it was deleted, the account no longer exists or a new key has to be created |
| Search Console | The account reads your property, and with what permission | The account has no access (with the properties it can see, and the one you may have meant), the property is mistyped, or the Search Console API isn’t enabled in the Google Cloud project |
| Analytics | The account reads your property, with its sessions for the last 28 days | The account has no access, the number isn’t a GA4 property, or the Analytics Data API isn’t enabled |
| Sheet (if your website has one) | The account edits the sheet and can write its ‘Mapa’ tab | The sheet isn’t shared with the account, or it is shared as Viewer and not as Editor; it doesn’t exist; the ‘Mapa’ tab belongs to someone else or is protected; or the Google Sheets API isn’t enabled |
To know that it can write, the sheet test really writes the header row of the ‘Mapa’ tab (and creates the tab if it isn’t there), just as the synchronisation would.
If Analytics has no key events (Analytics conversions: a form submitted, a purchase), the test passes but warns you: conversions will show as zero until you mark them in Analytics (Admin → Key events).
The list of accounts says for each one when it was tested and how it went.
When is Google read?
In each synchronisation of your website, at the same time as the website is read. Google provides the data with a delay of a few days, so the ERP works in complete weeks: it requests a week’s data when it is no longer going to change, and until then the summary says Up to date and requests nothing. The summary has a Google line with what has been saved.
The first time, the last 26 weeks are fetched; after that, each new week.
What do I see for each page?
On each page’s record (Map tab), the Performance on Google section:
- For the last four weeks with data: impressions, clicks and their percentage (CTR), average position, sessions (and how many with engagement) and conversions.
- The queries that bring traffic to it, with their impressions, clicks and position, for the last 28 days. If Google also shows another page of yours for the same query, it says so: ‘also appears: …’.
If something is missing (the website not connected, a page with no data yet, Analytics without key events), the section says so.
What is a shared-query conflict?
Two pages of yours that Google shows for the same query and that share its impressions: the second gets at least 20 % of those the first has. Google doesn’t know which is the right one and keeps alternating: it is cannibalisation measured by Google, not by the titles. It appears in the conflicts tray with the queries they share and the impressions and position of each page, and it is dealt with like any other.
Can I measure a page a month after publishing it?
Yes, with the example schedule Medir a los 30 días, which is created with the publishing board: 30 days after the ERP sees a page published, you get a notification with what it has achieved since it was published and the queries that bring traffic to it. It starts paused: turn it on in Tasks → Schedules when you want it.
Can I ask the assistant to do it?
Yes: ‘how many impressions does the time tracking page have?’, ‘which queries bring visits to the Verifactu article?’, ‘how has the page we published a month ago done?’. The assistant reads what the ERP has saved; it doesn’t go into Google.
What doesn’t it do?
- It isn’t an analytics dashboard. The ERP stores what it needs to decide: by page and week, and the main queries of each page. The full reports are in Search Console, Analytics and the Looker Studio dashboard.
- It doesn’t give the search volume of topics you haven’t written about: Google only counts what it already shows.
- Anonymous queries don’t appear. Google doesn’t provide very infrequent queries: the sum of a page’s queries is lower than its impressions.
- It doesn’t write to Search Console or Analytics. It only reads them. The only thing it writes is the map sheet, if you give it one.
Back to search visibility.
More about Search positioning
- Guest posts
- Proposed clusters
- Query real search data: what it costs
- Cross-checks between SEO and ads
- Add your website and test the connection
- Search data: volume, difficulty and Google results
- Marketing guidelines: what marketing tells the plan
- The editorial calendar
- A piece’s brief
- The content map: what each page of your website targets
- The Looker Studio dashboard: your content map alongside what Google measures
- The editorial plan