Search Console connection & property

What you see

• GSC connected in Explorer but clicks and impressions are zero.
• Property sc-domain:other.com but you scan www.client.com.
• Client has GSC under a different Google account than the agency.
• After OAuth: “property mismatch” error.

Why it happens

Search Console binds to Google account + property type:

• URL-prefix (https://www.example.com/) vs Domain (sc-domain:example.com).
• http vs https, www vs non-www must match scanned URL.
• GSC data lag 2–3 days — not realtime.
• Agency account only sees properties it was granted.

What Puluno does

Phase	Action
Connect	OAuth in Puluno account — read-only GSC API
Diagnose	compare property host vs scan URL
Display	clicks/impressions for scanned URL (not whole account export)

Puluno does not write to GSC (no bulk submission API in MVP).

Step by step

1. Client adds agency Google account as user on GSC property.
2. In Puluno account: Connect Search Console → pick correct property.
3. Run Explorer on the same canonical URL as property prefix.
4. Fetch GSC for URL — if zero, check 28-day window and indexation.
5. Property mismatch: switch property or scan the correct host.
6. Verify: GSC panel in report shows data for scanned URL.

Details: GSC & redirects.

Rollback — undo the change

Disconnect GSC in Puluno account — instant, Google data unchanged.

When it is not Puluno

• Client has no GSC — verify site ownership in Google first.
• Indexation blocked — Google not indexing, not GSC connect.
• Bulk “submit all URLs” request — outside Explorer scope.