Schema publishes as JSON-LD; broken-link proposals deploy as redirect rules
The other two publishable kinds materialize as rules: schema lives with the SEO rules, broken-link proposals live with the redirects — each with its own deploy semantics.
Schema → SEO rule#
Publishing a schema-markup-publish draft upserts an SEO rule named Schema markup: {schemaType} (deduplicated by path pattern + schema type) carrying your JSON-LD, then deploys SEO rules to the serving path. Invalid JSON is refused with Schema markup draft contains invalid JSON-LD. In the manual surface (Optimization → SEO & AI Search → Add rule) the same data lives in fields Schema @type (placeholder Product) and JSON-LD (placeholder { "@context": "https://schema.org", "@type": "Product", … }, with the client-side error JSON-LD must be valid JSON.). Timing, per the drawer footer: The first matching rule wins. Rules deploy on save and invalidate cached pages.
Broken links → redirect rule#
A broken-link-redirect-proposal publishes as a redirect rule named Redirect proposal: {path} with the source escaped to an exact match (^…$), status code 301, enabled — then redirect rules are deployed to the serving path. The manual surface is Advanced → Redirects (Add rule, fields Source regex, Target URL or absolute path with placeholder /new/$1 or https://example.com/new/$1, optional Country code, plus CSV import). Here the footer is stricter: Redirect changes affect live traffic only after Deploy is clicked. — the domain Deploy button is what rolls redirect drafts to the edge.
Choosing your layer#
Both are edge-layer artifacts (see Act in the right layer); neither touches your origin. Publish writes the rule, the panel's deploy semantics decide when traffic sees it, and the change log records who did what.