Domain Rating API
Check a domain-level DR signal in JSON. Use it for initial SEO screening, then inspect actual pages, backlink context and estimated traffic before deciding what to do.
One domain · DR score and rank when available
https://api.goanyapi.com/api/v1/drRun a request to see the visual result
The response is organized into metrics, lists and tables that match the JSON on the right.
Run a request to see the response here
Fill in the demo parameters to preview an example response for free. Sign in to send live requests with your own parameters.
Read a domain-level rating with context
Check one domain in the Tester, then read the domain and rating fields without treating DR as a search result rank.
GET https://api.goanyapi.com/api/v1/dr?domain=example.com
Authorization: Bearer YOUR_API_KEYRequest example only. DR is not a Google score or SERP rank.
Start with these JSON paths
data.domain- Queried domain represented by the response.
data.domain_rating- Available domain-level rating value.
What the data can tell you
One domain · Domain-level DR signal
Domain rating
Read the returned domain_rating for a queried domain as an external SEO metric. It is not a Google score and does not predict a specific page’s ranking position.
Interpret missing values
Keep absent fields distinct from a measured zero, and do not interpret a domain-level rating as a search-result position or a promise of visibility.
Prospect enrichment
Enrich a prospect list one domain at a time, then combine DR with relevant content, selected backlinks and estimated audience data from separate GoAnyAPI requests.
From a question to a useful result
A practical workflow using the available data.
Prioritize link prospects
Query candidate domains individually and record the returned rating with a retrieval date. Shortlist only after checking topical relevance and the actual pages where a link could appear.
Explain an SEO report
Explain DR as a domain-level SEO signal in your report, not a Google metric. Add backlink and traffic evidence from separate endpoints when a decision needs more context.
Investigate changes
Use the separate Domain Rating History API to inspect available month-by-month records. Keep historical availability and current-query values distinct instead of implying this endpoint returns a time series.
Domain Rating (DR) API FAQ
Questions about fit, interpretation and integration.
No. Domain Rating is a domain-level SEO metric, not a score issued by Google and not a direct promise of search positions. It should be interpreted with the site’s content, traffic and link context.
It is a domain-level rating value for SEO screening, not a Google or Bing result position. Keep the response date and combine it with relevant content, traffic and link evidence before making a decision.
No. A rating can help prioritize research, but placement relevance, the actual linking page, audience fit and link context still matter. Use the separate Backlink and Traffic APIs for additional signals.
No. This endpoint queries one domain’s current available values. Use the separate Domain Rating History API for available month-by-month data; it has its own parameters and billing rules.
No. The documented request accepts one domain. Query each domain separately from your application, respect its response state and preserve missing values rather than turning them into zeros.
The Tester and Docs show the current configured rate. Successful non-empty results use that rate; invalid parameters, failed requests and empty results do not consume credits.
Use the documented HTTP endpoint with a GoAnyAPI key to read JSON. An assistant needs a connected GoAnyAPI MCP tool; saving a prospect list or scheduled monitoring is your own workflow.
Continue with related GoAnyAPI APIs
Use separate requests for each signal; keep their meanings and dates distinct.