Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.schemagen.io/llms.txt

Use this file to discover all available pages before exploring further.

Client portfolios give your agency a dedicated, isolated workspace for every client you manage. Each portfolio keeps that client’s schemas, SDN configuration, and analytics completely separate from your other clients. You switch between clients from a single dashboard without logging out or switching accounts.
Client portfolios are available on the Agency plan only. Upgrade from Settings → Billing to unlock this feature.

​
What is isolated per client

When you create a client portfolio, SchemaGen provisions a separate environment for that client. The following data is scoped exclusively to that client:
  • Schema library — saved schemas, drafts, and published schemas belong to that client’s workspace only
  • SDN configuration — the Client ID and SDK snippet are unique per client, so schema delivery targets only that client’s site
  • Analytics — schema performance data, GSC tracking, and audit history are siloed per client
Clients cannot see each other’s data. If you have five clients, each one sees only their own schemas and analytics when you view their portfolio.

​
How to add a new client

1

Go to the Clients page

From the main dashboard, click Clients in the sidebar. This opens your Client Portfolio overview.
2

Click Add Client

Click the Add Client button in the top-right corner of the Clients page.
3

Enter client details

Fill in the client’s name and their website URL (for example, https://example.com). The name appears in your portfolio list and on any white-label exports.
4

Save the client

Click Save (or Create). SchemaGen creates the isolated workspace and generates a unique Client ID for that site.
5

Install the SDK on the client's site

Copy the SDK snippet that contains the client’s unique Client ID and send it to the client’s developer. Once installed, the SchemaGen SDK will deliver schemas to that domain.

​
Switching between clients

From the Clients page, each client appears as a card showing their site name, domain, number of managed schemas, and last audit date. Click any card to enter that client’s workspace. All views—schema builder, audit tool, analytics—update to show only that client’s data. To return to your agency overview, click Back to Dashboard at the top of the page.

​
The Client ID

Every client portfolio has a unique Client ID generated by SchemaGen at creation time. You use this ID in the SDK snippet installed on the client’s website. The SDK uses the Client ID to identify which schemas to fetch and inject on that domain. To find a client’s Client ID:
1

Open the client portfolio

Click the client’s card from the Clients page.
2

Go to SDK or Settings

Look for the SDK Setup or Settings section within the client workspace. The Client ID and ready-to-copy script tag are displayed there.
3

Copy the snippet

Copy the full script tag and pass it to the developer responsible for the client’s site. It only needs to be installed once.
Each client has a different Client ID. Using the wrong ID on a site will deliver another client’s schemas. Double-check the ID matches the correct domain before handing it off.

​
White-label “Send to Dev” exports

Agency plan users can export any schema as a developer-ready package for client handoff. The export includes the final JSON-LD output formatted for direct implementation, without any SchemaGen branding. To export a schema:
  1. Open the schema you want to export from within the client’s workspace.
  2. Click Send to Dev (or the export option in the schema actions menu).
  3. SchemaGen packages the JSON-LD into a clean, implementation-ready file you can attach to a ticket, email, or client report.
This is useful when a client’s team wants to implement schema directly in their CMS or source code rather than relying on the SDN for delivery.

​
Verified vs. pending SDK status

Each client card shows a status badge:
  • Verified — the SDK snippet is installed and SchemaGen has confirmed it can reach the client’s site. Schema delivery is active.
  • Pending SDK — the snippet has not yet been detected on the client’s domain. Send the SDK snippet to the client’s developer to complete setup.
The status updates automatically once SchemaGen detects the snippet on the live site.