Is a URL crawlable?
API · /robots-api
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 salute
salutare- Tempo di attività
- 100.00%
- Sondaggi del server · 24 ore su 24
- Latenza media
- 125 ms
- Sondaggi del server · 24 ore su 24
- Abbonati
- 4,091
- attiva
- Chiamate totali
- 57
- ultimi 7 giorni
Prezzi
Scegli un livello: fatturazione mensile, annullamento in qualsiasi momento.
Free
Gratis
- 2,000 chiamate/mese
- 2 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 2,000 llamadas/mes
- 2 req/seg
- Capacidad de rastreo y análisis
- Sin tarjeta de crédito
Starter
€5.90 /mese
- 37,500 chiamate/mese
- 8 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 37.5k calls/month
- 8 req/sec
- RFC 9309 match + sitemaps
- Email support
Pro
€19.70 /mese
- 202,000 chiamate/mese
- 20 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 202k calls/month
- 20 req/sec
- Crawler & SEO pipelines
- Priority support
Mega
€51.60 /mese
- 785,000 chiamate/mese
- 50 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 785k calls/month
- 50 req/sec
- Crawl-platform scale
- Dedicated SLA
Costruito da
Correlato APIs
Altro APIs con tag sovrapposti.
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
Title Case API
Convert a heading to proper headline (title) case the way editors do — not a naive capitalise-every-word. It capitalises the first and last words and all the major words, while keeping articles (a, an, the), coordinating conjunctions (and, but, or…) and prepositions lowercase, and always capitalises the word right after a colon. Choose AP style (lowercases short prepositions, capitalises longer ones) or Chicago style (lowercases prepositions of any length). Hyphenated compounds such as well-known and state-of-the-art are handled correctly. Perfect for article and blog titles, headings, SEO meta titles, product and section names, and CMS tooling. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. Distinct from a plain title/sentence case converter, which capitalises every word.
api.oanor.com/titlecase-api
Domande frequenti
Risposte rapide su prezzi, quote e integrazione.
Come ottengo una chiave API per robots.txt API?
Qual è il limite di velocità di robots.txt API?
Quanto costa robots.txt API?
Posso cancellare l'abbonamento in qualsiasi momento?
robots.txt API è conforme al GDPR?
Scegli un endpoint dall'elenco a sinistra per visualizzarne i dettagli e provarlo.
Frammenti di codice
Iscriviti per ottenere una chiave API, quindi chiama qualsiasi percorso sotto il tuo slug.
curl https://api.oanor.com/robots-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/robots-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/robots-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/robots-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())
Valutazioni
Accedi per votare.
Nessuna recensione ancora.
Discussione
Fai domande, condividi consigli, ricevi risposte dal provider e dagli altri sviluppatori. Pubblico — chiunque può leggere.
Accedi per scrivere o rispondere.
AccediNuova discussione
·
-
Risposta del provider
🔒 Discussione bloccata — non si può più rispondere.
-
·
- Nessuna discussione — inizia tu.
Supporto
Supporto privato 1:1 con il provider — fatturazione, integrazione, account. Solo tu e il team del provider vedete questi thread.
Accedi per aprire un ticket di supporto.
AccediApri nuovo ticket
Descrivi cosa ti serve. Il team del provider riceve un'email e risponde sulla pagina del ticket.
-
·
Urgente - Nessun ticket per questa API.