Schema Pro documentation
Setting it up, and how each part works: 20 sections, free to read before you buy.
- Getting startedWhen you activate Schema Pro, a notice offers a short setup.
- Multisite networksSchema Pro works on both a single site and a WordPress Multisite network.
- What structured data actually doesStructured data is a block of machine-readable JSON in the page head describing what the page is: an article with this headline and author, a recipe taking this long, a product…
- Setting up by handSchema Pro adds Schema.org structured data to your site so Google can show rich results — star ratings, prices, recipe cards, job listings and more.
- Adding your first schemaGo to Schema Pro → Schemas → Add schema and pick a type.
- Automatic fieldsA field marked Filled automatically if left empty pulls from the post being rendered: Headline / Name — the post title Description — the excerpt, or the first 55 words of the…
- Targeting rulesRules decide where a schema appears.
- Site IdentitySchema Pro → Site Identity produces the entity that represents the site.
- Per-post overridesSchemas are configured once and cover many posts, with most fields filling in from whichever post is being viewed.
- Working with an SEO pluginMost sites already run Yoast, Rank Math, SEOPress, All in One SEO or The SEO Framework, and those plugins output structured data of their own.
- Reading values from your own fieldsMost fields fill in from the post automatically, and anything you type applies to every post the schema covers.
- WooCommerceWith WooCommerce active, a Product schema reads straight from each product: price, currency, stock status, SKU, brand, GTIN, the sale end date, the average rating and the review…
- LanguagesThe plugin ships in English, Spanish and French, and follows your site language automatically.
- Seeing what your markup producesThe schema editor has two preview panels, and both update as you type — you do not need to save to see the effect of a change.
- ValidationSchema Pro → Tools lists every active schema that is missing a property Google requires.
- CachingRendered markup is stored per page and reused until the content or your settings change.
- Custom JSON-LDFor markup the plugin does not cover, add a Custom JSON-LD schema and paste your own object.
- Export and importTools → Maintenance → Export and Import copies your set-up to another site without copying the database.
- UninstallingDeleting the plugin leaves your schema data in place, so reinstalling restores everything.
- An admin without page loadsMoving between the plugin's screens does not reload the page, and neither does saving.
Nothing here matches that. Search everything
Still stuck? Ask the developers who wrote it. We aim to reply within one business day.