Resources · Make integration

DataForSEO Backlinks API Make integrationAutomate DataForSEO Backlinks API with Make.

Tired of copying backlink reports by hand? The DataForSEO Backlinks API Make integration gives you 21 action modules to pull link data into your scenarios. This guide is for SEO and ops teams: connect your account, build a first scenario, then pick the right module.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the DataForSEO Backlinks API Make integration do?

The DataForSEO Backlinks API Make integration lets a Make scenario, the automation you build as a chain of modules, ask DataForSEO for link data and pass the answer to your other apps. A module is one brick of that chain. All 21 modules here are actions: they run when something earlier in the scenario starts them.

Watch the links you win and lose. Put Get Bulk New & Lost Backlinks behind a schedule and send what it returns to the sheet or chat your team already reads.

Study a rival's link profile. Get Competitors and Get Domain Intersection are named for comparing domains, which is where most outreach lists start.

Screen a list of domains before you contact them. Get Bulk Spam Scores and Get Bulk Ranks work on several targets in one call, going by their names.

Know the limits before you build. The official doc gives no description for any module, so the notes below go by module names, and the doc itself says it was generated by AI and may contain mistakes. There is no trigger either: DataForSEO never starts a scenario on its own. For anything the list misses, Make an API Call reaches the rest of the API.

New to the editor? The Make training walks through the basics. The same app often has an n8n node too; the n8n vs Make comparison helps you pick, and Make pricing explains how operations are counted.

Connect

How do you connect DataForSEO Backlinks API to Make?

  1. 01

    Add a module and open the connection

    In your scenario, add any DataForSEO Backlinks API module and click Create a connection. A connection is your DataForSEO account linked to Make once, then reused by all 21 modules.

  2. 02

    Name the connection

    The Connection name field is optional. A clear label still helps when a client account and your own account sit side by side in the same Make organization.

  3. 03

    Paste your Basic Auth credentials

    In DataForSEO, open Dashboard, then API Access. Copy the login and the password shown there into Make, and save. You need an account with Backlinks API access and enough balance.

First scenario

Your first scenario with DataForSEO Backlinks API

GoalWhen the scenario's schedule fires, Make asks DataForSEO for a backlink summary, then fetches the new and lost backlinks.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big +. Search for DataForSEO Backlinks API and pick Get Backlinks Summary as the first module.

  2. 02

    Link your account

    Click Create a connection and paste the login and password from API Access. Then fill in the fields the module shows, starting with the domain you want to follow.

  3. 03

    Add the second module

    Click the + on the right of the first module and choose Get Bulk New & Lost Backlinks. Map values from the previous module instead of typing them again.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles, the items passed from one module to the next, so you can read what DataForSEO actually sent back.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario runs every 15 minutes by default; pick the interval that fits your reporting, then switch the scenario on.

Modules

What each DataForSEO Backlinks API module does

DataForSEO Backlinks API gives you 21 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

DataForSEO Backlinks API1

Get Anchors

ActionIn the docs only

Pull the anchor texts that point to a target, going by the module's name, so you see the words other sites use when they link to you.

When to use it
checking whether your brand name or a money keyword dominates the anchors before a link building push.
Watch out
the doc gives no description, so run it once and read the bundle before mapping anything.
DataForSEO Backlinks API7

Get Bulk New & Lost Referring Domains

ActionIn the docs only

Same idea one level up: whole referring domains gained or lost, for a list of targets. A domain counts once however many links it sends, which makes the signal less noisy.

When to use it
tracking whether a campaign brings new sites, not just more links from sites you already have.
Watch out
pair it with the backlink version if you need link-level detail.
DataForSEO Backlinks API8

Get Bulk Pages Summary

ActionIn the docs only

Summaries for several pages rather than whole domains, judging by the module title. Useful when a few URLs carry most of your business.

When to use it
watching the link profile of your key landing pages or product pages together in one operation.
Watch out
feed it exact page URLs from a sheet or a previous module; the doc says nothing about how it handles a domain entered alone.
DataForSEO Backlinks API9

Get Bulk Ranks

ActionIn the docs only

Rank values for a batch of targets, per its name, to sort a list of sites by link authority before anyone spends time on them.

When to use it
qualifying a prospect list for guest posts or partnerships, then keeping only the strongest rows in your sheet.
Watch out
the doc does not explain the rank scale, so compare targets with each other rather than against an outside metric.
DataForSEO Backlinks API10

Get Bulk Referring Domains

ActionIn the docs only

Referring domains for many targets in one pass, according to the title. For each entry of your list, you see which distinct sites link to it.

When to use it
scoring a batch of competitors or acquisition candidates side by side.
Watch out
for the actual list of domains behind one target, Get Referring Domains is the better pick.
DataForSEO Backlinks API11

Get Bulk Spam Scores

ActionIn the docs only

A spam score for each target in a list, going by the name. It helps you filter out doubtful sites automatically instead of eyeballing them.

When to use it
cleaning an outreach list before it reaches your email tool, or flagging risky linking domains for a disavow review.
Watch out
treat the score as a signal to check, not a verdict, since the doc gives no scale.
DataForSEO Backlinks API12

Get Competitors

ActionIn the docs only

Find the domains that share a link profile with yours, as the title implies. It turns a vague question about who competes for the same links into a list you can act on.

When to use it
the start of a competitor analysis, before comparing profiles with Get Domain Intersection.
Watch out
expect several results; add a filter in Make if you only want the first few.
DataForSEO Backlinks API13

Get Domain Intersection

ActionIn the docs only

Intersection means overlap: sites linking to several domains at once, going by the name. Those are the sites most open to linking to you as well.

When to use it
building an outreach list from sites that already link to two or three of your competitors.
Watch out
decide which domains you compare before the run; the doc does not document the inputs.
DataForSEO Backlinks API14

Get Domain Pages

ActionIn the docs only

The pages of a domain with their link data, by the look of the title. You find out which URLs attract links and which get none.

When to use it
spotting a competitor's most linked content to inspire your next article or resource page.
Watch out
a big site can return many bundles, and every later module processes each one as a separate operation.
DataForSEO Backlinks API15

Get Domain Pages Summary

ActionIn the docs only

A condensed view of a domain's pages instead of the full page list, judging by its title. Lighter to read and lighter to pass on.

When to use it
a client report that only needs the overview of a site, not every URL behind it.
Watch out
switch to Get Domain Pages when someone asks which page is behind a figure.
DataForSEO Backlinks API18

Get Page Intersection

ActionIn the docs only

The page-level cousin of Get Domain Intersection: overlap between specific URLs, going by the name. Sharper when you compete on one topic, not a whole site.

When to use it
finding sites that link to two competing guides so you can pitch yours to them.
Watch out
enter full page URLs; comparing a page with a domain gives a different question.
DataForSEO Backlinks API19

Get Referring Domains

ActionIn the docs only

The list of distinct sites that link to one target, as the name says. Each domain appears once, which keeps the list readable.

When to use it
pushing linking domains into a sheet so your team can tag partners, directories and doubtful sites.
Watch out
expect one bundle per domain; add an aggregator in Make if you want a single row or message.
DataForSEO Backlinks API20

Get Referring Networks

ActionIn the docs only

Referring networks group linking sources at a network level rather than by domain, going by the module title. It helps reveal many links coming from one owner.

When to use it
checking whether a sudden wave of links comes from a single network before you celebrate it.
Watch out
the doc gives no definition, so confirm what a network means here in the first bundle.
DataForSEO Backlinks API21

Make an API Call

ActionIn the docs only

Your way out when none of the named modules covers an endpoint: it calls any endpoint of the DataForSEO Backlinks API with the same connection.

When to use it
an endpoint you saw in the DataForSEO docs has no dedicated module in Make.
Watch out
you write the request yourself, so keep the vendor's API reference open while you set it up.
Need help

Need help automating DataForSEO Backlinks API with Make?

A person reads every message.

FAQ

DataForSEO Backlinks API and Make: common questions

01Is the DataForSEO Backlinks API Make integration free?
Yes on the Make side: it is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run and 512 MB of data transfer. DataForSEO is another matter: the doc requires an account with Backlinks API access and a sufficient balance, so check their pricing page before you schedule anything. Paid Make plans lower the interval to 1 minute and count usage in operations.
02What do you need to connect DataForSEO Backlinks API to Make?
You need a DataForSEO account with Backlinks API access and enough balance, plus the Basic Auth credentials from Dashboard, then API Access. Copy the login and the password into the Create a connection window in Make. The password stays visible only for the first 24 hours after registration; later, the Send by e-mail button sends it to your registration address. Once saved, the same connection serves every module of the app.
03Does the DataForSEO Backlinks API Make integration work in real time?
No, because the app has no trigger module: DataForSEO never starts a scenario by itself. You start it another way. The simplest is scheduling, the clock on the first module, which runs a new scenario every 15 minutes by default and down to 1 minute on paid plans. You can also place a trigger from another app first, such as a new row in a sheet, and let a DataForSEO module run right after it.
04What if a DataForSEO Backlinks API module is missing in Make?
Use Make an API Call. It reaches any endpoint of the DataForSEO Backlinks API with the connection you already set up, so an endpoint without a dedicated module is still within reach. Keep in mind that the official Make doc for this app gives no module descriptions and states it was generated by AI and may contain mistakes. Verify important details in the DataForSEO documentation, and contact DataForSEO directly for questions about their API.
05Should you use Make or n8n for DataForSEO Backlinks API?
It depends on the tool your team already runs. Make offers 21 ready modules for this app, a visual editor and a Free plan to test with, which is enough to judge whether it fits your reports. The same app often has an n8n node as well, so if your automations already live in n8n, check there before you rebuild anything. Choose on the modules you need and on where the rest of your workflows sit.