For Schema Studio 0.9.5. Reviewed October 10, 2026. Review tested versions, exclusions and limitations.
Edit fields and connect sources
Select the node in Graph, then open Fields & Sources. Add a relevant property, select a source or manual value, and inspect the resolved preview.
| Value | Source key | Use |
|---|---|---|
| WordPress title | post.title | A headline that follows the visible title. |
| SEO title | seo.title | A name that intentionally follows the SEO title. |
| Description | post.description or seo.description | Inspect the result; it can fall back to an excerpt. |
| Permalink | post.url | The current WordPress page URL. |
| Canonical | post.canonical | Respect a saved SEO canonical. |
| Dates | post.date_published, post.date_modified | Real WordPress dates. |
| Featured image | post.featured_image, post.featured_image_object | URL or object, as appropriate. |
| WordPress author | author.entity | Only if that account represents the actual author. |
Keys identify underlying bindings; the interface may use descriptive labels. Prefer bindings for changing template values. A manual headline in a site-wide template gives multiple pages the same headline.
Use manual values for facts without a suitable source. Where offered, a fallback should be truthful. Never add a dummy image, invented address or fabricated rating to clear a warning.
Nested values and relationships
Use visual object/list controls for addresses and lists of profiles. Use entity or node references for existing subjects. Relationships should point to the intended @id, rather than a display name entered as text.
Advanced JSON
Use Code when normal controls cannot express a requirement. Back up, inspect generated output and validate before applying custom code. Output JSON examples are not the plugin’s internal import-document format.
Links will be automatically removed from comments.