Domain property or URL-prefix property in Search Console?

Prefer the domain property for almost every client — it covers all subdomains and both http/https variants in one place, where a URL-prefix property only covers the exact prefix. The main reason to keep a URL-prefix property is legacy reports or a verification constraint. Note which property type is verified next to the GA4 link on the client's map so the gap is visible.

Does Phloz pull Search Console performance data?

No. Phloz has no Search Console connection and no Search Console node — it records whether the client's GA4 property is linked to Search Console, and to which property. The page exists so an SEO agency can check the foundation is correct — right property, durable verification, linked to GA4 — not to replace Search Console itself.

Why is the Search Console report in GA4 empty?

Almost always because the GA4 ↔ Search Console link was never created, or it links the wrong property. It's a quick fix in GA4's admin once you know it's missing — which is exactly the kind of silent gap the GA4 node's Search Console link field puts in front of you at onboarding instead of months later.

SEO

Google Search Console integration for digital marketing agencies

Search Console is the SEO agency's source of truth for how Google actually sees a client's site — impressions, queries, indexing, and Core Web Vitals — and it's the data feed an agency cannot recreate from anywhere else. The catch is that the right property has to be verified and linked the right way, and inherited accounts routinely have the wrong property type verified, a verification method that breaks on the next site migration, or no GA4 link at all. Recording the link on the client's GA4 property node makes "is Search Console linked for this client, and to which property?" a question the agency can answer at a glance.

How Phloz models Google Search Console

What Phloz records about Google Search Console on each client's tracking map, and what it doesn't. Only GA4, Google Tag Manager and Google Ads connect to Phloz (read-only, through a connected Google account); everything else is recorded by your team. Health states are set by the person who checks, the structural audit re-runs weekly, and graph relationships show what each node connects to — so a node marked broken or overdue for verification shows up in the cross-client tracking-health view.

No Search Console node type: the property is recorded on the client's Accounts card and on the GA4 property node that links to it
The GA4 ↔ Search Console link captured explicitly — present or missing — so the Search Console reports inside GA4 aren't silently empty
Property type and verification method (DNS / HTML file / tag / GA4) written in the GA4 node's notes, so a migration plan includes re-verification
No Search Console data: Phloz can't see verification status, queries, or indexing — those stay in Search Console

Common Google Search Console configuration gotchas

The configuration mistakes agencies most often make with Google Search Console, surfaced here as a checklist agencies can run at every client onboarding. Honest, useful, not gated behind a sales pitch — these are real and you should audit for them regardless of whether you use Phloz.

Wrong property type verified: a URL-prefix property (https://www.example.com) misses traffic on other protocol/subdomain variants. The domain property covers every variant — verify the domain property and most "missing data" complaints disappear.
Verification method breaks on migration: HTML-file and meta-tag verification silently fail when the site is rebuilt or replatformed. DNS (or GA4) verification is more durable — note the method so a migration includes re-verification.
No GA4 link: without linking Search Console to GA4, the organic-search reports inside GA4 stay empty and the agency loses the joined view. It's a two-minute link that's missing on a surprising share of inherited accounts.

At launch (V1)

There is no Search Console node and no Search Console connection. What Phloz records: on the GA4 property node, whether Search Console is linked (linked / not linked / planned) and which Search Console property; on the client's Accounts card, the property as an account ID. Property type and verification method go in notes.

Not built yet

Read-only sync via the Search Console API: surface verification status and the GA4↔Search Console link state directly in Phloz.

Why we built the integration this way

Most agency CRMs treat third-party tools as text fields: "GA4 Property ID" goes in a custom column on the client record. That works at one or two clients and breaks at five. With Google Search Console recorded on each client's tracking map — as its own typed node where Phloz has one, as fields and notes where it doesn't — the agency can answer "is this client's Google Search Console setup documented, and when was it last verified?" per client, and see every client ranked by tracking health.

Most of it is entered by hand at onboarding: only GA4 properties, GTM containers and Google Ads accounts can be imported from a connected Google account, and nothing syncs afterwards. The manual pass forces explicit verification at the exact moment the agency takes over the client's tracking — the cheapest moment to catch the gotchas listed above, before they become production issues.

When to use this in your client onboarding flow

The pattern we recommend: at every new client onboarding (see the client onboarding audit use case), spend 30 minutes documenting the client's Google Search Console configuration on the tracking map — IDs, tracking-code installations, conversion setup, the relationships to other systems. Verify each one fires by triggering a test event, then mark the node verified so the date is recorded. Add a recurring task (monthly, say) for the re-check, assigned to whoever owns tracking — the audit flags anything unverified for 30+ days either way.

Thirty minutes at onboarding costs far less than finding the same tracking issues during the first month of campaign optimisation — when finding them would mean a refund conversation. See the broader tracking infrastructure map use case for the agency-wide pattern.

Frequently asked questions

The three questions agencies ask most often about Phloz's Google Search Console integration. Honest answers — same data we'd give a friend evaluating the integration.

Domain property or URL-prefix property in Search Console?: Prefer the domain property for almost every client — it covers all subdomains and both http/https variants in one place, where a URL-prefix property only covers the exact prefix. The main reason to keep a URL-prefix property is legacy reports or a verification constraint. Note which property type is verified next to the GA4 link on the client's map so the gap is visible.
Does Phloz pull Search Console performance data?: No. Phloz has no Search Console connection and no Search Console node — it records whether the client's GA4 property is linked to Search Console, and to which property. The page exists so an SEO agency can check the foundation is correct — right property, durable verification, linked to GA4 — not to replace Search Console itself.
Why is the Search Console report in GA4 empty?: Almost always because the GA4 ↔ Search Console link was never created, or it links the wrong property. It's a quick fix in GA4's admin once you know it's missing — which is exactly the kind of silent gap the GA4 node's Search Console link field puts in front of you at onboarding instead of months later.

Other seo and adjacent tools, and how Phloz handles each.

Start your free trial

14 days free for new workspaces · No credit card · Starter tier free forever