About
About SEO Uptr and why links get an uptime treatment
We build a REST API over our own link index, and we wrote it for people who already own a pager.
The idea
Backlinks behave like dependencies. You did not write them, you cannot restart them, and they fail without any message. The people best prepared for that are site-reliability engineers, so SEO Uptr borrows their habits: baselines, severity levels, runbooks and cheap, frequent checks. That is backlink monitoring without the dashboard.
The service itself is simple. Our own crawler feeds our own index: 181,132,097 domains, 2,774,625,913 domain-to-domain links and about 798.5 billion backlinks, refreshed roughly monthly. You query it over HTTPS and get JSON.
What we stand behind
Four commitments, written as things you can test.
Plain pricing
Prepaid credit at $0.0001 each, no subscription, $100 free on sign-up.
Honest freshness
The index moves about monthly, and every page on this site says so.
Narrow scope
Link data only. For keyword research or rank tracking, use Ahrefs or Semrush.
Readable runbooks
Start with the severity table or the lost-link recipe.
Free first look
Four actions need no key at all, so you can test the shape of the data before signing in.
What we deliberately leave out
No keyword database. No rank tracker. No daily crawl of your own site. Those are real jobs and Ahrefs and Semrush do them well, so we do not pretend. Our scope is the link graph, and we try to be good at that one thing.
We also leave out scores that promise outcomes. Our DR is a plain log of referring domains, published as a formula, round(100 · log(ref_domains+1) / log(2·10^7)). It is meant for sorting a list of domains, and it is not a prediction of rankings. Compare it only with itself.
There are no ranking guarantees here, and no claim that any link pattern is safe from Google's spam systems. We describe what the data shows. You decide the rest.
How a typical team uses it
Picture this, strictly as an example and not a customer story: a small agency with 20 client sites. On Monday a cron job scores every client and every named rival in one call. On the first of the month it snapshots referring domains. A Slack message appears only if a threshold trips. Simple.
Cheap. That agency spends a few cents a month on credits. It spends its attention on the three clients whose numbers moved. Read the competitor job to see how that loop looks in practice, or the traffic runbook for the day something already broke.
Who writes this
The pages are written by the SEO Uptr research team. We do not publish named testimonials or customer case studies, because we would rather show you a worked example marked as hypothetical than an invented success story.
Ask through the account page. You can also read the reference first, which answers most of them.
Where the name comes from
Uptr is short for uptime report. A status page tells you whether a service is up, and the same idea applies to a link profile: is it where it was last week, and if not, by how much. We kept the name as a reminder of that question.
We write runbooks because a runbook survives staff turnover. Whoever is on call in March can read the same steps that were written in October, run the same three commands and reach the same conclusion. That is the standard. We try to meet it.
Feedback is welcome. If a recipe breaks or a number looks wrong, use the contact options on the account page and include the command you ran. Details help.
