In order to display broken pages only, you should call the Domain Pages endpoint using a filter as in the example below:

                login="login" \
                password="password" \
                cred="$(printf ${login}:${password} | base64)" \
                curl --location --request POST "https://api.dataforseo.com/v3/backlinks/domain_pages/live" \
                --header "Authorization: Basic ${cred}"  \
                --header "Content-Type: application/json" \
                --data-raw "[
                    {
                        "target": "example.com",
                        "backlinks_filters": ["dofollow", "=", true],
                        "filters": ["status_code", "in", [400,599]],
                        "order_by": ["page_summary.backlinks,desc","page_summary.rank,desc"],
                        "limit": 1000
                    }
                ]"
                

The table of Top Pages by backlinks is the front-center element of the Top Pages Report. Basically, this table reveals a domain’s most linked-to pages, along with a few important stats for each page, including its status code, Page Rank, number of incoming backlinks and referring domains, and the volume of organic traffic. This data will come in handy when analyzing a site’s top-performing content or looking to replicate competitor strategies based on their best-performing pages. Also, the Top Pages table can help users find the most linked-to broken pages on competitor sites and streamline dead link-building.

If you’d like to implement this table, below is a list of necessary endpoints and fields grouped by column:

By clicking on the drop-down button in the Backlinks column, users can open a nested table. This table is showing pages referring to the page from the URL column of the main table. By default, the drop-down table here allows users to check up to 5 top referring pages by rank. However, it’s also possible to expand the table to view more data.

To create this built-in functionality, you should call the Backlinks endpoint with the necessary URL as a target. The list below will help you draw parallels between the table columns and required response fields.

Similarly, users can open a different nested table by clicking on the drop-down button in the Referring domains column. This table is showing domains referring to the page from the URL column of the main table. By default, users can check up to 5 top referring domains by rank. However, it’s also possible to expand the table to view more data.

Note that to create this built-in functionality, you should call the Backlinks endpoint with mode set to one_per_domain and the necessary URL set as a target. The list below will help you draw parallels between the table columns and required response fields.

To create the graph of referring domains, you’ll need to call the Backlinks History endpoint. When setting a task, you should specify the necessary time period using the date_from and date_to fields. Once you receive a response, each backlinks_history item will be supplied with the number of referring_domains, new_referring_domains, and lost_referring_domains for a certain date.

Table Filters are a quick way to refine table data. With the first button, users can switch between all, new and lost referring domains. The second button will help users pull out data on both dofollow & nofollow links, only dofollow or only nofollow ones. Using the TLD from, users select TLDs for which to display data. Platform types selector will pick only domains on a certain type of platform (e.g., blog, cms). The link type button will help to extract data for backlinks of a certain type(s), namely, anchor, image, alternate, and redirect links. The total count below the filters will indicate the number of referring domains matching the set rules (corresponding field in the response: total_count).

Basically, each of the UI filters corresponds to a filter you’ll need to apply when making a request to the Referring Domains endpoint.

All. No filter.

New. "filters": ["first_seen", "<", "2021-11-19 00:00:00 +00:00"]. Use a date which is no further than two months ago.

Lost. "filters": ["lost_date", ">", "2015-01-01 00:00:00"]. This filter will extract domains for which lost_date is not null, meaning that such domains are lost as of the indicated date.

Dofollow & nofollow. No filter.

Dofollow. "backlink_filters": ["dofollow", "=", true]

Nofollow. "backlink_filters": ["dofollow", "=", false]

TLD from. Use referring_links_tld from the response of the Summary endpoint to show available options. To filter the data, specify the necessary TLDs as in the example: "filters": [["referring_links_tld.com", ">", 0], "or", ["referring_links_tld.org", ">", 0]].

Platform types. Use referring_links_platform_types from the response of the Summary endpoint to show available options. To filter the data, specify the necessary platform types as in the example: "filters": [["referring_links_platform_types.cms", ">", "0"], "or", ["referring_links_platform_types.blogs", ">", "0"]].

Link type. Use referring_links_types from the response of the Summary endpoint to show available options. To filter the data, specify the necessary link types as in the example: "filters": [["referring_links_types.anchor", ">", "0"], "or", ["referring_links_types.image", ">", "0"]].

The table of Referring Domains contains comprehensive data on domains pointing to the target. By default, referring domains are presented in descending order by rank, however, users can sort the table by other columns too. Applying different sorting, users can pinpoint top domains sending the most valuable links to the target, uncover sites driving it more traffic, and find the target’s oldest and most recent linking partners.

The table is based on data from the Referring Domains endpoint. Here’s an example of a cURL request you should make.

        login="login" \
        password="password" \
        cred="$(printf ${login}:${password} | base64)" \
        curl --location --request POST "https://api.dataforseo.com/v3/backlinks/referring_domains/live" \
        --header "Authorization: Basic ${cred}"  \
        --header "Content-Type: application/json" \
        --data-raw "[
            {
                "target": "backlinko.com",
                "limit": 100,
                "order_by": ["rank,desc"],
                "exclude_internal_backlinks": true,
            }
        ]"
        

Each table column (except for Organic Traffic) corresponds to the eponymous field from this endpoint’s response. Note that to display the number of Dofollow links from each domain, you should subtract the value in referring_links_attributes.nofollow from the value in backlinks for each returned domain.

In order to implement a bar showing all backlinks vs backlinks from this domain, you should use backlinks from the Summary endpoint response for a target and backlinks value returned in the Referring Domains endpoint.

If you’d like to display the Organic Traffic column, you’ll need to ccall the Bulk Traffic Estimation endpoint as described here, and use etv from the items.metrics.organic.

Alongside the bar of all backlinks vs backlinks from this referring domain, the table features a button clicking on which will open a nested table of referring pages. Basically, it lists backlinks to the target from the selected referring domain and shows several stats for each referring page. The table will display 5 referring pages by rank by default, however, it can also be expanded.

Note that to implement this table, you’ll need to make a request to the Backlinks endpoint applying a filter with the necessary domain as in the example.

                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": "as_is",
                        "filters": ["domain_from", "=","referring-domain.com"],
                        "limit": 1000
                    }
                ]"
                

The list below will help you draw parallels between the table columns and required response fields from the Backlinks endpoint.

• Domain Rank: domain_from_rank from the items object.
• Page Rank: page_from_rank from the items object.
• Link Rank: rank from the items object.
• Target URL: url_to from the items object.
• Backlinks Context: text_pre, anchor, text_post from the items object.
• DF/NF: dofollow from the items object. If true, the backlink is dofollow.
• Link type (e.g., anchor, image, link): item_type from the items object.
• Organic Traffic: etv from the items.metrics.organic in the Bulk Traffic Estimation endpoint response.
• First Seen: first_seen from the items object.
• Last Seen: last_seen from the items object.
• Links count: links_count from the items object.

This part of the Anchors report features a table of the top 10 anchors used to link to the target. They are sorted by the number of backlinks going to the target with each of these anchors. Once a user clicks on a specific anchor, the pie charts and tables on the right will show stats for that anchor. The first pie chart and table will indicate the distribution of TLDs and the count of domains that use the selected anchor when linking to the target. The second pie chart and table will highlight the semantic locations in HTML where links with the selected anchor are put.

To develop this functionality, use the Backlink Anchors endpoint.

        login="login" \
        password="password" \
        cred="$(printf ${login}:${password} | base64)" \
        curl --location --request POST "https://api.dataforseo.com/v3/backlinks/anchors/live" \
        --header "Authorization: Basic ${cred}"  \
        --header "Content-Type: application/json" \
        --data-raw "[
            {
                "target": "forbes.com",
                "limit": 10,
                "order_by": ["backlinks,desc"],
                "backlinks_filters": ["dofollow", "=", true]
            }
        ]"
        

The response will furnish you with all the necessary data. Anchor text will be provided in the anchor field, while the number of backlinks with this anchor will be returned in the backlinks field. Each backlinks_anchor element will also contain the referring_links_tld object with data for the TLDs and Domains table and pie chart. Similarly, data for the Locations table and pie chart can be found in the referring_links_semantic_locations object.

This table is the main component of the report with all the details for the target’s backlink anchors. For each anchor, users will see its rank (counted as rank across all anchors in the database), numbers of referring pages, referring domains, and backlinks pointing to the target with this anchor, as well as the date when the first backlink with this anchor was found.

If you’d like to implement this table, you should call the Backlinks Anchors endpoint. To allow filtering by certain anchor text, you should specify the filters array as in the example cURL request below.

                login="login" \
                password="password" \
                cred="$(printf ${login}:${password} | base64)" \
                curl --location --request POST "https://api.dataforseo.com/v3/backlinks/anchors/live" \
                --header "Authorization: Basic ${cred}"  \
                --header "Content-Type: application/json" \
                --data-raw "[
                    {
                        "target": "forbes.com",
                        "limit": 100,
                        "order_by": ["backlinks,desc"],
                        "filters": ["anchor","like","%news%"],
                        "backlinks_filters": ["dofollow", "=", true]
                    }
                ]"
                

Here is a list of necessary response fields for each column:

• Anchor text - anchor
• Anchor rank - rank
• Referring pages - referring_pages
• Referring domains - referring_domains
• Backlinks - backlinks
• First seen - first_seen

By clicking on the drop-down button in the Referring domains column, users can open a nested table. It shows domains referring to the target with the anchor indicated in the main table. Note that to create this built-in functionality, you should call the Backlinks endpoint with mode set to one_per_domain and the necessary anchor specified in the filters array.

                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": ["anchor", "=","best in class blog in the world"],
                        "limit": 1000
                    }
                ]"
                

The list below will help you draw parallels between the table columns and required response fields.

• Referring domain: domain_from from the items object.
• Domain Rank: domain_from_rank from the items object.
• Backlinks (total number of backlinks from this domain): group_count from the items object.
• Organic Traffic: etv from the items.metrics.organic in the Bulk Traffic Estimation endpoint response.
• First Seen: first_seen from the items object.

The table also features a button in the Backlinks column clicking on which will open a nested table of referring pages. Basically, it lists backlinks pointing to the target with the selected anchor and shows several stats for each referring page. The table will display 5 referring pages by rank by default, however, it can also be expanded.

Note that to implement this table, you’ll need to make a request to the Backlinks endpoint with mode set to as_is and necessary anchor specified in the filters array.

        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": "as_is",
                "filters": ["domain_from", "=","best in class blog in the world"],
                "limit": 1000
            }
        ]"
        

The list below will help you draw parallels between the table columns and required response fields from the Backlinks endpoint.

• Page Rank: page_from_rank from the items object.
• Domain Rank: domain_from_rank from the items object.
• Link Rank: rank from the items object.
• Target URL: url_to from the items object.
• Backlinks Context: text_pre, anchor, text_post from the items object.
• DF/NF: dofollow from the items object. If true, the backlink is dofollow.
• Organic Traffic: etv from the items.metrics.organic in the Bulk Traffic Estimation endpoint response.
• First Seen: first_seen from the items object.
• Last Seen: last_seen from the items object.

Getting back to the Link Gap Report, it can feature two types of data: on referring domains or pages that link to all specified targets. Users determine the type of data that will be shown by choosing a mode.

        login="login" \
        password="password" \
        cred="$(printf ${login}:${password} | base64)" \
        curl --location --request POST "https://api.dataforseo.com/v3/backlinks/domain_intersection/live" \
        --header "Authorization: Basic ${cred}"  \
        --header "Content-Type: application/json" \
        --data-raw [
            {
                "targets": {
                    "1": "http://planet.postgresql.org/",
                    "2": "http://gborg.postgresql.org/"
                },
                "include_subdomains": false,
                "limit": 5,
                "order_by": [
                    "1.backlinks,desc"
                ],
                "exclude_internal_backlinks": true
            }
        ]"
        

        login="login" \
        password="password" \
        cred="$(printf ${login}:${password} | base64)" \
        curl --location --request POST "https://api.dataforseo.com/v3/backlinks/page_intersection/live" \
        --header "Authorization: Basic ${cred}"  \
        --header "Content-Type: application/json" \
        --data-raw "[
            {
                "targets": {
                    "1": "adidas.com",
                    "2": "nike.com"
                },
                "limit": 5,
                "order_by": [
                    "1.rank,desc"
                ],
                "filters": [
                    [
                        "2.domain_from_rank",
                        ">",
                        400
                    ],
                    "and",
                    [
                        "1.dofollow",
                        "=",
                        true
                    ]
                ]
            }
        ]"
        

Note that users can still set domains or pages in either of the modes. Also, in both intersection modes, users can additionally specify domains or pages that receive no links from the resources linking to the targets. To implement this with DataForSEO API, you will need to use the exclude_targets array. Simply append this parameter to the body of your POST request, and the response will contain resources that link to targets but don’t link to exclude_targets.

        login="login" \
        password="password" \
        cred="$(printf ${login}:${password} | base64)" \
        curl --location --request POST "https://api.dataforseo.com/v3/backlinks/domain_intersection/live" \
        --header "Authorization: Basic ${cred}"  \
        --header "Content-Type: application/json" \
        --data-raw [
            {
                "targets": {
                    "1": "adidas.com",
                    "2": "nike.com"
                },
                "exclude_targets": [
                    "puma.com"
                ],
                "include_subdomains": false,
                "limit": 5,
                "order_by": [
                    "1.backlinks,desc"
                ],
                "exclude_internal_backlinks": true
            }
        ]"
        

Applying these filters, users can choose to obtain data only on specific top-level domains (TLDs) and dofollow or nofollow links. In DataForSEO API, this functionality corresponds to the parameters you’ll need to specify in the filters and/or backlinks_filters array(s) in the body of your POST request.

        {
            "filters": [
                [
                    "1.referring_links_tld.com",
                    ">",
                    0
                ],
                "and",
                [
                    "2.referring_links_tld.com",
                    ">",
                    0
                ]
            ],
            "backlinks_filters": [
                [
                    "dofollow",
                    "=",
                    true
                ]
            ]
        }
        

        {
            "filters": [
                [
                    "1.tld_from",
                    "=",
                    "com"
                ],
                    "and",
                [
                    "2.tld_from",
                    "=",
                    "com"
                ],
                "and",
                [
                    "1.dofollow",
                    "=",
                    true
                ],
                "and",
                [
                    "2.dofollow",
                    "=",
                    true
                ]
            ]
        }
        

When a user selects mode: intersect referring domains, the table of the Link Gap report will contain data on domains linking to all specified targets. So, once a user enters competitor sites as targets, the table will show websites linking to the user’s competitors. If a user additionally specifies their site as a target that should be excluded from cross-analysis, the table will show websites that link to all competitors but do not link to the user’s site.

As we explained in Intersecting Targets Input and Table Filters, you’ll need to configure your requests to the Domain Intersection endpoint according to the user preferences (of targets and filters). The response from this endpoint will supply you with all the data necessary for the table.

• Domain: 1.target and 2.target from the items object.
• Rank to {{target.1}}: 1.rank from the items object.
• Rank to {{target.2}}: 2.rank from the items object.
• {{target.1}} backlinks: 1.backlinks from the items object.
• {{target.2}} backlinks: 2.backlinks from the items object.
• Organic Traffic: etv from the items.metrics.organic in the Bulk Traffic Estimation endpoint response.
• First seen {{target.1}}: 1.first_seen from the items object.
• First seen {{target.2}}: 2.first_seen from the items object.

Clicking a button in the corresponding Backlinks column (for target1 or target2), users will open a nested table of referring pages. Basically, it will show users a list of all backlinks coming to the relevant targets from the domain indicated in the main table. The drop-down table will display 5 referring pages by rank by default, however, it can also be expanded.

Note that to implement this table, you’ll need to make a request to the Page Intersection endpoint indicating the same targets and exlude_targets as in the call to the Domain Intersection endpoint for the main table. You should also specify the related domain_from in the filters array.

        login="login" \
        password="password" \
        cred="$(printf ${login}:${password} | base64)" \
        curl --location --request POST "https://api.dataforseo.com/v3/backlinks/page_intersection/live" \
        --header "Authorization: Basic ${cred}"  \
        --header "Content-Type: application/json" \
        --data-raw "[
            {
                "targets": {
                    "1": "adidas.com",
                    "2": "nike.com"
                },
                "exclude_targets": [
                    "puma.com"
                ],
                "limit": 5,
                "order_by": [
                    "1.backlinks,desc"
                ],
                "filters": [
                    [
                        "1.domain_from",
                        "=",
                        "usatoday.com"
                    ],
                    "and",
                    [
                        "1.dofollow",
                        "=",
                        true
                    ]
                ]
            }
        ]"
        

The list below will help you draw parallels between the table columns and required response fields from the Page Intersection endpoint. Note that you should use data from the array with the number of the corresponding target (from 1 to 20). In the example below, we’re using data for target1.

• Referring page: 1.url_from from the items object.
• Domain Rank: 1.domain_from_rank from the items object.
• Page Rank: 1.page_from_rank from the items object.
• Link Rank: 1.rank from the items object.
• Target URL: 1.url_to from the items object.
• Backlinks Context: 1.text_pre, 1.anchor, text_post from the items object.
• DF/NF: 1.dofollow from the items object. If true, the backlink is dofollow.
• Link type (e.g., anchor, image, link): 1.item_type from the items object.
• Organic Traffic: etv from the items.metrics.organic in the Bulk Traffic Estimation endpoint response.
• First Seen: 1.first_seen from the items object.
• Last Seen: 1.last_seen from the items object.

When a user selects mode: intersect referring pages, the table of the Link Gap report will contain data on unique URLs linking to all specified targets. So, once a user enters competitor sites as targets, the table will show pages linking to the user’s competitors. Users can additionally specify their site as a target that should be excluded from cross-analysis. In that case, the table will show pages that link to all competitors but do not link to the user’s site.

As we explained in Intersecting Targets Input and Table Filters, you’ll need to configure your requests to the Page Intersection endpoint according to the user preferences (of targets and filters). The response from this endpoint will supply you with all the data necessary for the table.

• Domain: 1.target and 2.target from the items object.
• Rank to {{target.1}}: 1.rank from the items object.
• Rank to {{target.2}}: 2.rank from the items object.
• {{target.1}} backlinks: 1.backlinks from the items object.
• {{target.2}} backlinks: 2.backlinks from the items object.
• Organic Traffic: etv from the items.metrics.organic in the Bulk Traffic Estimation endpoint response.
• First seen {{target.1}}: 1.first_seen from the items object.
• First seen {{target.2}}: 2.first_seen from the items object.

Clicking a button in the corresponding Backlinks column (for target1 or target2), users will open a nested table of referring pages. Basically, it will show users a list of all backlinks coming to the relevant targets from the referring page indicated in the main table. The drop-down table will display 5 backlinks by rank by default, however, it can also be expanded.

Note that to implement this table, you’ll need to use data from the same call to the Page Intersection endpoint that you made for the Table of Intersecting Pages.

The list below will help you draw parallels between the table columns and required response fields from the Page Intersection endpoint. Note that you should use data from the array with the number of the corresponding target (from 1 to 20). In the example below, we’re using data for target1.

• Referring page: 1.url_from from the items object.
• Domain Rank: 1.domain_from_rank from the items object.
• Page Rank: 1.page_from_rank from the items object.
• Link Rank: 1.rank from the items object.
• Target URL: 1.url_to from the items object.
• Backlinks Context: 1.text_pre, 1.anchor, 1.text_post from the items object.
• DF/NF: 1.dofollow from the items object. If true, the backlink is dofollow.
• Link type (e.g., anchor, image, link): 1.item_type from the items object.
• Organic Traffic: etv from the items.metrics.organic in the Bulk Traffic Estimation endpoint response .
• First Seen: 1.first_seen from the items object.
• Last Seen: 1.last_seen from the items object.

You can read more about integrating Google Analytics data into third-party applications in Google’s official documentation.

Having established a firm understanding of how much traffic referral sources generate, it’s important to give users more detailed information on these sources. Are these sources reputable? How many visitors did they manage to attract? How many of these visitors bounced back to where they came from? Answering these questions would help your users dwell deeper into the backlink profile and estimate the value of each referral source.

To make this happen, you’d need to use a combination of DataForSEO Backlinks API and Google Analytics API. The former will provide you with the referral source’s rank and backlink data, while the latter is essential for obtaining all other metrics, namely: percentage of visits, new visits, pages per visit, and bounce rate.

The key to implementing this must-have feature is a synchronization of data obtained from both sources and cross-matching the corresponding parameters.

Google Analytics API

• Referral Source - indicates the domain of a referral website.
• Visits - is the number of visits a referring website generated.
• Visits % - the share of the traffic generated from the referral source in the total amount of referral traffic; can be calculated from the total amount of organic traffic and the number of visits from the given referral source.
• New Visits - is the number of visitors that visited the website for the first time from the referring source.
• Pageviews per visit - the average number of pages visitors coming from a referral website visited on the target website.
• Bounce Rate - indicates the number of visitors who returned back to the referral source without interacting with the target website.

DataForSEO Backlinks API

• Rank - domain rank of the referring website; you can learn more about it on our help center.
• Backlinks - the number of backlinks from the referral source.

You can obtain data for both these columns from the Referring Domains endpoint. Note that you should apply the filter by the referring domain in the POST request.

        login="login" \
        password="password" \
        cred="$(printf ${login}:${password} | base64)" \
        curl --location --request POST "https://api.dataforseo.com/v3/backlinks/referring_domains/live" \
        --header "Authorization: Basic ${cred}"  \
        --header "Content-Type: application/json" \
        --data-raw "[
            {
                "target": "inc.com",
                "limit": 5,
                "order_by": ["rank,desc"],
                "exclude_internal_backlinks": true,
                "backlinks_filters": ["dofollow", "=", true],
                "filters": [["domain", "=", “hackeundspitze.de”], “or”, [“domain”, “=”,“paypal.com”], “or” [“domain”, “=”,“startpage.com”]]
            }
        ]"
        

In the API response look for the “rank” and “backlinks” fields in the items array.

The table also features a button in the Backlinks column clicking on which will open a nested table of referring pages. Basically, it lists backlinks pointing to the target from the selected referral source and shows several stats for each referring page. The table will display 5 referring pages by rank by default, however, it can also be expanded.

Note that to implement this table, you’ll need to make a request to the Backlinks endpoint with mode set to as_is and a necessary domain specified in the filters array.

        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": "as_is",
              "filters": ["domain_from", "=","hackeundspitze.de"],
              "limit": 1000
            }
        ]"
        

The list below will help you draw parallels between the table columns and required response fields from the Backlinks endpoint.

• Domain Rank: domain_from_rank from the items object.
• Page Rank: page_from_rank from the items object.
• Link Rank: rank from the items object.
• Target URL: url_to from the items object.
• Backlinks Context: text_pre, anchor, text_post from the items object.
• DF/NF: dofollow from the items object. If true, the backlink is dofollow.
• Link type (e.g., anchor, image, link): item_type from the items object.
• Organic Traffic: etv from the items.metrics.organic in the Bulk Traffic Estimation endpoint response .
• First Seen: first_seen from the items object.
• Last Seen: last_seen from the items object.
• Links count: links_count from the items object.