This guide is intended to ease the process of modeling your backlink checking software with DataForSEO Backlinks API.
The Backlinks Section is an indispensable functionality part for any backlink analytics tool. It offers whopping data on the target’s backlinks, revealing the ones that are the most valuable, recently gained or lost, and backlinks that are no longer working.
With extensive customization opportunities, any user can tailor the data displayed in this section to their specific needs, be it a backlink audit for their site or competitive backlinks analysis. Whatever the use case, this section will help users to closely examine any of the target’s backlinks, and gain insights for their future link-building campaigns.
Accessing the Backlinks Report, users will discover a goldmine of data on backlinks for a target of any shape and size. Besides a detailed table view with custom data refinement options, users will get a brief summary of the target’s backlink quality and value.
With DataForSEO Backlinks API, you can let users enjoy deep backlink analytics at a lightning speed. Below, we will guide you through producing the Backlinks Report with the Backlinks API. We’ll explore all features and API parameters that help to deliver them.
login="login" \
password="password" \
cred="$(printf ${login}:${password} | base64)" \
curl --location --request POST "https://api.dataforseo.com/v3/backlinks/backlinks/live" \
--header "Authorization: Basic ${cred}" \
--header "Content-Type: application/json" \
--data-raw "[
{
"target": "dataforseo.com",
"mode": "as_is",
"filters": [["dofollow", "=", true], "and",["url_to", "like", "%blog/%"]],
"limit": 1000
}
Counters are a great way to give users a quick understanding of a target’s backlink performance. The total count of backlinks helps to evaluate the target’s authority, and it’s one of the main metrics used for competitive benchmarking. If the target is the whole domain, the counter of referring pages will be equally useful. Furthermore, if a user sets a page as a target, the number of referring pages will also be a crucial indicator of the page’s ranking potential.
As you’ve probably noticed, besides the Total backlinks and Referring pages counters, there are green and red highlights. These will help users to immediately see the number of new/lost backlinks and new/lost referring pages.
The counters of Referring IPs and Referring subnets will shed light on the target’s link-building strategy. In particular, if the count of referring IPs or subnets is too low, the target may be taking advantage of PBNs.
Similarly, the dofollow/nofollow backlinks ratio can reveal the quality of the target’s backlinks. For example, too many dofollow links may suggest link spam and such resources may even be penalized by Google.
In order to obtain values for these counters, you’ll need to make only one request to the Summary endpoint of Backlinks API. When setting a task, keep in mind the necessary scope that should be applied for the target. As explained in the Domain input part, you can specify a domain with or without its subdomains, a certain page, or all pages with a certain prefix.
login="login" \
password="password" \
cred="$(printf ${login}:${password} | base64)" \
curl --location --request POST "https://api.dataforseo.com/v3/backlinks/summary/live" \
--header "Authorization: Basic ${cred}" \
--header "Content-Type: application/json" \
--data-raw "[
{
"target": "example.com",
"internal_list_limit": 10,
"include_subdomains": true,
"backlinks_status_type": "all"
}
]"
{
"version": "0.1.20210622",
"status_code": 20000,
"status_message": "Ok.",
"time": "0.3804 sec.",
"cost": 0,
"tasks_count": 1,
"tasks_error": 0,
"tasks": [
{
"id": "07061551-1535-0265-0000-6d1a7e43cd21",
"status_code": 20000,
"status_message": "Ok.",
"time": "0.3483 sec.",
"cost": 0,
"result_count": 1,
"path": [
"v3",
"backlinks",
"summary",
"live"
],
"data": {
"api": "backlinks",
"function": "summary",
"target": "explodingtopics.com",
"internal_list_limit": 10,
"include_subdomains": true,
"backlinks_status_type": "all"
},
"result": [
{
"target": "explodingtopics.com",
"first_seen": "2019-08-18 09:32:39 +00:00",
"lost_date": null,
"rank": 244,
"backlinks": 1837,
"crawled_pages": 2073,
"info": {...},
"internal_links_count": 22805,
"external_links_count": 4815,
"broken_backlinks": 66,
"broken_pages": 111,
"referring_domains": 868,
"referring_main_domains": 835,
"referring_ips": 747,
"referring_subnets": 631,
"referring_pages": 1696,
"referring_links_tld": {...},
"referring_links_types": {...},
"referring_links_attributes": {
"noopener": 615,
"nofollow": 390,
"noreferrer": 15
},
"referring_links_platform_types": {...},
"referring_links_semantic_locations":{...}
}
]
}
]
}
login="login" \
password="password" \
cred="$(printf ${login}:${password} | base64)" \
curl --location --request POST "https://api.dataforseo.com/v3/backlinks/backlinks/live" \
--header "Authorization: Basic ${cred}" \
--header "Content-Type: application/json" \
--data-raw "[
{
"target": "example.com",
"limit": 100,
"mode": "one_per_domain",
"filters": [
[
[
"tld_from",
"=",
"com"
],
"or",
[
"tld_from",
"=",
"net"
]
],
"and",
[
"semantic_location",
"=",
"article"
],
"and",
[
"item_type",
"=",
"anchor"
]
]
}
]"
{
"version": "0.1.20210622",
"status_code": 20000,
"status_message": "Ok.",
"time": "2.9560 sec.",
"cost": 0,
"tasks_count": 1,
"tasks_error": 0,
"tasks": [
{
"id": "07051735-1535-0269-0000-11ca15abad0c",
"status_code": 20000,
"status_message": "Ok.",
"time": "2.9159 sec.",
"cost": 0,
"result_count": 1,
"path": [...],
"data": {...},
"result": [
{
"target": "example.com",
"mode": "one_per_domain",
"total_count": 8891875,
"items_count": 100,
"items": [...]
}
]
}
]
}
login="login" \
password="password" \
cred="$(printf ${login}:${password} | base64)" \
curl --location --request POST "https://api.dataforseo.com/v3/backlinks/backlinks/live" \
--header "Authorization: Basic ${cred}" \
--header "Content-Type: application/json" \
--data-raw "[
{
"target": "example.com",
"mode": "one_per_domain",
"filters": ["dofollow", "=", true],
"limit": 100
}
]"
login="login" \
password="password" \
cred="$(printf ${login}:${password} | base64)" \
curl --location --request POST "https://api.dataforseo.com/v3/dataforseo_labs/google/bulk_traffic_estimation/live" \
--header "Authorization: Basic ${cred}" \
--header "Content-Type: application/json" \
--data-raw "[
{
"targets": [
"https://dataforseo.com/",
"https://www.forbes.com/",
"https://edition.cnn.com/"
],
"location_code": 2840,
"language_code": "en"
}
]"
Corresponding fields in the Backlinks endpoint response: page_from_title, url_from from the items object.
Corresponding fields in the Backlinks endpoint response: page_from_rank from the items object.
Corresponding field in the Backlinks endpoint response: domain_from_rank from the item object.
Corresponding field in the Backlinks endpoint response: rank from the items object.
Corresponding fields in the Backlinks endpoint response: url_to, url_to_status_code from the items object.
Corresponding fields in the Backlinks endpoint response: text_pre, anchor, text_post from the items object.
Corresponding fields in the Backlinks endpoint response: dofollow from the items object. If true, the backlink is dofollow.
Corresponding fields in the Bulk Traffic Estimation endpoint response: etv from the items.metrics.organic.
Corresponding fields in the Backlinks endpoint response: first_seen from the items object.
Corresponding fields in the Backlinks endpoint response: last_seen from the items object.
The table also provides users with an opportunity to select specific columns that will be shown in the table. Besides the ones displayed by default, users can choose to view columns with the following data:
Corresponding field in the Backlinks endpoint response: item_type from the items object.
Corresponding field in the Backlinks endpoint response: flags from the items object.
Corresponding field in the Backlinks endpoint response: alt from the items object.
Corresponding field in the Backlinks endpoint response: prev_seen from the items object.
Corresponding field in the Backlinks endpoint response: semantic_location from the items object.
Corresponding field in the Backlinks endpoint response: page_from_external_links from the items object.
Corresponding field in the Backlinks endpoint response: page_from_internal_links from the items object.
Corresponding field in the Backlinks endpoint response: url_to_status_code from the items object.
Corresponding field in the Backlinks endpoint response: links_count from the items object.
Corresponding field in the Backlinks endpoint response: group_count from the items object.
Corresponding field in the Backlinks endpoint response: domain_from_ip from the items object.
The New Backlinks dashboard not only allows to oversee the website’s backlink growth dynamics but also makes it easy to focus on newly found backlinks. The Backlink API’s system of filters offers a convenient way to obtain only new backlinks. All you have to do is specify is_new = true in the array of filters.
The dashboard consists of four functional components, each of which provides a piece of information tailored to a certain use case. Combined together, these components offer a full overview of all new backlinks that a target website recently acquired.
Below, we’ll explain the components from this screen and will walk you through fine-tuning each component.
This graph puts the performance of the website’s backlink profile into a clear time frame. Using this feature a user can see the progress of backlink growth over the selected period of time and make their own conclusions on whether the link-building campaign of a target website is going in the right direction.
Knowing the number of new backlinks and referring domains a user can estimate the progress a website’s backlink profile is making and benchmark the growth velocity against the expectations.
You can obtain the number of new backlinks and referring domains by using the Backlinks History endpoint.
The new dofollow/nofollow backlinks ratio can tell whether the last link-building campaign was successful. Quality resources usually have between 50/50 and 30/70 dofollow/nofollow links, while websites without any nofollow backlinks appear rather suspicious (depending on the niche, of course).
The Lost Backlinks dashboard may be visually and functionally similar to the New Backlinks, but it serves a somewhat different purpose – fast-tracking the broken link-building campaigns and troubleshooting the link equity loss.
Backlinks API has a built-in capability to filter out lost backlinks – all you have to do is specify [“is_lost”, “=”, “true”] as a filter in the requests.
The Lost Backlinks dashboard is made up of several components that provide crucial information about the target website’s lost backlinks.
By looking at the Lost Backlinks Dynamics Graph a user will be able to tell whether the loss of backlink is an accumulative or a spike-like process and decide on the course of actions that need to be taken to mitigate it.
Just like in New Backlinks, this graph can be built on top of the Backlinks History endpoint’s data. By setting a certain time frame using the date_from and date_to fields you can set both custom and pre-defined time filters.
These counters help obtain the concrete numbers of lost backlinks and referring domains over a certain period of time.
You can obtain the number of lost backlinks and referring domains by using the Backlinks History endpoint.
The lost dofollow/nofollow backlinks ratio will help users estimate the magnitude of the link equity loss in a particular time range.
You can incorporate this bar into your application by using the Backlinks Summary endpoint and specifying the "is_lost" in the "backlinks_filters" array. The response of the API server will provide you with the number of nofollow links, and you'll get the number of dofollow ones by subtracting this value from the ovrall "backlinks" count.
The Broken Backlinks report will take users through the most significant metrics that help to efficiently line up fixes or create a promising dead link-building strategy. The pie chart, counters, and DF/NF bar neatly illustrate the extent of the issue and the scope of worthy backlinks users can poach or reinstate.
At the same time, the table will allow users to delve into adjustable details on each broken link, including the reason a link collapsed, the dofollow/nofollow indicator, and the link equity it can pass.
DataForSEO Backlinks API can swiftly supply you with structured data for all features in this report. We’ll spell everything out below, so read on.
The pie chart illustrating all & broken backlinks ratio immediately provides a perspective on link equity going to waste. With this simple chart, users can see the exact number of backlinks the target has left to rot. If the users are viewing their own domain profile, they will surely want to dig deeper and reclaim valuable links. In the case of competitor research, users might want to use the competitor’s dead backlinks to offer live links on their website as a replacement. Luckily, with all the data from the Broken Backlinks screen, they will be able to do both.
In order to add this particular chart to the Broken Backlinks screen of your tool, you’ll just need two fields from the response of the Summary endpoint: "backlinks" and "broken_backlinks"
The counters indicating the numbers of Broken Backlinks & Broken Pages bring forth a very important distinction. While the number of broken backlinks may sometimes be intimidating, it does not always mean the exact same number of URLs on the target site that need to be fixed. In fact, just one broken page on a website can cause dozens of backlinks to collapse. Based on the data from these counters, users analyzing the site they own can figure out the gravity of the situation before jumping on to the details. At the same time, these counters will allow users who are checking on their competitors to grasp the scope of potential backlinks they can gain from the given number of pages.
In order to add this particular chart to the Broken Backlinks screen of your tool, you’ll just need two fields from the response of the Summary endpoint: "broken_backlinks" and "broken_pages"
login="login" \
password="password" \
cred="$(printf ${login}:${password} | base64)" \
curl --location --request POST "https://api.dataforseo.com/v3/backlinks/backlinks/live" \
--header "Authorization: Basic ${cred}" \
--header "Content-Type: application/json" \
--data-raw "[
{
"target": "example.com",
"limit": 100,
"filters": [
[
"dofollow",
"=",
true
],
"and",
[
"is_broken",
"=",
true
]
]
}
]"
login="login" \
password="password" \
cred="$(printf ${login}:${password} | base64)" \
curl --location --request POST "https://api.dataforseo.com/v3/backlinks/backlinks/live" \
--header "Authorization: Basic ${cred}" \
--header "Content-Type: application/json" \
--data-raw "[
{
"target": "example.com",
"limit": 100,
"filters": [
[
"dofollow",
"=",
false
],
"and",
[
"is_broken",
"=",
true
]
]
}
]"
login="login" \
password="password" \
cred="$(printf ${login}:${password} | base64)" \
curl --location --request POST "https://api.dataforseo.com/v3/backlinks/backlinks/live" \
--header "Authorization: Basic ${cred}" \
--header "Content-Type: application/json" \
--data-raw "[
{
"target": "example.com",
"limit": 100,
"mode": "as_is",
"filters": [
[
"is_broken",
"=",
true
],
"and",
[
[
"tld_from",
"=",
"com"
],
"or",
[
"tld_from",
"=",
"net"
]
],
"and",
[
"semantic_location",
"=",
"article"
],
"and",
[
"item_type",
"=",
"anchor"
]
]
}
]"
This dashboard provides the growth dynamics of referring domains and backlinks, while also estimating the ranking score of the target domain and URL. In a nutshell, the Backlink Profile Overview is intended to showcase the backlink profile of any target – i.e., domain, subdomain, or webpage.
In-depth reports will provide users with deep insights on a site’s backlinks, revealing its top pages, referring domains, anchors, link gap and referral traffic. Making their way through each of these reports, users will get detailed performance stats, discover hidden backlinks opportunities and evaluate the site’s link-building strategies from different perspectives.