Nexscope

Page Keyword Density

Measure how often keywords appear on a page to check on-page optimization. Call the Page Keyword Density API via REST or MCP to automate SEO research.

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

What this API does

Measure how often keywords appear on a page to check on-page optimization. The request accepts keywordLength, limit, pageUrl, task_id. Its documented result includes densityRatio, frequency, keyword, missingFields.field, warnings.

Page Keyword Density API use cases

Build a keyword shortlist

To build a keyword shortlist, a search marketer submits keywordLength and limit to Page Keyword Density. The returned densityRatio, frequency, keyword help choose candidate search terms for further investigation.

Compare search demand signals

A search marketer uses Page Keyword Density with keywordLength and limit to compare search demand signals. The returned densityRatio, frequency, keyword help compare keyword demand within the requested market scope.

Plan a content or advertising test

For this workflow, a search marketer calls Page Keyword Density with keywordLength and limit to plan a content or advertising test. The result helps select terms for a content or advertising experiment.

Page Keyword Density API FAQ

What does the Page Keyword Density API return?

Measure how often keywords appear on a page to check on-page optimization. The documented output includes densityRatio, frequency, keyword, missingFields.field, warnings. It corresponds to the supplied keywordLength, limit, pageUrl, 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 Page Keyword Density 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 Page Keyword Density API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/seo/pageKeywordDensity 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_page_keyword_density. 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/pageKeywordDensity
MCP method
nexscope_page_keyword_density

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

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/pageKeywordDensity' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "keywordLength": 1,
  "limit": 20,
  "pageUrl": "https://www.nexscope.ai/",
  "task_id": ""
}'

Code example

{
  "keywordLength": 1,
  "limit": 20,
  "pageUrl": "https://www.nexscope.ai/",
  "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 or invalid API key (code 11209, including an incomplete or corrupted copy) or an expired website login session (code 12001), 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
POSThttps://api.nexscope.ai/seo/pageKeywordDensity

Run this API

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

Endpoint

MethodPOST
Pathhttps://api.nexscope.ai/seo/pageKeywordDensity
AuthBearer API key
Content-Typeapplication/json

Request parameters

NameTypeRequiredDescription
keywordLengthintegeroptional
Keyword length value used by this API operation.
Default: 1
Minimum: 1
Maximum: 5
limitintegeroptional
Limit value used by this API operation.
Default: 20
Minimum: 1
Maximum: 100
pageUrlstringoptional
Page url value used by this API operation.
Format: uri
Maximum length: 2048
task_idstringrequired
Task id value used by this API operation.
Minimum length: 1
Maximum length: 64

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": {
      "coverage": {
        "invalidItemCount": 1,
        "limit": 1,
        "maxCrawlPages": 9007199254740992,
        "offset": 1,
        "pagesCrawled": 9007199254740992,
        "providerTotal": 9007199254740992,
        "returnedCount": 1,
        "sampled": false,
        "stopReason": "synthetic",
        "truncated": false
      },
      "items": [
        {
          "densityRatio": 1.25,
          "frequency": 9007199254740992,
          "keyword": "synthetic"
        }
      ],
      "missingFields": [
        {
          "field": "synthetic",
          "reason": "synthetic"
        }
      ],
      "source": {
        "candidateId": "synthetic",
        "collectedAt": 9007199254740992,
        "observationKind": "synthetic",
        "product": "synthetic",
        "provider": "synthetic",
        "queriedAt": 9007199254740992,
        "sourceCallId": "synthetic",
        "sourcePlanVersion": "synthetic",
        "sourceSchemaVersion": "synthetic"
      },
      "warnings": [
        "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

NameTypeRequiredDescription
codeintegerrequired
0 is a successful envelope; inspect data.status separately.
Allowed: 0, 42008, 42009
coststringrequired
Elapsed processing milliseconds; not price. -1 for non-web context.
dataobjectrequired
Data value used by this API operation.
data.callIdstring | nulloptional
Call id value used by this API operation.
data.completedAtstring | integer | nulloptional
Completed at value used by this API operation.
data.coverageobjectoptional
Coverage value used by this API operation.
data.coverage.missingarrayoptional
Missing value used by this API operation.
data.coverage.missing[]objectrequired
Item in data coverage missing.
data.coverage.missing[].fieldstringoptional
Field value used by this API operation.
data.coverage.missing[].reasonstringoptional
Reason value used by this API operation.
data.coverage.statusstringoptional
Status value used by this API operation.
data.requestedAtstring | integer | nulloptional
Requested at value used by this API operation.
data.resultobject | nullrequired
Result value used by this API operation.
data.result.coverageobjectrequired
Coverage value used by this API operation.
data.result.coverage.invalidItemCountintegerrequired
Invalid item count value used by this API operation.
Minimum: 0
data.result.coverage.limitintegerrequired
Limit value used by this API operation.
Minimum: 0
data.result.coverage.maxCrawlPagesinteger | nullrequired
Max crawl pages value used by this API operation.
Minimum: 0
data.result.coverage.offsetintegerrequired
Offset value used by this API operation.
Minimum: 0
data.result.coverage.pagesCrawledinteger | nullrequired
Pages crawled value used by this API operation.
Minimum: 0
data.result.coverage.providerTotalinteger | nullrequired
Provider total value used by this API operation.
Minimum: 0
data.result.coverage.returnedCountintegerrequired
Returned count value used by this API operation.
Minimum: 0
data.result.coverage.sampledbooleanrequired
Sampled value used by this API operation.
Constant: true
data.result.coverage.stopReasonstring | nullrequired
Stop reason value used by this API operation.
data.result.coverage.truncatedbooleanrequired
Truncated value used by this API operation.
data.result.itemsarrayrequired
Items value used by this API operation.
Maximum items: 100
data.result.items[]objectrequired
Item in data result items.
data.result.items[].densityRationumber | nullrequired
Density ratio value used by this API operation.
Minimum: 0
Maximum: 1
data.result.items[].frequencyinteger | nullrequired
Frequency value used by this API operation.
Minimum: 0
data.result.items[].keywordstringrequired
Keyword value used by this API operation.
Maximum length: 4096
data.result.missingFieldsarrayrequired
Missing fields value used by this API operation.
Maximum items: 10000
data.result.missingFields[]objectrequired
Item in data result missingFields.
data.result.missingFields[].fieldstringrequired
Field value used by this API operation.
data.result.missingFields[].reasonstringrequired
Reason value used by this API operation.
data.result.sourceobjectrequired
Source value used by this API operation.
data.result.source.candidateIdstringrequired
Candidate id value used by this API operation.
Constant: MD-PW-12
data.result.source.collectedAtinteger | nullrequired
Collected at value used by this API operation.
Minimum: 0
Maximum: 9007199254740991
data.result.source.observationKindstringrequired
Observation kind value used by this API operation.
Constant: CRAWL_SAMPLE
data.result.source.productstringrequired
Product value used by this API operation.
Constant: on_page
data.result.source.providerstringrequired
Provider value used by this API operation.
Constant: DATAFORSEO
data.result.source.queriedAtintegerrequired
Queried at value used by this API operation.
Minimum: 0
Maximum: 9007199254740991
data.result.source.sourceCallIdstring | nullrequired
Source call id value used by this API operation.
data.result.source.sourcePlanVersionstring | nullrequired
Source plan version value used by this API operation.
data.result.source.sourceSchemaVersionstring | nullrequired
Source schema version value used by this API operation.
data.result.warningsarrayrequired
Warnings value used by this API operation.
Maximum items: 1000
data.result.warnings[]stringrequired
Item in data result warnings.
data.schemaVersionstring | nulloptional
Schema version value used by this API operation.
data.sourcestring | nulloptional
Source value used by this API operation.
data.statusstringoptional
Status value used by this API operation.
Allowed: SUCCESS, PARTIAL, EMPTY, PROCESSING, UNKNOWN, FAILED
data.usageobject | nulloptional
Usage value used by this API operation.
data.usage.billingStatusstring | nulloptional
Billing status value used by this API operation.
data.usage.chargedCreditsstring | integer | nulloptional
Charged credits value used by this API operation.
msgstring | nullrequired
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.
timestringrequired
yyyy-MM-dd HH:mm:ss
traceIdstring | nullrequired
Trace id value used by this API operation.
tsstringrequired
Epoch milliseconds; global long serializer.

Accepted processing response

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

NameTypeRequiredDescription
codeintegerrequired
0 is a successful envelope; inspect data.status separately.
Constant: 0
coststringrequired
Elapsed processing milliseconds; not price. -1 for non-web context.
dataobjectrequired
Data value used by this API operation.
data.callIdstring | nullrequired
Call id value used by this API operation.
data.reasonstringrequired
Reason value used by this API operation.
Constant: IN_PROGRESS
data.retryablebooleanoptional
Retryable value used by this API operation.
data.statusstringrequired
Status value used by this API operation.
Constant: PROCESSING
data.taskIdstring | nulloptional
Task id value used by this API operation.
msgstring | nullrequired
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.
timestringrequired
yyyy-MM-dd HH:mm:ss
traceIdstring | nullrequired
Trace id value used by this API operation.
tsstringrequired
Epoch milliseconds; global long serializer.

Error response

NameTypeRequiredDescription
codeintegerrequired
0 is a successful envelope; inspect data.status separately.
coststringrequired
Elapsed processing milliseconds; not price. -1 for non-web context.
dataobjectrequired
Data value used by this API operation.
data.callIdstring | nullrequired
Call id value used by this API operation.
data.reasonstring | nullrequired
Reason value used by this API operation.
data.retryablebooleanoptional
Retryable value used by this API operation.
data.statusstring | nullrequired
Status value used by this API operation.
data.taskIdstring | nulloptional
Task id value used by this API operation.
msgstring | nullrequired
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.
timestringrequired
yyyy-MM-dd HH:mm:ss
traceIdstring | nullrequired
Trace id value used by this API operation.
tsstringrequired
Epoch milliseconds; global long serializer.

Retrieve a processing result

A response withPROCESSING and a callIdmeans 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/pageKeywordDensity/calls/{callId} \
  -H "Authorization: Bearer nk-xxxxxxxxxxxxxxxxx"

Responses

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 or invalid API key (code 11209, including an incomplete or corrupted copy) or an expired website login session (code 12001), 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.

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_page_keyword_density",
    "arguments": {
      "keywordLength": 1,
      "limit": 20,
      "pageUrl": "https://www.nexscope.ai/",
      "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 keyword data can Page Keyword Density provide, and how might I use it?

AI answer

This API reports keyword frequency and density for a sampled page crawl. The example response is still PROCESSING, so it provides no measured keywords yet; use the completed data.result before interpreting results. The documented result is sampled and may be truncated or have missing values.

Data categoryDocumented fieldsWhat the values mean
Keywordsdata.result.items[].keywordKeywords returned from the crawl sample.
Occurrencedata.result.items[].frequencyRecorded occurrence count for each keyword; it may be null.
Densitydata.result.items[].densityRatioRecorded density ratio from 0 to 1 for each keyword; it may be null.
Sample coveragedata.result.coverage.returnedCount, data.result.coverage.sampled, data.result.coverage.truncated, data.result.coverage.pagesCrawledHow many items were returned and whether the crawl sample was limited.
Gaps and cautionsdata.result.missingFields[].field, data.result.missingFields[].reason, data.result.warningsFields that could not be supplied, their reasons, and other result warnings.
  • Check whether a target term appears among the returned keywords for a page.
    • Prompt example: “I am reviewing an ecommerce website. Could you check whether a target term appears among the returned keywords for a page? Show the relevant returned evidence and tell me what input you need from me.”
  • Compare the reported frequencies and density ratios of terms within the sampled result.
    • Prompt example: “I am reviewing an ecommerce website. Could you compare the reported frequencies and density ratios of terms within the sampled result? Show the returned values behind the comparison, and mark missing data.”
  • Use missingFields and warnings to decide whether a null or absent measure needs investigation.
    • Prompt example: “I am reviewing an ecommerce website. Could you use missingFields and warnings to decide whether a null or absent measure needs investigation? Show the relevant returned evidence and tell me what input you need from me.”
  • Check truncated and returnedCount before treating the returned keyword list as broad coverage.
    • Prompt example: “I am reviewing an ecommerce website. Could you check truncated and returnedCount before treating the returned keyword list as broad coverage? Show the relevant returned evidence and tell me what input you need from me.”

Related APIs