Parse a sitemap (urlset/index)
API · /sitemap-api
Sitemap API
Fetch and parse an XML sitemap (the sitemaps.org protocol). Pass a sitemap URL and the parse endpoint fetches it — following redirects and transparently gunzipping .gz sitemaps — and returns its type: a urlset with every URL and its lastmod, changefreq and priority, or a sitemapindex listing the child sitemaps, with offset/limit paging for large files. The urls endpoint goes further: when the sitemap is an index it fetches the child sitemaps too and flattens every page URL into a single list, with a configurable cap on URLs and child sitemaps and a truncated flag so you stay in control. The request is made server-side and private or internal targets are refused (SSRF-guarded). Built for SEO audits, building crawl queues and content inventories, change monitoring and migration checks. A sitemap fetcher and parser — distinct from generic XML-to-JSON conversion (xml), the robots.txt evaluator (robots) and the on-page SEO audit (seo). No upstream key, no cache.
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 923 ms
- Server probes · 24h
- Subscribers
- 3,297
- active
- Total calls
- 0
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 1,980 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 1,980 calls/month
- 2 req/sec
- Parse + flatten
- No credit card
Starter
€5.85 /month
- 37,000 calls / month
- 8 requests / second
- Hard cap (429 above quota, no overage)
- 37k calls/month
- 8 req/sec
- Index recursion + gzip
- Email support
Pro
€19.60 /month
- 200,000 calls / month
- 20 requests / second
- Hard cap (429 above quota, no overage)
- 200k calls/month
- 20 req/sec
- Crawl-queue & SEO pipelines
- Priority support
Mega
€51.40 /month
- 780,000 calls / month
- 50 requests / second
- Hard cap (429 above quota, no overage)
- 780k calls/month
- 50 req/sec
- Crawl-platform scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
robots.txt API
Fetch and evaluate any website's robots.txt. Pass a URL and a user-agent and the check endpoint tells you whether that URL is crawlable — selecting the most-specific user-agent group and applying the RFC 9309 longest-match Allow/Disallow rules (with * and $ wildcards, where Allow wins ties), and returning the matched rule, the group's crawl-delay and the sitemaps the site declares. The parse endpoint returns the whole file structured into per-user-agent groups (their allow and disallow lists and crawl-delay) plus the list of sitemaps. A missing robots.txt (404/403) means everything is allowed, exactly as the spec requires. The request is made server-side and private or internal targets are refused (SSRF-guarded). Built for SEO audits, crawler and scraper compliance, sitemap discovery and pre-flight "am I allowed to fetch this?" checks. A robots.txt evaluator — distinct from the on-page SEO audit (seo), the XML toolkit (xml) and link unfurling/preview (url). No upstream key, no cache.
api.oanor.com/robots-api
Readability API
Score how easy a piece of text is to read using the standard, peer-reviewed readability formulas — Flesch Reading Ease, Flesch-Kincaid Grade, Gunning Fog, SMOG, Coleman-Liau and the Automated Readability Index. Pass text and get all six scores back together with the underlying counts (words, sentences, syllables, complex and polysyllabic words, letters and characters), an averaged grade level, an estimated reading time and a plain-English interpretation of the reading ease. A second endpoint counts syllables for a word or for every word in a phrase. Supply text inline via ?text=, as a query parameter or in a request body; everything is computed locally with no network calls, so it is fast and deterministic. Built for content and copywriting tools, SEO and editorial workflows, education and accessibility (plain-language) checks, and UX-writing review. A readability scorer — distinct from sentiment/NLP analysis (nlp), spelling and grammar checking (grammar), the case and text utilities (text) and string similarity (similarity). No upstream key, no cache.
api.oanor.com/readability-api
SEO API
Run an on-page SEO audit on any URL — title and meta-description analysis, heading structure, content length, image alt coverage, canonical / viewport / Open Graph checks and an internal/external link breakdown — with an overall 0–100 score. Plus a dedicated link analysis endpoint.
api.oanor.com/seo-api
XML API
A fast, fully-local XML toolkit: convert XML to JSON and JSON to XML with configurable attribute handling, validate XML well-formedness with line and column error details, and pretty-print XML while preserving element order. Every endpoint accepts input via the query string or the request body, up to 2 MB. Pure server-side compute, no third-party upstream, so responses are instant and always available. Ideal for system integrations, SOAP and legacy interop, RSS and sitemap processing, config tooling and data pipelines.
api.oanor.com/xml-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Sitemap API?
What's the rate limit for Sitemap API?
How much does Sitemap API cost?
Can I cancel my subscription anytime?
Is Sitemap API GDPR-compliant?
Pick an endpoint from the list on the left to see its details and try it.
Code snippets
Sign up to get an API key, then call any path under your slug.
curl https://api.oanor.com/sitemap-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/sitemap-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/sitemap-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
"https://api.oanor.com/sitemap-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())
Ratings
Sign in to rate.
No reviews yet.
Discussion
Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.
Sign in to start a thread or reply.
Sign inNew thread
·
-
Provider answer
🔒 This thread is locked — no new replies.
-
·
- No threads yet — start the discussion.
Support
Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.
Sign in to open a support ticket.
Sign inOpen new ticket
Describe what you need help with. The provider team gets an email and replies on the ticket page.
-
·
Urgent - No tickets yet for this API.