Generate JSON-LD
Get a page's structured data without writing it by hand: a product page's title, price and availability land in the Product type, required properties filled and recommended ones added where the content allows. Pay per page, no subscription.
Run it online
Run this on our servers with your account. Free tools run in your browser; this one bills your KIT balance per the price above.
Structured data is the part of a page search engines read but visitors never see, and getting even one nested property wrong can quietly disqualify a rich result.
Data that search engines read and visitors never see
Structured data is the part of a page that search engines read but visitors never see. Its vocabulary defines dozens of types, from Product, Article and Recipe to Event, LocalBusiness and FAQPage, and each type has its own required and recommended properties and its own rules about which types can sit inside others. Writing it by hand means checking documentation constantly. One misplaced property or one wrong kind of value can make the markup fail validation without breaking the page itself, which is why the mistake can go unnoticed for months while a rich result is quietly lost.
From one landing page to a whole catalog
The generator reads a page, or a set of facts you provide, and maps titles, prices, dates, availability, author bylines and ratings onto the right type. Because the markup sits in its own block, separate from the visible layout, it can be regenerated whenever the content changes. A business with several branches can get LocalBusiness markup with the right address, opening hours and location for each branch page, and a catalog with thousands of products gets one block per page.
Why hand-written structured data goes wrong
Structured data vocabularies define dozens of types — Product, Article, Recipe, Event, LocalBusiness, FAQPage, and many more — each with its own required and recommended properties, and its own rules about which types nest inside others. Writing this by hand means constantly checking documentation, and a single misplaced property or wrong data type can mean the markup silently fails validation without breaking the page itself, which is exactly why it goes unnoticed for months.
What you can do with it
Local business listings
Create LocalBusiness markup with correct address, hours and geo fields for each location page of a multi-branch business.
FAQ
Is there a free trial available?
There's no free tier — free tiers get abused and slow everyone down. No subscription, no tokens, no invented credits, and a failed task is never charged.
Which structured data types can it produce?
It works with the common types such as Product, Article, Recipe, Event, LocalBusiness and FAQPage, picking the one that fits the page. It can also combine several, like an article with its breadcrumb trail, in one coherent block.
Will it invent details the page does not contain?
It fills required properties and adds recommended ones only where the source content supports them, such as a price, a date or an author byline that is really there. Review the result before publishing it.
Can I generate markup for a whole product catalog?
Yes. Submit the list of page addresses or the equivalent facts, and each page gets its own block of structured data back, ready to drop into its own place in the template.
Do I need to change my page templates?
No. The markup lives in its own block, separate from the visible page, so it can be added or regenerated whenever the content changes without anyone editing the page layout by hand.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/seo/schema-generate \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"text":"El informe trimestral cerró con 1,2 M€ de ingresos."}'const res = await fetch("https://api.kit.forhosting.com/seo/schema-generate", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"text": "El informe trimestral cerró con 1,2 M€ de ingresos."
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/seo/schema-generate",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"text": "El informe trimestral cerró con 1,2 M€ de ingresos."
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/seo/schema-generate", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"text":"El informe trimestral cerró con 1,2 M€ de ingresos."}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"text":"El informe trimestral cerró con 1,2 M€ de ingresos."}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/seo/schema-generate", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"text": "El informe trimestral cerró con 1,2 M€ de ingresos."
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "seo.schema_generate",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
413 | input_too_large | The file exceeds the size limit. |
422 | task_failed | The task failed after 3 retries. You are never charged for it. |
Technical notes
This endpoint reads a page or a set of facts you supply and generates JSON-LD with AI for the appropriate schema type, ready to review and drop into the page.
What happens when you submit a page
The task inspects the page's own content — titles, prices, dates, availability, author bylines, ratings, whatever is relevant to the detected type — and maps it onto the correct schema, filling required fields and adding recommended ones where the source data supports them. You can also point it at multiple types on one page, such as an Article combined with a BreadcrumbList, and it produces one coherent JSON-LD block rather than two competing scripts.
A brief note on the format itself
JSON-LD became the recommended syntax for structured data specifically because it lives in its own script tag, separate from the visible HTML, which means it can be generated and swapped independently of page templates. That separation is what makes an API-driven approach practical: the markup can be regenerated whenever the underlying content changes, without anyone touching the page's HTML by hand.
Batch generation across a catalog
Because pricing is per page, this scales naturally from a single landing page to a product catalog with thousands of SKUs — submit the list of page URLs or the equivalent structured facts, and each one gets its own JSON-LD block back, ready to drop into its own template slot.
Delivery and reliability
A page that fails to generate markup after three attempts returns a specific error instead of a charge, and you can resubmit that single page once the underlying content issue is fixed, without paying twice for the pages that already succeeded. The task runs asynchronously: submit it and get a task_id immediately, with results delivered by webhook or a signed link valid for 24 hours once generation finishes.
Integration use cases
E-commerce product pages
Generate Product schema with price, availability and rating fields across an entire catalog without writing JSON-LD templates by hand for each product type.
Recipe and content publishers
Produce Recipe or Article schema automatically as new posts go live, so rich results stay eligible without a manual markup step in the publishing workflow.
FAQ and how-to pages
Convert an existing FAQ page's questions and answers into valid FAQPage JSON-LD ready to embed without restructuring the page.
Technical questions
What schema types does this schema markup generator api support?
Common types including Product, Article, Recipe, Event, LocalBusiness, FAQPage and BreadcrumbList, with the correct type detected from the page or facts you submit.
Does it validate the output against the official schema?
No. The block is generated by AI for the appropriate schema type; it isn't checked against the schema.org vocabulary before being returned. Run it through Google's Rich Results Test or the Schema.org validator before publishing.
Can I generate schema for pages that don't exist yet?
Yes, you can submit raw facts (title, price, date, and so on) instead of a live URL and get the matching JSON-LD back.
How is pricing calculated for bulk pages?
A base $0.003 per request plus $0.0135 per page processed, so a 100-page catalog run is $0.003 plus $1.30.
How do I receive the generated JSON-LD?
Through a signed webhook when generation completes, or a signed link valid for 24 hours.
What happens if a page's content doesn't match any known schema type?
The task returns a clear error identifying the ambiguity instead of guessing, and you are not charged for that page.
Will multiple schema types on one page conflict with each other?
No, when a page needs more than one type the task merges them into a single coherent JSON-LD block rather than producing separate scripts.