Structured data diagnostics

Purpose and scope

LIOSFERA Schema Diagnostics inspects the HTML returned by published pages, extracts JSON-LD, Microdata and RDFa, and groups common structured-data findings. It operates alongside an existing SEO plugin instead of generating replacement markup. Results are diagnostic indicators, not evidence that a search engine will display a rich result.

Typical workflow

1. Run the test build only on a staging or isolated WordPress installation. In the plugin admin screen (Tools → Schema Diagnostics), select a published page for a single scan.
2. Review grouped findings, severity, affected examples and any suggested source of the markup.
3. Verify the actual markup and page content. Treat any identified source generator as an estimate, not proof.
4. Correct the underlying content or responsible generator configuration, then scan again to compare.

Bulk scans and history

Local MySQL job queues process published site URLs in bounded batches with configurable pauses and retries. The internal 0.3.x series documents a 90-day retention policy for historical rows, retaining five recent completed jobs and limiting cleanup work per cron pass. WP-Cron requires site traffic or a properly configured scheduler.

Validation boundaries

• The checker does not run client-side JavaScript, fetch remote JSON-LD contexts or replace formal Schema.org ontology validation.
• Duplicate-looking nodes or multiple JSON-LD blocks do not automatically prove a conflict.
• Do not invent prices, ratings or customer reviews to silence a warning.
• Google and Yandex checks are separate approximate profiles, not official certification.

Independent confirmation

Verify critical findings using Google Rich Results Test and the Yandex markup validator. Search engines may revise their eligibility requirements independently.

Compatibility

The current repository declares WordPress 6.5+ and PHP 8.2+ with DOM and mbstring. No LIO CMS or Cloud account is required.

← All documentation