Get your agency added to a client's Search Console

Confirm the correct Search Console property, distinguishing a Domain property from a URL-prefix property. Ask the client to identify the account they actually use for the work in scope, rather than choosing from a familiar-looking name. Also agree whether the immediate objective is assessment, configuration or ongoing delivery. These details determine which permission is reasonable and what your team will check afterward. If the client is unsure which asset belongs to the project, resolve that ownership or account-selection question before they approve access to an unrelated account.

The request needs a verified or delegated owner of the selected Search Console property. Send the instructions to that person or ask the client to involve them. A staff member who can read a dashboard may still lack permission to invite an agency. Repeating the same request with the same insufficient role will not fix that distinction. The authorized person should review the requested asset, recipient and permission before proceeding, and retain their own independent access after the agency is added.

Restricted fits reading search data; Full is appropriate when the engagement includes actions such as submitting sitemaps. The onboarding link does not request Owner access. Start by naming the actions the agency must carry out, then match the role to those actions. If the team only needs to inspect Google Search Console, explain why a viewing role may be sufficient. If a later task requires more authority, make that a deliberate scope decision with the client. Avoid requesting the broadest available role simply to prevent a possible future question; the current engagement should explain the permission being requested.

The client connects Google for reporting, then manually adds the agency as Full or Restricted in Users and permissions. Marking that step complete reports the client action; it does not replace verification by the agency. Read the status in the context of that workflow. An invitation, a client confirmation and usable Google Search Console access are related milestones, but they do not always happen at the same moment. Assign responsibility for the next step before marking delivery as ready. This prevents an agency teammate from arriving at a scheduled task and discovering that a required acceptance or platform action is still outstanding.

Use the exact agency Google email shown in the onboarding instructions. Verify it before creating or sending the onboarding request, especially when the agency works through more than one account. Ask the actual recipient to confirm the identity they will sign in with. A forwarded email or a similar display name is not reliable proof that the correct account has been added. For a staffing change, arrange the replacement person’s appropriate access and remove obsolete assignments through the relevant platform process.

After the platform action, open Search Console as the agency user, select the agreed property and confirm that its domain or URL prefix matches the production website. Record who performed that check and whether any required work remains blocked. Prefer a harmless viewing check over an unnecessary live edit. If a teammate cannot reach the asset, compare the actual recipient and role with the original request before asking the client to start again. Completion should mean the right person can reach the intended asset with the agreed capability, rather than only that a message or notification was received.

The reporting connection provides search clicks, impressions, queries and pages independently of the manual user-addition step. Search data has a publication delay, so check the latest available reporting day. Keep the client’s reporting expectation explicit in the service brief. If a metric is needed for a report, identify its source, date range and definition before promising that it will appear. A successful access step establishes only the capabilities described for this particular integration. It should not be used as evidence that another platform, a separate dataset or an unrelated source of business results has also been connected.

If Users and permissions is unavailable, involve the property owner. If the agency cannot see the property, compare the email that was actually added with the one specified on the link. Start with account identity and authority because those determine what the client can share. Write down the exact stage where the flow stopped rather than repeatedly recreating the same request. If Google Search Console shows an account-specific restriction, the appropriate platform administrator may need to resolve it first. Avoid broadening permissions or switching to another asset just to make a completion indicator appear; verify the intended account instead.

The onboarding flow avoids requesting ownership just to automate agency access. It connects reporting through the client authorization and gives the client instructions for adding the agency with the chosen user permission. That distinction is intentional. Verify the manual user addition independently, because reporting can already be working while the agency still cannot open the property under its own Google login.

Choose the property that matches the reporting scope agreed with the client. A Domain property and a URL-prefix property are separate objects, so compare their coverage before using their totals interchangeably. Record the exact property selected and any narrower views used for analysis. If several properties are relevant to a migration or a subdomain project, verify access and interpretation for each.

No. The link requests a Search Console user permission, not ownership of the website or the business. It does not grant registrar, hosting or CMS access either. If the SEO engagement needs website changes, coordinate the appropriate separate website invitation. Keep the distinction clear in the client brief so the client knows which systems the agency can actually operate.

State the latest available reporting day and compare periods that contain comparable data. The product describes a publication delay for Search Console, so the most recent calendar days may not be complete. Avoid calling that gap a traffic collapse. If investigating a change, preserve the property, date range and query or page filters so that another teammate can reproduce the same view.

Access lets the agency inspect data and, with the appropriate role, use supported Search Console actions. It does not establish that a page is eligible, indexed or well ranked. Treat technical diagnosis, content work and performance measurement as separate delivery tasks. Document the page and observed issue before taking action, and explain the actual evidence rather than promising a ranking result from the connection.

Remove the agency user from Search Console Users and permissions, and disconnect the Google reporting authorization separately. Any ownership verification arranged outside this flow needs its own review. Agree a handover point before removing access that is still needed to finish approved work. Confirm the business retains the people and permissions it needs after the agency leaves. Keep permission removal separate from decisions about delivered work or historical reporting data; those are different questions. Record which Google Search Console assignments were removed and which, if any, remain for an explicitly agreed support period, with a clear owner for the final review.

Inspect the agreed property and document the search-performance period, relevant pages and migration or indexing question being investigated. If the task requires website changes, coordinate the separate CMS or hosting permission with the developer. For reporting, align the property scope and available data-through date before comparing periods. The useful first deliverable is a specific search diagnosis with reproducible page or query context, rather than a promise that gaining access will itself change indexing or rankings.