Screening a prospect list: one bulk call, then three compares
A consultant's list often has hundreds of domains and no time. To check my website backlink position against a long set of targets, run one bulk call to sort, then compare for the shortlist.
LinkSkimmr research team ·
Step one: sort the whole list for 1 credit
bulk_dr takes up to 2,000 domains in a single call, by GET with ?domains= or a POST body. A POST is easier once the list passes a few dozen entries.
bash
curl -X POST "https://linkskimmr.com/api.php?action=bulk_dr&key=sk_live_..." \
--data-binary @prospects.txt
# prospects.txt: your list of bare domains
# billed once: 1 credit = $0.0001
Parameters and what they do
Taken from the API reference. Every call returns ok, and authenticated ones add _credits with the cost and the remaining balance.
Parameter
Used with
Meaning
action
all
Which endpoint to run, for example bulk_dr or compare
q
single-domain actions
The domain being looked up
domains
bulk_dr, compare
List of domains; up to 2,000 for bulk_dr, up to 20 for compare
key
paid actions
Your sk_ key, or send Authorization: Bearer instead
page, per
listings
Pagination; per ranges from 10 to 5000
sort, order
listings
Sort field plus asc or desc
From two thousand rows to a shortlist of twenty
Sort the bulk output by DR, cut the bottom, then cut anything whose DR is far outside the band your client lives in. Done.
A hypothetical for scale: a list of 1,500 guest-post targets drops below 400 once you remove everything under DR 20, and the rest of the work happens on a short list instead of a spreadsheet nobody wants to open. That is an example, not a measured result.
Then use compare, which takes up to 20 domains for 1 credit. Pick the survivors in batches of twenty, and you can read the profile of each side by side before anyone writes an outreach email.
When the list is your own clients
The same trick works on a portfolio. Put every client domain in one file and run it on the first of each month.
A monthly sweep is the honest rhythm, since our index refreshes about once a month and anything faster mostly shows noise. Store each month's output next to the date, and a column of DR values turns into a trend line within a quarter.
If one client drops several points at once, run the ten-minute routine on that site and check the top pages for redirect trouble before blaming anyone.
Screen hygiene
Strip protocol and paths so the file holds bare domains
Deduplicate before the call, not after
Keep the lookup date in the filename of the output
Check the HTTP code: 401 means a missing or bad key, 402 means the credit ran out
Spot-check five survivors with the free overview call
A cost sketch, hypothetical
Example only: a 1,800-domain list costs 1 credit to sort, three compares of twenty survivors cost 3 more, and an overview of each shortlisted site is free. Four credits is $0.0004.
Fit check
Good for screening, not for judging a single site
DR is a blunt size measure. It sorts a list quickly and cannot tell you whether a particular site is relevant, edited or read by anyone, so the last step is always a human glance.
Index refreshed about monthly
Our DR is not Ahrefs DR or Moz DA
$100 free credit covers about a million basic calls
Bulk questions
Is the bulk output the same as a full report?
No. bulk_dr returns the rating for each domain so you can sort a list. For anchors, linking domains and top pages on a chosen site, call the 2-credit actions one site at a time.
What if my key runs out mid-job?
The API returns HTTP 402 when credit runs out. Top up in USDT (TRC-20) from the account page and rerun only the calls that failed.