SmartBlocks Troubleshooting
Common SmartBlocks issues are often informational readiness signals, campaign state, or integration configuration—not plugin failures.
Page Readiness looks wrong
Info signals are not errors
These are valid fallback behavior:
- OG title/description — falls back to SEO title/meta description
- Canonical — empty dedicated canonical but permalink exists
- Primary keyword — falls back to Focus Keyword from Rank Math/Yoast
- GEO section — excluded when page is not local-intent
- Categories/tags on pages — info-only, not penalized
See SmartBlocks User Guide — valid fallbacks.
Visibility Campaign stuck or empty
- Confirm campaign has posts in scope and baseline snapshot completed
- Safe Fix only applies high-confidence registry keys—moderate items need FAQ Guided Action
- Check user capability for governed apply actions
- Review Visibility Ledger for blocked or skipped events with evidence
FAQ / schema not appearing on frontend
- FAQPage schema requires grounded FAQ rows in post meta—not placeholder content
- Schema output is conditional; verify FAQ shortcode/block is on the page
- Rank Math/Yoast may own Article schema—SmartBlocks defers when configured
- Use schema-only mode when enabling meta without ungrounded FAQ rows
Recommendation will not apply
- Key must exist in
smartblocks_recommendation_registry - Handler may require preview, confirmation, or missing dependencies
- Moderate-risk FAQ actions require review—automatic apply is blocked by design
Ledger or snapshots missing
- Ledger events require an explicit logging path—check event key and source
- Daily snapshots may lag until cron or manual refresh runs
- Compare views need both before and after snapshot IDs
Telemetry shows no crawler data
- Telemetry needs front-end requests and configured detection—allow time for accumulation
- Cache/CDN may mask bot traffic on heavily cached pages
- GSC bridge requires Search Console connection in Integrations
Media readiness not in ledger
Requires Vexal Media active alongside SmartBlocks. Media readiness appears in snapshot metadata.media_readiness after Media Apply Fix or readiness refresh.