REST API & Webhooks
AI Visibility (GEO) API
The GEO score endpoints are not available. HubSEO has no GEO measurement pipeline, so they return 501.
HubSEO does not measure how generative search engines quote or cite a domain. The GEO endpoints exist so clients get an explicit answer instead of invented numbers: they always return 501 Not Implemented with no score.
Get Domain GEO Score
GET /api/v1/domains/{domain}/geo-score
GET /api/v1/geo/score?domain={domain}Headers
Authorization: Bearer hub_live_YOUR_API_KEYParameters
| Parameter | In | Type | Required | Description |
|---|---|---|---|---|
domain | path or query | string | Yes | Bare hostname (e.g. example.com). |
Response (501 Not Implemented)
{
"data": null,
"evidence": [],
"methodology_version": "geo-evidence-v1",
"measured_at": null,
"confidence": null,
"status": "unmeasured",
"error": {
"code": "evidence_not_available",
"message": "Verified evidence is not available for geo score."
}
}The response carries X-HubSEO-Data-Status: unmeasured. A missing or invalid domain returns 400.
For what HubSEO does measure about AI search readiness (robots.txt crawler access, llms.txt, structured data), run an audit at /seo-audit.