Editing schema in the editor

The Schema Editor is a full JSON-LD code editor with syntax highlighting, live validation, and auto-save. Change any field by hand, watch for errors and warnings as you type, and your edits save automatically a few seconds after you stop typing.

Every schema SuperSchema generates is fully editable. The Schema Editor is a real code editor (the same engine that powers VS Code), so you get syntax highlighting, bracket matching, and inline error markers. You can change any value, add or remove properties, and the editor checks your work as you go and saves it for you. Nothing here touches your live site. You are editing the schema in your Library, not the markup on your page.

Making edits #

The editor shows one schema as formatted JSON-LD. Click into any line and type. As you edit, the header shows a running count of errors and warnings, and a "Valid" badge appears when the JSON is clean. Paste is auto-formatted, so if you drop in a block of JSON it gets tidied to two-space indentation.

Change a value: click the text, edit it, and move on. The editor keeps the JSON formatted.
Add a property: add a new line with the property name and value, keeping valid JSON syntax (quotes, colons, commas).
Remove a property: delete its line. Watch the trailing comma on the line above so the JSON stays valid.
Reformat on paste: pasted content is indented automatically, so you can copy from another source without cleaning it up by hand.

Live validation #

The editor validates as you type and, if you click Validate, checks the schema against the schema.org rules SuperSchema uses. Results show as counts in the header and as a list below the editor.

Errors: Something that breaks the schema: malformed JSON, a missing quote or comma, or a property in the wrong shape. The header shows a red error count. Fix errors before you publish, because search engines and AI will skip invalid markup.
Warnings: A best-practice note rather than a blocker: for example a description that is longer than the ideal range. The header shows a yellow warning count. You can save and publish with warnings.
Valid: A green "Valid" badge means no errors and no warnings were found in the current content.
Invalid JSON: A red "Invalid JSON" note next to the save status means the current text cannot be parsed as JSON, so it was not saved. This usually means a missing comma, quote, or bracket. The last valid version is preserved.

Tip The Validate button runs a fuller check that lists each issue by field, so you can see exactly which property has a problem rather than just a total count.

How saving works #

Stop typing. About three seconds after your last keystroke, the editor saves.
Watch the status next to the "Schema Editor" title: it reads "Saving..." then "Saved".
If the current text is not valid JSON, you will see "Invalid JSON" instead and the change is not saved. Fix the syntax and it saves on the next pause.

Note Auto-save waits until your text parses as valid JSON. A broken state (mid-edit, with a missing bracket) is never saved over your last good version, so you cannot lose your schema by pausing in the middle of an edit.

Tip The editor is careful not to move your cursor while it saves. When a save completes in the background, your place and scroll position stay put, so it never jumps under you.

Copying the schema out #

When your schema looks right, use the Copy Schema button in the editor header. It copies the schema already wrapped in the script tag your page needs, ready to paste into your site's <head>. The button walks through a short "Copying..." then "Copied!" confirmation so you know it worked.

Dark and light mode #

The editor opens in dark mode. Use the sun or moon button in the header to switch between dark and light, whichever is easier on your eyes. This only changes the editor theme, not your schema.

If something goes wrong #

Save stuck on "Invalid JSON": you have a syntax error. Look for a missing comma between properties, an unquoted string, or an unclosed bracket or brace. The last valid version is safe.
A red error count that will not clear: open the list under the editor to see which field is flagged, then correct that property.
You want to start over: regenerate the schema, or run Refine with AI, to get back to a clean, valid version.

Warning Editing the schema here changes the copy in your Library, not the markup on your live page. After you edit, copy the updated schema and re-paste it into your site (or redeploy it) for the change to take effect.