Pull backlink data from both Ahrefs API v3 and the Semrush Backlinks API for a cross-verified backlink audit
domain: docs.ahrefs.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
For Ahrefs, create an API key in Account settings (workspace owner/admin only) and authenticate requests with an Authorization: Bearer header; note keys expire after one year and must be rotated
Query the relevant Ahrefs Site Explorer v3 backlinks endpoints for referring domains, backlink lists, and anchor text, applying the documented row-limit and filtering parameters per plan tier
For Semrush, call the Backlinks API (v4 analytics/backlinks endpoints, e.g. the overview report) with a target and scope (ROOT_DOMAIN, SUBDOMAIN, SUBFOLDER, or PAGE) parameter
Track API unit consumption for Semrush calls before running large jobs, since cost varies by endpoint and row count and can exhaust a plan's balance quickly on wide audits
Normalize both providers' output (domain rating/authority scores are provider-specific and not directly comparable) into a common schema keyed by referring domain and target URL
Flag backlinks appearing in only one provider's index as lower-confidence signals rather than treating either dataset as a complete crawl of the link graph
Known gotchas
Ahrefs and Semrush maintain independent web indexes with different crawl coverage and refresh cadence, so backlink counts and 'toxic link' scores will disagree between the two — cross-referencing, not picking one as ground truth, is the point
Authority-style metrics (Ahrefs Domain Rating, Semrush Authority Score) are proprietary and not equivalent across vendors despite superficially similar 0-100 scales
Both APIs meter usage (rows/units) rather than being flat-rate, so an unbounded backlink audit against a high-authority domain can consume a disproportionate share of a monthly quota in one run
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?