Connect Google Search Console
Add our reader as a user, paste your property, done. Plus the Domain-vs-URL-prefix property trap.
Updated 2026-09-13
Same pattern as GA4: one user invite, one pasted value. (New to connecting data? Start here.)
Step 1: add the user
- Open your Connect your data page and copy the reader email from the Search Console card.
- In Search Console, open Settings, then Users and permissions.
- Add the reader email as a user. Restricted permission is enough.
Step 2: paste your property
Paste your property exactly as Search Console shows it. That's the key phrase, because Search Console has two property types for the same website:
- A URL-prefix property looks like
https://example.com/ - A Domain property looks like
sc-domain:example.com
Paste whichever one you actually verified and shared, character for character.
The trap: two property types, one site
Many sites have both property types, or a human verified one and pastes the other. The permissions don't transfer between them: sharing the Domain property doesn't grant access to the URL-prefix property, and vice versa. It's the most common reason a Search Console connection fails.
We soften it for you: if a URL-prefix connection is refused, we automatically retry as the Domain property (sc-domain: plus your host) before reporting failure. If it still fails, open Users and permissions on the property you pasted and confirm the reader email is actually listed on that one.
What we read once connected
Branded vs non-branded clicks, total impressions, and average position, over the last 28 days. Your real branded clicks feed Return's branded demand dimension: actual humans typing your name and choosing you, which no public signal can measure as directly. The full read list.
Revoking access
Remove the reader from Users and permissions on the property. Done.
Next: Connect HubSpot.
See this on your own brand
Run a free scan and get your Brand Echo, every score explained and cited.
Measure my Brand Echo