Enter a domain, URL, IP, email, or record and get a focused result without setup.
On-page SEO checker
Enter a page URL to audit its titles, meta tags, canonical, robots directives, headings, content, links, images and structured data, with 38 checks and a 0-100 score.
Run the check, then ship the workflow
Use the browser tool for a fast answer, then move the same logic into scripts, monitoring, or product flows when it becomes repeatable.
Outputs highlight statuses, risks, records, and next actions instead of raw provider noise.
Use the request and response examples to turn a one-off check into an API call or recipe.
Used by people at these companies
What this tool helps you decide
Each page is shaped around a practical operational question, not just a raw lookup.
See the current DNS, registration, security, pricing, or reputation evidence.
Compare the result with related checks so the next move is easier to trust.
Copy examples, open linked tools, or move into API documentation when you need scale.
Trust signals before you integrate
Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.
OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.
Authenticated endpoints use API keys with clear credit costs before you call them.
Start with 10,000 monthly credits and upgrade only when usage grows.
Start from the curl and HTTP samples, then map the parameters into your application code.
Key Features
Pass, warn and fail results with a severity for every check, from missing titles to mixed content.
Audit the page after JavaScript runs to see what modern crawlers see on single-page apps.
Title and description lengths, canonical, robots, language, viewport, Open Graph and Twitter cards in one view.
Example request
GET /v1/onpage?url=example.com
GET /v1/onpage?url=example.com/blog/post&render=true
Built on the same API
The browser experience previews DomScan's structured endpoints, so teams can validate a use case before writing code.
Frequently asked questions
Aim for 90 or more. Fix failed high-severity checks first, such as a missing title, a missing H1 or conflicting canonicals.
It is reported as a warning, because noindex is sometimes intentional. Check that only pages you want hidden carry it.
Use the API to audit pages one request at a time, for example the URLs from your XML sitemap.

