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.

Publishing a schema makes it live on the Schema Delivery Network. From that moment, every page on your site that matches the schema’s target URL will have the JSON-LD injected by the SDK on each page load. This page walks you through publishing your first schema, editing a live schema, and managing schema delivery after it goes live.

​
Prerequisites

Before you can publish a schema to the SDN, you need:
  • The SchemaGen SDK installed on your site (see the SDK installation guide)
  • At least one schema saved as a draft in your dashboard
If the SDK isn’t installed yet, any schemas you publish will be ready on the SDN but won’t appear on your site until the script tag is in place.

​
Publishing a draft schema

Run schema validation before publishing. The validator checks your JSON-LD against Schema.org specifications and Google Rich Result guidelines, so you catch issues before they affect your site’s structured data.
1

Open the schema

In your dashboard, navigate to Schemas and locate the schema you want to publish. Schemas in draft status are not yet live on the SDN.
2

Review the target URL

Confirm the Page URL field contains the exact URL of the page where this schema should appear. The SDN uses this URL to match incoming requests from the SDK. If the URL is wrong, the schema won’t be delivered to the correct page.
3

Validate the schema

Click Validate to run the schema through SchemaGen’s validator. Review any issues or warnings before continuing. Resolve critical issues before publishing—warnings are informational but issues can prevent rich results.
4

Click Publish

Click the Publish button. SchemaGen will prompt you to confirm that you want to make this schema live on the SDN.
5

Confirm

Confirm the action. The schema status changes from draft to published immediately. The SDN begins delivering the JSON-LD to matching page URLs on the next SDK request.
Do not publish schemas that have validation errors. A schema with structural or property errors can cause Google to ignore the structured data entirely, or flag your site in Search Console. Fix all errors before publishing—warnings are safe to publish with, but errors are not.

​
What happens when you publish

The moment you publish:
  • The schema status updates to published in your dashboard
  • The SDN edge makes the JSON-LD available for delivery
  • Any page request matching your schema’s target URL will receive the schema on the next SDK call
  • The change is reflected without any code change, CMS update, or site deployment
There is no propagation delay. The SDN does not cache schema data between requests (Cache-Control: no-store), so published schemas are live immediately.

​
How URL targeting works

The SDN delivers schemas by matching the URL the SDK sends—the exact URL of the page the visitor is on—against the Page URL you set on each schema. For the schema to be delivered:
  • The page URL reported by the SDK must match the schema’s target URL
  • The schema must have published status
  • If domain locking is enabled on your client, the requesting domain must be on the allowlist
Set the Page URL to the full, absolute URL of the target page, including the protocol: https://yoursite.com/services/dentistry.

​
Editing a published schema

You can edit a published schema at any time from the dashboard. Changes go live on the SDN as soon as you save—there is no separate republish step. To edit a published schema:
  1. Open the schema from your Schemas list
  2. Make your changes to any fields, properties, or the target URL
  3. Click Save
The updated JSON-LD is available on the SDN immediately. The next page load that triggers an SDK request for that URL will receive the updated schema.
If you change the target URL of a published schema, delivery for the old URL stops immediately and begins for the new URL. Plan URL changes carefully, especially on high-traffic pages.

​
Pausing a schema

Pausing removes a schema from SDN delivery without deleting it. Use this when you need to temporarily stop delivering a schema—for example, during a site migration or if you discover an issue after publishing. To pause a schema:
  1. Open the schema from your Schemas list
  2. Click Pause
The schema status changes from published to paused. The SDN stops delivering it immediately. Your schema data, target URL, and all settings are preserved—unpause at any time to resume delivery. Paused vs. draft: Both states mean the schema is not delivered. The difference is intent—draft schemas are being built, paused schemas were previously live and are temporarily suspended.

​
Deleting a schema

Deleting a schema permanently removes it from your dashboard and the SDN. This action cannot be undone. To delete a schema:
  1. Open the schema from your Schemas list
  2. Click Delete (or the trash icon)
  3. Confirm the deletion
If the schema was published at the time of deletion, the SDN stops delivering it immediately. Consider pausing instead of deleting if there’s any chance you’ll want the schema again.
Deleting a schema is permanent. All schema data, history, and settings are removed and cannot be recovered. If you’re unsure, pause the schema instead.