Overview
SEO Scraper works by parsing the HTML content of a web page to extract the SEO data. It returns the meta title, meta description, and more in a structured format.
Live Test SEO Data Scraper API →
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/seoscraper \
-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/seoscraper', {
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/seoscraper",
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/seoscraper", 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 scrape SEO data from 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",
"title": "APIVerve — One key for 300+ production APIs",
"description": "Consistent schemas, predictable credit pricing, and an uptime SLA on every paid plan across 300+ production APIs. One key, one bill, zero glue code.",
"keywords": "",
"author": "",
"canonical": "",
"og:title": "APIVerve — One key for 300+ production APIs",
"og:description": "Consistent schemas, predictable credit pricing, and an uptime SLA on every paid plan across 300+ production APIs. One key, one bill, zero glue code.",
"og:image": "https://apiverve.com/social-images/page-home.png",
"og:url": "https://apiverve.com",
"og:type": "website",
"og:site_name": "APIVerve",
"twitter:card": "summary_large_image",
"twitter:title": "APIVerve — One key for 300+ production APIs",
"twitter:description": "Consistent schemas, predictable credit pricing, and an uptime SLA on every paid plan across 300+ production APIs.",
"twitter:image": "https://apiverve.com/social-images/page-home.png",
"twitter:site": "",
"robots": "",
"viewport": "width=device-width, initial-scale=1, maximum-scale=1",
"charset": "utf-8"
}
}
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 URL that was scraped |
title | string | "APIVerve — One key for 300+ production APIs" | Page title tag content for SEO optimization |
description | string | "Consistent schemas, predictable credit pricing, and an uptime SLA on every paid plan across 300+ production APIs. One key, one bill, zero glue code." | Meta description tag for search engine snippets |
keywords | string | "" | Meta keywords tag for SEO targeting |
author | string | "" | Author meta tag content for attribution |
canonicalPremium | string | "" | Canonical URL specified in page meta tags |
og:title | string | "APIVerve — One key for 300+ production APIs" | Open Graph title for social media preview |
og:description | string | "Consistent schemas, predictable credit pricing, and an uptime SLA on every paid plan across 300+ production APIs. One key, one bill, zero glue code." | Open Graph description for social sharing |
og:image | string | "https://apiverve.com/social-images/page-home.png" | Open Graph image URL for social previews |
og:url | string | "https://apiverve.com" | Open Graph canonical URL for social sharing |
og:type | string | "website" | Open Graph content type like website or article |
og:site_name | string | "APIVerve" | Open Graph site name for consistency |
twitter:card | string | "summary_large_image" | Twitter card type like summary_large_image |
twitter:title | string | "APIVerve — One key for 300+ production APIs" | Twitter card title for social preview |
twitter:description | string | "Consistent schemas, predictable credit pricing, and an uptime SLA on every paid plan across 300+ production APIs." | Twitter card description for social sharing |
twitter:image | string | "https://apiverve.com/social-images/page-home.png" | Twitter card image URL for social media |
twitter:site | string | "" | Twitter account handle for attribution |
robots | string | "" | Robots meta tag directives for search indexing |
viewport | string | "width=device-width, initial-scale=1, maximum-scale=1" | Viewport meta tag for mobile responsive design |
charset | string | "utf-8" | Character encoding declared in page metadata |
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. |
Use cases
- Link Preview Generation
- Chat applications fetch page titles, descriptions, and Open Graph image URLs to display rich snippet cards when users paste web links.
- Search Snippet Auditing
- Content marketing platforms read title tags and meta descriptions across blog posts to flag missing or truncated text before publishing.
- Competitor Tag Tracking
- Monitor competing landing pages by inspecting robots directives, meta keywords, and Twitter card types to catch changes in their promotion strategies.
- Indexing Rule Verification
- When auditing website migrations, technical consultants verify robots directives and page titles to confirm search bots can crawl target pages correctly.
Other ways to use SEO Data Scraper
Set up SEO Data Scraper 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 Scraping: