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
- 1607 ms
- Server probes · 24h
- Subscribers
- 3,297
- active
- Total calls
- 60
- 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
Google Trends API
Live trending Google searches by country, with no key. This reads Google's own public Daily Search Trends RSS feed and returns it as clean JSON: what people are searching for right now in any country, each trend with its approximate search volume, the news stories driving it and a representative image. The trending endpoint lists the current trending searches for a country (term-centric, ranked, with volume and the top news story); the news endpoint flattens the news articles powering those trends (article-centric — the "what is driving search right now" view, each article tagged with its trend, source and link); and the geos endpoint lists the supported countries. The real-time search-interest / trends-discovery layer for news, marketing, SEO, social-listening and content tools. Distinct from wiki-pageview and platform-specific trend APIs — this is Google web-search trends. Live from Google Trends; short cache only.
api.oanor.com/googletrends-api
URL Canonicalize API
Normalize URLs to a canonical form so you can deduplicate, compare and clean them. The canonicalize endpoint lower-cases the scheme and host, drops the default port (80 for http, 443 for https), resolves ./ and ../ path segments and fixes percent-encoding using the standard WHATWG URL parser, then applies the cleanups you choose: strip marketing and analytics tracking parameters (all utm_* plus gclid, fbclid, msclkid, yclid, mc_eid and many more), sort the remaining query parameters into a stable order, optionally drop the #fragment, and add or remove the trailing slash. It returns the canonical URL, the fully parsed components and the exact list of changes it made. The compare endpoint canonicalizes two URLs and tells you whether they point to the same resource — perfect for catching duplicate links that differ only by tracking codes, casing, port or parameter order. Everything is computed locally with no network calls, so it is instant, private and safe. Ideal for crawlers and SEO tooling, link deduplication and analytics, cache keys, bookmarking and content pipelines. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This canonicalizes the URL string; it does not fetch it or follow redirects — for link previews and unshortening use a URL-unfurl API.
api.oanor.com/urlcanon-api
JSON-LD API
Generate valid schema.org JSON-LD structured data from simple fields — the markup Google and other search engines use for rich results. The generate endpoint builds ready-to-embed JSON-LD for the types that matter most for SEO: Article (and BlogPosting / NewsArticle) with author and publisher, Product with offers, price, availability and an aggregate rating, Organization and LocalBusiness with postal address and opening hours, Person, WebSite with a Sitelinks search box (SearchAction), BreadcrumbList, FAQPage, Event and Recipe with ingredients and step-by-step instructions. Pass plain fields — or JSON arrays and newline lists for breadcrumbs, FAQ questions, ingredients and social profiles — and get back a clean JSON-LD object, optionally wrapped in a ready-to-paste <script type="application/ld+json"> tag. The types endpoint documents every supported type and its fields. Everything is assembled locally and deterministically, so it is instant and private. Ideal for CMS and static-site pipelines, SEO tooling, e-commerce product pages, documentation and content platforms. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This GENERATES schema.org markup; to extract structured data or Open Graph tags from a page use an HTML-parsing API, and to audit on-page SEO use an SEO API.
api.oanor.com/jsonld-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.