A high score is a research input, not the offer itself
A domain-authority backlink usually means a link from a site described using an authority metric. The phrase leaves important questions unanswered: which provider, which page or domain, which date, and what publishing relationship? A label such as “DA67” describes a reported value; it does not describe the exact page, the reader’s need or what the publisher will deliver.
Begin with the proposed source page and useful destination. Then use a named metric to prioritize further investigation among comparable candidates. Do not turn a supplier’s short label into proof that the score came directly from the named original provider or was measured today. Keep the supplied value intact while recording what is still unknown.
Keep the metrics and their scopes separate
Moz’s 2019 explanation of Domain Authority describes a comparative prediction of ranking potential, rather than a Google score. Its legacy API documentation distinguishes root-domain DA from page-level PA. These sources explain the concepts; their historical model and API version are not presented here as the current implementation.
Ahrefs defines Domain Rating as domain-wide backlink-profile strength on a logarithmic scale. Semrush’s Authority Score combines link, estimated-traffic and profile signals. Similar numeric ranges do not make these measures interchangeable. Do not average DA, DR and Authority Score, infer a missing one from another, or treat a domain score as the score of the precise article containing your reference.
A saved catalog record shows why the dates matter
The table uses a real, anonymized catalog record observed on 2026-10-26, selected by stable record order rather than quality. It is not a recommendation or a representative sample of the network. No publisher domain is disclosed. The supplier supplied DA 5 and PA 18; its catalog synchronization occurred on 2026-10-26. The underlying metric measurement date and exact measured PA page were not supplied.
A separate saved analytics report contains Authority Score 2, collected on 2026-10-24 at 14:30 UTC, with worldwide/desktop labels. That is historical report evidence, not a new check. DR and the catalog’s first-seen timestamp are absent. The missing values remain unknown, not zero; a first-seen date would not establish domain registration age anyway. Different field origins must stay visible beside the numbers.
| Field | Saved value | Date and scope | Interpretation |
|---|---|---|---|
| Supplier DA | 5 | Catalog sync 2026-10-26 | Measurement date and original provenance unconfirmed |
| Supplier PA | 18 | Catalog sync 2026-10-26 | Exact measured page and date unconfirmed |
| Saved Authority Score | 2 | Collected 2026-10-24 14:30 UTC; worldwide / desktop | Separate historical analytics observation |
| DR | Not supplied | No observation supplied | Unknown; do not infer from DA |
| First seen | Not supplied | Catalog history field absent | Unknown; not domain registration age |
Compare like with like before deciding what to inspect
For a useful comparison, hold the provider, metric definition, entity scope and observation period as consistent as possible. If one candidate has fresh provider evidence and another only an undated supplier label, record the asymmetry. It may justify asking for better evidence, not automatically rejecting the second publisher or declaring the first safer. A change in the comparison set can also change a relative score.
A higher number does not answer whether the source is relevant, whether an article has useful content, whether the proposed location is available or whether the relationship is paid. Review those separately. For a “high DA” offer, request the exact source opportunity, metric provenance and commercial terms before making a selection. A current catalog filter is a starting point for research, not an independently verified score certificate.
Build a metric record that survives a handoff
Save the supplied label and value, original provider if confirmed, entity scope, measured date if known, collection date and evidence reference. Keep unknowns explicit. The worked CSV reproduces the anonymized observations; the blank sheet provides the same review columns. Neither file performs a new measurement, refreshes analytics or reveals a locked publisher domain.
Next, connect the metric record to a page-level editorial review and a concrete delivery check. Assign someone to resolve missing provenance, examine the proposed passage and confirm the final reference after publication. The quality guide covers broader publisher evidence; the analysis guide keeps data-source limits visible; the HTML guide checks actual link attributes. This record connects their evidence without collapsing it into one score.
Download the metric evidence example · Download a blank metric review
Do not price a guaranteed ranking change from one number
There is no fixed number of DA or DR points that this guide can promise for one acquired link. A source’s score is not an additive transfer to your own score, and a change in a proprietary metric is not proof of a Google ranking change. Report observed publication, relevant visits and agreed business outcomes separately, with their own dates and measurement limits.
This page does not certify dated high-score lists, named-platform placements or free opportunities. A numerical threshold such as DA90 is not a universal quality requirement. If a supplier advertises a specific score, verify its identity, scope and freshness rather than selecting by the digits alone. Preserve the initial record so a later revision can be explained instead of silently replacing the original evidence.