Win more clicks from Google with rich results — stars, prices, FAQs and more — set up in two minutes, no code.
The complete list — what each part does and what it is there for.
Article, Recipe, Product, FAQ, How-to, Local Business, Job Posting, Event, Course, Video, Review and more — plus Custom JSON-LD for anything the list does not cover.
Every schema on a page is combined into a single JSON-LD @graph, which is what Google recommends. Fewer bytes than separate blocks, and no conflicting signals from markup scattered across the page.
Headline, description, image, author, dates and permalink are read from the post being viewed. One schema targeted at a post type covers every post in it, so a working setup is usually two clicks.
Price, stock, SKU, ratings, brand and GTIN read straight from each product. Woo's own product markup is switched off so search engines see one clean answer, not two competing ones.
Apply a schema to the whole site, one post type, a taxonomy archive, a single post, or any mix. Exclusions win over inclusions, so "every post except this one" is a single rule pair.
Anything public on your site appears in the targeting rules automatically. No mapping step, no configuration file.
Change a headline, image or rating for one post from the post editor, without touching the schema every other post shares. Empty fields show exactly what will be output instead.
Point any field at a custom field, an ACF field, the author profile or a term field. One schema then produces the right value on every post, instead of the same value everywhere.
A report lists every active schema missing a property Google requires, so a page that will not qualify for rich results is visible to you first.
Declare the site as an organisation or a person, with logo, contact details and social profiles. Other schema types reference it, so one correct answer improves everything else.
Yoast, Rank Math, SEOPress, All in One SEO and The SEO Framework are detected automatically. Site identity, breadcrumbs and the sitelinks box stand down rather than emitting a second, conflicting copy.
A short wizard asks who publishes the site and what its posts are, then creates working markup and shows you it is live. No schema.org vocabulary required.
Each type says what it gets you in search results and links to Google's own guidance, and fields tell you the format, the units and an example.
Fully translation-ready, with Spanish and French supplied. Any other language can be added by dropping in a translation file.
Four purpose-built database tables instead of postmeta, targeting matched in a single indexed query however many schemas you have, and rendered markup cached per URL.
Every screen in the plugin arrives without a page load, and every save happens where you are standing. WordPress fetches the whole of wp-admin's CSS and JavaScript again to change one panel; this fetches the panel. The screen you are on is still there while the next one is on its way, and the one you are heading for is usually already in hand — a pointer takes a moment to reach a menu item, and that moment is spent fetching.
A save answers in the corner of the screen, bordered in the colour of what it is telling you and saying what was saved rather than just "Saved". Four seconds, and hovering holds it open. No reload, and no scrolling back to find a notice above the header three hundred pixels from the button you just pressed.
A WordPress admin request spends about a second in its own bootstrap before a plugin gets a word in, and fetching when your pointer arrives only buys back a fraction of it. So the plugin's other screens are fetched quietly while you read the first one — one at a time, only while the browser is idle, and never on a metered connection. By the time you click a tab the answer has been in memory for seconds.