silkra

Troubleshooting

What usually went wrong, and what to try first.

Summarize

Start with the symptom. Most of these point at a setting or a surface, not a reinstall.

Start screen and preview

SymptomTry this
Preview is empty, or the site will not mapConfirm the host is reachable. Try a sitemap URL, or a list if you already have URLs. Robots or a blocked sitemap can hide the folder map even when the site is up.
The path you typed was not foundSilkra falls back to folders it did find. Pick one, or paste a path that exists.
Folder count is unknownThe folder exists but was not in the sitemap. Start anyway and use the page limit.
Host is unreachableEdit the URL. Check the host, protocol, and that you can open it in a browser.

How to start a crawl →

The crawl

SymptomTry this
Pages are thin or emptySwitch JavaScript rendering to Always render on SPAs. Static HTML only is the wrong call there.
Timeouts or a stalled runRaise request timeout, slow the pace, or lower max pages. Pause, then resume.
403 or a bot wallTry the Chrome user-agent. Leave robots on unless you run the host. Some hosts you cannot crawl.
Rate-limitedThe notice shows on the progress view. Conservative pace or Eco mode, then try again.
Interrupted banner on the tableResume, keep the partial version, or delete that version. There is no undo on delete.
  • Stop: keeps what you already have.
  • Cancel: tears the run down.

Crawl settings →

After the crawl

SymptomTry this
First run is slow, or it is downloadingThe first intelligence pass on a machine may download an on-device model, about 35MB, once.
Map or semantic search is unavailableEmbeddings and clusters are still running, or this crawl has none. Wait, or check that the run finished.
Refresh produced no change logThe first crawl has none. You need a completed refresh (v2 or later). If the refresh failed, there is nothing to compare.
Paid features locked after a cold start offlineSign in again. Last-known plan only holds on a warm session.

Refreshing a crawl → Change log → Semantic map →

Connectors and MCP

SymptomTry this
Connector will not connectConfirm you are signed in and your plan includes integrations. Retry OAuth, or replace the key or credentials requested on the connector page.
Card says ReconnectThe saved authorization expired or was revoked. Open the connector and authorize that provider again.
Agent says a connected service is unavailableOpen the connector, finish any site, project, board, or team binding, then turn on Available to agent.
Search Console columns are missingConnect Search Console, pick a property that covers this host, and make it available to the workspace.
Ahrefs rejects the keyUse an Ahrefs MCP key, not an API v3 key.
Data provider returns no resultConfirm the provider plan includes API or MCP access and has units or credits remaining.
Webflow cannot match a pageConfirm the bound site owns the crawled URL. CMS and collection item pages are not writable in this version.
WordPress reads a page but cannot update SEO fieldsYoast or Rank Math may need their metadata fields exposed to the REST API.
Jira, monday.com, or Linear rejects approved workConfirm the bound destination still exists and check its required fields or board columns.
Drive export fails after connectingOpen Google Drive, reconnect the account, then retry the export.
MCP client shows no sitesSync a completed crawl from Manage MCP on the desktop, then reconnect the client.

Connections → MCP →

Workspaces

SymptomTry this
Signed out, workspaces still thereExpected. Sign-out does not delete local work.
Deleted the wrong workspaceGone on this device. There is no undo.
At the workspace capDelete one you do not need, or upgrade. The start screen says so before you scrape.

Workspaces →