# Moz alternative, compared on shape

> Proprietary authority metrics against measured observations with named provenance. What netweft refuses to compute, and why that is sometimes the wrong choice.

Source: https://netweft.com/compare/moz

netweft is a Moz alternative for teams that want numbers from a named provider rather than a proprietary authority score. Moz is organised around metrics it computes itself from an index it maintains itself. netweft deliberately publishes no score of its own invention — every number in it either came from a named provider or is a direct observation, and it says which. That is a real trade, and for some teams it is the wrong one.

Nothing below states Moz's price, counts its features or rates its data.

## What a lookup costs

**netweft.** Priced per operation in credits, and the price is shown before the operation runs. One credit is $0.0001 of raw vendor cost, the reservation is a ceiling, and the settled charge is read off what the vendor actually billed.

**Moz.** Priced per seat and per plan, with monthly allowances — keyword lookups, tracked keywords, crawled pages — that reset on a cycle. What an individual lookup costs is not a number the interface has to show you, because it is not a number the billing model uses.

## What ranking history is

**netweft.** A rank check is a stored observation: keyword, location, device, position, the URL that held it, and the moment it was taken. History is the list of those rows, and a week where the domain did not rank is stored as a category rather than as a zero or a gap.

**Moz.** Rank history is a first-class feature in every suite of this kind. What differs is not whether it exists but whether the absence of a ranking is a value you can read back, and whether the number you are shown was observed or derived.

## What a machine can read

**netweft.** The whole HTTP API is described by an OpenAPI 3.1 document, and there is an MCP server at POST /mcp under a scoped API key, so an agent can read a workspace's audits, keywords, rankings and project overview without a person in the loop.

**Moz.** An HTTP API is normally available on the higher tiers, priced in its own units. An MCP surface, where one exists, is a separate product decision from the API.

## Whose metrics you are reading

**netweft.** No score netweft invented appears anywhere in the product. Keyword difficulty comes from the provider and is labelled as the provider's; a position is a position; a crawled issue is classified by severity against a documented rule, not scored.

**Moz.** Domain Authority and Page Authority are the product's own metrics, modelled from its own index, and much of the tool is organised around them.

## What netweft does not do

- Domain Authority, or any proprietary authority metric
- A link index crawled in-house
- Local listing management
- Content optimisation tooling
- A free tier of any kind

## Pick Moz when

Domain Authority is the reason to use Moz. It is a metric a lot of the industry has agreed to talk in, and netweft does not compute it or any substitute for it. If a report has to carry a DA number, netweft cannot produce one.