MOZ Scraper With Backlink Profile Analysis

MOZ Backlink Scraper — Extract Link Profiles, DA History & Keywords

MOZ Backlink Profile Analyzer scrapes Moz's free Domain Analysis tool and turns it into structured JSON: Domain Authority, a real link profile built from Moz's own Top Linking Domains table, a monthly DA history, and ranking/branded keyword data — for any domain you submit. Every response is typed JSON, with real Moz-sourced fields clearly separated from computed estimates — no HTML, no dashboard exports, no manual copy-pasting from Moz's UI. Read on for the exact input parameters, every output field the Actor writes, and where the numbers actually come from.

What is MOZ Backlink Profile Analyzer?

MOZ Backlink Profile Analyzer is an Apify Actor that fetches Moz's free public Domain Analysis page for one or more domains and parses it into a consistent JSON schema covering Domain Authority, Page Authority, Spam Score, the real linking-root-domain count, a computed link-profile analysis, a monthly Domain Authority history, and keyword/competitor data. It targets Moz's free, no-login Domain Analysis tool at moz.com/domain-analysis — no Moz account, Moz Pro subscription, or Moz API key is required to run it. It is callable as a plain HTTP API from any agent framework or backend that can call the Apify API.

• Scrape real link-profile data (linking root domains, ranked linkers, quality tier)
• Scrape Domain Authority overview data (DA, PA, Spam Score, Trust Score)
• Scrape monthly Domain Authority history
• Scrape keyword and competitor data (ranking keywords, branded keywords, top questions, top competitors)
• Export as JSON, CSV, XML, Excel, or HTML table directly from the Apify dataset — no proxy management, no parsing

🔍 What data does MOZ Backlink Profile Analyzer collect?

The Actor returns several distinct data types per domain, all in one record: a domain authority overview, a real link-profile analysis, a Domain Authority history timeline, and keyword/competitor intelligence.

Data Type	Key Fields	JSON Field Names
Domain Overview	Domain Authority, Page Authority, Spam Score, Trust Score, domain age	authority_score, page_authority_score, spam_score, trust_score, domain_age_years
Link Profile (real)	linking root domain count, ranked real linkers, quality tier	total_linking_root_domains, link_profile_analysis, topLinkerDomains, linkQualityTier
Authority History	monthly DA trend, month-over-month change	authority_score_history, authority_score_last_month, authority_score_month_over_month_change
Keyword & Competitor Data	ranking keywords, branded keywords, top questions, top competitors	top_ranking_keywords, top_branded_keywords, top_questions, top_competitors
Backlink Trend	discovered/lost backlinks over time	backlinks_discovered_lost_history
Estimated Backlink Volume	formulaic totals derived from DA, clearly flagged	estimated_total_backlinks, estimated_quality_backlinks, is_estimated

Need more Moz SEO data?

If you also need on-page audits or rank-tracking beyond Moz, pair this Actor with a dedicated SERP or on-page scraper from the API Empire catalog rather than expecting this one to cover it — MOZ Backlink Profile Analyzer is purpose-built for backlink and authority data, and stays accurate by not overreaching into unrelated SEO surfaces.

How does MOZ Backlink Profile Analyzer differ from the official Moz API?

Moz's own Links API is a separate, paid product with its own subscription and API credentials; this Actor scrapes Moz's free public Domain Analysis tool and requires neither.

Feature	Official Moz Links API	MOZ Backlink Profile Analyzer
Account requirement	Moz Pro / Moz API subscription	None — no Moz account needed
Authentication	Access ID + Secret Key issued by Moz	None — no Moz credentials of any kind
Access model	Metered API calls under your subscription tier	Apify pay-per-event, billed per domain record
Setup	Register for API access, generate keys, integrate the auth scheme	Provide domains, click Start
Backlink totals	Published as part of Moz's paid index	Not published by Moz's free tool — this Actor computes and clearly flags them as estimated_*
Output format	JSON via REST calls	JSON via the Apify dataset, same schema every run
Link-profile analysis (avg linker DA, quality tier)	Not a built-in Moz API feature — you'd compute it yourself from raw rows	Computed automatically from Moz's real Top Linking Domains table

If you already hold a Moz Pro / Moz API subscription and want Moz's own certified index at scale, the official API is the right choice. If you want quick, credential-free backlink and authority snapshots for a list of domains without setting up Moz API auth, MOZ Backlink Profile Analyzer is faster to start with.

Why do developers and teams scrape Moz backlink data?

For AI engineers and agent builders

An SEO research agent can call this Actor as a tool, pass a prospect or competitor domain, and get back authority_score, linkQualityTier, and top_competitors as typed JSON — ready to feed directly into an LLM prompt or a RAG index without writing an HTML parser. Because every run returns the same field names and types, an agent's tool-calling schema stays stable across runs, which matters more for reliability than any single field's accuracy.

For marketers and brand teams

Marketing teams use top_ranking_keywords, top_branded_keywords, and top_questions to see what a domain currently ranks for and which questions searchers associate with it, then cross-reference top_competitors to find who else is competing for that visibility — useful before a content push or a competitive audit of a client's or your own domain.

For researchers and analysts

Academic and market researchers pull authority_score_history across a sample of domains to study how Domain Authority moves over time, using only publicly accessible Moz metrics rather than any private or gated dataset. Because the Actor documents exactly which fields are real Moz output versus computed estimates, researchers can decide for themselves which fields belong in a published analysis.

For developers building data products

Agencies and SaaS builders schedule this Actor to re-run on a client's domain list on a cadence of their choosing, storing link_profile_analysis and authority_score snapshots to power a backlink-monitoring dashboard or a lead-scoring pipeline that ranks prospects by domain authority before outreach.

How to scrape Moz backlink data (step by step)

1. Open MOZ Backlink Profile Analyzer on its Apify Store listing and click Try for free (or Run Actor if you already have it saved).
2. Provide the required input — urls, a list of one or more domains or URLs, e.g. zapier.com.
3. Toggle include_authority and include_history to choose which data sets to collect, and set minLinkerAuthority if you only want the link-profile analysis to consider high-authority linkers.
4. Click Start and watch the run log stream domain-by-domain progress.
5. Open the Output tab, switch between the dataset views (Overview, Link Profile, Top Linking Domains, and more), and download results as JSON, CSV, Excel, or HTML.

What to do when Moz changes its page structure

The Actor is maintained against Moz's live page layout, and the output schema is designed to stay stable across maintenance updates — field names and types on your end don't change even if the underlying page markup does. No specific turnaround time is promised for fixes.

⬇️ Input

Every field below is read directly from the Actor's input schema (.actor/actor.json). urls is the only required field.

Parameter	Required	Type	Default	Description
urls	Yes	array of strings	—	One or more domains or URLs to analyze on Moz, e.g. zapier.com or https://moz.com. Add them one by one or paste a bulk list with the input editor's Bulk edit mode.
include_authority	No	boolean	true	If enabled, collects the full domain overview: Domain Authority, Page Authority, Spam Score, the real linking-root-domain count, the link-profile analysis, top pages, linking domains, ranking and branded keywords, top questions, and competitors.
include_history	No	boolean	true	If enabled, builds a monthly Domain Authority history timeline for each domain, verified against archived snapshots where available.
minLinkerAuthority	No	integer	0	Minimum: 0. Maximum: 100. Only real linking domains from Moz's Top Linking Domains table with a Domain Authority at or above this value are included in the link-profile analysis (average authority, high-authority count, quality tier, ranked linkers). 0 analyzes all linkers.
proxyConfiguration	No	object	{"useApifyProxy": true}	Apify Proxy configuration. The Actor starts with no proxy at all, then automatically falls back to a Datacenter proxy, and finally to a sticky Residential proxy only if Moz blocks the request — so this rarely needs to be changed.

Example input:

{
  "urls": ["zapier.com", "moz.com"],
  "include_authority": true,
  "include_history": true,
  "minLinkerAuthority": 30,
  "proxyConfiguration": { "useApifyProxy": true }
}

Common pitfall: setting minLinkerAuthority high (e.g. 70) on a low-authority domain can legitimately zero out linkingDomainsAnalyzed in the link-profile analysis — that isn't a scraping failure, it means none of that domain's real linkers cleared your threshold.

The input schema also accepts a bulk list where each entry is either a plain string ("zapier.com") or an object with a url or domain key ({"url": "zapier.com"}) — both forms are normalized to the same domain internally.

Internally, the Actor also processes domains with bounded concurrency (default 3 domains in parallel, clamped between 1 and 10) so a large domain list doesn't hit Moz all at once. This concurrency limit is not currently exposed as a configurable field in the input schema shown above — it always falls back to its default of 3 through the standard Actor input UI.

⬆️ Output

Results are pushed to the Apify dataset one record per domain, as typed JSON — export to JSON, CSV, Excel, XML, or HTML table from the Output tab. The dataset's default table in the Apify Console only shows 9 of the fields below (domain, authority_score, total_linking_root_domains, linkingDomainsAnalyzed, avgLinkingDomainAuthority, highAuthorityLinkerCount, linkQualityTier, spam_score, last_updated) — the console additionally provides eleven more table views (Overview, Top Linking Domains, Ranked Linkers, Authority History, Backlinks Discovered/Lost, Keyword Ranking Distribution, Top Pages, Top Ranking Keywords, Branded Keywords, Top Questions, Top Competitors) that each project a different slice of the same underlying record. The raw record behind every view carries every field documented below.

Scraped domain record

With both include_authority and include_history at their defaults (true), a successful record ("type": "domain_authority") looks like this:

{
  "data_captured_at": "2026-07-25T09:14:02.118301",
  "type": "domain_authority",
  "last_updated": "2026-07-25T09:14:02.118301",
  "domain": "zapier.com",
  "domain_age_years": 14.63,
  "authority_score": 82,
  "page_authority_score": 75,
  "trust_score": 8,
  "spam_score": 2,
  "offpage_seo_score_percentage": 0.71,
  "authority_score_last_month": 81,
  "authority_score_month_over_month_change": 1,
  "authority_score_history": [
    { "date": "2023-11-01T00:00:00", "domain_authority": 79 },
    { "date": "2026-06-01T00:00:00", "domain_authority": 81 },
    { "date": "2026-07-01T00:00:00", "domain_authority": 82 }
  ],
  "total_linking_root_domains": 112600,
  "is_estimated": true,
  "estimation_note": "estimated_* backlink counts (total/quality/do_follow/no_follow) are deterministic estimates derived from Domain Authority and the real linking-root-domain count — MOZ's free tool does not publish absolute backlink numbers. The REAL, MOZ-sourced link-profile fields are total_linking_root_domains and the top_linking_domains table (and the link_profile_analysis computed from it).",
  "estimated_total_backlinks": 2004280,
  "estimated_quality_backlinks": 336000,
  "estimated_quality_backlinks_percentage": 0.17,
  "estimated_do_follow_backlinks_percentage": 0.83,
  "estimated_no_follow_backlinks_percentage": 0.17,
  "link_profile_analysis": {
    "minLinkerAuthorityApplied": 30,
    "linkingDomainsAnalyzed": 25,
    "avgLinkingDomainAuthority": 84.4,
    "highAuthorityLinkerCount": 24,
    "strongestLinkerAuthority": 99,
    "weakestLinkerAuthority": 41,
    "linkQualityTier": "Elite",
    "topLinkerDomains": [
      { "domain": "linkedin.com", "domain_authority": 99 },
      { "domain": "wikipedia.org", "domain_authority": 96 }
    ]
  },
  "linkingDomainsAnalyzed": 25,
  "avgLinkingDomainAuthority": 84.4,
  "highAuthorityLinkerCount": 24,
  "linkQualityTier": "Elite",
  "backlinks_discovered_lost_history": [
    { "date": "2026-05-27T00:00:00", "discovered": 412, "lost": -96 },
    { "date": "2026-07-24T00:00:00", "discovered": 388, "lost": -71 }
  ],
  "keywords_ranking_distribution": [
    { "domain": "zapier.com", "position": "1-3", "ranking_keywords": 1840 },
    { "domain": "zapier.com", "position": "4-10", "ranking_keywords": 5210 }
  ],
  "top_pages": [
    { "page_url": "zapier.com/", "page_authority": 75 }
  ],
  "top_linking_domains": [
    { "domain": "linkedin.com", "domain_authority": 99 },
    { "domain": "wikipedia.org", "domain_authority": 96 }
  ],
  "top_ranking_keywords": [
    { "keyword": "zapier", "rank": 1 }
  ],
  "top_branded_keywords": [
    { "keyword": "zapier pricing", "volume": 8400 }
  ],
  "top_questions": [
    { "question": "What exactly does Zapier do?", "relevance": 28.43 }
  ],
  "top_competitors": [
    { "domain": "www.reddit.com", "visibility": 6.88 }
  ]
}

estimated_total_backlinks, estimated_quality_backlinks, estimated_quality_backlinks_percentage, estimated_do_follow_backlinks_percentage, and estimated_no_follow_backlinks_percentage are computed from Domain Authority and the real linking-root-domain count — Moz's free tool does not publish absolute backlink totals, and every record says so via is_estimated and estimation_note. total_linking_root_domains, top_linking_domains, and link_profile_analysis are built from Moz's real, published Top Linking Domains table.

Failed domain record

If Moz returns no results for a domain after exhausting the proxy fallback ladder, an error record is pushed instead — with a different, smaller shape:

{
  "data_captured_at": "2026-07-25T09:15:41.902003",
  "type": "error",
  "domain": "not-a-real-domain-example.invalid",
  "error": "MOZ returned no results after exhausting the proxy ladder (last error: rate-limited / no results). The target may be temporarily unavailable or the domain is invalid."
}

Error records are pushed to the dataset for visibility but are not charged — only the row_result event on a successful type: "domain_authority" record is billed. If you're reconciling dataset rows against charges, filter on type == "domain_authority" (or type != "error") to see only the billed rows.

Field reference

Every key the Actor can write to a successful record, grouped by what it covers:

Field	Type	Description
data_captured_at	string	ISO timestamp when this record was captured.
type	string	"domain_authority" for a successful record, "error" for a failed one.
last_updated	string	ISO timestamp, matching data_captured_at at capture time.
domain	string	Normalized domain — scheme, path, port, and userinfo stripped, lowercased.
domain_age_years	number | null	Domain age computed from its RDAP registration date; null if the RDAP lookup fails. Present only when include_authority is true.
authority_score	integer	Moz Domain Authority (0–100), parsed from Moz's Domain Authority metric card.
page_authority_score	integer | null	Page Authority of the domain's top-linked page (from Moz's Top Pages by Links table) — used as a domain-level Page Authority proxy, since Moz's free tool does not expose a separate domain-wide PA metric card.
trust_score	integer	authority_score divided by 10 and rounded. A derived convenience figure, not a distinct value Moz's page publishes.
spam_score	number	Moz Spam Score, parsed from its metric card.
offpage_seo_score_percentage	number	A 0–1 score this Actor derives from authority_score and page_authority_score. Not a native Moz metric.
authority_score_last_month	integer	Domain Authority value one month back in the built history.
authority_score_month_over_month_change	integer	authority_score minus authority_score_last_month.
authority_score_history	array	33 monthly {date, domain_authority} points. Months that match a verified Wayback Machine snapshot use that real value; other months follow a deterministic walk anchored to the current score.
total_linking_root_domains	integer	Real linking-root-domain count, from Moz's Linking Root Domains metric card.
is_estimated	boolean	true whenever the estimated_* backlink fields below are present — flags that those specific fields are not real Moz data.
estimation_note	string	Plain-language explanation of exactly which fields are real Moz data and which are estimates.
estimated_total_backlinks	integer	Deterministic estimate derived from total_linking_root_domains. Moz's free tool does not publish this figure.
estimated_quality_backlinks	integer	Deterministic estimate derived from estimated_total_backlinks and authority_score.
estimated_quality_backlinks_percentage	number	estimated_quality_backlinks divided by estimated_total_backlinks.
estimated_do_follow_backlinks_percentage	number	Deterministic estimate derived from authority_score.
estimated_no_follow_backlinks_percentage	number	1 - estimated_do_follow_backlinks_percentage.
link_profile_analysis	object	Full analysis computed from Moz's real Top Linking Domains table — see nested fields below.
linkingDomainsAnalyzed	integer	Promoted copy of link_profile_analysis.linkingDomainsAnalyzed, for easy dataset filtering.
avgLinkingDomainAuthority	number | null	Promoted copy of link_profile_analysis.avgLinkingDomainAuthority.
highAuthorityLinkerCount	integer | null	Promoted copy of link_profile_analysis.highAuthorityLinkerCount.
linkQualityTier	string | null	Promoted copy of link_profile_analysis.linkQualityTier.
backlinks_discovered_lost_history	array	{date, discovered, lost} points parsed from Moz's inline discovered/lost chart data.
keywords_ranking_distribution	array	{domain, position, ranking_keywords} points parsed from Moz's inline ranking-distribution chart data.
top_pages	array	{page_url, page_authority} rows from Moz's Top Pages by Links table.
top_linking_domains	array	{domain, domain_authority} rows from Moz's real Top Linking Domains table.
top_ranking_keywords	array	{keyword, rank} rows from Moz's Top Ranking Keywords table.
top_branded_keywords	array	{keyword, volume} rows from Moz's Branded Keywords table.
top_questions	array	{question, relevance} rows from Moz's Top Questions table.
top_competitors	array	{domain, visibility} rows from Moz's Top Search Competitors table.

Nested inside link_profile_analysis:

Field	Type	Description
minLinkerAuthorityApplied	integer	The minLinkerAuthority threshold that was applied to this analysis.
linkingDomainsAnalyzed	integer	Count of real linkers at or above the threshold that carry a numeric Domain Authority.
avgLinkingDomainAuthority	number | null	Average Domain Authority of the analyzed linkers.
highAuthorityLinkerCount	integer | null	Count of analyzed linkers with Domain Authority ≥ 50.
strongestLinkerAuthority	integer | null	Highest Domain Authority among analyzed linkers.
weakestLinkerAuthority	integer | null	Lowest Domain Authority among analyzed linkers.
linkQualityTier	string | null	Elite (avg DA ≥ 70), Strong (≥ 50), Moderate (≥ 30), or Emerging (below 30).
topLinkerDomains	array	The analyzed linkers sorted by Domain Authority descending, each {domain, domain_authority}.

If a run fails for a domain, the error record only carries data_captured_at, type, domain, and error — none of the fields above.

A transparency note on two fields: trust_score and offpage_seo_score_percentage are calculated by this Actor from authority_score and page_authority_score rather than read from a dedicated Moz metric card. Unlike the estimated_* backlink fields, they are not marked with is_estimated — treat them as directional convenience figures derived by this Actor, not certified Moz output, the same way you should treat page_authority_score itself as a proxy (the top linked page's PA) rather than a distinct domain-wide metric Moz's free tool publishes separately.

🆚 How does MOZ Backlink Profile Analyzer compare to other Moz scrapers?

Feature	MOZ Backlink Profile Analyzer	Generic alternative
Output format	Typed JSON, stable schema every run	Often raw HTML or inconsistent field names
Real vs. estimated data	Explicitly flagged (is_estimated, estimation_note)	Frequently presents formulaic numbers as if they were real Moz data
Link-profile analysis	Computed automatically (avg linker DA, quality tier, ranked linkers)	Usually just a raw table dump, no analysis layer
Proxy/anti-bot handling	Automatic no-proxy → Datacenter → Residential fallback ladder	Varies; many require you to configure proxies manually
Authority threshold filtering	Built in via minLinkerAuthority	Not commonly offered

If you're building an AI agent or RAG pipeline, the output format row is the decision-maker — parsing HTML inside an agent loop is a reliability failure mode, not a feature. A scraper that hands back typed JSON with documented, honestly-labeled fields is the one you can wire into a tool call without a post-processing step.

How many results can you scrape with MOZ Backlink Profile Analyzer?

The Actor itself sets no hard cap on how many domains you can list in urls — you can submit a single domain or a large bulk list in one run. Each domain in the list produces exactly one dataset record (a success record or an error record), processed with bounded concurrency so multiple domains are analyzed in parallel rather than strictly one at a time. The Domain Authority history feature is internally capped at 33 months of trend data per domain and verifies at most 8 archived snapshots per domain against the Wayback Machine — increasing the number of domains in your list does not change either of those per-domain limits. No benchmark run time is published here; actual duration depends on how many domains you submit, whether include_history is enabled, and how often Moz's free tool rate-limits your requests.

Integrate MOZ Backlink Profile Analyzer and automate your workflow

MOZ Backlink Profile Analyzer works with any language or tool that can send an HTTP request, because it runs on the Apify platform and is called through the standard Apify API.

REST API integration

from apify_client import ApifyClient

client = ApifyClient("<YOUR_API_TOKEN>")

run = client.actor("<YOUR_USERNAME>/moz-backlink-profile-analyzer").call(
    run_input={
        "urls": ["zapier.com", "moz.com"],
        "include_authority": True,
        "include_history": True,
        "minLinkerAuthority": 30,
    }
)

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item["domain"], item["authority_score"], item["linkQualityTier"])

Works in Python, Node.js, Go, Ruby, and cURL — any client that can call the Apify API with your API token.

Automation platforms (n8n, Make, LangChain)

In n8n, use the Apify node (or a plain HTTP Request node against the Apify API) to start a run, wait for it to finish, then pull the resulting dataset items into the rest of your workflow. In Make, the Apify app's "Run Actor" and "Get Dataset Items" modules cover the same run-then-fetch pattern without custom code. In LangChain, Apify's dataset loader integration can pull a finished run's dataset directly into a document loader, so link_profile_analysis and keyword fields land in a vector store or agent context without an intermediate parsing step.

Is it legal to scrape Moz backlink data?

Yes — MOZ Backlink Profile Analyzer only collects data Moz already publishes on its free, publicly accessible Domain Analysis pages, with no login or paywall bypass involved. The domains, Domain Authority scores, linking-domain lists, and keyword data returned here are business and SEO metrics about websites, not personal data about individuals, so this falls under general web-scraping and terms-of-service considerations rather than GDPR or CCPA, which govern personal data. That said, Moz's own terms of service govern how you may use data pulled from its site, and database-rights or contractual restrictions can still apply depending on your jurisdiction and use case. Consult legal counsel for commercial use cases involving bulk data collection at scale.

❓ Frequently asked questions

Does MOZ Backlink Profile Analyzer work without a Moz account?

Yes. It scrapes Moz's free, public Domain Analysis tool, which requires no login, no Moz Pro subscription, and no Moz API key. You only need an Apify account to run the Actor.

How often is the scraped data updated?

Every run performs a live fetch of Moz's Domain Analysis page for each domain at the moment you run it — nothing is served from a cache. The one exception is the Domain Authority history: months without a verifiable archived snapshot are filled with a deterministic estimate rather than a second live measurement, so the current month's values are always live but older history points may be interpolated.

What happens if Moz has no data for a domain, or the domain is invalid?

The Actor still returns a record — Domain Authority defaults to 0 when Moz's page doesn't expose a metric card value, and if Moz never returns a valid results page for that domain after the proxy fallback ladder is exhausted, the Actor pushes an error record ("type": "error") instead of a domain record. Error records are not charged.

Can I scrape private or Moz Pro–gated data?

No. This Actor only reads what Moz's free Domain Analysis tool shows to any visitor. It does not access Moz Pro dashboard features, Moz API–only fields, or any account-gated Moz data.

Do I need to sign up for anything besides Apify?

No. There is no separate signup, trial, or API key for Moz involved — you provide domains and run the Actor from your Apify account under the Actor's pay-per-event pricing.

Does MOZ Backlink Profile Analyzer work for AI agent workflows and LLM pipelines?

Yes — it's callable as a standard HTTP endpoint through the Apify API by any agent framework, so it can be wrapped as a tool in an agent loop. Every response is typed JSON with stable field names (authority_score, linkQualityTier, top_competitors, and so on), so there's no HTML or selector parsing step before passing the result into an LLM.

How does MOZ Backlink Profile Analyzer handle Moz's rate limiting?

Moz's free tool limits how many full reports a single IP can pull before showing a rate-limit page instead of real results. The Actor detects that condition (a non-200 response, or a 200 response that doesn't contain real report content) and escalates through a fallback ladder — starting with no proxy, then a Datacenter proxy, then a sticky Residential proxy — retrying with exponential backoff at each level before moving to the next.

How does MOZ Backlink Profile Analyzer compare to other Moz scrapers?

As observed on their own Apify Store listings (checked 2026-07-25), most comparable Actors on the Store are built around a different SEO data provider entirely — for example, DataForSEO Backlinks Analyzer (alizarin_refrigerator-owner/dataforseo-backlinks) requires you to bring your own DataForSEO API login and password and bills $0.05 per query, with a separate demo mode for testing without credentials. MOZ Backlink Profile Analyzer needs no third-party API credentials at all, since it reads Moz's own free public tool directly, and it adds a computed link-profile analysis (average linker authority, quality tier) that a raw API pass-through does not provide on its own.

Does MOZ Backlink Profile Analyzer return data in a format LLMs can use directly?

Yes. Every field is typed, normalized JSON with stable field names across runs — no HTML, no selectors, no parsing. Pass a record directly into an LLM's context window, index it into a vector store, or route it through an agent tool call.

Can I use MOZ Backlink Profile Analyzer without managing proxies?

Yes. The Actor manages its own proxy escalation — direct requests first, then Apify Datacenter, then Apify Residential — and only touches proxy infrastructure when Moz actually blocks a request. The proxyConfiguration input exists for advanced overrides but does not need to be changed for normal use.

What happens when Moz changes its page structure or blocks the scraper?

The Actor is maintained against Moz's current page layout, and the output schema is designed to stay stable on your end — the same field names and types keep working even after a maintenance update fixes a layout change. No specific turnaround time is promised.

💬 Your feedback

Found a bug, a Moz page layout the parser doesn't handle, or a field you need that isn't here? We want to know. Reach out through the Issues tab on this Actor's Apify Store page, or contact API Empire through your Apify Console — reports like this drive real maintenance updates, not just this README.