Serverless AI SEO Content Generation
AI powered SEO content generation service that creates optimized SEO content including meta titles, descriptions, and keywords based on the provided context.
Endpoint
Generate SEO-optimized content based on context
POSThttps://api.xtartapp.com/data/seo
*Authentication
You must use a Bearer token provided by the dashboard to use for authentication. Add the token to the Authorization header.
Request body
Name | Type | Required | Max | Description |
---|---|---|---|---|
context | string | Yes | 2500 | The context to generate SEO content from |
language | string | Yes | - | The language to generate the SEO content in. Supported languages: auto, en, es, fr, de, zh, ja, ko, pt, it, ru, ar, hi |
brand | string | No | 100 | Optional brand name to incorporate into the SEO content |
industry | string | No | 100 | Optional industry context to help optimize the SEO content |
Response
Name | Type | Description |
---|---|---|
data | object | The data of the SEO content generation |
data.title | string | SEO-optimized meta title (50-60 characters) |
data.description | string | Compelling meta description (150-160 characters) |
data.headings | array | Suggested heading structure with levels and text |
data.keywords | object | Target keywords for optimization, split into primary and secondary |
data.urlSlug | string | SEO-friendly URL slug suggestion |
data.contentOutline | array | Outline of key points to cover in the content |
data.language | string | The language code used for content generation |
metadata | object | Metadata about the SEO content generation process |
metadata.cost | number | The cost of the SEO content generation request ($0.001 per request) |
Errors
{
"error": "string",
"code": "string"
}
HTTP Status | Error Code | Message |
---|---|---|
400 | INVALID_PAYLOAD | Occurs when the payload is invalid. |
400 | INVALID_REQUEST | Ex.: The request is invalid. |
400 | SEO_GENERATION_ERROR | Ex: could not generate SEO content | parsing error |
400 | HARM_CONTENT | Ex.: The content is harmful and cannot be processed. |
400 | INSUFFICIENT_BALANCE | The user has insufficient balance |
401 | UNAUTHORIZED | Ex.: The token is invalid. |
429 | TOO_MANY_REQUESTS | Ex.: The request limit has been reached. |