Validate an hreflang cluster API
Check BCP 47 codes against the IANA subtag registry and reciprocal return tags across caller-supplied page alternates.
The Validate an hreflang cluster operation is part of the Technical SEO Audits Robots Sitemap Hreflang API on BRAINIAC.software. Check BCP 47 codes against the IANA subtag registry and reciprocal return tags across caller-supplied page alternates. It is exposed as POST /api/v1/seo-technical/hreflang-validate and priced at $0.03 USDC on Base. Payment uses the x402 exact scheme: an unpaid call returns HTTP 402 with payment requirements; after paying the exact USDC amount, retry the same request with a payment-signature header and Idempotency-Key. No account and no API key are required. Data sources for this product: Caller-supplied robots.txt, sitemaps, crawl exports, logs, backlinks and Search Console rows processed locally IANA Language Subtag Registry (public domain) vendored in src/data/seo-technical/ schema.org vocabulary subset (CC BY-SA 3.0) vendored in src/data/seo-technical/ Googlebot IP ranges (CC BY 4.0) vendored as googlebot.json web.dev Core Web Vitals thresholds (CC BY 4.0) Limitations: Pure computation on caller input: no request-time crawl or third-party SEO API is called. Outputs are lookups or prechecks for human review. They are not legal, customs, tax, medical, or identity determinations. schema-org-validate uses a Product/Offer vocabulary subset from vendored schema.org data. Bing crawler IP ranges are not bundled. Outputs are compliance prechecks, drafts, or data lookups for human review. They are not official determinations, legal advice, identity confirmation, or certified filings. Related operations in this group include Test URLs against robots.txt, Validate a sitemap or sitemap index, Audit canonical tags in a crawl export, Analyse redirect chains and loops. Open the group documentation for the full request schema, field notes, and response examples before integrating.
/api/v1/seo-technical/hreflang-validateExample request
curl -i -X POST "https://www.brainiac.software/api/v1/seo-technical/hreflang-validate" \
-H 'content-type: application/json' \
-H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
--data-binary @- <<'JSON'
{
"pages": [
{
"url": "https://ex.com/en/",
"canonical": "https://ex.com/en/",
"alternates": [
{
"hreflang": "en",
"href": "https://ex.com/en/"
},
{
"hreflang": "de-DE",
"href": "https://ex.com/de/"
},
{
"hreflang": "x-default",
"href": "https://ex.com/"
}
]
},
{
"url": "https://ex.com/de/",
"canonical": "https://ex.com/de/",
"alternates": [
{
"hreflang": "de-DE",
"href": "https://ex.com/de/"
},
{
"hreflang": "en",
"href": "https://ex.com/en/"
},
{
"hreflang": "x-default",
"href": "https://ex.com/"
}
]
},
{
"url": "https://ex.com/",
"canonical": "https://ex.com/",
"alternates": [
{
"hreflang": "x-default",
"href": "https://ex.com/"
},
{
"hreflang": "en",
"href": "https://ex.com/en/"
},
{
"hreflang": "de-DE",
"href": "https://ex.com/de/"
}
]
}
]
}
JSONAn unpaid probe returns HTTP 402 with x402 payment requirements. After paying the exact USDC amount on Base, retry the identical request with a payment-signature header.
FAQ
- Do I need an API key? No. Pay the listed USDC amount with x402.
- What network? Base (eip155:8453), USDC.
- Is this an official determination? No. Results are for human review against the cited sources.
Related operations
- Test URLs against robots.txt — $0.02 USDC
- Validate a sitemap or sitemap index — $0.03 USDC
- Audit canonical tags in a crawl export — $0.03 USDC
- Analyse redirect chains and loops — $0.02 USDC
Related APIs
Technical SEO Audits Robots Sitemap Hreflang APIFull docsHow it works