Schema Pro plugin review and common issues

Test your page at search.google.com/test/rich-results and review the specific error messages. Common issues: required fields are empty (e.g., Review schema without a rating value), custom field mapping is pointing to an empty or incorrectly named field, or conflicting schema from your SEO plugin is producing duplicate or contradictory structured data. In Schema Pro settings, enable Test Mode to preview schema output before it goes live. Disable schema output from your SEO plugin for the same post type to avoid conflicts.

Check the conditional targeting in your schema rule. Schema Pro uses WordPress conditional tags — if the condition specifies “Posts in Category: Reviews,” it applies only to posts currently assigned to that category. If posts were recently moved into the category, clear any schema caches and ensure the posts are saved/updated after the category assignment. Also check if another schema rule with a higher priority is overriding the global rule for specific posts.

Having two plugins output schema for the same page can confuse search engines. Disable schema output from your SEO plugin for the post types handled by Schema Pro. In Yoast SEO, go to SEO → Schema and set the content type schema to “None.” In Rank Math, go to the post’s schema tab and remove the auto-generated schema. This lets Schema Pro control structured data while your SEO plugin handles meta tags, sitemaps, and other functionality.

In Schema Pro → Create Schema, select your schema type and then click on any field value. A dropdown appears offering options including “Custom Field.” Enter the ACF field name (not label) — for example, “review_rating” — and Schema Pro will pull that field’s value for the schema property. For ACF repeater fields, Schema Pro has limited support — complex nested data may require a custom implementation using Schema Pro’s developer filters.

Yes. Create a new schema in Schema Pro, select FAQ type, and set the conditional to apply to “All Posts” or a specific post type. For the FAQ data, you can either manually enter questions per post (Schema Pro adds fields to the post editor) or map to custom fields if you store FAQ data in ACF or similar. FAQ schema requires structured question/answer pairs — Schema Pro adds a repeatable field in the editor for entering them per post, even when a global rule applies the schema type.

Yes, but you should disable Rank Math’s schema output for post types you are managing with Schema Pro to avoid conflicts. Rank Math → Meta Box → Schema provides good schema for most use cases at no cost. Schema Pro adds value when you need more schema types than Rank Math supports, global conditional rules, or custom field mapping — use cases that go beyond what the bundled schema in SEO plugins handles.

Likely not. For FAQ, Article, and Product schema on a single standard site, Rank Math (free) or AIOSEO (Pro) handles the same requirements without an additional plugin. Schema Pro earns its price on sites with multiple schema types, large content archives needing global rules, or complex custom field integrations. For a straightforward site, the schema bundled in your existing SEO plugin is sufficient.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.