Targeting rules

Rules decide where a schema appears. Each rule is either Show on or Hide on, and exclusions always win.

Available targets:

• Entire site — every page
• Front page, Blog index, Search results, 404 page
• Every single post and page (on a shop, Every single post, page and product) — any single piece of content of any post type, including custom ones. On a shop that is also the cart, checkout and account pages.
• All {post type} — one post type, including custom ones
• Archives: {taxonomy} — category, tag or custom taxonomy archives
• Author archives, All archives
• A specific post or page
• A specific category, tag or term

For the last two, start typing the title or name in the box beside the rule and pick it from the list. Each result shows what kind of thing it is and its ID, so two pages with the same title can be told apart. If you already know the ID, type the number instead. A name typed but never picked from the list names nothing, so that rule is not saved and the message after saving says so. The Applies to column on the Schemas screen then shows the page's title.

A common pattern is one broad include plus a narrow exclude:

Show on   All posts
Hide on   A specific post or page   →   Privacy Policy

That applies the schema to every post except the privacy policy.

A new schema starts on Every single post and page, except for the types made of one page's own content — FAQ, How-to, Q&A, Recipe, Event, Job Posting, Review, Item List, Video, Audio and Podcast Episode. Those start on A specific post or page, with the cursor in the box, because questions or ingredients typed into the schema would otherwise appear on every page. Saved without a page chosen, the schema is on no page yet, and the message after saving says so. If one of those types has such content typed in and its rules cover more than a single page, the validation report warns that every page gets the same one.

Priority#

When several schemas match one page, they are all output, ordered by priority (lower first). Priority only decides order — it never suppresses a schema. To stop one appearing, add an exclusion rule or set its status to Draft.