How to Connect Multiple Client Websites to Claude Without Sharing Google Passwords

The problem: an AI assistant with access to too many clients

Suppose you manage SEO for six companies. Every week someone asks the same question: what happened in organic search and what should we fix next? You can export Search Console data for every account, paste CSV files into Claude and ask for summaries. It works for a single report, but it becomes an access and accuracy problem when you repeat it across clients.

An analyst can accidentally attach the wrong file, a spreadsheet can retain data from another customer, and a recurring prompt can report the wrong Search Console property. The challenge isn’t just the AI. It is identity, scoping and repeatability.

The wrong solution is to ask every client for a Gmail password. Password sharing removes accountability, makes revocation difficult and expands the damage if a laptop or account is compromised.

A better setup has three layers: client-approved Google Search Console property permissions, a connector that can retrieve those properties, and a per-user or per-group permission system for analysts and assistants.

This article covers that setup using Claude and GSC Magic as examples. It also explains where native Google permissions end and a hosted workspace’s permissions begin.

Step 1: have each client delegate Search Console access

Start with the account that will administer SEO reporting. It should be an agency-controlled Google identity with a named owner, strong authentication and an offboarding process—not an employee’s personal Gmail account that could leave the business next month.

Ask a client to open their Search Console property’s user and permissions settings and add the agreed agency account with only the permission necessary for the task. You do not need the client’s email password or an exported OAuth token.

The client remains in control of that delegation. If the relationship ends, they can remove your access from Search Console. On your side, revoke the connector and remove the client property from the workspace as well.

Google’s Search Console permission documentation describes owner and user roles. Before requesting full control, check what the planned operations actually need. Reading performance data and modifying property configuration are different actions.

Write down an access register: client, exact property identifier, authorized Google identity, permission level, approval date and who can request changes. This may sound formal for a small agency, but a few lines in an internal spreadsheet prevent many cross-client mistakes.

Step 2: choose the correct Search Console property identifier

Google Search Console can represent a website as a domain property, such as sc-domain:example.com, or a URL-prefix property, such as https://www.example.com/. They are not interchangeable labels.

A domain property can represent multiple protocols and subdomains, while a URL-prefix property has more specific boundaries. A company may have separate properties for a shop, marketing site and help center, or different language domains.

When importing properties, match the exact identifier agreed with the client. Do not assume that the first property returned under an account is the one you need.

This becomes critical with multi-client reporting. An AI agent may be able to call a tool with a site parameter; you want that parameter to resolve to the correct customer before a query runs.

For a first check, ask the agent to list the accessible properties and read back the selected identifier. If the response differs from the client’s approved property, stop instead of generating a report from the wrong website.

Step 3: connect through OAuth rather than sharing a Google password

A hosted MCP service such as GSC Magic can manage the connection between Claude and Google search data. The operator signs in using Google OAuth, grants the requested scopes and can later revoke the connection.

OAuth is not a guarantee that every implementation is secure. You still need to examine the scopes, storage practices, request permissions and provider. But it avoids handing Google account passwords directly to staff, assistants or third-party scripts.

For GSC Magic, create a workspace at GSC Magic, complete the Google connection and import the approved Search Console properties. On a new account the 7-day Pro trial requires no card. The standard Pro plan supports up to 10 sites. The Agency tier supports up to 25 sites and five team seats, with groups that constrain which properties members and connected agents can access.

The Google identity connected to the service must still have access to those properties. A paid subscription cannot create permission to a client’s Search Console account.

If you want the AI tool in a local coding environment, the Claude Code guide covers its MCP connection. For the conversational app, use the Claude integration guide and confirm the connector is actually enabled in the Claude account you intend to use.

Step 4: separate clients using groups, roles and tokens

The fact that an agency-level Google account can view 25 properties does not mean every employee should be able to query all 25.

An agency workspace should distinguish a workspace owner, administrators who manage approved access, analysts who need certain client sites and viewers who may only need dashboard results. In GSC Magic Agency, client groups and team roles provide this additional application-level separation.

For example, a consultant responsible for Acme’s content should be assigned only the Acme site group. An assistant authenticated as that consultant should not see a client named Northstar merely because the same agency connected both properties through Google.

That is application-level authorization, not a change to Google’s original property delegation. If the agency’s OAuth account has broad permissions, the connector must reliably enforce user and group restrictions at query time.

Before onboarding clients, run a negative test: sign in as a member restricted to one client, request a different client’s report and confirm that the request is denied. Don’t treat a decorative group selector as proof of isolation.

You should also determine what a viewer can access, how tokens expire, how invitations work and whether the connector’s write operations can be disabled. GSC Magic keeps its Free plan read-only and has an optional write mode for eligible paid-plan operations.

Step 5: ask questions that identify the client and the date range

Once the properties and groups are in place, Claude can answer questions from connected data without a repeated manual CSV export. A good prompt includes the property, reporting windows, metric and expected evidence.

Here are three useful examples:

For the approved Acme Search Console property, compare Google web clicks in the last complete 28 days against the preceding 28 days. Return the top five pages responsible for any decline and the query changes behind them. Do not include data from other clients.

For Northstar, find pages with high impressions but low CTR. Separate mobile and desktop where the data supports it, and list proposed checks rather than assuming a title rewrite will work.

Create a concise monthly SEO narrative for the approved client property. Report clicks and impressions from Search Console, then label any GA4 outcome metric by its exact event definition. Flag incomplete data.

These prompts do not guarantee that an AI model will avoid mistakes. They make the task verifiable by naming the data scope, dates and evidence requirements.

Whenever a result matters commercially, open the underlying Search Console report or compare the tool’s numeric response against the source. Google explains why chart, table and query-filtered totals can differ.

Step 6: define a safe client reporting process

A repeatable workflow is more valuable than asking a new question every month. Give your team one template: summary, measured changes, affected URLs, supporting evidence, recommended actions and uncertainties.

Search Console provides clicks, impressions, CTR and average position. GA4, when properly configured, can add sessions, events and business outcomes. Neither automatically proves that an SEO change caused a sale. Keep the two sources separately labeled.

The automated client reporting guide explains a report structure and the review controls an agency should apply. The dedicated SEO client reporting page shows the Agency workflow and plans.

With GSC Magic, monthly client-group email reports are an Agency feature. On Pro, a single consultant can use the AI assistant to prepare drafts, but the same automatic client-group delivery should not be assumed to be available.

A client-facing report should be reviewed before being treated as business advice. The manager should verify property identity, date ranges, totals, sensitive information and recommendations.

What a small agency should pay for—and what it should not

For one freelance SEO working with a handful of websites, a $34 monthly Agency seat structure may be unnecessary. A $19 Pro account has up to 10 sites and is designed for individual workflows.

When a team needs named seats, client groups and automatic email reports, the Agency plan becomes more relevant. Its standard limits are 25 sites and five seats, with a listed yearly option of $340. These are the current GSC Magic launch prices described on the pricing page; compare the actual checkout options before committing.

For agencies exceeding those limits, a custom enquiry is more honest than assuming an unlimited workspace. Use the Agency contact form to specify the number of properties, team members and any reporting constraints.

You should also account for the AI provider’s own account and feature limits. Buying access to an MCP service does not necessarily include a separate Claude subscription or unlock an AI client’s connector functionality on every tier.

Security checklist before the first client goes live

The main risk in a multi-client workflow is not a dramatic “AI hack.” It is an ordinary access error that exposes one client’s data to another.

Before rollout, confirm each of the following:

• The client explicitly approved delegation to an agency-managed Google identity.
• The property identifier matches the client’s real domain or agreed URL prefix.
• Every analyst and assistant has only the properties they need.
• A restricted member fails when trying to access an unrelated customer.
• Connector scopes and optional write tools were reviewed.
• All users have appropriate authentication protection and offboarding steps.
• Reports display data source, property, complete date window and limitations.
• Manual review is required before sharing sensitive findings outside the team.

Do not paste OAuth tokens, API keys, passwords or client-specific secrets into an AI prompt. Use the connector’s supported authentication flow. If permissions are revoked, confirm that access no longer works and that stale shared links or exports are handled appropriately.

Our separate MCP security checklist covers tokens, revocation and prompt injection in greater detail.

Common mistakes when connecting many sites

The first common mistake is treating a Google connection as if it grants universal Search Console access. It does not; access is specific to properties and to the Google identity that consented.

The second is trusting a plausible AI summary without checking the property or dates. A report with beautiful prose but the wrong customer is worse than no report at all.

The third is conflating scheduled AI prompts with scheduled client reports. MCP provides tools that compatible agents can call. Some platforms support scheduling, and some reporting products include scheduled email delivery; those are distinct capabilities.

The fourth is chasing perfect automation before building a stable report. Start with one customer, reproduce the data manually and document the expected output. Only then repeat it for the rest of the portfolio.

Frequently asked questions

Do clients need to give the agency their passwords?

No. They can delegate access to a designated Google identity through Search Console permissions. That delegation should be documented and revoked when the relationship ends.

Can different analysts access different clients through Claude?

Yes, if the selected connector and workspace enforce per-user or per-group access. Do not rely solely on the AI prompt to prevent cross-client disclosure.

Does MCP automatically send monthly reports?

No. MCP is a tool interface. GSC Magic’s Agency plan has monthly client-group email reporting; other MCP workflows require an explicit scheduler or reporting service.

Can a client have access without seeing other clients?

A group-restricted or viewer role can be appropriate, provided the workspace’s permission model is configured and tested. Always verify effective access before issuing an invitation.

Can the assistant change Search Console settings?

Some connectors offer write tools. Review the specific scope, plan, Google authorization and switch controlling write mode. For routine analysis, prefer read-only access.

Start with one approved property

Choose one client who can approve the necessary Search Console delegation, connect only that property and verify a simple 28-day comparison. Have the analyst reproduce the result in Search Console, test that an unrelated client remains inaccessible, then document the reporting prompt.

Once that process is reliable, add the next property. Scale the evidence and permissions together, rather than scaling the number of AI-generated reports first.

For a hosted team setup, explore GSC Magic for SEO agencies, automated client reporting and the Claude connection guide.