Skip to content
netweft

Five connections, each with a stated permission.

Nothing here is connected by signing in. Google access is requested at the moment a project connects it and not before, so an account that never connects Search Console never grants the scope — and each row below says plainly what netweft is allowed to do with it.

Google Search Console

Per project

Real queries, clicks and impressions for the project's own site, read straight from Google. It sits beside the rank record rather than replacing it: one is what Google reports about a property, the other is what was observed at a position on a date.

Read-only, requested at connection time rather than at sign-in

Google Analytics 4

Per project

Sessions, engaged users and key events for the project. Connected separately from Search Console, so a workspace that wants one and not the other grants one and not the other.

Read-only, requested at connection time rather than at sign-in

DataForSEO

Per workspace

Where netweft's real SEO data comes from — keyword metrics, SERP positions, backlink summaries, domain overviews. The provider sits behind a port, cached and rate limited per workspace. A mock implementation serves deterministic fixtures with no credentials, which is what lets the product run offline; nothing above the port knows which one answered.

Server-side, through a port with a mock implementation behind it

Polar

Per workspace

Subscriptions, top-ups and invoices. Polar is the merchant of record, so the checkout, the tax handling and the receipts are theirs, and the only thing netweft stores is which plan a workspace is on and what it has left.

Merchant of record. netweft never sees or stores a card number

MCP, for agents

Per workspace

An MCP server at POST /mcp, so an agent can read a workspace without a person in the loop. 25 tools across 6 scopes, none of which writes, starts a crawl or spends a credit.

Scoped API key, read-only over stored rows

Everything optional degrades rather than fails.

The cache and the rate limiter fail open. If either cannot answer, every lookup misses and every request is allowed — that is the intended degraded behaviour rather than a failure mode, and it is why a project that has connected nothing still works. The data provider is the same shape: a mock implementation serves deterministic fixtures with no credentials, so the product runs with no vendor account at all, and nothing above the port knows which one answered.

Connect one thing and see what it changes.

Connect Search Console to one project and the first scheduled rank check has something to sit beside.

There is no free tier. Three plans from $50 a month, each opening with a free trial.