Overview
SEO Validator works by fetching and parsing a web page, then evaluating its on-page SEO signals — title, meta description, H1 structure, canonical link, mobile viewport, image alt text and external-link rel attributes. It returns each check as a structured field, a list of issues to fix, and a weighted 0-100 score with an A–F grade so you can gauge a page's SEO health at a glance.
Endpoint
One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.
curl -X POST https://api.apiverve.com/v1/seovalidator \
-H "x-api-key: your_api_key_here" \
-H "Content-Type: application/json" \
-d '{
"url": "https://apiverve.com"
}'const res = await fetch('https://api.apiverve.com/v1/seovalidator', {
method: 'POST',
headers: {
'x-api-key': 'your_api_key_here',
'Content-Type': 'application/json',
},
body: JSON.stringify({
"url": "https://apiverve.com"
}),
});
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const { data } = await res.json();
console.log(data);import requests
res = requests.post(
"https://api.apiverve.com/v1/seovalidator",
headers={"x-api-key": "your_api_key_here"},
json={
"url": "https://apiverve.com"
},
timeout=15,
)
res.raise_for_status()
print(res.json()["data"])package main
import (
"fmt"
"io"
"net/http"
"strings"
)
func main() {
body := strings.NewReader(`{
"url": "https://apiverve.com"
}`)
req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/seovalidator", body)
req.Header.Set("Content-Type", "application/json")
req.Header.Set("x-api-key", "your_api_key_here")
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
out, _ := io.ReadAll(res.Body)
fmt.Println(string(out))
}Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.
Authentication
Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Parameters
Sent as JSON in the request body. Premium parameters are accepted on every plan but only take effect on plans that include them.
| Parameter | Type | Description |
|---|---|---|
urlRequired | string | The URL of the web page to validate the SEO metrics of url |
Response
Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.
{
"status": "ok",
"error": null,
"data": {
"url": "https://apiverve.com",
"passed": false,
"issueCount": 6,
"issues": [
"Image missing 'alt' attribute: '/assets/img/hero-diagram.png'",
"Image missing 'alt' attribute: '/assets/img/logo-mark.svg'",
"External link missing 'rel' attribute: 'https://twitter.com/apiverve'",
"External link missing 'rel' attribute: 'https://github.com/apiverve'",
"External link missing 'rel' attribute: 'https://status.apiverve.com'",
"Missing meta 'keywords' tag in head"
],
"checks": {
"hasTitle": true,
"titleLength": 54,
"hasMetaDescription": true,
"metaDescriptionLength": 158,
"hasMetaKeywords": false,
"h1Count": 1,
"hasCanonical": true,
"hasViewport": true,
"imagesTotal": 8,
"imagesMissingAlt": 2,
"externalLinksTotal": 10,
"externalLinksMissingRel": 3
},
"seoScore": 93,
"grade": "A"
}
}Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
url | string | "https://apiverve.com" | The validated URL that was analyzed for SEO issues |
passed | boolean | false | Whether the URL passed all SEO validation checks |
issueCount | number | 6 | Total number of SEO issues found on the page |
issues | array | [Image missing 'alt' attribute: '/assets/img/hero-diagram.png', ...] | Array of SEO issues found (missing alt tags, missing meta tags, multiple H1s, etc.) |
checks | object | {...} | Structured per-rule breakdown of the on-page SEO signals behind the issue list, exposed as booleans, counts and lengths |
hasTitle | boolean | true | Whether the page has a non-empty <title> tag in the head |
titleLength | number | 54 | Character length of the title (null when absent); ~50-60 characters is the common recommendation |
hasMetaDescription | boolean | true | Whether the page has a meta description tag |
metaDescriptionLength | number | 158 | Character length of the meta description (null when absent); ~150-160 characters is the common recommendation |
hasMetaKeywords | boolean | false | Whether a meta keywords tag is present (largely deprecated for ranking) |
h1Count | number | 1 | Number of H1 tags on the page; exactly one is recommended |
hasCanonical | boolean | true | Whether the page declares a canonical link tag |
hasViewport | boolean | true | Whether the page declares a mobile viewport meta tag |
imagesTotal | number | 8 | Total number of <img> elements on the page |
imagesMissingAlt | number | 2 | Number of images missing an alt attribute |
externalLinksTotal | number | 10 | Total number of external (http/https) links on the page |
externalLinksMissingRel | number | 3 | Number of external links missing a rel attribute |
seoScorePremium | number | 93 | Composite 0-100 on-page SEO health score, weighted by real ranking impact (title, meta description and H1 weigh most; image-alt and link-rel penalties scale with the proportion of elements affected). Higher is better |
gradePremium | string | "A" | Letter grade derived from the score: A (90+), B (80+), C (70+), D (60+) or F |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted | A key restriction or IP allow-list; see key scoping. |
429 | Rate limited, or out of credits | Read error to tell them apart; see rate limits. |
Other ways to use SEO Quick Validator
Set up SEO Quick Validator on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.
Related
More in Data Validation: