Page SEO Evidence

Collect on-page SEO data for a URL, incl. tags, headings and content. Call the Page SEO Evidence API via REST or MCP to automate SEO research.

CostRecent 10 credits / call

Try online

POST · https://api.nexscope.ai/seo/pageEvidenceMCP · nexscope_seo_page_evidence

Website & On-Page SEO

What this API does

Collect on-page SEO data for a URL, incl. tags, headings and content. The request accepts url. Its documented result includes requestedUrl, snapshots.capturedAt, snapshots.evidence.canonical, snapshots.evidence.description, snapshots.evidence.h1, snapshots.evidence.html.content, snapshots.evidence.html.sha256, snapshots.evidence.html.truncated.

Page SEO Evidence API use cases

Investigate Page SEO Evidence

To investigate page seo evidence, a search marketer submits url to Page SEO Evidence. The returned requestedUrl, snapshots.capturedAt, snapshots.evidence.canonical help investigate the requested operation.

Collect Page SEO Evidence evidence

A search marketer uses Page SEO Evidence with url to collect page seo evidence evidence. The returned requestedUrl, snapshots.capturedAt, snapshots.evidence.canonical help compare evidence for the requested scope.

Review Page SEO Evidence results

For this workflow, a search marketer calls Page SEO Evidence with url to review page seo evidence results. The result helps review the returned facts with the team.

Page SEO Evidence API FAQ

What does the Page SEO Evidence API return?

Collect on-page SEO data for a URL, incl. tags, headings and content. The documented output includes requestedUrl, snapshots.capturedAt, snapshots.evidence.canonical, snapshots.evidence.description, snapshots.evidence.h1, snapshots.evidence.html.content, snapshots.evidence.html.sha256, snapshots.evidence.html.truncated. It corresponds to the supplied url. 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 Page SEO Evidence API cost?

The current documented cost is Recent 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 Page SEO Evidence API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/seo/pageEvidence 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_seo_page_evidence. The same documented request parameters apply; use Online test to review a request before adding it to your app.

View plans and credits Connect this API with MCP

Try this API

Endpoint

https://api.nexscope.ai/seo/pageEvidence

MCP method

nexscope_seo_page_evidence

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/pageEvidence

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/pageEvidence' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "url": "nexscope"
}'

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

Code	Description
200	HTTP request completed. Check JSON code; only 0 indicates business success or acceptance.
400	Request JSON or required API parameters are invalid.
401	API key is missing, invalid, or cannot be matched to a user.
5xx	API execution or upstream service failed.

View parameters & response Try online

All categories/ Website & On-Page SEO

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

Run this API

Send a JSON request to execute this API and receive the documented response payload.

Open tester

Endpoint

Method	`POST`
Path	`https://api.nexscope.ai/seo/pageEvidence`
Auth	`Bearer API key`
Content-Type	`application/json`

Request parameters

Name	Type	Required	Description
`url`	`string`	required	Public HTTP(S) URL only; no credentials, IP literals or nonstandard ports. Minimum length: 1 Maximum length: 2048

Code example

{
  "url": "nexscope"
}

Response example

Example response envelope from the documented SEO API contract.

{
  "code": 0,
  "cost": "-1",
  "data": {
    "callId": "synthetic-call",
    "completedAt": null,
    "coverage": {
      "missing": [
        {
          "field": "synthetic",
          "reason": "UPSTREAM_FIELD_MISSING"
        }
      ],
      "status": "PARTIAL"
    },
    "requestedAt": "123",
    "result": {
      "requestedUrl": "synthetic",
      "snapshots": [
        {
          "capturedAt": 9007199254740992,
          "evidence": null,
          "finalUrl": "synthetic",
          "id": "synthetic",
          "missing": [
            {
              "field": "synthetic",
              "reason": "synthetic"
            }
          ],
          "sourceEndpoint": "synthetic",
          "status": "synthetic"
        }
      ]
    },
    "schemaVersion": "synthetic",
    "source": "synthetic",
    "status": "PARTIAL",
    "usage": {
      "billingStatus": "UNAPPROVED",
      "chargedCredits": "0"
    }
  },
  "msg": null,
  "time": "2026-01-01 00:00:00",
  "traceId": "synthetic-trace",
  "ts": "9007199254740993"
}

Response fields

Name	Type	Required	Description
`code`	`integer`	required	0 is a successful envelope; inspect data.status separately. Allowed: 0, 42008, 42009
`cost`	`string`	required	Elapsed processing milliseconds; not price. -1 for non-web context.
`data`	`object`	required	Data value used by this API operation.
`data.callId`	`string`	optional	Call id value used by this API operation. Format: uuid
`data.completedAt`	`string \| integer \| null`	optional	UTC epoch milliseconds.
`data.coverage`	`object`	optional	Coverage value used by this API operation.
`data.coverage.missing`	`array`	optional	Missing value used by this API operation.
`data.coverage.missing[]`	`object`	required	Item in data coverage missing.
`data.coverage.missing[].field`	`string`	optional	Field value used by this API operation.
`data.coverage.missing[].reason`	`string`	optional	Reason value used by this API operation.
`data.coverage.status`	`string`	optional	Status value used by this API operation.
`data.reason`	`string`	optional	Stable reason on errors 42001 through 42011; accepted errors retain callId.
`data.requestedAt`	`string \| integer \| null`	optional	UTC epoch milliseconds.
`data.result`	`object \| null`	required	Result value used by this API operation.
`data.result.requestedUrl`	`string \| null`	optional	Requested url value used by this API operation.
`data.result.snapshots`	`array`	optional	Snapshots value used by this API operation.
`data.result.snapshots[]`	`object`	required	Item in data result snapshots.
`data.result.snapshots[].capturedAt`	`integer \| null`	optional	Captured at value used by this API operation.
`data.result.snapshots[].evidence`	`any`	optional	Evidence value used by this API operation.
`data.result.snapshots[].finalUrl`	`string \| null`	optional	Final url value used by this API operation.
`data.result.snapshots[].id`	`string \| null`	optional	Id value used by this API operation.
`data.result.snapshots[].missing`	`array`	optional	Missing value used by this API operation.
`data.result.snapshots[].missing[]`	`object`	required	Item in data result snapshots[] missing.
`data.result.snapshots[].missing[].field`	`string \| null`	optional	Field value used by this API operation.
`data.result.snapshots[].missing[].reason`	`string \| null`	optional	Reason value used by this API operation.
`data.result.snapshots[].sourceEndpoint`	`string \| null`	optional	Source endpoint value used by this API operation.
`data.result.snapshots[].status`	`string \| null`	optional	Status value used by this API operation.
`data.retryable`	`boolean`	optional	Retryable value used by this API operation. Constant: false
`data.schemaVersion`	`string`	optional	Schema version value used by this API operation. Constant: 1.0
`data.source`	`string`	optional	Source value used by this API operation. Constant: dataforseo
`data.status`	`string`	optional	Status value used by this API operation. Allowed: SUCCESS, PARTIAL, EMPTY, PROCESSING, UNKNOWN, FAILED
`data.usage`	`object \| null`	optional	Usage value used by this API operation.
`data.usage.billingStatus`	`string \| null`	optional	Billing status value used by this API operation.
`data.usage.chargedCredits`	`string \| integer \| null`	optional	Charged credits value used by this API operation.
`msg`	`string \| null`	required	Available upstream msg/errmsg/message is preferred for success and failure; Chinese is translated to English. Missing successful message is null. Platform-only errors and task states use platform English. Message text never determines success or retry.
`time`	`string`	required	yyyy-MM-dd HH:mm:ss
`traceId`	`string \| null`	required	Trace id value used by this API operation.
`ts`	`string`	required	Epoch milliseconds; global long serializer.

Any of option 1

Name	Type	Required	Description
`data.result.snapshots[].evidence`	`object`	optional	Evidence value used by this API operation.
`data.result.snapshots[].evidence.canonical`	`string \| null`	optional	Canonical value used by this API operation.
`data.result.snapshots[].evidence.description`	`string \| null`	optional	Description value used by this API operation.
`data.result.snapshots[].evidence.h1`	`array`	optional	H1 value used by this API operation.
`data.result.snapshots[].evidence.h1[]`	`string \| null`	required	Item in data result snapshots[] evidence h1.
`data.result.snapshots[].evidence.html`	`object`	optional	Html value used by this API operation.
`data.result.snapshots[].evidence.html.content`	`string \| null`	optional	Content value used by this API operation.
`data.result.snapshots[].evidence.html.sha256`	`string \| null`	optional	Sha256 value used by this API operation.
`data.result.snapshots[].evidence.html.truncated`	`boolean`	optional	Truncated value used by this API operation.
`data.result.snapshots[].evidence.httpStatus`	`integer \| null`	optional	Http status value used by this API operation.
`data.result.snapshots[].evidence.metaRobots`	`array`	optional	Meta robots value used by this API operation.
`data.result.snapshots[].evidence.metaRobots[]`	`string \| null`	required	Item in data result snapshots[] evidence metaRobots.
`data.result.snapshots[].evidence.textLength`	`integer \| null`	optional	Text length value used by this API operation.
`data.result.snapshots[].evidence.title`	`string \| null`	optional	Title value used by this API operation.

Any of option 2

Name	Type	Required	Description
`data.result.snapshots[].evidence`	`object`	optional	Evidence value used by this API operation.
`data.result.snapshots[].evidence.links`	`array`	optional	Links value used by this API operation.
`data.result.snapshots[].evidence.links[]`	`object`	required	Item in data result snapshots[] evidence links.
`data.result.snapshots[].evidence.links[].text`	`string \| null`	optional	Text value used by this API operation.
`data.result.snapshots[].evidence.links[].url`	`string \| null`	optional	Url value used by this API operation.
`data.result.snapshots[].evidence.linksTruncated`	`boolean`	optional	Links truncated value used by this API operation.
`data.result.snapshots[].evidence.text`	`string \| null`	optional	Text value used by this API operation.
`data.result.snapshots[].evidence.textTruncated`	`boolean`	optional	Text truncated value used by this API operation.
`data.result.snapshots[].evidence.title`	`string \| null`	optional	Title value used by this API operation.

Accepted processing response

code 0 confirms acceptance. Use data.callId to query the same request; processing is not completion.

Name	Type	Required	Description
`code`	`integer`	required	0 is a successful envelope; inspect data.status separately. Constant: 0
`cost`	`string`	required	Elapsed processing milliseconds; not price. -1 for non-web context.
`data`	`object`	required	Data value used by this API operation.
`data.callId`	`string \| null`	required	Call id value used by this API operation.
`data.reason`	`string`	required	Reason value used by this API operation. Constant: IN_PROGRESS
`data.retryable`	`boolean`	optional	Retryable value used by this API operation.
`data.status`	`string`	required	Status value used by this API operation. Constant: PROCESSING
`data.taskId`	`string \| null`	optional	Task id value used by this API operation.
`msg`	`string \| null`	required	Available upstream msg/errmsg/message is preferred for success and failure; Chinese is translated to English. Missing successful message is null. Platform-only errors and task states use platform English. Message text never determines success or retry.
`time`	`string`	required	yyyy-MM-dd HH:mm:ss
`traceId`	`string \| null`	required	Trace id value used by this API operation.
`ts`	`string`	required	Epoch milliseconds; global long serializer.

Error response

Name	Type	Required	Description
`code`	`integer`	required	0 is a successful envelope; inspect data.status separately.
`cost`	`string`	required	Elapsed processing milliseconds; not price. -1 for non-web context.
`data`	`object`	required	Data value used by this API operation.
`data.callId`	`string \| null`	required	Call id value used by this API operation.
`data.reason`	`string \| null`	required	Reason value used by this API operation.
`data.retryable`	`boolean`	optional	Retryable value used by this API operation.
`data.status`	`string \| null`	required	Status value used by this API operation.
`data.taskId`	`string \| null`	optional	Task id value used by this API operation.
`msg`	`string \| null`	required	Available upstream msg/errmsg/message is preferred for success and failure; Chinese is translated to English. Missing successful message is null. Platform-only errors and task states use platform English. Message text never determines success or retry.
`time`	`string`	required	yyyy-MM-dd HH:mm:ss
`traceId`	`string \| null`	required	Trace id value used by this API operation.
`ts`	`string`	required	Epoch milliseconds; global long serializer.

Retrieve a processing result

A response with PROCESSING and a callId means the result is still being prepared. Use the result query below with the returned identifier. This lookup reads the stored result and does not spend credits.

curl -X GET https://api.nexscope.ai/seo/pageEvidence/calls/{callId} \
  -H "Authorization: Bearer nk-xxxxxxxxxxxxxxxxx"

Responses

Code	Description
200	HTTP request completed. Check JSON code; only 0 indicates business success or acceptance.
400	Request JSON or required API parameters are invalid.
401	API key is missing, invalid, or cannot be matched to a user.
5xx	API execution or upstream service failed.

Data source, freshness, and limitations

Source, freshness, coverage, rate limits, and estimation notes are not specified in this API definition unless they appear in the request or response field documentation above. Do not assume official marketplace data or real-time freshness when it is not explicitly documented.

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_seo_page_evidence",
    "arguments": {
      "url": "nexscope"
    }
  }
}

Legacy MCP v1

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

GET / POST /mcp/legacy

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

SEO Page Evidence

Collect on-page SEO data for a URL, incl. tags, headings and content. Call the Page SEO Evidence API via REST or MCP to automate SEO research.

Live request

Estimated 10 credits / callAPI usage records

URL

Public HTTP(S) URL only; no credentials, IP literals or nonstandard ports.

Up to 2048 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/pageEvidence

Processing result endpoint

https://api.nexscope.ai/seo/pageEvidence/calls/{resultId}

MCP method

nexscope_seo_page_evidence

API key*

JSON payload*

cURL

curl -X POST \
  https://api.nexscope.ai/seo/pageEvidence \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "url": "nexscope" }'

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 identifier

Result response

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

Related APIs

Page Structured Data

Extract the structured data (schema markup) found on a page.

Page Screenshot

Capture a full-page screenshot of any URL for audits and visual checks.

Website Audit Summary

Get an SEO audit summary of a website, with issues found during a crawl.

Website Page Checks

Run on-page SEO checks on the pages of a website.