How to send a SEOKit report to a client

Save the report, add the client’s email and send the link. The client signs in with Google, reads that property in read-only mode through your connection, and never gets your password, a seat or a Search Console role. In practice: open the report, choose Save and share, name it, add the client’s email (up to 25 per report) and save.

Setting up and sending

First choose the property, dates and filters you want the client to see, then open Save and share in a report that has that dialog, such as Rank Changes or CTR Benchmark. Give the report a clear name and add each client’s email. Addresses are checked, lower-cased and de-duplicated, and a report takes at most 25 clients.

On save, SEOKit emails the link to the clients if email delivery is configured on the server. If it is not, the clients are still saved and have access; the dialog says that email is not configured, and you copy the link and send it yourself. Always send the client link from Shared Reports rather than the address from your browser, because it is the link that checks the client list.

What the client can and cannot do

The link sends anyone who is not signed in to the sign-in page. Only a signed-in person whose email is on the list gets in; everyone else sees “report access denied”. The client reads the property through your connection in read-only mode: no GA4 or merchant data, no write actions, and no seat. Because the access is to the property rather than to a single report, a listed client can open its other Search Console reports in the workspace as well. Add only people you would let read that property’s data, and invite someone as a teammate instead when they need GA4 or a seat-based arrangement.

Adding a client to a SEOKit report does not add them in Search Console and changes nothing in Google; their access exists only while their email is on the list. Search Console roles are managed by property owners (managing owners, users and permissions), and the article on users and permissions covers that side.

Managing and removing access

The Shared Reports page in the account menu lists every report with Share, Link, a button that opens the client view, and a delete button that needs a second click. Access ends when the email leaves the list or the report is deleted, so remember to save the updated list, and delete finished engagements to withdraw the access they granted. Test the arrangement before the first real send: add a second Google account of your own as the client, open the link in another browser and look at what it shows.

When something goes wrong

If the client sees “report access denied”, they signed in with a different email from the one on the list, so add that address. If the client is asked to connect Search Console, the report was saved before the owner connection was recorded: open it, save the client list again and retry. If the client wants GA4 numbers, report clients never see GA4; invite them as a teammate with the GA4 switch on. And “Email is not configured” only means the server has no outgoing mail settings: the client is saved with access, so copy the link and send it yourself. The team and shared reports documentation describes the rest.

Go further

Docs: team and shared reports: Invitations, seats and the client list. Playbook: share work with a team: Teammate access with GA4 and write levels. FAQ: users and permissions in Search Console: Search Console roles and limits.