Getting started with Schema Studio

For Schema Studio 0.9.5. Reviewed October 10, 2026. Review tested versions, exclusions and limitations.

Understand what structured data does

Structured data describes a page in a format software can read. An article can identify its headline, author, publisher and publication date. Schema.org supplies the vocabulary; JSON-LD expresses it. Schema Studio builds JSON-LD from information you provide in WordPress.

Think of a graph as connected records: this page contains this article, this person wrote it, and this organization published it. Each record is a node. A stable @id identifies it; a relationship points to that ID.

Describe the page you have. Markup should agree with the visible content and verified facts. Adding a type does not create content, establish an affiliation or guarantee a search feature.

Schema.org validity, Google feature eligibility and search appearance are separate questions. Valid markup does not guarantee a rich result. Read Google’s structured-data introduction and quality guidelines.

Property

A fact or relationship, such as headline, image or author.

Source binding

A value read from WordPress or the active supported SEO plugin instead of typed separately.

Template

A reusable graph configuration applied to selected content.

Reusable entity

A Person or Organization used across pages with the same identity.

Canonical URL

The preferred page URL. It differs from an entity ID such as https://example.com/#organization.

Start with one page

You do not need JSON for normal editing. Begin with a draft or low-risk page before applying a site-wide template.

1. Back up. Keep a current full WordPress backup and export the plugin’s backup before changing existing configurations.
2. Choose who manages schema. Review output modes before combining plugins.
3. Set your identity. In Global settings, enter the real Person or Organization. Preserve its existing identity ID.
4. Open a page or post. Use Open Schema Studio and inspect its current graph.
5. Choose a suitable node. Use WebPage for an ordinary page, or Article/BlogPosting for a real article. Inspect inherited nodes before adding duplicates.
6. Use Fields & Sources. Bind changing values such as titles, URLs and dates to corresponding sources.
7. Preview and validate. Inspect resolved values and relationships. Fix errors and read warnings in context.
8. Commit. Close the studio and use WordPress Save or Update. Reload to confirm persistence.
9. Check the public page. Open published content while signed out and test its actual JSON-LD. Drafts are not expected to be public.

Done means: values survive reload, the intended public graph appears, IDs remain stable, and markup describes the visible page.

Choose a type that matches the content

This is a modeling starting point, not a promise of Google enhancements. The vocabulary is broader than the verified workflow scope. WooCommerce schema is outside the 0.9.5 approved scope.

Set your site identity once

Open Schema Studio → Global settings. Choose Organization for a business or institution, or Person when an individual represents the site. Enter a truthful name, website URL and appropriate image or logo.

1. Inspect the identity ID. An ID ending in #organization or #person identifies a subject; it is not another page you need to create.
2. Keep the same ID for the same real subject. Changing its label does not require a new ID.
3. Use the actual Organization logo or Person image. A company logo does not represent a person’s portrait.
4. Use sameAs for authoritative profiles of that same subject, not unrelated pages or every site that mentions it.
5. When changing identity type, review and accept the preview, save, and recheck references.

Whether to emit global WebSite and identity nodes depends on output mode. Inspect competing base graphs before enabling both.