Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.schemagen.io/llms.txt

Use this file to discover all available pages before exploring further.

The Schema Delivery Network (SDN) is SchemaGen’s core delivery engine. It separates your structured data from your website’s source code entirely—install a single script tag once, and every schema you create, edit, or remove takes effect immediately from the dashboard, with no code changes, CMS access, or developer involvement required.

​
How the SDN works

When a visitor lands on a page of your site, the SchemaGen SDK (loaded via your script tag) sends a request to the SDN edge with your client ID and the current page URL. The SDN matches that URL against your published schemas and returns the appropriate JSON-LD, which the SDK injects directly into the page’s DOM before search engines crawl it. 
Visitor loads page
  → SDK calls GET /api/inject?clientId=YOUR_CLIENT_ID&url=https://yoursite.com/page
  → SDN returns matching published schemas as JSON-LD
  → SDK injects <script type="application/ld+json"> tags into the DOM
The SDK tag itself is lightweight and loads asynchronously—it never blocks your page from rendering.
The SDK script uses the async attribute, so it loads in the background and has no impact on your page’s rendering or Core Web Vitals scores.

​
Installing the SDK

Add this single tag to the <head> of every page on your site—or use your CMS’s global head injection setting. Replace YOUR_CLIENT_ID with the client ID shown in your SchemaGen dashboard. 
<script async
  src="https://schemagen.io/sdk.js"
  data-client-id="YOUR_CLIENT_ID">
</script>
This is the only change you ever need to make to your site. All schema management happens from the dashboard after this point.

​
Edge-optimized delivery

The SDN runs on edge infrastructure, meaning schema requests are resolved at network locations geographically close to your visitors. In practice, this means:
  • Sub-100ms response times for schema fetches worldwide
  • No caching of schema data (Cache-Control: no-store)—so published changes and pauses take effect instantly on the next page load
  • Per-request tracing via X-Schemagen-ID and X-Schemagen-Duration response headers, useful if you’re debugging delivery with your browser’s developer tools

​
Schema states

Every schema in your dashboard has one of three statuses. The status controls whether the SDN delivers it to your site.

Draft

The schema is saved in your dashboard but not yet live. The SDN will never deliver a draft schema, regardless of URL targeting. Use this state to build and review before going live.

Published

The schema is live on the SDN. Whenever the SDK detects a page URL that matches this schema’s target, the JSON-LD is injected into the DOM. Changes to a published schema go live instantly.

Paused

The schema is temporarily removed from delivery without being deleted. The SDN stops serving it immediately, but all your data and settings are preserved. Unpause to resume delivery at any time.

​
The old way vs. the SDN way

Managing structured data without SchemaGen means your schema lives inside your codebase—tied to templates, CMS themes, or developer-managed JSON-LD files. Every change requires a ticket, a deployment, and a wait.
SituationWithout the SDNWith the SDN
Add a new schema to a pageFile a developer ticket, wait for deploymentPublish from the dashboard in seconds
Fix a schema errorFind the template file, update it, redeployEdit the schema, save—live instantly
Remove a schema temporarilyRequires code change and deploymentClick Pause—removed from delivery immediately
Update schema across many pagesRepetitive, error-prone manual workUpdate once, targeting applies everywhere
The SDN eliminates the dependency on development cycles for anything schema-related. SEO teams get direct control.

​
What gets delivered

The SDN matches schemas to pages using the pageUrl field you set when creating or editing a schema. When the SDK requests schemas for a URL, the SDN returns only the published schemas whose target URL matches the current page. The SDK then injects each one as a separate <script type="application/ld+json"> block. The inject API response includes:
  • schemas — the raw JSON-LD objects ready for injection
  • items — full schema records including metadata
  • meta — delivery metadata including API version, a unique request ID, and server timestamp

​
Next steps

Publishing schemas

Step-by-step guide to taking a draft schema live on the SDN.

Domain locking

Restrict which domains can receive schemas from your SDN client (Agency plan).