Generate JSON-LD
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. This endpoint reads a page or a set of facts you supply and generates valid JSON-LD matched to the correct schema type, so the markup does its job the first time.
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.
The problem with hand-written schema
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 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 validated JSON-LD block back, ready to drop into its own template slot.
Delivery and reliability
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. A page that fails to generate valid 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.
What you can do with it
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.
Local business listings
Create LocalBusiness markup with correct address, hours and geo fields for each location page of a multi-branch business.
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.
FAQ
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?
Yes, every generated block is checked against the schema.org vocabulary before being returned, so what you get is structurally valid JSON-LD.
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.
Is there a free trial available?
There's no free tier — free tiers get abused and slow everyone down. Access runs on a prepaid ForHosting KIT balance: top up from $10.00 (it never expires) and each request is charged at its published price, so a call with no balance returns HTTP 402. No subscription, no tokens, no invented credits, and a failed task is never charged.
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.
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, and soon from our app, email and Telegram.
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 '{"input":"…"}'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({
"input": "…"
})
});
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={
"input": "…"
},
)
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" => '{"input":"…"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"input":"…"}`)
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
{
"input": "…"
}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. |