Skip to content
netweft

Guides tagged credits

10 guides

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

  7. 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.

  8. 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.

  9. 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.

  10. 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.

All guides