SEO Authority & Backlink Analyzer — Moz Alternative

Analyze domain authority signals and backlink profiles. Export provider domain ranks, spam signals, referring domains, anchors, and top pages for link research. Metrics are provider-specific, not official Moz scores. For link researchers, dataset rows represent the selected authority summary, referring domain, anchor, backlink, or page report.

Workflow: put the results to work

Start with a domain overview and review its provider rank alongside backlinks and referring domains. Inspect anchors or top pages when you need to understand the link profile. Keep the metric definitions visible: a provider rank is not automatically equivalent to Moz Domain Authority.

Moz Alternative — Domain Authority, Spam Score & Backlinks

Moz Alternative is an Apify Actor for SEO teams, analysts, and agents that need Moz-style domain authority, spam score, linking domains, backlinks, anchors, and top pages from a domain or page URL. It accepts one target for single-report modes, or a domain list for bulk authority. One dataset row represents one domain, backlink, referring domain, anchor, or page, and the useful fields include domainRank, pageRank, spamScore, backlinks, referringDomains, sourceUrl, targetUrl, anchor, and status. The outcome is a structured dataset you can review in Apify, read through the API, or use through Apify MCP.

Best fit and connected workflows

Use this Actor when you want to turn a hostname or URL into a link-profile view with comparable authority-style metrics.

• Check a single domain or page in domain_authority mode for an overview row with rank, spam score, backlinks, and referring domains.
• Run bulk_authority when you want the same authority-style fields for a short domain list.
• Switch to backlinks, referring_domains, anchors, or top_pages when you want to inspect the underlying link graph by row.
• Keep includeSubdomains on when subdomain data belongs in the report, and use excludeInternalBacklinks when you want summary and referring-domain views to focus on external subdomain links.
• For related search-workflow analysis, you can connect this output to other Apify Actors in your own workflow after you identify the domains or pages you want to inspect further.

How this workflow compares with Moz

Decision	This Actor	Moz	Suitable fit
Scope	A bounded domain-authority and link-profile workflow with six documented report modes	A broader SEO product experience with its own interface and product workflows	Use this Actor for focused, programmable reports; use Moz when the broader product experience is central to the work
Starting point	One domain or page, or a short domain list for bulk authority	Inputs and projects managed inside the Moz product	Use this Actor when the starting information already exists in an automated workflow
Output	Structured Apify dataset rows plus OUTPUT and RUN_SUMMARY	Output presented through Moz's own product surfaces	Use this Actor when dataset export, API readback, or Actor chaining is required
Billing	Pay per event plus Apify platform usage, with current terms on the live Pricing tab	Moz's own current commercial terms	Compare the current plans against the exact report volume and operating workflow
Integrations	Apify API, dataset exports, schedules, webhooks, and Apify MCP	Moz's broader native product workflows	Choose according to the downstream system that needs the result

This Actor is a focused automation route for the documented reports rather than a representation of Moz's complete product suite.

Input fields

Field	Type	Purpose
mode	string enum	Selects the report type: domain_authority, bulk_authority, backlinks, referring_domains, anchors, or top_pages. Default: domain_authority.
target	string	Domain or URL to analyze for single-target modes. Accepts a bare domain or a full URL.
targets	array of strings	Domain list for bulk_authority. Example: ["moz.com", "ahrefs.com"].
maxResults	integer	Maximum dataset rows to write, from 1 to 100. Default: 5.
includeSubdomains	boolean	Includes subdomain data in authority and link reports. Default: true.
excludeInternalBacklinks	boolean	Removes internal subdomain links from summary and referring-domain reports. Default: true.

Focused JSON example

{
  "mode": "backlinks",
  "target": "moz.com",
  "maxResults": 5,
  "includeSubdomains": true,
  "excludeInternalBacklinks": true
}

Output fields

One dataset item represents a single report row. Fields vary by mode, and the schema preserves both row-level link data and summary metrics.

Field	Type	Meaning
mode	string	Report type that produced the row.
target	string or null	Normalized domain or page analyzed.
domain	string or null	Domain associated with the row.
pageUrl	string or null	Page URL for page-level rows.
domainRank	integer or null	Moz-style 0-100 authority score from the upstream index.
pageRank	integer or null	Page-level rank from the upstream index.
spamScore	number or null	Spam score for the target or source.
backlinks	integer or null	Backlink count for the row.
referringDomains	integer or null	Referring domain count for the row.
sourceUrl	string or null	Source URL for backlink rows.
targetUrl	string or null	Destination URL for backlink rows.
anchor	string or null	Anchor text for backlink or anchor rows.
dofollow	boolean or null	Link attribute for backlink rows.
firstSeen	string or null	First observed timestamp.
lostDate	string or null	Lost date when available.
source	string	Source label for the row.
fetchedAt	string	Timestamp for the fetch.
status	string	Row status.
providerTaskId	string or null	Upstream task identifier when available.

Illustrative JSON record

{
  "mode": "domain_authority",
  "target": "moz.com",
  "domain": "moz.com",
  "domainRank": 72,
  "spamScore": 4,
  "backlinks": 41000,
  "referringDomains": 8900,
  "source": "moz_alternative/domain_authority",
  "fetchedAt": "2026-08-22T00:00:00.000Z",
  "status": "OK"
}

How it works

This Actor uses owner-managed API credentials already configured in the Actor environment. It reads the selected mode and target fields, normalizes the domain or URL, and writes dataset rows for the requested report type. The dataset schema includes overview, backlinks, and top-pages views, while the key-value store publishes compact OUTPUT and detailed RUN_SUMMARY records. The Actor is usable through Apify MCP as well as through the Apify API and standard dataset exports.

Use with AI agents (MCP)

This Actor can be used through Apify MCP as an Apify Actor tool. The exact Actor identity is khadinakbar/moz-alternative.

Use it when an agent needs a structured link-profile report from a domain or page URL and should read back the dataset rows plus the key-value-store summary records.

Use khadinakbar/moz-alternative for moz.com in domain_authority mode. Return the row fields domainRank, spamScore, backlinks, referringDomains, source, fetchedAt, and status. Then read the OUTPUT and RUN_SUMMARY records and summarize the report type and item count.

Interpretation notes for agents:

• domainRank is a Moz-style authority score from the upstream index, and the dataset schema labels it as a 0-100 field.
• sourceUrl, targetUrl, and anchor are most useful in backlinks mode.
• pageUrl is most useful in top_pages mode.
• OUTPUT is the compact run summary, while RUN_SUMMARY adds detailed provider cost and request counts.
• maxResults controls the number of dataset rows written, up to the schema maximum.
• Cost planning should account for one request event per upstream SEO API task and one record event per saved row.

Use with the Apify API

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({
  token: process.env.APIFY_TOKEN,
});

const run = await client.actor('khadinakbar/moz-alternative').call({
  mode: 'domain_authority',
  target: 'moz.com',
  maxResults: 5,
  includeSubdomains: true,
  excludeInternalBacklinks: true,
});

const dataset = await client.dataset(run.defaultDatasetId).listItems();
console.log(dataset.items);

Best results and outcome guidance

• Use a real domain or page URL such as moz.com or https://www.moz.com.
• Choose domain_authority for a single overview row, then move to backlinks, referring_domains, anchors, or top_pages when you need row-level detail.
• Use bulk_authority with a short targets list when you need comparable authority-style rows for several domains.
• Keep maxResults small when you are validating the output shape, then raise it for larger exports.
• Treat domainRank and pageRank as upstream index scores, and use spamScore, backlinks, and referringDomains together for a fuller read of the link profile.

Design note

I found that the output contract separates overview fields from row-level backlink and top-page fields, which makes the same Actor useful for both a one-row audit and a multi-row export.

FAQ

Which input mode should I use for a single domain overview?

Use domain_authority. It returns one domain or page row with authority-style metrics, spam score, backlinks, and referring domains.

Which mode is suited to a domain list?

Use bulk_authority. It accepts a targets array and writes one row per domain in the bulk list.

Which mode returns source and destination URLs?

Use backlinks. That view is designed for sourceUrl, targetUrl, anchor, dofollow, and related backlink fields.

Which mode is most useful for page-level research?

Use top_pages. It focuses on pageUrl, pageRank, backlinks, referringDomains, and spamScore.

Can I use this Actor from Apify MCP?

Yes. The Actor is available as khadinakbar/moz-alternative and can be called as an Apify Actor tool through MCP.

Responsible use

Use this Actor for authorized SEO research and analysis of public web data that you are permitted to process. Keep the output in your own review and compliance workflow. Moz is a trademark of its owner. This independent Actor is not affiliated with, associated with, or endorsed by Moz.

Pricing and run costs

This Actor uses Pay per event plus Apify platform usage. The Pricing tab lists the current event rates and billing terms.

Event	Billing unit	When it applies
apify-actor-start	Actor Start	Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event).
seo-api-request	SEO API request	Charged once for each successful upstream SEO API task used to build the report.
authority-record	Authority record	Charged once for each validated domain-authority, backlink, referring-domain, anchor, or top-page row persisted to the dataset.

Run cost combines the charged events and Apify platform usage. Review the run charge limit and requested result count before starting.

Connect an AI agent

Use the Apify MCP configurator to choose an available client connection. Inspect this Actor’s current input schema and required credentials before running it.