Google Search Console has no native equivalent of Google Ads Manager (MCC) — no multi-client dashboard, no centralized view across all properties. Every client site needs to be accessed individually, which creates real operational friction at scale. An agency managing 50 or 100 client properties is navigating between 50 or 100 separate GSC interfaces, each requiring individual login and data export.
This isn't going to change from Google's end anytime soon. The scalable solution is building around the constraint rather than waiting for a native fix.
Property Setup: Domain vs. URL Prefix
The first decision for each new client property is which verification type to use. This matters more than most people realize for long-term property management.
| Property Type | Coverage | Verification Method | Best For |
|---|---|---|---|
| Domain property | All subdomains, all protocols (http/https) | DNS TXT record | Recommended for most sites |
| URL prefix property | Specific URL prefix only | Multiple options including HTML file or meta tag | Subdomain-specific tracking, URL path segmentation |
Domain properties are recommended for most agency setups: they cover all subdomains and both HTTP and HTTPS versions of the site under one property. This reduces the number of properties you need to manage per client and gives a complete picture of total search presence.
The limitation: domain property verification requires DNS TXT record access. If your client's DNS is managed through a registrar where they control access and turnaround is slow, URL prefix properties with HTML file or meta tag verification can be faster to set up.
Access Permissions: What Level to Request
GSC has three permission levels:
- Owner: Full access including user management and property deletion. Requires verification. Typically held by the client or their technical team.
- Full user: Can view all data and submit sitemaps. Cannot manage other users. Appropriate for agency day-to-day work.
- Restricted user: View-only on most reports. Cannot submit sitemaps. Appropriate for read-only reporting access.
Best practice for agency access: request Full user access on each client property. This provides everything needed for operational work without requiring Owner-level DNS verification on the agency's account. Ask clients to grant access from their verified Owner account rather than trying to add the agency's account as a verified owner.
One specific operational note: when clients change their internal team or change agencies, GSC access needs to be updated manually for each property. This is an underappreciated source of access loss — a client's IT admin leaves, their GSC account becomes orphaned, and the agency's access depends on an account that may be deactivated. Ensuring clients have at least two Owner-level accounts for each property reduces this risk.
The 1,000-Property Limit
GSC allows up to 1,000 properties per Google account. Large agencies approaching this limit typically use multiple Google accounts for property management — splitting clients across accounts by team, region, or alphabetically. The limit is per account, not per person, so this workaround is straightforward.
A more common operational problem than the property limit itself: the cognitive overhead of managing 200+ properties across multiple accounts. Agencies at this scale typically need a property registry — a spreadsheet or CRM entry for each client that includes which GSC account hosts the property, the property URL, verification type, current access permissions, and last data export date.
Pulling Data Across Multiple Properties at Scale
The GSC API is the only way to aggregate data across multiple client properties programmatically. Manual export from each property is workable for 5-10 clients; it doesn't scale.
The GSC API allows up to 2,000 requests per day per Google Cloud project. Agencies with many properties need careful rate limit management — with 100 clients and daily data pulls for each, you can exceed this limit quickly. Solutions include using multiple Cloud projects (one per client or per client tier), staggering API calls across time windows, or using a GSC BigQuery export which runs server-side without counting toward API quotas.
BigQuery Export for Multi-Client Reporting
Each client's GSC property can be connected to a BigQuery dataset. If each client has their own GCP project, their BigQuery export is isolated to their project. If the agency hosts a shared GCP project, client data can be organized into separate BigQuery datasets within the same project.
The BigQuery approach has several advantages over API-based reporting at scale:
- Data is stored permanently — no 16-month retention limit
- Full row access — no 1,000-row export cap
- SQL-accessible — any report shape is possible without additional tool dependencies
- No API quota consumption for stored historical queries
Access Management When Client Relationships Change
Agency-client relationships end. The access management implications of this are usually underplanned:
- When offboarding, the agency's Full user access needs to be revoked from each GSC property — this doesn't happen automatically. Build a property access list and use it during offboarding.
- Data in the agency's BigQuery exports is technically the agency's; data in the client's GSC property is the client's. If the client requested a BigQuery export be set up in the agency's GCP project, agree upfront on data ownership and handover procedures.
- If the agency's Google account that holds Full user access is deactivated, access is lost. Use a role-based email (seo@agency.com) rather than individual team member accounts for property access grants.
The Practical Workflow at Scale
At around 20+ client properties, the agency needs:
- A central property registry (spreadsheet minimum; ideally a CRM field or project management integration)
- Standardized access request process: what level, which email, what verification type
- Automated data extraction (API or BigQuery) with standardized report templates
- Access audit schedule: quarterly review of who has access to what across all properties
At 50+ properties, add a dedicated onboarding/offboarding checklist for GSC access specifically, and at least two owner-level contacts per client property to prevent orphaned access situations.
None of this is technically complex. It's operational discipline that's easy to skip on a small book and increasingly painful to retrofit at scale. The agencies that handle multi-property GSC cleanly do so because they systematized it early — not because they found a better tool.