RankParse
All workflows
Domain Diagnostics

Authority Metric Disagreement

Explain why authority-related metrics disagree and identify which signal should drive decisions for the current use case.

Best for: Use this when stakeholders question authority changes or when competitor comparisons seem inconsistent.

Required inputs

  • Domain · example.com

Estimate

7-11 credits

Expected output blocks

3

Run in cloud agentGet API key

Run in your agent

Follow these two steps to execute this workflow in cloud mode.

Step 1

Connect RankParse MCP

Pick your client and follow copy-paste setup steps.

1
Runclaude mcp add --transport http rankparse https://mcp.rankparse.com/sse --header "X-API-Key: rp_your_key_here"
2
UseStart a new Claude Code session and ask for backlink/authority analysis.

Fastest path if you are in terminal and want zero UI setup.

Step 2

Run this prompt

Paste this prompt into your agent and replace placeholders like {{domain}}.

You are an SEO analyst agent running in cloud mode.
You have RankParse MCP connected as "rankparse".

Workflow: Authority Metric Disagreement
Intent: Prevent bad decisions caused by over-indexing on a single metric.

Diagnose authority metric disagreement for {{domain}}.

Use:
1) get_domain_authority
2) get_domain_rank
3) get_referring_domains(limit=100)
4) get_backlinks(limit=100, sort="importance")

If {{benchmark_domain}} is provided, repeat (1) and (2) for the benchmark and compare.

Output:
- metric_snapshot
- disagreement_causes
- confidence_level
- decision_rule_for_this_case
- next_measurement_plan

Important:
- Use the listed RankParse tools for data retrieval.
- Return strict JSON only (no markdown).
Use REST instead

REST fallback (cURL)

Use this only if MCP is unavailable in your runtime.

export RP_API_KEY="rp_your_key_here"
export TARGET_DOMAIN="example.com"
export BENCHMARK_DOMAIN="peer.com"
export LIMIT="100"

curl "https://api.rankparse.com/v1/domain-authority?domain=$TARGET_DOMAIN" \
  -H "X-API-Key: $RP_API_KEY"
curl "https://api.rankparse.com/v1/domain-rank?domain=$TARGET_DOMAIN" \
  -H "X-API-Key: $RP_API_KEY"
curl "https://api.rankparse.com/v1/referring-domains?domain=$TARGET_DOMAIN&limit=$LIMIT" \
  -H "X-API-Key: $RP_API_KEY"
curl "https://api.rankparse.com/v1/backlinks?domain=$TARGET_DOMAIN&limit=$LIMIT&sort=importance" \
  -H "X-API-Key: $RP_API_KEY"

# Optional benchmark comparison
curl "https://api.rankparse.com/v1/domain-authority?domain=$BENCHMARK_DOMAIN" \
  -H "X-API-Key: $RP_API_KEY"
curl "https://api.rankparse.com/v1/domain-rank?domain=$BENCHMARK_DOMAIN" \
  -H "X-API-Key: $RP_API_KEY"
Advanced: raw MCP config JSON

MCP config (JSON)

Use this only when your client expects raw MCP JSON configuration.

{
  "mcpServers": {
    "rankparse": {
      "url": "https://mcp.rankparse.com/sse",
      "headers": {
        "X-API-Key": "rp_your_key_here"
      }
    }
  }
}

Expected output

  • Metric snapshot

    Current authority, rank, breadth, and quality context in one view.

  • Disagreement causes

    Root causes for conflicting metric stories.

  • Decision rule

    Which metric to prioritize for the immediate task and why.

Advanced details

Next actions

  • Align stakeholders on a primary metric for this workflow.
  • Log diagnosis assumptions for future trend reviews.
  • Set next re-check window with the same comparison inputs.

MCP tools

  • get_domain_authority

    Primary authority signal.

  • get_domain_rank

    Graph and edge-count perspective.

  • get_referring_domains

    Breadth and distribution of linking domains.

  • get_backlinks

    Link-level context for outliers.

REST endpoints