Audit Seo
by HubVibe in Security & trust
SEO audit of a web page (on-page SEO check) for any live URL or raw HTML: title tag, meta description, H1 heading structure, canonical link, OpenGraph and social tags, JSON-LD structured data, html lang attribute. Rule-by-rule findings with severity and what is missing or malformed.
POST https://hubvibe-io.com/audit/seo
Last 30 days
Status and outage history · Atom feed
- Uptime
- 100%
- Response time
- 357 ms typical, 539 ms slowest 5%
- Last check
- 59 min ago
- Next check
- any minute now
How to call it
POST https://hubvibe-io.com/audit/seo
Each call costs $0.05 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
POST https://hubvibe-io.com/audit/seo
content-type: application/json
{
"url": "https://example.com"
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
html | string | No | Raw HTML source to audit instead of fetching a URL. |
language | string | No | Optional BCP-47 language tag (en, ja, ko, pt-BR): the human-readable text of the findings is returned in this language; rule ids, severities, URLs and numbers are untouched. Default: English. |
url | string (uri) | No | Live, fetchable http(s) URL to audit. |
Example response
The provider's example. We can't check it without paying.
{
"findings": [
{
"detail": "No meta description found",
"id": "missing-meta-description",
"severity": "critical"
},
{
"detail": "No canonical link found",
"id": "missing-canonical",
"severity": "minor"
}
],
"pass": false,
"status": "ok"
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.05.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://hubvibe-io.com/audit/seo' \
-H 'content-type: application/json' \
--data-raw '{"url":"https://example.com"}'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://hubvibe-io.com/audit/seo' \
-H 'content-type: application/json' \
--data-raw '{"url":"https://example.com"}' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.05 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.05" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.05 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fhubvibe-io.com%2Faudit%2Fseo&method=POST
const res = await pay("https://hubvibe-io.com/audit/seo", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"url": "https://example.com"
}),
});
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.05 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.05"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.post(
"https://hubvibe-io.com/audit/seo",
json={
"url": "https://example.com",
},
)
print(res.status_code, res.text)Security scan
- No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 59 min ago | Passed | 402 | 373 ms | $0.05 |
| 5 h ago | Passed | 402 | 370 ms | $0.05 |
| 9 h ago | Passed | 402 | 539 ms | $0.05 |
| 13 h ago | Passed | 402 | 409 ms | $0.05 |
| 17 h ago | Passed | 402 | 357 ms | $0.05 |
| 21 h ago | Passed | 402 | 451 ms | $0.05 |
| 24 h ago | Passed | 402 | 357 ms | $0.05 |
| 28 h ago | Passed | 402 | 117 ms | $0.05 |
| 31 h ago | Passed | 402 | 446 ms | $0.05 |
| 35 h ago | Passed | 402 | 288 ms | $0.05 |
| 38 h ago | Passed | 402 | 116 ms | $0.05 |
| 42 h ago | Passed | 402 | 117 ms | $0.05 |
| 46 h ago | Passed | 402 | 395 ms | $0.05 |
| 2 days ago | Passed | 402 | 431 ms | $0.05 |
| 2 days ago | Passed | 402 | 351 ms | $0.05 |