Web Data

Duplicate content checker API

Compare 2 to 10 pages in one request. Get a similarity score for every pair of pages based on their main content, groups of near duplicates, and repeated titles, meta descriptions and H1s.

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

urls
Response fields

Example response

statuspairsclustersduplicatesduplicates.titlesduplicates.meta_descriptionsduplicates.h1
Status coverage

HTTP status codes

200400401402429

Endpoints

GET /v1/duplicate-content
Credits: 5Authentication: 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

Main content only

Headers, navigation, footers, sidebars and forms are removed before comparing, so shared templates do not inflate the score.

Similarity and containment

Similarity measures overlap between two pages; containment shows how much of the shorter page appears in the longer one.

Canonical aware

Pairs where one page already declares the other as canonical are flagged, so you can focus on unresolved duplicates.

Metadata duplicates

Repeated titles, meta descriptions and H1s are grouped with the URLs that share them.

Example request

GET /v1/duplicate-content?urls=example.com/a,example.com/b,example.com/c bash
curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/duplicate-content?urls=example.com/a,example.com/b,example.com/c"

Example response

200 OK json
{
  "status": "ok",
  "pairs": [
    { "a": "https://example.com/a", "b": "https://example.com/b", "similarity": 0.91, "containment": 0.96, "near_duplicate": true, "canonicalized": false }
  ],
  "clusters": [["https://example.com/a", "https://example.com/b"]],
  "duplicates": {
    "titles": [{ "value": "trail running shoes", "urls": ["https://example.com/a", "https://example.com/b"] }],
    "meta_descriptions": [],
    "h1": []
  }
}

Frequently asked questions

When are two pages near duplicates?

When their similarity is 0.8 or higher. Pages above that level usually compete with each other in search.

How is similarity calculated?

Each page's main text is split into overlapping five-word sequences, and the score is the share of sequences the two pages have in common.

What if a page cannot be read?

It is listed with its reason and left out of every comparison. If fewer than two pages can be read, the result is unknown and refunded.

How many credits does it cost?

Five credits per request for up to 10 URLs.

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