Release gates
Catch missing or changed SEO fields before a production release is treated as complete.
Evidence-led page checks
On-Page SEO Audit API
Turn repeatable page checks into structured evidence for release gates, monitoring, and content QA. The weighted score summarizes only the supported checks, while every result retains its own pass state, severity, observed evidence, and recommended action.
Endpoint
POST /v1/seo-auditA working request
Set your key once in a server-side environment variable, then send a JSON request.
cURL
curl --request POST \
--url "https://api.tooltrace.io/v1/seo-audit" \
--header "X-ToolTrace-Key: ${TOOLTRACE_KEY}" \
--header "Content-Type: application/json" \
--data '{
"url": "https://example.com"
}'Response scope
What the API returns
The response is structured for software, with source evidence kept beside the extracted or inspected data.
- Page and fetch evidence
- Metadata and canonical signals
- Technical SEO findings
- Structured issue details
- Warnings and actionable context
Practical uses
Template monitoring
Check representative pages after CMS, theme, or rendering changes.
Content operations
Give editors clear technical findings alongside content review workflows.
Implementation guidance
Use the result with context.
Technical health is one part of search performance
A clean audit does not guarantee rankings. Search visibility also depends on relevance, usefulness, reputation, links, competition, and search demand.
Use findings to remove technical obstacles, then evaluate the page as a real answer for its intended audience.
Test representative page types
A homepage result does not prove product, article, category, and account templates are healthy. Keep a small, stable set of URLs that represents each public template.
Authentication, limits, and errors
Send your key through the X-ToolTrace-Key header from server-side code. Read credit and rate-limit headers after every request. Validation, blocked destination, authentication, plan, and upstream fetch errors use structured responses that applications should handle by code rather than message text.
Use a dedicated key for each environment. Review current fields in the interactive API reference and compare usage limits on the pricing page.