Nexscope

Website Links

List the internal and external links found on a website, incl. broken links. Call the Website Links API via REST or MCP to automate SEO research.

CostEstimated 10 credits / call
Try online
POST · https://api.nexscope.ai/seo/websiteLinksMCP · nexscope_website_links

What this API does

List the internal and external links found on a website, incl. broken links. The request accepts limit, offset, task_id. Its documented result includes broken, direction, dofollow, fromUrl, targetStatusCode, text, toUrl, missingFields.field.

Website Links API use cases

Investigate Website Links

To investigate website links, a search marketer submits limit and offset to Website Links. The returned broken, direction, dofollow help investigate the requested operation.

Collect Website Links evidence

A search marketer uses Website Links with limit and offset to collect website links evidence. The returned broken, direction, dofollow help compare evidence for the requested scope.

Review Website Links results

For this workflow, a search marketer calls Website Links with limit and offset to review website links results. The result helps review the returned facts with the team.

Website Links API FAQ

What does the Website Links API return?

List the internal and external links found on a website, incl. broken links. The documented output includes broken, direction, dofollow, fromUrl, targetStatusCode, text, toUrl, missingFields.field. It corresponds to the supplied limit, offset, task_id. Optional fields can be absent; a missing value should not be interpreted as a measured zero. Example values illustrate the response shape, rather than live account results.

How many credits does the Website Links API cost?

The current documented cost is Estimated 10 credits / call. This is the same cost shown at the top of this page. If a range or estimate is displayed, the final charge depends on the request. Review your available credits and the pricing page before calling the API, and check API usage records for the actual charge.

How do I call the Website Links API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/seo/websiteLinks with your API key as a Bearer token and the JSON inputs shown in API integration. In a compatible MCP client such as Claude or Cursor, connect Nexscope and call nexscope_website_links. Use the MCP arguments shown in the MCP guide, or switch Online test to MCP to review its request before adding it to your app.

View plans and creditsConnect this API with MCP

Try this API
Endpoint
https://api.nexscope.ai/seo/websiteLinks
MCP method
nexscope_website_links

Step 1 of 3 · Authenticate

Authentication

All run endpoints require a user API key. Send it as a bearer token in the Authorization header.

Authorization: Bearer nk-xxxxxxxxxxxxxxxxx
Missing or invalid API keys return an authentication error. Manage keys from .

Step 2 of 3 · Send a request

POSThttps://api.nexscope.ai/seo/websiteLinks

Run an API

Send a JSON request body using the parameters described below.

Example request

Replace YOUR_API_KEY, then run this command in your terminal.

curl -X POST 'https://api.nexscope.ai/seo/websiteLinks' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "limit": 20,
  "offset": 0,
  "task_id": ""
}'

Code example

{
  "limit": 20,
  "offset": 0,
  "task_id": ""
}

Step 3 of 3 · Inspect the result

Check the response

Read code for the request status and data for the result. Open the parameter and response reference for the full field definitions.

HTTP status codes

CodeDescription
200Default HTTP response for both success and many business errors. Only outer JSON code 0 indicates success or asynchronous acceptance; inspect data for the result.
429Execution admission rate limit; honor Retry-After when present.
503Execution admission is temporarily unavailable; honor Retry-After when present.
Opt-inX-Nexscope-Http-Status: semantic maps controller-handled business errors to HTTP status on run and task routes. Pre-authentication failures, such as a missing API key (code 11209), may still return HTTP 200 before this mapping. Always check the outer JSON code; malformed requests and infrastructure failures may also return non-200 HTTP responses.
All categories/ Website & On-Page SEO

Step 1 of 2 · Connect your MCP client

MCP

V2 recommended

Connect remote agents through the standard MCP 2025-11-25 Streamable HTTP endpoint. Use OAuth 2.1 Authorization Code with PKCE, or an API key for compatibility.

POST https://api.nexscope.ai/mcp
MCP-Protocol-Version: 2025-11-25
Content-Type: application/json
Authentication

OAuth clients request the mcp:tools scope. The endpoint's 401 response advertises protected-resource metadata for authorization discovery.

Step 2 of 2 · Call the tool

Call a tool

{
  "jsonrpc": "2.0",
  "id": "tool-call-1",
  "method": "tools/call",
  "params": {
    "name": "nexscope_website_links",
    "arguments": {
      "limit": 20,
      "offset": 0,
      "task_id": ""
    }
  }
}

Legacy MCP v1

Existing API-key clients can continue using the compatibility endpoint. New integrations should use MCP v2.

GET / POST /mcp/legacy

What can you do with this API?

Data explained and practical use cases

AI Guide

Question

What data can Website Links provide, and how might I use it?

AI answer

Website Links returns link records from a website crawl. Given a crawl task ID, its completed result can show where a link appears, where it points, and what the crawl observed about it.

Data categoryDocumented fieldsWhat the values mean
Link pathdata.result.items[].fromUrl, data.result.items[].toUrlThe page containing the link and its destination.
Internal or externaldata.result.items[].directionWhether the link is classified as INTERNAL, EXTERNAL, or UNKNOWN.
Broken destinationdata.result.items[].broken, data.result.items[].targetStatusCodeA broken-link flag and the destination's observed HTTP status, when available.
Link presentationdata.result.items[].text, data.result.items[].typeLink text and whether the record is an anchor, image, canonical, meta, alternate, redirect, or unknown type.
Follow attributedata.result.items[].dofollowWhether the link is marked as followable, when known.
Sample limitsdata.result.coverage.returnedCount, data.result.coverage.truncated, data.result.missingFields[].reasonHow many records were returned, whether the sample was cut short, and reasons for missing values.
  • Locate source pages that point to broken destinations so an editor can inspect those links.
    • Prompt example: “I am reviewing an ecommerce website. Could you locate source pages that point to broken destinations so an editor can inspect those links? Show matching records and source links where the API provides them; ask me for any required identifier or filter.”
  • Review external links found in the crawl and their destination status codes.
    • Prompt example: “I am reviewing an ecommerce website. Could you review external links found in the crawl and their destination status codes? Show the relevant returned evidence and tell me what input you need from me.”
  • Inspect anchor text and destination pairs for misleading or unclear navigation.
    • Prompt example: “I am reviewing an ecommerce website. Could you inspect anchor text and destination pairs for misleading or unclear navigation? Show the relevant returned evidence and tell me what input you need from me.”
  • Examine canonical or redirect-type link records separately from ordinary anchors.
    • Prompt example: “I am reviewing an ecommerce website. Could you examine canonical or redirect-type link records separately from ordinary anchors? Show the relevant returned evidence and tell me what input you need from me.”

These are sampled crawl observations, not a guaranteed inventory of every site link. A null broken flag or status code does not establish that a destination works.

Online test

Execute the current API with your API key and JSON payload. Online tests use this site's configured API environment; the Endpoint and copyable examples use the public integration address.

Uses your signed-in Nexscope session
SEO API Lab

Website Links

List the internal and external links found on a website, incl. broken links. Call the Website Links API via REST or MCP to automate SEO research.

Live request
Estimated 10 credits / callAPI usage records
Value sent as the “limit” request parameter.

1–100

Value sent as the “offset” request parameter.

0–1000

*
Value sent as the “task_id” request parameter.

Up to 64 characters

Live calls may use Data credits.

Processing result

If a request is still processing, use the returned identifier to retrieve its stored result. The tester recognizes the identifier automatically, and result queries do not spend credits.

Live response

Results

Your live result will appear here.

Complete the request fields above and run the API. No sample response is substituted.

Test with an API key or MCP
Estimated 10 credits / callAPI usage records

Try it

Send a real request with the same contract shown in the reference.

Endpoint
/seo/websiteLinks
Processing result endpoint
https://api.nexscope.ai/seo/websiteLinks/calls/{resultId}
MCP method
nexscope_website_links
cURL
curl -X POST \
  https://api.nexscope.ai/seo/websiteLinks \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "limit": 20, "offset": 0, "task_id": "" }'
Response
No response yet. Run the request to see the response here.
Processing result

Use the identifier returned by Run request. The tester selects the correct result query automatically, and result queries do not spend credits.

Result response
No task result yet. Query the task to see the generated output here.

Related APIs