Guides

Working notes and step-by-step playbooks: ranking drops, site migrations, keyword gaps, rank tracking, crawl cost and reading an SEO workspace from an agent. Every guide opens with the answer.

Every guide is also served as markdown at its own path plus .md.

How netweft is built, and a prompt to build your own

netweft is four Cloudflare Workers over one D1 database: static marketing and dashboard sites, a Hono API with Workflows and a cron, and an analytics relay. Six decisions shaped it: a provider port, reserve-then-settle credits, stored snapshots, one-statement D1 guards, a read-only MCP surface and no free tier.

Engineering October 15, 2026 5 min read

Read the newest guide

Method

11 guides

What to track, what to audit, and what each number on the screen is for.

Checking a site migration in the first week

Before a migration, audit the old site and run a rank check so there is a baseline. After it, crawl the new site and fix Broken internal link, Redirect chain, Page returns an error, Conflicting canonical and noindex first, then compare a fresh rank check and Search Console with the baseline.

October 15, 2026 3 min read
Diagnosing a ranking drop before you change anything

Confirm the drop is real in the keyword's stored history, check whether the ranking URL changed, compare Search Console clicks and impressions for the same window, then audit the affected page. Change nothing until one of those names a cause.

October 15, 2026 3 min read
Measuring and earning mentions in AI answers

Record your competitors, check AI visibility once per assistant, read Mentions and Share of voice against them, then improve the pages assistants already cite and write the pages your strongest competitors have and you lack. Check again about once a month, when the dataset is rebuilt.

October 15, 2026 2 min read
Finding keyword gaps against a competitor

List the keywords a competitor ranks for, remove the ones your own domain already ranks for, and keep the rest that match a page you could write. In netweft that is two Ranking keywords lookups on Domain overview, a save, a tag, and a tracker on the survivors.

October 15, 2026 3 min read
Planning a topic cluster from one seed keyword

Research a seed, group the ideas into one broad hub term and the narrower questions under it with tags, give each planned page one group, record the pages as hub and spoke key pages in project context, and audit the cluster for orphan pages once it is live.

October 15, 2026 3 min read
Refreshing pages that rank just off page one

Sort Search Console queries by impressions, keep those with an average position between 8 and 20, group them by the page that ranks, and refresh the page that collects the most impressions first. Track the queries before the change ships so the result is measurable.

October 15, 2026 3 min read
Auditing by template, not by page

A large site is a few templates rendered many times, so a finding on forty product pages is usually one fault in one template. netweft groups URLs into shapes by replacing ids, dates and long slugs, measures performance once per shape, up to ten pages, and lists duplicates with the pages sharing them.

October 8, 2026 3 min read
Choosing which keywords to track

Track the keywords whose movement would change what you do next, and save the rest. At the default depth a rank check is 40 credits per keyword per device, so 100 keywords checked weekly on both devices cost about 32,000 credits a month.

October 8, 2026 4 min read
Reading a site audit by severity

Work critical first: server errors, broken internal links, missing titles and pages the crawler was blocked from. Warnings hold most of the ranking work, from duplicate titles to thin content and orphan pages. Info findings are often deliberate. A 403 or 429 means the crawl was refused, not that a page is broken.

October 8, 2026 3 min read
Volume, CPC, difficulty and intent: what each number is for

Volume says how often a term is searched, the twelve-month history says when, cost per click says what a visit is worth to advertisers, difficulty estimates how hard the first page is to reach, and intent says what the searcher wants. None of them says whether your page can rank: that is what a rank check is for.

October 8, 2026 3 min read
What a 500-page crawl costs, and why Lighthouse is opt-in

A crawled page costs one credit, so a 500-page crawl is 500 credits. A Lighthouse pass costs 50 credits a page, so netweft measures a sample, the start URL and one page per URL shape up to 10, adding at most 500 credits. It is opt-in per audit.

March 10, 2026 3 min read

Pricing

5 guides

What an operation costs, and how the balance behaves around it.

Spending a trial's credits on one real domain

A trial gets 3,000 to 8,000 credits by plan, 10 paid requests a minute and no auto top-up. Spend them on one domain you know: an overview, its referring domains, metrics for your terms, one audit, and a tracker on twenty keywords and one device, run by hand.

October 8, 2026 3 min read
Top-ups and auto top-up: when to turn it on

A dollar buys 2,500 top-up credits, from $10 a purchase. They never expire and are spent after plan credits. Auto top-up starts on: under 10% of the allowance it buys $20 more, at most 3 times and $60 a day.

October 8, 2026 3 min read
Reserve, then settle: pricing a call before you know its cost

netweft reserves credits at the rate card's price before a paid call goes out, then reads the real charge off the response and settles against it. The reservation is a ceiling, so a cheaper operation releases the difference, and a workspace that cannot cover it is refused before anything is bought.

September 12, 2026 3 min read
Why netweft has no free tier

Every netweft lookup costs real vendor money before anybody pays anything, so a free tier spends that money on accounts that will never convert. Instead there is a read-only demo, and a short trial with 3,000 to 8,000 credits by plan, a tighter rate limit and no auto top-up.

September 12, 2026 3 min read
What an SEO data lookup actually costs

Almost every number in an SEO tool is bought from a data vendor per call or per keyword. netweft prices one credit at $0.0001 of raw vendor cost, reserves credits before a call runs, and settles the reservation against what the vendor actually charged.

February 17, 2026 4 min read

Integrations

3 guides

Google, agents and the API: what connects, and what it reads.

An agent's first five calls over MCP

Start with whoami for the workspace and plan, list_projects to find the domain, get_project_overview for counts and the latest audit, then get_rank_trend or get_keyword_rank_history for what moved. Read get_credit_balance before suggesting paid work. Every call reads stored rows and spends nothing.

October 8, 2026 3 min read
GA4 beside Search Console, per project

Search Console reports what happened on Google: impressions, clicks, click-through rate and position, by query and page. GA4 reports what happened next: sessions, active users, engagement rate and key events, by channel, device and landing page. netweft reads both read-only, per project, for no credits.

October 8, 2026 3 min read
Why connecting Search Console is two steps, not one

Google access is granted once per account, and the property a project reads is chosen per project. netweft keeps them as two separate steps because a single control that sometimes does one and sometimes both is unpredictable.

February 24, 2026 3 min read

Engineering

6 guides

How netweft is built, and why it is built that way.

How netweft is built, and a prompt to build your own

netweft is four Cloudflare Workers over one D1 database: static marketing and dashboard sites, a Hono API with Workflows and a cron, and an analytics relay. Six decisions shaped it: a provider port, reserve-then-settle credits, stored snapshots, one-statement D1 guards, a read-only MCP surface and no free tier.

October 15, 2026 5 min read
Why netweft's cache and rate limiter fail open

netweft's cache and rate limiter fail open: a cache that cannot answer is a miss, and a limiter that cannot count lets the request through, so the product keeps working, more slowly and more permissively. Choosing that up front is what stops a performance dependency becoming an availability one.

September 12, 2026 2 min read
Why the SEO data provider sits behind a port

netweft's SEO data provider is an interface with two implementations: DataForSEO for real data, and a mock serving deterministic fixtures with no credentials. Nothing above the port knows which answered, so the product runs offline, every test is deterministic, and credit accounting is identical on both paths.

September 12, 2026 2 min read
What a scoped API key is actually protecting

Because every netweft MCP tool is read-only over rows already stored — none of them writes, crawls or spends a credit — a scope cannot withhold a capability, only a subject. The useful one is billing: it is how a key handed to an outside integration is stopped from reading the workspace's balance and plan.

September 12, 2026 2 min read
Reading an SEO workspace from an agent

netweft exposes MCP at POST /mcp under an API key, alongside an OpenAPI 3.1 document for the whole HTTP API. An agent reads a workspace's stored audits, keywords, rankings and project overview, and reading costs no credits because the credits were spent when the observation was made.

March 3, 2026 3 min read
Why a rank tracker should store snapshots, not recompute them

Store each rank check as an immutable snapshot — position, URL and the timestamp it was seen — rather than deriving history on read. A recomputed history can change without the SERP changing, which makes it useless as evidence.

February 10, 2026 4 min read

The product behind the notes.

netweft stores every rank check as an observation and prices every lookup before it runs. Pro starts with a trial.

Start a trial See the whole rate card

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

Guides

The product behind the notes.

Analytics cookies