Schemas are configured once and cover many posts, with most fields filling in from whichever post is being viewed. Occasionally one post needs something different — a headline that reads better in search results than on the page, or a rating that applies only to that review.

Open the post and find the Schema Pro panel below the editor. Every schema that applies to that post is listed, with its fields — including one aimed at the Front page when this page is your front page, and leaving out any the post is hidden from by a Hide on rule. Each box shows the value that would be used if you leave it empty, so you can see what you are changing.

Anything you type there applies to that post alone. The schema itself, and every other post it covers, is untouched. Clearing the box restores the automatic value.

Repeating fields — FAQ questions, How-to steps — are deliberately not offered per post: they belong to the schema as a whole, and a half-overridden list is worse than none.

Above the fields, the panel says whether this post is missing a required property, schema by schema and in plain words, for example "Blog posts: Image is read from each post, and “My first post” has none." Something the post fills in for itself, such as its featured image, is shown as a warning; a property the schema itself should give is shown in red. When nothing is missing it says "Nothing to fix in this post's markup." Under Markup for this post it shows the post's own JSON-LD, folded away until you open it, and Test with Google opens Google's Rich Results Test on the post's address. The test link only appears for a published post Google can reach: not for a draft, a private or password-protected post, or a site on a local address. A new post that has never been saved is not checked yet.

The check reads the post as it was saved when the editor opened. The block editor does not redraw this panel after Update, so reload the screen to see the check again; the numbers under Tools change as soon as the save has finished.

Per-post overrides