Skip to content

Free DR lookups need no key. Sign in for $100 in credit.

LinksVerifier
LinksVerifierSign up

Hypothetical

Backlink audit example: one 40-link order, re-checked

Every figure here is invented to show the method. No real client, vendor or result is described.

This is an example

The agency, the vendor, the domains and every number below are made up. They exist to show arithmetic and structure. Your batch will differ.

The setup

Imagine an agency that bought 40 placements for one client site, at a fixed price per link, with a promised DR floor of 30 and a 60-day replacement window. The vendor sheet lists 40 source URLs and 40 anchors.

Nothing here is unusual. The question is how to turn that sheet into a pass-fail table. We use three checkpoints: delivery day, day 30 and day 60.

Checkpoint results in the invented batch

All figures hypothetical
CheckpointLive page fetchedHost in refdomains listRel as orderedNotes
Day 038 of 400 of 40 (not indexed yet)36 of 382 URLs 404, 2 rel=sponsored added
Day 3037 of 4029 of 4035 of 371 more removed, index refreshed on day 22
Day 6036 of 4034 of 4035 of 36Replacements pending for 4

What the example teaches

Day 0 shows zero hosts in the index. That is normal. A zero at delivery is not a defect; a zero after two refreshes is.

By day 60 four links are gone. Two more changed, because they carry a sponsored label that the order did not mention. Notice the difference. Whether the label counts as a defect depends on the contract, so the sheet should say what was ordered in plain words. The glossary lists the rel values you can quote.

The rating floor is checked once with bulk_dr. One call. In the example, 40 domains in one call cost 1 credit, and 3 domains score below 30 using our formula. Those three go into the ticket first because they are objective and cheap to prove.

Sorting the invented failures

Of the 4 missing pages, assume 3 were removed by the publisher and 1 moved to a new URL. The move is easy to miss. A redirect from the old address would show as a 301 in the saved header dump, which is why headers go into storage beside the HTML.

The 2 sponsored labels are a different class of problem. Not broken. They are not broken links, and the vendor may well say the label is the honest option. Decide in advance whether a label counts, because a dispute settled by taste wastes a week.

Credits spent in the example

StepCallsCreditsDollars
bulk_dr on 40 domains11$0.0001
refdomains at day 0, 30 and 6036$0.0006
anchors at day 6012$0.0002
Total59$0.0009

Rough edges we left in on purpose

The live-page column comes from curl on the tester's machine, not from our API. We do not offer that check, and pretending we did would hide the most laborious part of the job.

Credits are almost beside the point. The labour is reading 40 pages. If you want to cut that, script the grep from the mistakes list and keep your eyes for the 4 or 5 rows that fail.

For a month-by-month view of a whole client portfolio, move on to the cost table. If rankings moved after the batch, the traffic-drop runbook is the next stop.

Verdict rules the example agency might write

  • Pass: page live, host found in the index, rel matches the order, rating at or above 30.
  • Pending: page live and correct, but the host is not in the index and no refresh has happened since placement.
  • Fail: page missing, noindex present, rel different from the order, or rating below the floor.
  • Escalate: any row that fails twice across two checkpoints, with the saved HTML attached to the ticket.