What should agencies look for in SEO software?
Three things matter more than the feature list: client data that can never cross over, pricing that doesn't explode with each new site, and output your team can act on without rebuilding it in a spreadsheet.
- Separation: one client's keywords, knowledge and content must never reach another client's drafts or CMS.
- Per-client context: market, country, competitors and positioning set per site.
- Prioritised work: a ranked list of what to ship this week for each client, not a 300-row audit.
- Proof: before and after numbers per piece of work, from the client's own Search Console.
- Room to grow: adding a site shouldn't mean a new tier.
How does LogNorm organise client sites?
LogNorm has two levels. A workspace is your team: members, roles, plan, credits, billing and AI keys. Inside it, each website is one site you grow, with its own moves, weekly plan, keywords, topics, competitors, audits, AI prompts, Search Console connection, CMS connection and results.
| Shared across the workspace | Separate for each website |
|---|---|
| Members and roles | Market (country and language), positioning and ideal customer |
| Plan, credits and billing | Crawl, SEO audit and GEO audit |
| AI provider keys | Keywords, topics and rank tracking |
| Weekly capacity and the Monday digest | Competitors and AI visibility prompts |
| Company Brain sources you choose to share | Search Console and CMS connections, moves, plan, content and results |
You switch between client sites from the website menu in the sidebar. Each site has one market, from 94 countries, so a client serving two countries is added once per country. See Workspaces, websites and team.
How is client data kept apart?
By rules in the product, not by convention. The places where agency tools usually leak are knowledge, publishing and AI agents, and LogNorm scopes all three to one website.
- Company Brain: each source belongs to one website or is shared on purpose. Writing for a site searches that site's sources plus shared ones, never another website's.
- Publishing: a website has at most one CMS, and a CMS serves at most one website, so an article for one client can never land in another client's CMS.
- Brand identity: brand terms and owned sites are set per website, so AI answers count mentions for the right client.
- AI agents: a connected Claude Code or Codex agent works on the one website picked at sign-in. Connect again for another client.
How do you onboard a new client site?
Add the site, give LogNorm the client's context and connect their data. Owners and admins can add websites; analysis starts the moment you add one.
- Add the website
Enter the address, check the market (country and language) and click Add and analyze. The crawl, SEO audit and first moves follow on their own.
- Describe the client
Edit details sets the name, what the product does and its ideal customer. These feed every move and brief for that site.
- Load their knowledge
Add the client's homepage, pricing and positioning to the Company Brain, scoped to that website only. Set brand terms and owned sites in Brand identity.
- Connect their data
Connect the client's Google Search Console property and, if you publish for them, their CMS. Both belong to that website alone.
- Track the field
Run Discover competitors and add the prompts their buyers ask AI assistants, within your plan's limits.
Search Console needs a Google account with access to the client's property; LogNorm asks only for read-only access. See Google Search Console.
Should each client get their own workspace?
It depends on whether the client needs to log in. Roles in LogNorm apply to the whole workspace, so anyone you invite, even as a Viewer, can read every website in it.
| One agency workspace | A workspace per client | |
|---|---|---|
| Best when | Only your team logs in | Clients need their own access |
| Billing | One plan and one credit balance for all sites | Each workspace has its own plan and billing |
| Client access | Not recommended: members see every site | Invite the client to their workspace only |
| Switching | Website menu in the sidebar | Workspace menu at the top of the sidebar |
You can belong to several workspaces and switch between them, so mixing both setups works too.
How does the work get done across clients?
Each client site gets its own ranked backlog and weekly plan. Audits, Search Console, keyword research, competitors and AI answers all become moves, ranked head to head for that client's business.
Your team owns and plans moves by role: Editors plan, review and publish, Contributors see the moves assigned to them, Analysts run research. AI agents can take fix and content moves too, with drafts going to a person for review. Every shipped move is measured against that client's own Search Console baseline at 28 and 90 days. The Growth Plan page shows the weekly flow.
What doesn't LogNorm do for agencies yet?
LogNorm has no white-label reports, client portal or branded PDF exports. If client-facing reporting is the main job you need software for, pair LogNorm with a reporting tool.
Data leaves as CSV: every audit finding, AI visibility sources and historical runs, and reports agents build from LogNorm's data. The weekly capacity target is also shared across all websites in a workspace, so set it for the whole team rather than per client.
Which plan fits an agency?
Scale is built for agencies: 10 websites, unlimited members and the highest credit allowance. Growth covers 3 websites and 10 members, which suits a consultant with a few retainers.
Need more sites without a new tier? An extra website is an add-on at $29 a month. Seats come in packs of 5, and tracked AI prompts in packs of 50. Current prices and allowances are on the pricing page.
Frequently asked questions
Can I manage multiple client websites in one LogNorm account?
Yes. Add each client as a website in one workspace, up to your plan's limit, and switch between them from the sidebar. You can also belong to several workspaces.
Can clients log in to see their own site?
Yes, in a workspace of their own. Roles cover the whole workspace, so don't invite a client into a workspace that holds other clients' sites.
Does LogNorm offer white-label reports?
No. Findings, AI visibility data and agent-built reports export as CSV for your own reporting.
Can one client's content end up in another client's CMS?
No. A CMS connection belongs to exactly one website, and the same CMS can't be connected to a second website in the workspace.
Do AI agents work across all client sites?
No, deliberately. Each connected agent works on one website. To work on another client, connect it again and pick that site.
Can I bill each client separately?
Yes, with a workspace per client: each workspace has its own plan, billing and credit balance. In one shared agency workspace, a single plan and credit balance cover every site.
Keep reading
- All solutionsSee how different teams use LogNorm to find what holds growth back, rank the work and ship it with their AI agents, from solo founders to growth teams.
- Workspaces, websites and teamRoles, websites and invitations.
- Company BrainSources scoped per website or shared.
- Company Brain product tour
- SEO project managementRanked backlog and weekly plan per site.
- Publishing docsCMS publishing destinations and how drafts reach them.
- SEO KPIs that predict growthWhat to report to clients.