Skip to main content
Use Domain Pages Summary when you want the pages on a domain or subdomain, each with its own backlink summary: rank, backlink count, referring domains, and spam score. A typical use is finding a site’s most-linked pages, then looping over those pages in a later step.

Configuration

Add this step from the Research group in Search steps…. A value with no scheme, such as example.com, is sent as a domain. www. is removed. A URL with a real path, such as https://example.com/blog/post, is sent as a page. https://example.com/ is treated as the domain example.com. A path without https://, such as example.com/blog, is rejected.

Output

Click Run in the step header to test the step. Fetch Hive shows the page list in Output after the run completes. Use the variable picker in a later step to insert the exact output path available for that run. The list of pages is:
Each item includes url, rank, backlinks, referring_domains, referring_pages, backlinks_spam_score, first_seen, and lost_date, plus breakdowns such as referring_links_tld and referring_links_countries. The object also includes target, total_count, and items_count. Inside an iteration over {{step_2.output.items}}, the page URL is:
There is no results or pages list, and the URL is not link or page_url. Use Backlinks Summary when you need one profile for the whole site instead of a page list.

Example

Add Domain Pages Summary from the Research group in Search steps…. Set Name to something like Most linked pages. Enter example.com in Target, or insert a variable that resolves to a domain. Leave Sort on backlinks, highest first, then click Run and review Output before looping over items in a later step.

Cost

Hosted runs convert the recorded service cost plus a 6% service fee into task credits. The charge is per request. It does not grow with the number of pages returned. See Task costs.

Notes

  • If the provider rejects the target or a filter, the step fails and the error message is the provider’s message. When the step fails then decides whether the workflow stops or continues.
  • Personal model keys are not used. This step always runs as a hosted provider call.