Web Data

Site audit and SEO crawler API

Crawl up to 50 pages of a website from a start URL and get a technical SEO report in one response: broken internal links, redirects, duplicate titles, descriptions and content, thin and noindex pages, and the most common on-page issues.

Category Web Data
Endpoints 1
Key Features 4
Frequently asked questions 4

Used by people at these companies

InstantOutseerMongoDBRespondentSage Expense ManagementInstantlyD.R. HortonWhatConvertsAdobeLLM Pulse

Trust signals before you integrate

Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.

Live Service status

Check live service health and documented failure responses before you integrate.

OpenAPI API artifacts

OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.

API keys Protected access

Authenticated endpoints use API keys with clear credit costs before you call them.

10,000 Free allowance

Start with 10,000 monthly credits and upgrade only when usage grows.

What this API helps you ship

Use this page as a production brief: endpoints, examples, response shape, and the workflow pieces needed to plug DomScan into your own product.

Product workflows

Embed domain checks, DNS intelligence, risk signals, or enrichment into onboarding, search, and internal tools.

Analyst automation

Replace repeated manual lookups with scheduled jobs, alerting, and reproducible investigation steps.

Clean JSON data

Use predictable fields, documented status codes, and credit costs instead of scraping provider pages.

AI and ops tooling

Feed agents, dashboards, SOAR playbooks, and CRMs through OpenAPI, SDK, Postman, or MCP.

Integration workflow

A simple path from first request to repeatable production usage.

1
Authenticate once

Send your API key with the documented header and keep requests consistent across services.

2
Query with examples

Start from the curl and HTTP samples, then map the parameters into your application code.

3
Operate and monitor

Use status codes, credit costs, and response fields to build retries, logs, and alerts.

Developer kit

Jump from this page into machine-readable docs, request collections, SDKs, or agent tooling.

Parameters and response map

Scan the inputs, output fields, and status codes before wiring the endpoint into your client.

Request parameters

Parameter

urlmax_pages
Response fields

Example response

statussummarysummary.pages_crawledsummary.pages_oksummary.pages_not_foundsummary.average_scoresummary.crawl_completeissuesissues.broken_internal_linksissues.duplicate_meta_descriptionsissues.thin_pagesissues.onpage_checks
Status coverage

HTTP status codes

200400401402429

Endpoints

GET /v1/site-audit
Credits: 10-35Authentication: Authentication required

Trust signals before you integrate

Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.

Service status API artifacts

OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.

API keys Protected access

Authenticated endpoints use API keys with clear credit costs before you call them.

Free allowance Sign up for free

Start with 10,000 monthly credits and upgrade only when usage grows.

Active Example request

Start from the curl and HTTP samples, then map the parameters into your application code.

Key Features

Polite crawling

Pages are discovered through internal links, robots.txt is followed and a few pages are fetched at a time within a fixed time budget.

Site-level issues

Broken internal links with the pages that link to them, internal redirects, canonicalized and noindex pages, and thin content.

Duplicate detection

Duplicate titles, meta descriptions and H1s, plus pairs of pages with near-duplicate main content.

Every page audited

Each crawled page gets the full on-page audit, with its score, depth, inlinks and failed checks.

Example request

GET /v1/site-audit?url=example.com&max_pages=25 bash
curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/site-audit?url=example.com&max_pages=25"

Example response

200 OK json
{
  "status": "ok",
  "summary": { "pages_crawled": 25, "pages_ok": 24, "pages_not_found": 1, "average_score": 88, "crawl_complete": false },
  "issues": {
    "broken_internal_links": [{ "url": "https://example.com/old-sale", "http_status": 404, "linked_from": ["https://example.com/"] }],
    "duplicate_meta_descriptions": [{ "value": "shop trail shoes", "urls": ["https://example.com/a", "https://example.com/b"] }],
    "thin_pages": [{ "url": "https://example.com/contact", "word_count": 74 }],
    "onpage_checks": [{ "check": "images_alt", "pages": 12 }]
  }
}

Frequently asked questions

How many pages can I crawl?

10, 25 or 50 pages per request. The response says how many discovered pages were not crawled, so you can see the coverage.

Does it follow robots.txt?

Yes. Pages disallowed for all crawlers are skipped. If robots.txt cannot be read, only the start page is audited.

Why are some links not checked?

Only crawled pages are checked. Links to pages beyond the page limit are counted as discovered but not crawled.

How many credits does it cost?

10 credits for 10 pages, 20 for 25 and 35 for 50. If the start page cannot be read, the request is refunded.

Related tools and resources

HTTP status codes

These are the HTTP status codes to handle, so you can tell apart successful responses, auth issues, credits, rate limits, missing data, and upstream failures.

OK 200

Request successful

Bad Request 400

Invalid parameters

Unauthorized 401

Missing or invalid API key/session.

Payment Required 402

Not enough credits to run this request.

Too Many Requests 429

Rate limit exceeded