A portal is a read-only link that shows one client the work on one project. No login, no seat, no access to anything else in your account.
Creating one
From the project, create a share link and choose which sections it includes. The client opens the link and sees only those sections, for only that project.
Choose the sections deliberately
The default should be outcomes, not plumbing:
Usually include — rankings, traffic, the work completed, AI visibility summary, audit score over time.
Usually leave out — operational alerts, raw error logs, credit balances, anything that reads as internal noise. A client seeing "crawl partially failed" will ask about it, and the answer is a conversation about our infrastructure rather than their results.
What a client cannot do
They cannot sign in, see your other projects, see your billing, change anything, or reach any part of your account. The link resolves to one project and the sections you picked, and nothing else.
Making it useful rather than decorative
A portal that shows numbers with no interpretation gets opened once. Give each number something to compare against and something to conclude:
- Rankings with the change since last month, not just today's position
- The work completed — the single most under-used section, and the one that answers "what am I paying for"
- AI visibility with the gap list, so there is a visible plan and not just a score
Revoking
Revoke the link when the engagement ends. It stops working immediately, and anyone holding the URL gets nothing.
Next
- What each section of the app is for
- Reading your site audit results