{
"requestId": "46cd4f3d-38c3-4840-8ee5-820a4c0efd53",
"result": {
"inputUrl": "https://example.com/",
"normalizedUrl": "https://example.com/",
"finalUrl": "https://example.com/",
"httpStatus": 200,
"contentType": "text/html",
"redirectCount": 0,
"responseBytes": 559,
"seo": {
"score": 68,
"grade": "D",
"severityCounts": {
"critical": 0,
"error": 1,
"warning": 8,
"info": 0
},
"snapshot": {
"title": "Example Domain",
"titleLength": 14,
"description": null,
"descriptionLength": 0,
"canonical": null,
"robots": null,
"lang": "en",
"viewportMeta": true,
"h1Count": 1,
"headingOrderSkips": 0,
"wordCount": 21,
"imageCount": 0,
"imagesMissingAlt": 0,
"jsonLdBlocks": 0,
"jsonLdInvalid": 0,
"openGraphTags": 0
},
"issues": [
{
"id": "canonical-missing",
"category": "indexability",
"severity": "warning",
"message": "No canonical URL was found.",
"evidence": null,
"recommendation": "Add an absolute canonical URL for the preferred page."
},
{
"id": "title-length",
"category": "metadata",
"severity": "warning",
"message": "The title length is outside the usual descriptive range.",
"evidence": 14,
"recommendation": "Use a concise title of roughly 15 to 65 characters."
},
{
"id": "description-missing",
"category": "metadata",
"severity": "error",
"message": "The meta description is missing.",
"evidence": null,
"recommendation": "Add a useful page summary."
},
{
"id": "thin-static-copy",
"category": "content",
"severity": "warning",
"message": "The returned HTML contains little text.",
"evidence": 21,
"recommendation": "Confirm the page provides enough useful crawlable content."
},
{
"id": "open-graph-incomplete",
"category": "metadata",
"severity": "warning",
"message": "Core Open Graph metadata appears incomplete.",
"evidence": 0,
"recommendation": "Add intentional Open Graph title, description, type, and URL values where sharing matters."
},
{
"id": "hsts-missing",
"category": "security",
"severity": "warning",
"message": "Strict-Transport-Security was not observed.",
"evidence": false,
"recommendation": "Consider HSTS after confirming HTTPS coverage."
},
{
"id": "csp-missing",
"category": "security",
"severity": "warning",
"message": "Content-Security-Policy was not observed.",
"evidence": false,
"recommendation": "Add a tested CSP appropriate to the application."
},
{
"id": "frame-protection-missing",
"category": "security",
"severity": "warning",
"message": "No framing protection was observed.",
"evidence": false,
"recommendation": "Define an intentional framing policy."
},
{
"id": "nosniff-missing",
"category": "security",
"severity": "warning",
"message": "X-Content-Type-Options: nosniff was not observed.",
"evidence": false,
"recommendation": "Add the nosniff response header."
}
]
},
"technologies": [
{
"name": "Cloudflare",
"category": "cdn",
"evidence": [
"header:server",
"header:cf-ray"
]
}
],
"technologyNames": [
"Cloudflare"
],
"technologyCategories": [
"cdn"
],
"securityHeaders": {
"strictTransportSecurity": false,
"contentSecurityPolicy": false,
"clickjackingProtection": false,
"contentTypeOptions": false,
"referrerPolicy": false,
"permissionsPolicy": false,
"crossOriginOpenerPolicy": false,
"crossOriginResourcePolicy": false,
"presentCount": 0,
"assessedCount": 8,
"missing": [
"strict-transport-security",
"content-security-policy",
"clickjacking-protection",
"x-content-type-options",
"referrer-policy",
"permissions-policy",
"cross-origin-opener-policy",
"cross-origin-resource-policy"
]
},
"evidenceBoundary": "Detections are evidence-based fingerprints from the fetched public response, not a guarantee of the complete server-side stack or technology version. Static HTML evidence is not browser-rendered content, a Lighthouse score, Google Search ranking data, a penetration test, or a guarantee of indexing or ranking."
}
}
curl --location --request POST 'https://zylalabs.com/api/13595/website+seo+audit+api/30325/audit+a+public+web+page' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{"url":"https://example.com/","options":{"timeoutMs":10000,"maxResponseBytes":500000,"maxRedirects":3}}'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Website SEO Audit API simply include your bearer token in the Authorization header.
| Header | Description |
|---|---|
Authorization
|
Required
Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.
|
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
(Save 2 months with annual billing 🎉)
Audit one public page for static SEO signals, 65+ technology fingerprints, and eight security headers with bounded redirects, response size, and private-network blocking.
The API returns data related to static SEO signals, technology fingerprints, and security headers. This includes the HTTP status, content type, redirect count, response size, and a detailed SEO score with severity counts for issues found.
Key fields in the response include `inputUrl`, `httpStatus`, `seo.score`, `seo.grade`, and `seo.severityCounts`. These provide insights into the page's SEO performance and any issues detected during the audit.
The response data is structured in a JSON format, with a top-level object containing `requestId` and `result`. The `result` object includes details about the URL, HTTP status, response size, and a nested `seo` object with specific SEO findings.
The API provides information on SEO performance, technology used on the page, and security headers. It includes metrics like SEO score, redirect counts, and specific issues categorized by severity (critical, error, warning, info).
The primary parameter for the endpoint is the `inputUrl`, which specifies the public web page to be audited. Users can customize their requests by providing different URLs to analyze various pages.
Data accuracy is maintained through deterministic analysis of the HTML content without browser rendering. The API uses established algorithms to evaluate SEO signals and technology fingerprints, ensuring reliable results.
Typical use cases include website audits for SEO optimization, technology stack identification, and security assessments. Webmasters and SEO professionals can use the data to improve site performance and compliance with best practices.
Users can analyze the SEO score and severity counts to prioritize fixes. The detailed findings, such as missing meta tags or security headers, guide users in enhancing their web pages for better search engine visibility and security.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund