#seo

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

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

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

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

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.oanor.com/sitemap-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

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

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