# Why We Stopped Buying Domain Authority and Computed Our Own

> Agent-friendly Markdown of https://www.buildseo.org/blog/why-we-stopped-buying-domain-authority — full index for AI agents: https://www.buildseo.org/llms.txt

_Authority scoring · 9 min read — Anurag Pattnaik, Platform engineering, Andolasoft · July 21, 2026_

A rented quality metric makes every qualification decision unexplainable and every renewal a dependency. Here is the signal set we replaced it with, how the weights were chosen, and what it costs to be wrong.

Every link-building pipeline needs a gate. Before an agent writes copy for a publisher, uploads a logo, and files a form, something has to decide whether that publisher is worth the attempt at all. For most of the category, that gate is a number bought from a vendor — a single composite score that arrives with no derivation and no recourse.

We built the first version of BuildSEO that way too. It worked until an operator asked a reasonable question about a rejected publisher: why? We could point at a threshold. We could not explain the number the threshold was applied to.

## What a rented score actually costs

Three costs, in ascending order of severity. The metered API bill is the obvious one and the least important. The second is coupling: a qualification stage that cannot run without a third-party quota is a pipeline that stops when someone forgets to renew a key. The third is the one that matters — an opaque score cannot be argued with, so it cannot be improved.

> If you cannot show an operator why a publisher scored 47, you have not built a qualification system. You have bought a coin flip with a decimal point.

## The signal set

The BuildSEO Authority Score is assembled from eight public signals, each independently observable and each stored with its own contribution to the total. Nothing in the list requires a paid data partner.

| SIGNAL | MAX |
| --- | --- |
| Index status | 18 |
| Organic visibility | 18 |
| Spam signals (inverted) | 16 |
| Category fit | 15 |
| Technical health | 14 |
| Domain age | 11 |
| HTTPS and content size | 8 |

Hard-fail checks sit in front of the score, not inside it. A publisher that is unreachable, de-indexed, serving over plain HTTP, or classified into an excluded vertical never reaches the weighting step. Scoring a site we would refuse to submit to is wasted compute and a misleading record.

## Where the weights came from, and why they are provisional

The initial weights are a judgment call by the engineers and SEO operators who ran these campaigns by hand for years. We are explicit about that in the product: early scores are provisional. The weights only become defensible once enough placements have completed a full lifecycle for us to regress against real outcomes — acceptance rate and, more importantly, whether the link is still live ninety days later.

Because each signal's contribution is persisted per publisher, recalibration is a re-weighting exercise rather than a re-crawl. That property is the whole argument for computing the score yourself.

## The middle band belongs to a human

Scores in the 40 to 59 range, and any otherwise-qualified publisher where the model's confidence is low, route to an explicit operator review queue. This was not the original design. The original design auto-rejected them, which quietly discarded a meaningful slice of usable inventory and gave us no signal about the boundary.

Treating manual review as a first-class state rather than a stall changed the qualification state machine and, unexpectedly, became the fastest source of calibration data we have.

**Takeaways**

- Store each signal's contribution, not just the total — auditability and recalibration are the same feature.
- Keep hard-fail checks outside the weighted score so rejections stay unambiguous.
- Route the ambiguous band to a review queue; it is inventory and training data at once.
- Treat vendor authority metrics as optional enrichment, never as a gate you cannot open yourself.

## Keep Reading

- [The Hidden Cost of Manual Link Submission: A 5-Year ROI Case Study](https://www.buildseo.org/blog/the-hidden-cost-of-manual-link-submission.md): One agency spent $840k on manual link building over five years. We mapped where every dollar went, and why their cost per verified link was 12× higher than they reported.
- [Cost Per Link: How To Calculate It, Why Vendors Hide It, and What It Actually Means](https://www.buildseo.org/blog/cost-per-link-what-it-actually-means.md): Every link-building platform quotes a different number. Here's how to calculate the one that matters: cost per link still live at 90 days. And why that number is the only one your CFO should care about.
- [The Link Database Advantage: Why Campaign Two Should Cost 20% Less Than Campaign One](https://www.buildseo.org/blog/link-building-database-compounding.md): Campaign one teaches you everything about your vertical. Campaign two should cost less, take less time, and deliver more verified links — because you kept what you learned.

## See the Score Run on Your Category

We will qualify live publisher inventory in your vertical and show you every signal behind it. Schedule a demo: https://calendly.com/buildseo-sales/30min

---

[All posts](https://www.buildseo.org/blog.md) · [BuildSEO AI](https://www.buildseo.org/index.md)