Extract structured SEO tags, social cards, and schema from any URL.
SEO Data Scraper parses any public URL to collect title tags, meta descriptions, robots directives, and Open Graph or Twitter card previews. Paid plans add canonical URLs to verify indexing rules.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"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"
}
}
About the SEO Data Scraper API
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.
What people use it for
- 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.
Ways to call it
One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.
- JSON
- Default REST response
- XML
- Markup format
- YAML
- Human-readable
- CSV
- Tabular export
- GraphQL
- Query language
- MCP
- For AI agents
Other ways to use SEO Data Scraper
Same data, same APIVerve account, same credit balance — one key works on all of them.
Does it extract Open Graph tags and Twitter cards alongside standard meta tags?
Does it return JSON-LD structured data or heading tags?
Is the canonical URL included on the Free plan?
How far does the Starter plan go for page scrapes?
Does the scraper return live page data or cached snapshots?
Can I display scraped SEO data inside my own client-facing tool?
Request parameters — POST /v1/seoscraper
Sent as JSON in the request body. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
Required
| Parameter | Type | Example | Description |
|---|---|---|---|
urlRequired | string | https://apiverve.com | The URL of the web page to scrape SEO data from url |
curl -X POST "https://api.apiverve.com/v1/seoscraper" \
-H "x-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"url":"https://apiverve.com"}'Authentication
Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
content-typeRequired | POST body | application/json |
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.
Response — POST /v1/seoscraper
Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.
{
"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 g… | 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 g… | 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 |
Response headers
Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
What a call costs — 10 credits per call
Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.
| Plan | Per month | Credits | SEO Data Scraper calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 20 | Free |
| Starter | $29.99 | 200,000 | 20,000 | $1.50 |
| Pro | $99.99 | 1,000,000 | 100,000 | $1.00 |
| Mega | $299.99 | 4,000,000 | 400,000 | $0.75 |
Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.
Call it from cURL — POST /v1/seoscraper
No SDK to install — this is a plain HTTPS call to /v1/seoscraper with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/seoscraper" \
-H "x-api-key: YOUR_API_KEY"Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Node.js — POST /v1/seoscraper
Install the Node.js SDK, then call the SEO Data Scraper API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/seoscraperconst res = await fetch("https://api.apiverve.com/v1/seoscraper", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Python — POST /v1/seoscraper
Install the Python SDK, then call the SEO Data Scraper API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
pip install apiverve-seoscraperimport requests
res = requests.get(
"https://api.apiverve.com/v1/seoscraper",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from C# / .NET — POST /v1/seoscraper
Install the C# / .NET SDK, then call the SEO Data Scraper API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.SEODataScraperusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/seoscraper");
Console.WriteLine(json);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Go — POST /v1/seoscraper
No SDK to install — this is a plain HTTPS call to /v1/seoscraper with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/seoscraper", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from PHP — POST /v1/seoscraper
No SDK to install — this is a plain HTTPS call to /v1/seoscraper with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/seoscraper");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Ruby — POST /v1/seoscraper
No SDK to install — this is a plain HTTPS call to /v1/seoscraper with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/seoscraper")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyResources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Zero-code embed — one snippet, no backend
Drop an interactive SEO Data Scraper form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — SEO Data Scraper API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the SEO Data Scraper API.