On-page analysis  /  API %

SEO Audit

Titles, meta, headings, images, links, structured data, hreflang, readability and a weighted 0-100 score with per-check status. Parsed at the edge with HTMLRewriter, so a full audit costs pennies and returns in under a second.

checking 8 endpoints Cloudflare edge
seo-audit · live
$ curl -s "https://seo-audit.ayamk.in/v1/meta?url=https%3A%2F%2Fexample.com" | jq
{
  "url": "https://example.com",
  "finalUrl": "https://example.com/",
  "title": "Example Domain",
  "titleLength": 14,
  "metaDescription": null,
  "canonical": null,
  "robots": { "index": true, "follow": true, "raw": null },
  "lang": "en",
  ...
01 - ENDPOINTS

8 endpoints, one key

Every route below is described in the OpenAPI document. Import it into Postman or generate a client.

MethodPathWhat it does
GET/v1/auditFull on-page audit plus a weighted score breakdown.
GET/v1/metaTitle, description, canonical, robots, Open Graph, Twitter, JSON-LD.
GET/v1/linksInternal vs external links, anchor texts, rel attributes.
GET/v1/keywordsTerm frequency, TF-IDF ranking and density for a page or raw text.
GET/v1/readabilityFlesch, Flesch-Kincaid, Gunning fog, sentence stats.
GET/v1/robotsParsed robots.txt groups, rules, crawl-delay, sitemaps.
GET/v1/sitemapSitemap index or urlset, parsed and counted.
POST/v1/textReadability plus keyword analysis on raw text.
02 - RESPONSE

What you actually get back

curl
curl -s "https://seo-audit.ayamk.in/v1/meta?url=https%3A%2F%2Fexample.com" | jq
200 application/json
{
  "url": "https://example.com",
  "finalUrl": "https://example.com/",
  "title": "Example Domain",
  "titleLength": 14,
  "metaDescription": null,
  "canonical": null,
  "robots": { "index": true, "follow": true, "raw": null },
  "lang": "en",
  "openGraph": { "title": null, "description": null, "image": null },
  "twitterCard": { "card": null, "title": null },
  "jsonLd": [],
  "hreflang": [],
  "favicon": null,
  "durationMs": 143
}
Limit worth knowing. Audits the HTML of a single public page. It does not crawl a whole site, render JavaScript, or measure Core Web Vitals.
03 - WHY

Built for the boring part

No headless browser bill

HTMLRewriter parses the document as a stream. You get structured findings in one pass instead of paying for a Chrome instance per page.

Checks you can act on

Every check returns pass, warn or fail with its weight and a message. Change one field, watch the score move by a known amount.

SSRF safe by default

Every fetch is resolved first and rejected if it points at a private address, on every redirect hop. Safe to expose behind a public form.

04 - PRICING

Priced per request, not per seat

Basic
$0
25 requests / month
Card required by the marketplace. Enough to ship an integration.
Ultra
$75/mo
100,000 requests
Batch jobs and backfills.
Mega
$150/mo
400,000 requests
For platform-scale volume. Overage billed per request.

All plans are managed by the RapidAPI marketplace, which applies a marketplace fee before payout. Annual and custom limits are available on request.

05 - USE CASES

Where this earns its place

01

Client reporting in an SEO tool

02

Content QA before publishing

03

Competitor snapshots

04

Migration checks

06 - FAQ

Questions we get asked

Will it work on JavaScript-heavy sites?

You get the server-rendered HTML. Single-page apps that render entirely in the browser will look thin. That is a real signal too, but treat the numbers accordingly.

Can I audit a local or intranet URL?

No. Private ranges, localhost and metadata endpoints are blocked twice: on hostname pattern and on DNS resolution of every redirect hop. That is deliberate.

How is the score calculated?

Each check carries a fixed weight and returns pass, warn or fail. The score is the weighted sum normalised to 0-100, and the full breakdown is in the response so you can explain it to a client.

Do you cache pages?

No page bodies are stored. DNS answers are cached for 10 minutes at the edge.

Subscribe to SEO Audit

Free tier included. The listing is published on the RapidAPI marketplace; the key works against every endpoint on this page.