Schema Pro stores each markup configuration as a wp_schema_pro custom post type with the schema type, target rules, and per-field mapping stored on the post and in meta keys like bsf-schema-pro-schema-type, bsf-aiosrs-target-rules, and per-field mapping entries that link schema fields to ACF, post meta, or custom callbacks. The default Schema Pro admin lists markup posts one row at a time and shows the schema type and target rule count without exposing which of the targeted posts actually have all required fields populated today.

SleekView Kanban resolves every markup post into the list of target posts it applies to, then reads the field-level data the markup expects from each target post's meta. Pick a derived validation_state field that buckets target posts by required field completeness and an editorial sign-off flag and every target becomes a card grouped under Unmapped, Mapped, In Validation, and Validated. Card fronts can show the target post title, the markup schema type, the required field completeness, the assigned editor, and the last updated date so the SEO lead can act on the board without opening every target post in a separate editor tab.

Dragging a card between columns writes back through standard WordPress meta APIs. A move from Mapped to In Validation sets the editorial sign-off flag so the editor knows the target is queued for a Search Console rich result test, and a move from In Validation to Validated flips that flag so the target is treated as schema-ready for the next Search Console review.

Schema Pro is brilliant at the markup rules engine and unhelpful at showing the whole team where target coverage stands across the site today. The default workflow means inspecting each markup rule and opening every resolved target in a separate tab to check field completeness, but planning a quarterly sprint means pivoting that data into a spreadsheet, and the spreadsheet goes stale within a week. By the time the SEO lead has reconciled the spreadsheet, an editor has published a product review without the brand field set and another article that should carry an event markup is missing a start date entirely.

A kanban view that reads and writes the same Schema Pro markup and target meta the admin uses keeps the team and the schema state aligned. Unmapped, Mapped, In Validation, and Validated all live on one board. Schema types, completeness percentages, editors, and last updated dates are visible on every card.

The team can ship rich results faster, the SEO lead can plan a coverage sprint in minutes instead of hours, and the schema data never drifts from what Schema Pro actually outputs as JSON-LD across the public front end every day.