/on-page

SEO Audit API for technical page analysis

View examples Talk to sales

Check example.com/category

example.com/category

example.com

Status: 200 · meta description: missing

Internal link checks

example.com

Two broken links to investigate

Canonical and duplicate checks

example.com

Inspect page status, metadata, links and crawl checks. Use URL analysis, site crawls and rendering options to build a repeatable technical SEO workflow.

example.com/category

example.com

Status: 200 · meta description: missing

Internal link checks

example.com

Two broken links to investigate

Workflows

Illustrative workflows built with search data

Workflows

Illustrative workflows built with search data

On-Page API capabilities

Inspect an individual URL or submit a bounded crawl. Record the target, crawl limits and rendering options so later checks describe the same site scope.

Running shoes — research example

             example.com
            

Ask which question you need to answer first. Then select the data family, fields, and collection cadence that support that decision.

Results

Review pages, resources, uncrawlable assets, non-indexable pages and pages associated with a resource. Separate a collection limitation from an issue confirmed on the site.

Running shoes — organic result

             example.com
            

Example ranking: 1 · United States · desktop · organic result.

Trail running shoes — category page

             example.com
            

Inspect URLs and crawl websites to investigate metadata, page status, links and technical checks. Use browser-based analysis only where the selected route and site require it.

Running guide — informational page

             example.com
            

Use comparable inputs for repeated research. Inspect the source context before interpreting a change as a trend.

Example Brand — citation research

             example.com
            

Plan API requests for individual tasks or discuss a bulk dataset when your analysis needs a broader historical view.

Highlights

Inspect internal links and redirect chains. Prioritize broken paths and redirect behavior that prevent users or crawlers reaching important pages.

Structured data for your workflow

              "content"
             
              : {
             
              "
              
              keyword
              
              "
             
              :
             
              url: https://example.com 
              
              "
              
              Group crawl issues by type and priority, then check affected URLs after a fix.
              
              "
             
              :
             
              "
              
              organic
              
              "
             
              example.com
             
              "
              
              location
              
              "
             
              :
             
              "
              
              United States
              
              "
             
              example.com
             
              "
              
              Find broken links, duplicate content, missing metadata, and other crawl checks.
              
              "
             
              :
             
              "
              
              desktop
              
              "
             
              }

Structured outputs

Investigate duplicate content, duplicate tags, keyword density, parsed content and raw HTML. Confirm the affected page before treating every automated warning as a ranking problem.

Structured data for your workflow

Use supported JavaScript rendering, browser options, and Lighthouse analysis when the site needs them. 1 The demo records are illustrative. Discuss production access, request volume, and collection cadence with the DataSEO team. 2 3 Crawl websites, inspect individual URLs, and surface technical issues across metadata, internal links, content, and performance. 4 .

AI Summary

Use Lighthouse, waterfall and screenshot capabilities when the investigation requires them. A lab run describes its test conditions and does not replace real-user Core Web Vitals.

Illustrative response fields

Read crawl summaries and task status, then compare affected URLs after remediation. Keep evidence, impact and the verified outcome attached to each reported issue.

Queued collection 69.6% / 454ms

Live collection 67.8% / ~1.2s

SEO Labs 80.0% / 4.3s avg

Sample collection 46.0% / 2.7s

Sample collection 41.0% / 1.3s

Example collection 43.0% / 547ms

Sample collection 50.0% / 583ms

Accuracy / Latency

Example technical seo

Accuracy / Latency

Example coverage (%)

30%

40%

50%

60%

70%

80%

90%

Queued collection 69.6% / 454ms

Live collection 67.8% / ~1.2s

SEO Labs 80.0% / 4.3s avg

Sample collection 46.0% / 2.7s

Sample collection 41.0% / 1.3s

Example collection 43.0% / 547ms

Sample collection 50.0% / 583ms

300ms 500ms 1s 2s 4s

Latency (ms, log scale)

Pricing

Collection scope and access

Request a quote for your volume

View examples Talk to sales

batch Queued

Scheduled data collection

live Live

Instant page analysis starts with a URL. A site crawl uses task-based collection with a target and crawl limits; confirm the scope before submitting a large site.

extended Extended

Confirm the selected route and source

FROM IDEA TO FIRST REQUEST

Build with On-Page API

Inspect response status, page title, description, canonical signals and available content checks. Investigate the affected URL before treating every warning as a ranking issue.

Read the docs ↗Talk to our team ↗

NODE.JS

// Server-side example; configure your deployment and credentials.
const url = new URL("/v3/on_page/instant_pages", process.env.DATASEO_API_ORIGIN);
const auth = Buffer.from(`${process.env.DATASEO_LOGIN}:${process.env.DATASEO_PASSWORD}`).toString("base64");
const response = await fetch(url, {
  method: "POST",
  headers: {Authorization: `Basic ${auth}`, "Content-Type": "application/json"},
  body: JSON.stringify([{"url": "https://example.com"}])
});
if (!response.ok) throw new Error(`HTTP ${response.status}`);
const data = await response.json();
for (const task of data.tasks ?? []) {
  if (task.status_code !== 20000) throw new Error(task.status_message);
}
// Use task.result only after checking task status.

Browse the complete API endpoint reference