Can anyone on the team query any client workspace?

Yes, for any workspace that has been synced to the cloud. Teammates in the organization query it over MCP from Claude, ChatGPT, Cursor, or another MCP client. The crawl itself runs in the desktop app, and workspaces that aren't synced stay on the machine that crawled them.

Can we keep each client in its own workspace?

Yes. Each client site gets its own workspace, so crawls, history, and findings stay separate and are one click apart.

How do Team plans work?

Silkra Team plans start at three seats, and you can add more as the team grows. Agent credits are pooled across all seats, and synced storage is shared. See pricing for current rates.

Does client data leave our computers?

Crawling and embeddings run on the strategist's computer. To improve the analysis, small snippets such as page titles and short excerpts are sent through Silkra's proxy for AI enrichment. Whole crawls are only uploaded for workspaces the team chooses to sync.

Does it fit the tools the team already runs?

Yes. Search Console, Ahrefs, Jira, Linear, WordPress, and more connect to Silkra, so findings can become tickets and approved fixes can go out to the CMS. Nothing is published or filed until a person approves it.

For agencies

Crawl a client site once. The whole team works from it.

Silkra turns crawling into a team sport. Sync a crawl and any teammate can query it from Claude, ChatGPT, or Cursor, so anyone can pick up any client.

See Team plans Download free

Audit a new client in an afternoon. Crawl locally and see the site grouped by topic, with issues ranked by what to fix first. Walk into kickoff with findings.
Move between clients without losing the thread. Each client gets its own workspace, with past crawls kept so you can see exactly what moved.
Use crawl data inside Claude and ChatGPT. Connect once and the AI tool reads the real crawl, so briefs and answers come from the pages, not guesses.
Share one source of truth. Synced workspaces are shared across the team, so no account lives in just one person's head.

Take on more clients without stretching the team.

Your strategists still run every audit: they ask the questions, dig into the findings, and make the calls. The difference is that the Silkra agent sits right on top of the crawl, so it already has every finding and piece of evidence. Ask for a document or a sheet and it's built in minutes, not after hours of sorting through spreadsheets, so each strategist can deliver more in the same week.

Strategists spend their hours on strategy, not on assembling evidence
Deliverables go out faster, so each strategist can take on more clients and the agency earns more
Every deliverable is backed by the crawl, so clients see proof

Internal linking opportunities

Can you help me find internal linking opportunities?

I’ll compare the site’s topic relationships with its link graph and look for relevant pages that are not connected.

Reviewed link architecture · Found related pages

I found 7 pages that are isolated inside their own semantic groups. They cover closely related topics without linking to nearby pages in the same group, so those sections read more like collections than connected pathways.

/guides/content-audits could link to /resources/seo-audit-checklist when it introduces the audit process.
/blog/automate-client-reporting and /templates/client-report cover the same workflow, but neither page links to the other.

1 sourceIsolated links

Build a sheet with recommended link targets

Created sheet · Link targets

Link targets

Sheet · 10 rows

I added ten link targets. Each row names the page to edit, the related page it should link to, and anchor text to start from.

Send follow-up...Medium

acme.com237 pages

TableLink targets

Link targets

Page to edit	Link to	Suggested anchor	Semantic group
/guides/content-audits	/resources/seo-audit-checklist	SEO audit checklist	Content strategy
/blog/automate-client-reporting	/templates/client-report	client report template	Automation
/templates/client-report	/blog/automate-client-reporting	automating client reports	Templates
/blog/content-gap-analysis	/guides/build-a-content-brief	build a content brief	Content strategy
/guides/automated-reporting	/guides/connect-your-data	connect your data	Automation
/docs/workspaces	/docs/getting-started	getting started	Product education
/resources/seo-audit-checklist	/guides/content-audits	content audits	Templates
/customers/shoreline	/guides/automated-reporting	automated reporting	Customer stories
/blog/marketing-workflows	/guides/automated-reporting	reporting workflows	Automation
/guides/build-a-content-brief	/resources/content-brief-template	content brief template	Content strategy

10 rowsSaved sheet

Ask anything about the crawl. Question the whole site in plain language and get answers that point back to the pages, issues, and links behind them.
Build the deliverable in the chat. Ask for a document, sheet, or chart and the agent drafts it from the crawl evidence. Refine it with follow-ups.
Send findings to where the work happens. Turn issues into Jira, Linear, or monday.com tickets and push approved fixes to the CMS once someone signs off.

Every client crawl, ready for any teammate.

Crawl a client site once and sync it, and anyone on the team can query it from Claude, ChatGPT, or Cursor. When a strategist is out, whoever steps in gets the structure, the content, and the open issues in minutes, not an afternoon in old docs and sheets.

One crawl per client, shared by the whole team
Query it from the AI tools the team already uses
Anyone can step in on a client in minutes

Using Silkra, I'm covering the Northwind call at 2pm. Give me a quick briefing on the site.

Claude

I'll read Northwind from the team's synced crawls.

Silkra · get site overview1,240 pages

Silkra · list issues62 open

Silkra · get changesSince last crawl

Northwind is a 1,240-page site organized into six topic groups, with camping gear and trail guides making up most of the content. The most pressing issue is 38 product pages that share duplicate titles, so that's the best place to start if the client asks what needs fixing. A smaller cluster of 12 pages links to URLs that no longer exist.

Since the last crawl, 14 pages were added and the returns policy was rewritten, which is worth mentioning if it comes up on the call. I can draft talking points or a one-page summary if that would help.

Crawl and sync a client workspace. Crawl locally, then sync the workspaces the team should share. Anything you don't sync stays on your machine.
Connect the AI tools the team already uses. Add Silkra to Claude, ChatGPT, Cursor, or any MCP client, so strategists stay in the tools they already work in.
Anyone can ask about any client. Strategists query the same crawl over MCP, with answers that point back to the pages behind them.

Priced per seat, shared by the whole team.

Start with three seats and add more as the team grows. Agent credits and cloud storage are pooled, so a busy week for one strategist doesn't leave anyone stuck.

Compare all plans

Team

$60per seat / month

3 seats minimum: $180/month

Everything in Base, for every seat
350 agent credits per seat, pooled
Shared team workspaces
Automated change monitoring
3 GB of cloud storage per seat

Agency questions

Create your first workspace.

Turn websites into SEO knowledge bases. Free to start.

Download for desktop