A Link-Building Proposal Shows a High DR. What Should You Verify?

A high Domain Rating (DR) or Domain Authority (DA) score is not proof that a website is a useful publisher, that a proposed link will help your business, or that a vendor has earned the score legitimately. DR is Ahrefs' proprietary comparison of backlink profiles; DA is Moz's proprietary metric. Neither is a Google ranking score. Treat either as a screening clue, then inspect the actual sites, pages, links, commercial terms, and risk controls.

The goal of a vendor review is not to label a provider a scam from one metric. It is to establish what you are buying, what evidence supports the claim, how the link will be qualified, and what would make you reject the placement. Google defines link spam by intent to manipulate ranking systems and lists buying or selling ranking links, automated link creation, excessive exchanges, and paid links that pass ranking credit among its examples. Paid advertising and sponsorship can be legitimate when links are qualified with rel="sponsored" or rel="nofollow". Google Search spam policies · Ahrefs on DR

Read the score as a vendor metric, not a guarantee

Ask which tool produced the number, when it was checked, and whether the screenshot shows the root domain or a specific URL. Third-party metrics use their own crawls and calculations; values can differ across tools and change as their databases update. A high score alone says little about a site's current editorial purpose, audience, search visibility, outbound-link behavior, or fit for your readers.

Ask for the proposed publisher URL and the exact target page before discussing a package. Review the site manually: Does it publish coherent work for a real audience? Are recent articles on-topic? Do author and contact details make sense? Are pages dominated by thin guest posts, unrelated categories, or commercial anchors? Does the sample page attract relevant readers or appear to exist mainly to host links? A genuine editorial site can still be a poor fit; a weak-looking score is not, by itself, evidence of manipulation.

Request evidence that can be checked

Do not request private Search Console access as a routine sales proof. If a publisher voluntarily shares first-party evidence, document the property, permission, date range, and limits; otherwise, do not pretend a third-party estimate is verified traffic. Never share your account credentials or grant broad access just to validate a sales pitch.

Evaluate the proposed method before the price

Ask the provider to classify each placement: independent editorial coverage, paid sponsorship, guest contribution, directory listing, or another format. These are not interchangeable. A paid relationship should be disclosed to readers where required and its link qualified appropriately. A vendor promising guaranteed ranking improvement, a fixed number of “authority” points, or a specific AI citation lift is promising an outcome that a score or placement cannot establish.

Inspect anchor text and destination. A natural citation should help a reader reach a relevant source; a package built around repeated commercial exact-match anchors is a warning sign. Check whether the page is indexable and canonicalized as expected, but remember that eligibility checks do not guarantee indexing or ranking. Do not buy a placement solely because a tool estimates traffic or because the page has a high score.

Set acceptance criteria in writing before purchase: approved publisher list; topic and audience fit; final URL; target destination; anchor review; sponsorship disclosure and link qualification; minimum editorial standards; removal or replacement terms; and a report containing the live page and date checked. If the vendor will not specify these, pause the transaction. Do not let a numeric score substitute for the terms.

Run a bounded post-placement review

For any approved placement, save the proposal, final URL, rendered link, qualification attribute, publication date, and invoice. Check whether the page loads, is relevant, and matches the agreed terms. Track referral visits and assisted outcomes separately from rankings; annotate the placement date and avoid attributing broad organic changes to one link without supporting evidence. If a link violates policy or contract terms, document the facts and contact the vendor through the agreed remedy. For a large or suspicious link pattern, assess it against Google's documentation rather than filing a speculative disavow request.

60-second first-pass checklist

1. Open the exact publisher URL and article, not just the score screenshot.
2. Search the site for recent topics, authorship, and unrelated sponsored content.
3. Confirm what DR or DA measures, which tool reported it, and the check date.
4. Ask for the link attribute, anchor, destination, disclosure, and removal terms.
5. Compare the acquisition method with Google's link-spam examples.
6. Mark the proposal continue, request evidence, or decline; do not call it fraudulent from the score alone.

Short-video script: The score is not the placement

Opening: “An SEO vendor sent you a DR screenshot. What does that actually prove?”

Visual: Show a generic score card, then the actual publisher page and link context.

Narration: “DR and DA are third-party metrics, not Google scores. Check the exact page, audience, editorial context, anchor, link qualification, and contract terms. A high number is a clue to investigate—not proof of traffic, quality, or ranking impact.”

Close: “Ask for the live sample URL before you buy a package.”

Educational carousel: Six checks before buying a link placement

1. Cover: “High DR? Verify the placement.”
2. Metric: Identify the tool, date, and URL scope behind DR or DA.
3. Publisher: Read recent pages; check topic fit, authorship, and actual reader purpose.
4. Link: Confirm anchor, destination, disclosure, and rel qualification.
5. Method: Compare the sales method with Google's link-spam policies.
6. Contract: Record acceptance, removal, replacement, and reporting terms.
7. Decision: Continue, request evidence, or decline—without treating one score as a verdict.

Field experiment thread: Test the vendor's evidence before a purchase

1/ Select a proposed placement that has not yet been purchased. Save the pitch and the exact publisher URL.

2/ Record the claimed metric, tool, check date, country, sample article, anchor, destination, link attribute, price, and promised outcome. Mark missing fields as “not supplied.”

3/ Have a second reviewer independently assess topic fit, recent editorial quality, disclosure, and policy risk using the same checklist. Do not show them the vendor's DR number until their first rating is complete.

4/ Compare the reviewers' findings with the written offer. Ask the vendor to resolve material gaps; do not infer deception from a mismatch alone.

5/ Decide using pre-set criteria: accept, request evidence, or decline. This is a due-diligence test, not an experiment that proves a ranking effect. If a placement is later approved, track referral and business outcomes separately from ranking changes.

Tool-neutral prompt pack: Review a link-building offer

Prompt 1 — Claim audit

Review this proposal [text] and publisher URL [URL]. Separate claims, supplied evidence, missing evidence, and assumptions. Explain what DR/DA can and cannot establish. Do not call the vendor fraudulent and do not predict ranking gains.

Prompt 2 — Policy comparison

Compare the described acquisition method [method] with the supplied current Google Search spam-policy source [URL]. Quote only short relevant phrases, classify each risk as supported, uncertain, or not indicated, and identify what additional facts are needed. Do not invent policy violations.

Prompt 3 — Contract checklist

Turn this quote and contract excerpt [text] into acceptance criteria for publisher URL, article, link target, anchor, qualification, disclosure, publication date, removal/replacement, and reporting. Flag ambiguous terms. Do not approve or buy anything.

Stop-doing swipe file: Replace score-based buying

Stop: “This domain has DR 80, so the link is safe and powerful.”
Use: “The tool reports DR 80 on [date]. We still need to review the live publisher, specific page, audience, context, and method.”

Stop: “Guaranteed do-follow links will raise rankings.”
Use: “Show the acquisition method and link qualification. We will not treat a paid ranking guarantee as evidence of a safe or effective placement.”

Stop: “A traffic screenshot proves real readers.”
Use: “Name the data source, date range, country, and landing pages. If those cannot be checked, label the claim unverified.”

Stop: “The vendor is a scam because its score looks suspicious.”
Use: “The score alone does not establish fraud. Here are the specific claims and evidence gaps we can verify.”

Hook–Value–Template: Review before you buy

Hook: “A backlink score is not a publisher review.”

Value: Separate the third-party metric from the actual editorial page and contract. This helps a team question weak evidence without making unsupported accusations or promising ranking outcomes.

Template: “For [publisher URL], the vendor claims [metric/value] from [tool] checked on [date]. The proposed page is [URL], the link points to [destination], uses [anchor], and is qualified as [attribute]. The commercial relationship is [disclosure]. Evidence supplied for audience and editorial fit: [items]. Unresolved questions: [items]. Decision: [continue / request evidence / decline]. We will measure [referrals and qualified outcomes] separately from [rankings].”

Example: “For example.com/article, the proposal shows DR 62 from Ahrefs, checked 12 October. We have the live sample page, but no evidence for country-level audience or removal terms. The vendor has been asked for those details; no purchase decision has been made.”

This checklist evaluates a proposal; it does not establish that any specific vendor manipulated a metric. Verify the current policy and contract before acting.